On Mon, 2019-11-18 at 12:32 +0100, Toke Høiland-Jørgensen wrote: > > Dropping this kind of error packet before it goes into the driver, > > should be the right direction. > > So I still wonder why this happens from higher up in the stack. If > there's a legitimate reason, maybe dropping the packet is not the right > thing? And if there is *no* legitimate reason, maybe the packet should > be dropped higher up in the stack instead? Agree, this is really weird, it'd be good to know the actual packet this happens with. Don't think I've ever seen this. johannes
