So I've done some more testing, and it's definitely some kind of
interaction between ixl & lagg, and maybe even ix & lagg.
It doesn't matter if lagg is using "lacp" or "loadbalance" (with the
switch set appropriately), it happens on both. I did find out that
statically adding an arp entry for the
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
kristof added inline comments.
INLINE COMMENTS
sys/netpfil/pf/pf_if.c:130 I don't understand why this is required. Surely if
an ifnet lives in V_ifnet (so, lives in the current vnet) ifp->if_vnet is
always going to be curvnet?
sys/netpfil/pf/pf_if.c:141 Why add curvnet here?
pfi_attach_ifn
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208985
--- Comment #3 from CTurt ---
Thanks for your response.
I firmly believe any `malloc` with an unchecked size from userland to
absolutely be a bug. As demonstrated by my PoC code, when accessible, this can
be used to at minimum panic a syst
