Uh... TCPv4 err messages foobar()'d?

ramune@relaypoint.net
Thu, 9 Apr 1998 20:46:15 -0700

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Peeter Joot: "Re: patch: new sysctl to remove hardcoded ELOOP limit"
Previous message: George: "can't locate module ^^F^Y^C$J solved!"

Hi all,

Uh... did someone screw up somewhere? Or am I missing
something? These were in my logs (somewhat trimmed).

TCPv4 bad checksum from 43.96.60.207:0050 to 29.251.170.206:0438, len=146/146/166
TCPv4 bad checksum from 43.96.60.207:0050 to 29.251.170.206:0438, len=492/492/512
TCPv4 bad checksum from 43.96.60.207:0050 to 29.251.170.206:0438, len=32/32/52
TCPv4 bad checksum from 43.96.60.207:0050 to 29.251.170.206:0439, len=146/146/166
TCPv4 bad checksum from 43.96.60.207:0050 to 29.251.170.206:0439, len=492/492/512
TCPv4 bad checksum from 43.96.60.207:0050 to 29.251.170.206:0439, len=492/492/512
TCPv4 bad checksum from 43.96.60.207:0050 to 29.251.170.206:0439, len=32/32/52
TCPv4 bad checksum from 43.96.60.207:0050 to 29.251.170.206:043a, len=146/146/166
TCPv4 bad checksum from 43.96.60.207:0050 to 29.251.170.206:043a, len=492/492/512
TCPv4 bad checksum from 43.96.60.207:0050 to 29.251.170.206:043a, len=32/32/52

-- DN

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

Next message: Peeter Joot: "Re: patch: new sysctl to remove hardcoded ELOOP limit"
Previous message: George: "can't locate module ^^F^Y^C$J solved!"