VirtualBox

Opened 15 years ago

Last modified 5 years ago

#4626 new defect

PPPoE fails over bridged HP8510w 4965AG WLAN card

Reported by: Kinnoken Owned by:
Component: network Version: VirtualBox 3.0.2
Keywords: PPPoE DSL HP8510w 4965 Cc:
Guest type: Windows Host type: Windows

Description (last modified by Valery Ushakov)

I have a problem where I have a host machine, an HP8510w laptop with an intel 4965AG WLAN card. I am running Vista 64 Ultimate (same problem with Win 7 64 RTM) with a guest machine running Windows XP Sp3. The most important aspects of this setup is that the guest machine is set to be bridged to my WLAN card (Intel 4965AG). I am using static IP's with a router.

After the Guest OS is installed, I have configured an IP address. I can ping the router from the Host OS and I can also ping the router from the Guest OS. All other aspects of networking seem to be working. (I do not use DHCP purely because of my network setup but I feel this is unimportant).

I have several PPPoE accounts and a router that is in bridge mode. When I try to initiate a PPPoE connection in the Guest OS (WinXP), PADI packets leave the guest machine, go through the bridged network, reach the router. The router then sends a PADO response which can be seen on the Host OS and is also passed on to the Guest OS.

Unfortunately, the Guest OS is ignoring these packets as the target MAC address does not seem to be for the Guest OS (Which is understandable, but surely the bridging driver/service installed on the Host OS NIC is supposed to correct this?)

This seems to be a problem with the bridging driver/service for VirtualBox. This may not be of any concern to you, but the problem also exists in VMware Workstation. This is not a problem for Microsoft Virtual Machine though.

I have discovered a slight workaround. If I set the MAC address of the virtual network card in the guest to the same MAC address of the Host OS WLAN card, the PADO packets are relayed and it now works. Unfortunately, this causes other problems with Linux Guest's trying to use the same workaround and I cannot use this solution permanently.

I have attached the Vbox.log, as well as two wireshark captures from both the host and the guest machine.

Attachments (3)

VBox.log (79.0 KB ) - added by Kinnoken 15 years ago.
VirtualBox log as requested
Host-os-pppoe-win64.txt (114.5 KB ) - added by Kinnoken 15 years ago.
Wireshark packet capture from host machine
Guest-os-pppoe-winxp.txt (104.5 KB ) - added by Kinnoken 15 years ago.
Guest OS packet capture

Download all attachments as: .zip

Change History (6)

by Kinnoken, 15 years ago

Attachment: VBox.log added

VirtualBox log as requested

by Kinnoken, 15 years ago

Attachment: Host-os-pppoe-win64.txt added

Wireshark packet capture from host machine

by Kinnoken, 15 years ago

Attachment: Guest-os-pppoe-winxp.txt added

Guest OS packet capture

comment:1 by marzen, 5 years ago

I have the same issue here and still in v5.2 there seems to be no fix for this. I also guess that the problem in #14404 has the same root cause and was closed with wrong assumptions.

I am using an AVM Fritz!Box 7390 as PPPoE modem with passthrough enabled and a VirtualBox host with an Intel Centrino Wireless-N 2230 Wifi adaptor that guests use as Network Bridge.

All PADI requests to the network are sent out with the Source MAC of the host but not with the source MAC of the guest as I could see in a pcap trace. Of course the PADO responses never find their way back to the guest like this. If I use a wired connection with a Network Bridge via an Intel 82579LM Gigabit Adapter it sents out the PADI requests properly adressed with guests source MAC. Thus the PADO responses are going backwards the right way and are received by the guest correctly.

This is a general problem imho with WiFi-Adaptors used as network bridge which not has been solved yet.

BR marzen

comment:2 by Socratis, 5 years ago

See ticket #10019, comments 18 and 19.

comment:3 by Valery Ushakov, 5 years ago

Description: modified (diff)

Right, PPPoE is not supported. "Bridging" to wifi is not actually bridging, but more like an Ethernet-level NAT. For IP traffic we can look at the destination IP address and dispatch incoming packets accordingly. With PPPoE there's no such indication. Some heuristic can be worked out, probably, but this is not a common usage scenario, so it's rather unlikely that this will ever get any attention/resources.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use