Opened 17 years ago
Closed 15 years ago
#945 closed defect (fixed)
VM can send but not receive traffic through TAP interface
Reported by: | Azzie | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 1.5.2 |
Keywords: | network tap | Cc: | azzie@… |
Guest type: | other | Host type: | other |
Description
Test procedure:
- Host (Linux 2.6.23.9) is connected to LAN through eth0
- eth0 is bridged with vbox0 (TAP)
- I boot the VM and choose to boot from LAN
Observations:
- On the host
overlord linux # tcpdump -i vbox0 tcpdump: WARNING: vbox0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on vbox0, link-type EN10MB (Ethernet), capture size 96 bytes 00:31:36.417877 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:31:36.431399 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548 00:31:38.944662 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:31:38.963307 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548 00:31:43.723376 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:31:43.743677 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548 00:31:52.290219 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:31:52.307821 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548 00:32:08.273038 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:32:08.284300 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548 00:32:41.006979 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:32:41.025565 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548
- The VM prints "No IP.No IP.No IP.No IP.No IP.No IP." The screenshot is attached.
Interpretation:
- The VM sends a DHCP request
- The request is bridged, received by the DHCP server, responded and bridged again
- The DHCP reply is sent over the TAP interface
- The VM does not receive the response
Attachments (1)
Change History (5)
by , 17 years ago
Attachment: | virtualbox-problem.png added |
---|
comment:2 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Closing. No response and we changed the hostif networking with 2.1.0 anyway.
comment:3 by , 16 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
I have the exact same problem.
Some info: Host is Vista Guest is Ubuntu 8.04 Virtual box is 2.2.4r47978
It was running fine in bridge mode and then I changed to NAT. I needed to do some test in bridge mode so I turn back into that mode. Since then I get the same problem as above, i.e. in the host I see the dhcp request going out, the reply coming back but nothing in the guest (using wireshark I see only tx).
Under ifconfig, rx count is not zero but it has not changed in a while, particularly when I restart the dhcp client. I suspect the traffic is coming form the host.
comment:4 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
There were fixes which might be related to your problem in later releases. Please reopen if you still see this problem with VBox 3.0.10.
Screenshot of the VM