Very interesting
> The machine that recorded this stuff is running 2.0.31 w/ 2.0.29 networking,
> because after 24 hours of heavy stress testing on it barfed out a stream of
> oops-es and rebooted. This implies to me that either my problems are
> probably NOT the 2.0.30 network codes fault.
Of course the 2.0.29 networking doesnt have the teardrop fix in it..
> I'm just a lowly sysadmin, so I don't know what to do with these oopses
> other than send them to you.. dmesg said:
I need to the symbols tables from the matching kernel to be useful
(System.map)
> IP: Invalid IP fragment (offset > end) found from 198.137.241.30
> IP: Invalid IP fragment (offset > end) found from 198.137.241.30
Thats an attack ok. Not only do such packets not occur statistically often
but they wouldnt be coming from 'whitehouse.gov' apparently either
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu