Re: sound and TCP checksums in 2.1.126pre2, 2.1.125ac3

Alan Cox (alan@lxorguk.ukuu.org.uk)
Sun, 18 Oct 1998 15:37:26 +0100 (BST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Alan Cox: "Re: Cyrix Detection hangs machine on 2.0.35, 2.0.36pre13, and late 2.1.1xx"
Previous message: Alan Cox: "Re: 2.2 missing features"

> I'm also seeing quite a few of these messages now, also in both
> 2.1.126pre2 and 2.1.125ac3:
>
> Oct 17 16:31:01 localhost kernel: TCPv4 bad checksum from 198.68.17.24:006e to 204.214.99.68:0401, len=532/532/552
> Oct 17 16:31:01 localhost kernel: TCPv4 bad checksum from 198.68.17.24:006e to 204.214.99.68:0401, len=532/532/552

Note that these are normally debugging messages. A few or a short burst
probably just indicates somehting on the net scrambled a few packets -
especially since one address isnt local. If you suddenely keep getting lots
of them what net driver are you using

-
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: Alan Cox: "Re: Cyrix Detection hangs machine on 2.0.35, 2.0.36pre13, and late 2.1.1xx"
Previous message: Alan Cox: "Re: 2.2 missing features"