Date: Fri, 4 Jan 2013 17:42:17 GMT From: Alexander <st41ker@st41ker.net> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/174975: Latest virtualbox-ose-kmod 4.2.6 commit (309876) breaks VLAN tagging Message-ID: <201301041742.r04HgHu2094541@red.freebsd.org> Resent-Message-ID: <201301041750.r04Ho0QI039955@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 174975 >Category: ports >Synopsis: Latest virtualbox-ose-kmod 4.2.6 commit (309876) breaks VLAN tagging >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 04 17:50:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Alexander >Release: 8.3-RELEASE >Organization: >Environment: FreeBSD backup.megacom.ua 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 #0: Tue Jun 12 0 0:39:29 UTC 2012 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GEN ERIC amd64 >Description: 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 >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201301041742.r04HgHu2094541>