TCP bad checksum

Lenart Gabor (lgb@hal2000.hal.vein.hu)
Fri, 4 Dec 1998 14:39:54 +0100

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Richard B. Johnson: "Re: Linux timekeeping plans"
Previous message: Alexandr D. Kanevskiy: "[2.1.13x] 2.1.13x + Gated OSPF = trubble."

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 ? And what do these messages
mean exactly ? (So what did 192.225.44.214 with my machine, or is it somewhat
kernelbug ?)
(2.1.131UP)

thx

---[ LGB/DC ]------------------[ root@hal2000 ]-----------------[ LINUX ]---
"The truth is out there" "We're living together" "The future is dark."
---[ 88/422022-4602 ]--[ http://www.hal.vein.hu/~lgb ]------[ 87/477074 ]---

-
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/

Next message: Richard B. Johnson: "Re: Linux timekeeping plans"
Previous message: Alexandr D. Kanevskiy: "[2.1.13x] 2.1.13x + Gated OSPF = trubble."