|Summary:||emulators/virtualbox-ose 4.3.20_2, partially works with LAGG(4) as Bridged Adapter.|
|Product:||Ports & Packages||Reporter:||214748mv|
|Component:||Individual Port(s)||Assignee:||Virtualbox Team (Nobody) <vbox>|
|Severity:||Affects Only Me||CC:||samy.mahmoudi, w.schwarzenfeld|
Description 214748mv 2014-12-19 16:27:04 UTC
The laptop is running 11.0-CURRENT r275768M with the lagg(4) interface as explained in the FreeBSD Handbook ‘Example 31.3. Failover Mode Between Ethernet and Wireless Interfaces’. In /etc/rc.conf I have added: # cat /etc/rc.conf | egrep 'ifconfig|wlans|cloned' ifconfig_re0="up" ifconfig_ath0="ether 18:67:b0:39:bd:23" wlans_ath0="wlan0" ifconfig_wlan0="WPA" cloned_interfaces="lagg0" ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP" In Virtualbox if I specify in the VM Settings, the network adapter as Bridged Adapter, it works only with the lan cable connected to the laptop. If I disconnect the cable, the VM network adapter stops working.
Comment 2 Walter Schwarzenfeld 2018-01-11 18:35:46 UTC
Is this still relevant? No maintainer feedback till now!
Comment 3 Samy Mahmoudi 2020-07-21 19:43:20 UTC
(In reply to Walter Schwarzenfeld from comment #2) > Is this still relevant? I can confirm this is still relevant in 12.1-RELEASE, at least with a similar setup: em0 (MASTER) / wlan0. To reproduce: • set up your lagg interface so that em0 is MASTER,ACTIVE • configure a VM to use lagg0 (possibly instead of em0) as a bridged interface • launch this VM • ping an external host from the guest (should be successful) • execute 'ifconfig em0 down' on the FreeBSD host • ping an external host from the guest (should not be successful) Scientific control: • execute 'ifconfig em0 up' on the FreeBSD host • ping an external host from the guest (should be successful again) Please also see bug 240746.
Comment 4 Samy Mahmoudi 2020-07-21 19:51:59 UTC
The following note might help to understand the issue: Note: Bridging to a wireless interface is done differently from bridging to a wired interface, because most wireless adapters do not support promiscuous mode. All traffic has to use the MAC address of the host's wireless adapter, and therefore Oracle VM VirtualBox needs to replace the source MAC address in the Ethernet header of an outgoing packet to make sure the reply will be sent to the host interface. When Oracle VM VirtualBox sees an incoming packet with a destination IP address that belongs to one of the virtual machine adapters it replaces the destination MAC address in the Ethernet header with the VM adapter's MAC address and passes it on. Oracle VM VirtualBox examines ARP and DHCP packets in order to learn the IP addresses of virtual machines. Source: https://www.virtualbox.org/manual/ch06.html#network_bridged