Summary: | igb interface not receiving vlan packets since 12.3 | ||
---|---|---|---|
Product: | Base System | Reporter: | sec |
Component: | kern | Assignee: | freebsd-net (Nobody) <net> |
Status: | Closed DUPLICATE | ||
Severity: | Affects Only Me | CC: | kbowling, mike, natalino.picone, pat, pkubaj, zi |
Priority: | --- | Keywords: | IntelNetworking, regression |
Version: | 12.3-RELEASE | ||
Hardware: | Any | ||
OS: | Any |
Description
sec
2022-05-03 12:30:58 UTC
if you add -e to the flags, does it then work for you ? i.e tcpdump -nei igb5 ? In the meantime I found https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260468 which seems match with my problem. So from 12.2 to 12.3 hwfiltering seems to have gotten enabled by default && can't be disabled anymore. As a workaround I have created vlan interfaces via ifconfig $iface.$vlan create ran that in a loop for all vlans currently in use, and I can see the traffic again in tcpdump The change to enable vlan filtering should probably be put somewhat prominently in the release notes. Additionally it would be good if the fix from #260468 could be merged to 12.3 :-) (In reply to sec from comment #2) I had the same issue and I agree that 260468 should be merged on 12.3. Does anybody know why hwfiltering has been enabled by default? I ran into this as well. This resolved my issue: ifconfig igb0 -vlanhwfilter -vlanhwtag (In reply to Ryan Steinmetz from comment #4) This is not working as the 12.3 intel driver contains a bug. ifconfig reports that features have been disabled, but they are not. See https://reviews.freebsd.org/D33154 which I think should also be merged on 12.3 (In reply to Natalino Picone from comment #5) My use case is closer to what sec@42.org described--where I have vlan interfaces created. I don't think my situation is identical to what you reported, but, seems related. It looks like https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260468 was fixed, 12.3-RELEASE is now EOL and 12.4-RELEASE contains the fixes. Is it OK to assume that this bug may be closed now? *** This bug has been marked as a duplicate of bug 260468 *** |