Hello Jari, Just a thought, as networking is not my strong point... shouldn't the guest's NIC be on a different subnet, such as 192.168.2.1 in order for packages for 192.168.1.x to be forwarded to the host?
I'm sure Alexey will correct me here if I am wrong :) Regards, Michael Jari Aalto wrote: > I'm running vbox from the SVN build under root account, so no device group > permission changes have been needed. > > Problem: > > The guest VM (Debian 4.0) can't interact with the host network interface > (tap0). > > - The VM network setting has been set to HOST and menu "Host interface > setting / > interface name" is set to tap0. > - The Linux Host (also Debian) has tap0 created (but unconfigured). It > is running in bridged mode[1] > - The guest[2] has ethernet device eth1, but any attempt to configure with: > > ifconfig eth1 .... netmask ... > route ... > > produces valid ifconfig and route, but the guest can't send > packets to the Host network. The Host's tap0 settings does not > change with these guest commands. > > I understood from the Vbox manual (5.3.3.2.1; end of section) that the > Vbox will interact with the Host system and forward any Guest's > "ifconfig" calls to the tap0 network settings. I'm not trying to > create tap-adapters on the fly with "Setup/Terminate" application > scripts. > > Have I understood correctly. What is the missing piece here? > > Jari > > ----------------------------------------------------------------------- > > [2] Guest: /etc/network/interfaces > > iface eth1 inet static > address 192.168.1.7 > netmask 255.255.255.0 > broadcast 192.168.1.255 > gateway 192.168.1.1 > > > [1] Host 'ifconfig' > > br0 Link encap:Ethernet HWaddr 00:D0:59:36:5D:4E > inet addr:192.168.1.3 Bcast:192.168.1.31 Mask:255.255.255.0 > inet6 addr: fe80::2d0:59ff:fe36:5d4e/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:1728 (1.6 KiB) > > eth0 Link encap:Ethernet HWaddr 00:D0:59:36:5D:4E > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:5228473 errors:0 dropped:0 overruns:0 frame:0 > TX packets:5228473 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1224296764 (1.1 GiB) TX bytes:1224296764 (1.1 GiB) > > ra0 Link encap:Ethernet HWaddr 00:08:A1:A7:B0:F9 > inet addr:192.168.1.3 Bcast:192.168.1.31 Mask:255.255.255.224 > inet6 addr: fe80::208:a1ff:fea7:b0f9/64 Scope:Link > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:58348805 errors:0 dropped:0 overruns:0 frame:0 > TX packets:23772687 errors:301 dropped:301 overruns:0 carrier:0 > collisions:666611 txqueuelen:1000 > RX bytes:3676348854 (3.4 GiB) TX bytes:73126697 (69.7 MiB) > Interrupt:11 > > tap0 Link encap:Ethernet HWaddr 4A:01:EA:3C:93:EE > inet6 addr: fe80::4801:eaff:fe3c:93ee/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:97 errors:0 dropped:16 overruns:0 carrier:0 > collisions:0 txqueuelen:500 > RX bytes:0 (0.0 b) TX bytes:4422 (4.3 KiB) _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
