> Dec 3 19:11:35 oxygene kernel: TCPv4 bad checksum from 192.225.44.214:0050 to 193.6.41.138:04d3, len=20/20/40
> Dec 3 19:12:03 oxygene kernel: TCPv4 bad checksum from 192.225.44.214:0050 to 193.6.41.138:04fc, len=20/20/40
> Dec 3 19:12:26 oxygene kernel: TCPv4 bad checksum from 192.225.44.214:0050 to 193.6.41.138:050d, len=20/20/40
> Dec 3 19:13:13 oxygene kernel: TCPv4 bad checksum from 192.225.44.214:0050 to 193.6.41.138:050e, len=20/20/40
> Dec 3 19:14:03 oxygene kernel: TCPv4 bad checksum from 192.225.44.214:0050 to 193.6.41.138:04fc, len=20/20/40
> Dec 3 19:14:26 oxygene kernel: TCPv4 bad checksum from 192.225.44.214:0050 to 193.6.41.138:050d, len=20/20/40
> Dec 3 19:15:13 oxygene kernel: TCPv4 bad checksum from 192.225.44.214:0050 to 193.6.41.138:050e, len=20/20/40
> Dec 4 14:19:27 oxygene kernel: Socket destroy delayed (r=0 w=128)
> What do hex numbers after target IP address mean ?
They're presumably the port number in hexadecimal, which in the above
case translates to port 80 (the www port), indicating that the problem
was coming from software claiming to be a browser if I'm reading it
correctly.
Don't ask me re the rest of your message though, I don't have the
faintest...
Best wishes from Riley.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/