Page MenuHomeFreeBSD

if_bridge: count the drops of the fragmentation path
ClosedPublic

Authored by netchild on Fri, Sep 4, 1:52 PM.
Tags
None
Referenced Files
F173567721: D59391.id186474.diff
Sat, Sep 26, 9:44 PM
F173530719: D59391.id185937.diff
Sat, Sep 26, 3:39 PM
Unknown Object (File)
Sat, Sep 26, 6:07 AM
Unknown Object (File)
Fri, Sep 25, 3:08 AM
Unknown Object (File)
Fri, Sep 25, 2:12 AM
Unknown Object (File)
Thu, Sep 24, 4:53 PM
Unknown Object (File)
Sat, Sep 19, 4:05 PM
Unknown Object (File)
Sat, Sep 19, 4:51 AM
Subscribers

Details

Summary

Add error counter handling in bridge_fragment().

Assisted-by: Claude Code (Fable 5, Opus 5)

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

netchild held this revision as a draft.
netchild published this revision for review.Fri, Sep 4, 1:53 PM

The following part may need to get a rework for this change... investigating...

		default:
			if (V_pfil_onlyip)
				goto bad;

rework: the bad: counter is removed; only the fragmentation path is counted

netchild retitled this revision from if_bridge: count the packets bridge_pfil() drops on error to if_bridge: count the drops of the fragmentation path.Sat, Sep 5, 5:23 PM
netchild edited the summary of this revision. (Show Details)

The bad: label in the previous revision gets called for ether types 0x88e1 (HomePlug AV management frames) and 0x8912 (not named in sys/net/ethernet.h) via the default: case and with net.link.bridge.pfil_onlyip=1. This looks to me like a policy drop and not an error path. As such I removed that part. Correct me if I get this wrong... (447 such packets in 300s doesn't not sound like an error to me).

This revision is now accepted and ready to land.Tue, Sep 8, 12:14 PM