[Bug 242637] [patch] emulators/virtualbox-ose: fix bridging when the ng_ether node name does not match the interface name

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Dec 14 19:25:58 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242637

            Bug ID: 242637
           Summary: [patch] emulators/virtualbox-ose: fix bridging when
                    the ng_ether node name does not match the interface
                    name
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: vbox at FreeBSD.org
          Reporter: landonf at FreeBSD.org
          Assignee: vbox at FreeBSD.org
             Flags: maintainer-feedback?(vbox at FreeBSD.org)

Created attachment 209951
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209951&action=edit
Patch for current (5.2.34) emulators/virtualbox-ose

This patch fixes bridging in cases where the interface's ng_ether netgraph node
name does not match its interface name.

This is commonly seen with VLANs configured in rc.conf; for example:

  ifconfig_igb0="up"
  vlans_igb0="12"

This will create an 'igb0.12' VLAN interface, but because '.' is a reserved
character in netgraph node names, the corresponding netgraph node will be named
'igb0_12':

    Name: igb0_12         Type: ether           ID: 00000007   Num hooks: 0

Currently, VBoxNetFlt assumes a 1:1 correspondence between interface name and
ng_ether node name; when attempting to bridge to igb0.12, the node named
"igb0.12" is not found, and VBoxNetFlt's netgraph initialization silently
fails.

Rather than assume the node name, this patch enumerates all ng_ether nodes,
using the NGM_ETHER_GET_IFNAME control message to identify the ng_ether node
corresponding to the target interface.

I've attached patches for the current emulators/virtualbox-ose port, as well as
a patch relative to the 6.1 patch posted on 2019-12-13
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234878).

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list