Hello Leandro, If you manually assign an IP address to the interface in the XP guest, do you get connectivity?
It shouldn't be necessary to manually set promiscuous mode, since this is done automatically by the kernel bridge code in at least the kernel version I looked at. You also should be able to leave eth0 (possibly also tap0?) as dhcp, as the Debian bridging scripts set the IP address to zero. Regards, Michael Leandro Guimaraes Faria Corcete DUTRA wrote: > Well, sorry for the subject, it really fails to convey the real > situation. > > I had a 1.3.8 installation working OK, as host Debian etch/lenny with > some sid bits and a MS WXP guest. But it really bothered me to have to > manually intervene to set up networking, but I was too lazy or busy to > delve into the mysteries of /etc/network/interfaces. > > Now when I upgraded to 1.4.0 everything seemed to work the same, only > better. It was only today that I realised the manual now actually > instructs to fix things in /etc, and that was what I did. No more > copy-and-paste of commands! > > Only problem being that now MS WXP can’t get an address anymore. I did > a little research, found > http://www.mail-archive.com/[email protected]/msg01212.html, and > realised eth0 wasn’t in promiscuous mode; I fixed that, but I don’t know > enough about networking to really make sense of tcpdump. > > My /etc/network/interfaces: > > auto lo > iface lo inet loopback > > allow-hotplug eth0 > iface eth0 inet manual > pre-up ifconfig eth0 0.0.0.0 promisc up > > auto eth0 > > auto br0 > iface br0 inet dhcp > bridge_ports all eth0 > pre-up ifconfig eth0 0.0.0.0 promisc up > > auto tap0 > iface tap0 inet manual > up ifconfig $IFACE 0.0.0.0 up > down ifconfig $IFACE down > tunctl_user ldutra > > > It seems a mess to me, probably because I had a 1.3.8 setup, fixed it > based on 1.4.0 documentation, and then made eth0 promiscuous without > really understanding all of it. > > I tried tcpdump, as per the message I found in the archive above, but > never found the answer to: > > 16:54:50.554500 arp who-has a10-595 tell 10.10.0.1 > 16:54:50.554544 arp reply a10-595 is-at 00:0a:5e:43:7d:e0 (oui Unknown) > > > a10-595 is my MS WXP guest. 10.10.0.1 is the router and DHCP (I > guess), and the host is a10-074, 10.10.5.147. > > How to troubleshoot? > > _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
