Hi. I've got an odd situation here on 8.2-STABLE with virtualbox-ose-4.0.4 and a guest built from the same /usr/obj. Upgraded to VirtualBox 4.0.8 (including rebuilding/reloading the kmod) with no change.
Host rc.conf:
Everything works fine on the host. Bridge a VirtualBox guest though, and everything goes wrong. Bridged to bge0.100, the guest sends tagged packets (correct) but receives nothing (tcpdump -ni em0 on the guest shows nothing despite it being a noisy network) The host interface does go PROMISC as expected while the guest's running.
Bridge the guest to bge0 and tcpdump -eni em0 on the guest shows vlan100 traffic natively (incorrect - it should be .1q encapsulated now) but no other vlans. Outgoing traffic from the guest is not tagged (correct)
Even stranger is when I create a vlan interface on the guest, packets sent through that also come out untagged (should be double-tagged?), and there's no packets received on the guest's subinterface.
Previously with VLANs out of the equation, Virtualbox worked perfectly.
Any ideas?
Host rc.conf:
Code:
vlans_bge0="100"
ifconfig_bge0="inet 10.0.0.1/24"
ifconfig_bge0_100="inet 192.168.0.1/24"
ifconfig_bge0_101=...
...
Everything works fine on the host. Bridge a VirtualBox guest though, and everything goes wrong. Bridged to bge0.100, the guest sends tagged packets (correct) but receives nothing (tcpdump -ni em0 on the guest shows nothing despite it being a noisy network) The host interface does go PROMISC as expected while the guest's running.
Bridge the guest to bge0 and tcpdump -eni em0 on the guest shows vlan100 traffic natively (incorrect - it should be .1q encapsulated now) but no other vlans. Outgoing traffic from the guest is not tagged (correct)
Even stranger is when I create a vlan interface on the guest, packets sent through that also come out untagged (should be double-tagged?), and there's no packets received on the guest's subinterface.
Previously with VLANs out of the equation, Virtualbox worked perfectly.
Any ideas?