Hi Frank,
the file you mention contains:
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:0c:29:f3:f7:08", ATTR{type}=="1", NAME="eth0"
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="08:00:27:44:a8:ca", ATTR{type}=="1", NAME="eth1"
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="08:00:27:b0:2f:27", ATTR{type}=="1", NAME="eth2"
So, all of them use the same driver except for the MAC addresses.
I cannot connect with any web site on the internet
from the guest OS.
I tried to telnet, ssh, wget, ...etc
all came back with Temporary (sic!) failure in name resolution.
On the guest, resolv.conf contains 10.0.2.3 as the nameserver.
Seems more permanent failure than temporary :)
Is anyone having such a problem with networking the guest?
-JD
Frank Mehnert wrote:
On Tuesday 26 February 2008, JD wrote:
However, still no ethernet :(
The VM is configured to use NAT.
In the guest I do not see eth0 getting configured.
In fact when I try to config eth0, I get
*error fetching interface information. Device not found.
On the guest eth1 has ip 10.20.2.15 and in guest
I can ping 10.0.2.2 (which is the vmbox virtual
interface on the host - invisible to the host).
So, why isn't vmbox virtual iface forwarding the
packets to the host for nat'ing ?
Note that ping (ICMP) will not work for NAT, this is described
in the user manual. So check if NAT works with another protocol,
for instance http.
It is also possible that your guest assigns the virtual network
card which is connected to the VirtualBox NAT engine to eth1
instead of eth0. If you can only access eth1 but not eth0 in
the guest then this is most likely because the udev daemon has
reserved eth0 for another MAC address. Just use eth1 in this
case or remove the static udev rules which were created by
/lib/udev/write_net_rules
-- most likely the file
/etc/udev/rules.d/70-persistent-net.rules
Kind regards,
Frank
------------------------------------------------------------------------
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
