don't have bpf_detachd give up the bd mtx to call ifpromisc.
instead, have it return an interface reference and make the caller
responsible for the ifpromisc call. this gets rid of window that
releasing the bd mtx opens and the NET_LOCK call for ifpromisc opens.
that window allows allows an interface we're trying to attach to
in bpf_setif, or switch dlts on in bpf_setdlt, to be removed from
the system before bpf can properly account for it. so we need to
keep the bd mtx hold.
found by tom smyth whoe also tested a few versions of this diff.
devel/py-qt-builder: update to 1.21, adds support for qt 6.12.
see https://pyqt-builder.readthedocs.io/en/stable/releases.html#v1-21-0
switches RDEP from qtbase to qt6base, probably because it just has the
right magic to find our suffixed qmake..
built all the direct consumers without issues (py-qt5, py-qt6,
py-qscintilla, py-qtwebengine, py-qt6webengine, qgis...)
i missed a chunk when getting rid of the IFT_IEEE8023ADLAG fiddling
trunk_port_ioctl was checking that IFT_IEEE8023ADLAG was set on the
port, which isnt true anymore.
dont switch if_type to IFT_IEEE8023ADLAG on ports anymore.
if_type should be immutable and set by the driver providing the
interface.
from what i can tell, the main reason to do this was to mark an
interfaces as "in use" by trunk, but we can figure that out by using
ac_trport now.
don't let a vxlan interface set itself as the parent.
fixes part of the problems in the "vxlan(4): vxlan accepted as its
own parent" email tom smyth sent to bugs@
this doesnt prevent configuration of interface topologies with
loops, but it's a good start.
don't let an nvgre interface set itself as the parent.
fixes part of the problems in the "gre(4): nvgre accepted as its
own parent" email tom smyth sent to bugs@
this doesnt prevent configuration of interface topologies with
loops, but it's a good start.
