VirtualBox

Ticket #3289 (new defect)

Opened 5 years ago

Last modified 4 years ago

DHCP does not work over wireless when using Host Interface and Linux Host and Windows XP/Vista Guest

Reported by: chrisdos Owned by:
Priority: major Component: network/hostif
Version: VirtualBox 2.1.2 Keywords:
Cc: chris@… Guest type: Windows
Host type: Linux

Description (last modified by frank) (diff)

It seems that DHCP is not working correctly when using Linux as the host and Windows XP/Vista/7 as the guest. Networking is configured as using a Host Interface for the guests.

I've verified that the DHCP server is receiving the request and sending out the appropriate information, but the Windows guest is not receiving it. This is from the server:

Feb  6 11:25:11 windwalker dhcpd: DHCPDISCOVER from 08:00:27:2f:91:7d via eth1
Feb  6 11:25:11 windwalker dhcpd: DHCPOFFER on 192.168.9.73 to 08:00:27:2f:91:7d via eth1
Feb  6 11:25:14 windwalker dhcpd: DHCPDISCOVER from 08:00:27:2f:91:7d via eth1
Feb  6 11:25:14 windwalker dhcpd: DHCPOFFER on 192.168.9.73 to 08:00:27:2f:91:7d via eth1
Feb  6 11:25:21 windwalker dhcpd: DHCPDISCOVER from 08:00:27:2f:91:7d via eth1
Feb  6 11:25:21 windwalker dhcpd: DHCPOFFER on 192.168.9.73 to 08:00:27:2f:91:7d via eth1

If I assign a static IP to the Windows guest, networking seems to work correctly from all the tests I've performed.

Host Information:

  • Distro: Debian
  • Kernel: 2.6.28 from kernel.org with TuxOnIce patches
  • Hardware: Thinkpad W500
  • Wireless Driver: iwlagn

Guest Information:

  • Windows XP SP3 with all patches
  • Windows Vista SP1 with all patches
  • Windows 7 Build 7000 with all patches

Attachments

VBox.log Download (38.2 KB) - added by chrisdos 5 years ago.
Virtual Box Log
DHCP_Packet_Capture.wireshark Download (7.9 KB) - added by frank 5 years ago.
Capture file by the reporter

Change History

Changed 5 years ago by chrisdos

Virtual Box Log

comment:1 Changed 5 years ago by chrisdos

Disabling IPv6 had no affect.

comment:2 Changed 5 years ago by aleksey

Could you try any Linux guest? Could you run packet capture in the guest, re-initiate DHCP discovery by 'repairing' the network connection and upload/paste the result?

comment:3 Changed 5 years ago by chrisdos

A Debian Lenny linux guest results in the same problems. I performed a full packet capture of session running dhclient.

The bug report tool does not seem to let me attach the wireshark/libpcap/tcpdump file. So I've put the file up on my web server for you to download:  http://www.chrisdos.com/DHCP_Packet_Capture.wireshark

Changed 5 years ago by frank

Capture file by the reporter

comment:4 Changed 5 years ago by frank

I've attached that file. Please could you repeat that experiment but with NIC tracing enabled? That is,

VBoxManage modifyvm VM_NAME -nictrace1 on
VBoxManage modifyvm VM_NAME -nictracefile1 /home/foo/bar

Please do TCP capturing in parallel and attach both resulting file to this defect.

comment:5 Changed 5 years ago by frank

  • Host type changed from other to Linux

comment:6 Changed 5 years ago by chrisdos

comment:7 Changed 5 years ago by frank

  • Description modified (diff)

comment:8 Changed 5 years ago by aleksey

Hm... Ethernet address reported by DHCP (08:00:27:2f:91:7d) is different from the one that VM has (08:00:27:e7:ea:1f). How did you obtain DHCP_Packet_Capture.wireshark? By doing wireshark's "capture" on host's interface VM is "bridged" to? It is wlan0, right? If it is the case wireshark should report two DHCP Discover packets since one of them is going to the host and the other one is going to the external network (the wire). Moreover, in case of wireless interface the one going to the external network should have source Ethernet address replace with host's Ethernet address. I definitely do not see such packets going out to DHCP host, hence no DHCP replies.

Could paste the output of 'ifconfig -a' from the host?

comment:9 Changed 5 years ago by chrisdos

It's been awhile, but the The DHCP_Packet_Capture.wireshark was obtained from inside the guest. I can run further captures for you if you like from using the wlan0. Here is the results of ifconfig -a:

dummy0 Link encap:Ethernet HWaddr ea:89:a5:d2:21:b2

BROADCAST NOARP 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:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr 00:1c:25:97:c8:68

inet addr:172.28.201.239 Bcast:172.28.201.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2089575 errors:0 dropped:0 overruns:0 frame:0 TX packets:1421991 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:2027817654 (1.8 GiB) TX bytes:147968874 (141.1 MiB) Memory:fc000000-fc020000

gre0 Link encap:UNSPEC HWaddr 00-00-00-00-FF-00-00-00-00-00-00-00-00-00-00-00

NOARP MTU:1476 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:0 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 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:13610 errors:0 dropped:0 overruns:0 frame:0 TX packets:13610 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9044078 (8.6 MiB) TX bytes:9044078 (8.6 MiB)

pan0 Link encap:Ethernet HWaddr e6:5c:7e:e3:27:39

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:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

tun7 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

inet addr:10.9.8.2 P-t-P:10.9.8.1 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP 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:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

tunl0 Link encap:IPIP Tunnel HWaddr

NOARP MTU:1480 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:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vboxnet0 Link encap:Ethernet HWaddr 00:76:62:6e:65:74

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)

wlan0 Link encap:Ethernet HWaddr 00:16:ea:b1:72:78

BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:154890 errors:0 dropped:0 overruns:0 frame:0 TX packets:134873 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:118736635 (113.2 MiB) TX bytes:20440154 (19.4 MiB)

wmaster0 Link encap:UNSPEC HWaddr 00-16-EA-B1-72-78-00-00-00-00-00-00-00-00-00-00

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)

comment:10 Changed 5 years ago by aleksey

I see that wlan0 is not configured now. Could you detach the wired Ethernet, connect to DHCP server via wireless and repeat the test doing capture on host's wlan0?

comment:11 Changed 5 years ago by chrisdos

Well, I just tested it after upgrading to 2.2.4-47978_Debian_lenny, and appears that this problem has been fixed. The bridging function seems to be working fine now. The only thing I've noticed that when the Client OS transfers a lot of data, it really impacts the HOST connections performance. So at this point, it looks like you can close this ticket.

comment:12 Changed 4 years ago by regeland

Not quite fixed yet in 3.1.2 with Linux Host, XP guest. See  http://www.virtualbox.org/ticket/5887.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use