On Mon, Feb 18, 2008 at 05:39:03PM +0200, Pekka Pietikainen wrote:
When playing with some L2 level fuzzing I started getting lots of
protocol 0300 is buggy, dev eth3 spew in dmesg. That interface is also
capturing the traffic that's being sent, that's probably why the
dev_queue_xmit_nit
When playing with some L2 level fuzzing I started getting lots of
protocol 0300 is buggy, dev eth3 spew in dmesg. That interface is also
capturing the traffic that's being sent, that's probably why the
dev_queue_xmit_nit codepath is getting called in the first place.
Tested on
