Bug 240746 - emulators/virtualbox-ose: bridge network not working on lagg or bridge interface
Summary: emulators/virtualbox-ose: bridge network not working on lagg or bridge interface
Status: Closed Works As Intended
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: vbox (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-22 09:37 UTC by Stéphane D'Alu
Modified: 2021-01-01 22:55 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (vbox)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stéphane D'Alu 2019-09-22 09:37:00 UTC 
If using the "bridge network" with a bridge or lagg interface, it is not possible for the vm to have network access. Tested on freebsd 12.0 with virtualbox 5.2.32 and 6.0.12
Comment 1 Samy Mahmoudi 2020-07-21 20:13:33 UTC 
(In reply to sdalu from comment #0)

On 12.1-RELEASE, I can choose a lagg interface as "bridged networking" in VirtualBox 5.2.30 and have a partially functional setup: the problem only happens to me when I unplug my ethernet cable or execute 'ifconfig em0 down'.

I have already experienced similar issues on 12.0-RELEASE but I can't remember if my setup was partially functional (like in 12.1-RELEASE) or completely broken (like in your case). Could you confirm bridge networking is not working when your MASTER interface is ACTIVE?

Also, please have a look at bug 196133.
Comment 2 Samy Mahmoudi 2020-07-21 20:28:20 UTC 
(In reply to sdalu from comment #0)
(In reply to sdalu from comment #0)

You could also find the following page useful, albeit quite old: https://wiki.zs64.net/VirtualBox_on_FreeBSD_cheat_sheet
Comment 3 Samy Mahmoudi 2020-07-21 20:30:27 UTC 
I am sorry for the copy-paste error.
Comment 4 Stéphane D'Alu 2021-01-01 22:55:24 UTC 
Sorry for my late answer, I'm closing the bug. 
If I remember correctly it involved a wireless interface which is not supported according to  bug 196133  you mentionned