David Murphy wrote: [...] > Ok, I ran tcpdump on tap1 and eth0 while running an "ipconfig /renew" on > the guest. I should preface this by saying I'm very amateur at packet > analyzing. > > Looks like it's not a VirtualBox problem. tap1 shows: > > 08:57:29.896419 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, > Request from 08:00:27:xx:xx:xx (oui Unknown), length: 300 > 08:57:32.896155 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, > Request from 08:00:27:xx:xx:xx (oui Unknown), length: 300 > 08:57:40.903887 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, > Request from 08:00:27:xx:xx:xx (oui Unknown), length: 300 > 08:57:56.903685 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, > Request from 08:00:27:xx:xx:xx (oui Unknown), length: 300 > > So the DHCP requests are getting to the host interface. eth0 shows the > following (after removing some NTP traffic). 192.168.2.10 is my host > machine, 192.168.2.1 is my router/DHCP server. > > 08:57:30.043666 arp who-has 192.168.2.10 tell 192.168.2.1 > 08:57:30.043707 arp reply 192.168.2.10 is-at 00:20:ed:xx:xx:xx (oui > Unknown) > 08:57:55.051446 IP 192.168.2.10.iad3 > 192.168.2.1.domain: 52618+ AAAA? > scs.msg.yahoo.com. (35) > 08:57:55.099360 IP 192.168.2.1.domain > 192.168.2.10.iad3: 52618 1/1/0 > CNAME[|domain] > 08:57:55.099460 IP 192.168.2.10.iad3 > 192.168.2.1.domain: 31736+ A? > scs.msg.yahoo.com. (35) > 08:57:55.113080 IP 192.168.2.1.domain > 192.168.2.10.iad3: 31736 9/7/7 > CNAME[|domain] > 08:58:00.051047 arp who-has 192.168.2.1 tell 192.168.2.10 > 08:58:00.051408 arp reply 192.168.2.1 is-at 00:0e:2e:xx:xx:xx (oui Unknown) > > So there's a couple of arp requests, first from the router for the host, > then the other way around. And the stuff in the middle looks like random > crap from something else I ran. So in my totally inexpert estimation, it > looks like the bridge isn't passing on the DHCP requests from the guest?
[...] The setup looks correct to me, and your conclusion sounds very plausible. However it's a good question why the bridge doesn't pass the DHCP packets (it should, because they are broadcasts). The only problem pattern which might match vaguely is that some inofficial howtos omit putting eth0 in promisc mode. This is necessary to avoid ARPs to the guests getting lost (and a few other similar problems). Check if "ifconfig eth0" includes the PROMISC option. Note that some packet sniffers don't bother setting the PROMISC option to the previous value, they just turn it off. -- Klaus Espenlaub InnoTek Systemberatung GmbH, http://www.innotek.de _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
