Hello, When the host system uses VLAN interfaces all it's tagged traffic becomes untagged when any VBox VM started. I guess it is connected to the recent VLAN tagging support in the vboxnetflt driver. How-To-Repeat: 1) Create vlan interface on the host system 2) Start VBox VM 3) Check host availability on vlan interface
Responsible Changed From-To: freebsd-ports-bugs->vbox Over to maintainer (via the GNATS Auto Assign Tool)
Hello, It seems like the issue is still persists. Could you, please clarify the status of this PR? -- Thanks, St41ker.
Hello, It seems like the issue is still persists and reproducable in all FreeBSD versions. Could you, please clarify the status of this PR? Thank you.
Is this patch the fix? http://lists.freebsd.org/pipermail/freebsd-emulation/2013-May/010605.html
Hello. Actually, I have no idea. Unfortunately, I have only one production system with VirtualBox since that we decided to move all our VMs to XEN. -- Sent from Blackberry device -----Original Message----- From: Christopher Weimann <cweimann@gmail.com> Date: Wed, 19 Jun 2013 15:33:12 To: <bug-followup@FreeBSD.org>; <st41ker@st41ker.net> Subject: Re: ports/174975: Latest emulators/virtualbox-ose-kmod 4.2.6 commit (309876) breaks VLAN tagging Is this patch the fix? http://lists.freebsd.org/pipermail/freebsd-emulation/2013-May/010605.html
Is this PR still relevant?
We have version 5.2.4. This is overcome I think.