Comment # 4
on bug 11597
from Christopher Maynard
(In reply to Guy Harris from comment #1)
> Unfortunately, there's no "assume packets *don't* have FCS" setting for
> Ethernet, so we may need to make that a tri-state option (assume they do,
> assume they don't, use the heuristic).
I was pretty sure there was a confirmed kernel bug where driver(s) were
incorrectly padding minimum Ethernet frames by an extra 4 bytes, but I can't
find it now. If this can be confirmed, then we might even have a quad-state
option - the 3 above and a 4th one "assume the device is running a faulty
driver and log an expert info for the excess 4 bytes".
You are receiving this mail because:
- You are watching all bug changes.