It seems that Virtualbox uses different PXE "roms" depending on the installation of Extension pack or not.
i.e. without extension pack, it seems to use a limited version of iPXE, and maybe some image format are not handled (Exec format error, Could not boot image, etc.)
Showing posts with label network. Show all posts
Showing posts with label network. Show all posts
Monday, January 7, 2013
Friday, November 23, 2012
mac os x and cisco vpn problem
To solve the well-known problem in Mac OS X (Lion) related to a Cisco VPN, you can follow these steps.
The problem is: using the built in VPN client to connect to a Cisco ASA, there is a problem related to DNS.
There is no way, using the GUI, to solve the issue. You can set network interface order, but your corporate network DNS will never be involved. So you can ping a connect to your private network using IP addresses, but not domain names (if they are not on a public internet accessible DNS).
With an administrative account, from terminal, create a directory called resolver under /etc
sudo mkdir /etc/resolver
Create a file (called in example with your private domain)
sudo vi /etc/resolver/work.com
Edit it (according to your network)
domain work.com
nameserver 10.10.0.127
nameserver 10.10.0.128
port 53
So, to resolve hostnames ending with work.com, the system will use the right DNS.
Safari works. Using terminal, ping works, but nslookup and host commands do not work.
The problem is: using the built in VPN client to connect to a Cisco ASA, there is a problem related to DNS.
There is no way, using the GUI, to solve the issue. You can set network interface order, but your corporate network DNS will never be involved. So you can ping a connect to your private network using IP addresses, but not domain names (if they are not on a public internet accessible DNS).
With an administrative account, from terminal, create a directory called resolver under /etc
sudo mkdir /etc/resolver
Create a file (called in example with your private domain)
sudo vi /etc/resolver/work.com
Edit it (according to your network)
domain work.com
nameserver 10.10.0.127
nameserver 10.10.0.128
port 53
So, to resolve hostnames ending with work.com, the system will use the right DNS.
Safari works. Using terminal, ping works, but nslookup and host commands do not work.
Thursday, October 18, 2012
Centos 6: bridge vlan and bond
/etc/sysconfig/network-scripts/ifcfg-em1
DEVICE=em1
BOOTPROTO=none
HWADDR=78:2b:cb:xx:xx:xx
ONBOOT=yes
MASTER=bond0
SLAVE=yes
TYPE=Ethernet
IPV6INIT=no
USERCTL=no
/etc/sysconfig/network-scripts/ifcfg-em2
DEVICE=em2
BOOTPROTO=none
HWADDR=78:2b:cb:yy:yy:yy
ONBOOT=yes
MASTER=bond0
SLAVE=yes
TYPE=Ethernet
IPV6INIT=no
USERCTL=no
/etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0
ONBOOT=yes
BOOTPROTO=none
BONDING_OPTS="mode=4 miimon=100 lacp_rate=1"
TYPE=Ethernet
IPV6INIT=no
USERCTL=no
NOZEROCONF=yes
/etc/init.d/network restart
vconfig add bond0 11
brctl addbr brvlan11
brctl addif brvlan11 bond0.11
/etc/sysconfig/network-scripts/ifcfg-bond0.11
DEVICE=bond0.11
ONBOOT=yes
BRIDGE=brvlan11
VLAN=yes
/etc/sysconfig/network-scripts/ifcfg-brvlan11
DEVICE=brvlan11
ONBOOT=yes
TYPE=Bridge
BOOTPROTO=static
IPADDR=10.96.11.40
NETMASK=255.255.255.0
GATEWAY=10.96.11.1
VLAN=yes
STP=on
DELAY=0
On the HP switch
configure
trunk 3-4 Trk4 LACP
vlan 11
tagged Trk4
end
Subscribe to:
Posts (Atom)