TCPv4 and bad checksums + addrconf_ifdown: device not found.

Riccardo Facchetti (fizban@mbox.vol.it)
Sat, 24 May 1997 12:30:21 +0200 (MET DST)

Running 2.1.40 compiled with gcc-2.7.2.1/binutils 2.7.0.9.
SMP=1 commented out.

During PPP sessions, I usually receive these kernel msgs (dmesg output):

registered device ppp0
ppp0 UP fl=00000051 pa=2F991FC3/FFFFFFFF brd=00000000 dst=4A676397
TCPv4 bad checksum from 02cf80d0:0050 to 2f991fc3:052a, len=492/492/512
TCPv4 bad checksum from 02cf80d0:0050 to 2f991fc3:052a, len=492/492/512
TCPv4 bad checksum from 02cf80d0:0050 to 2f991fc3:052a, len=492/492/512
TCPv4 bad checksum from 02cf80d0:0050 to 2f991fc3:052a, len=492/492/512
TCPv4 bad checksum from 02cf80d0:0050 to 2f991fc3:052a, len=492/492/512
TCPv4 bad checksum from 02cf80d0:0050 to 2f991fc3:052a, len=492/492/512
TCPv4 bad checksum from 02cf80d0:0050 to 2f991fc3:052a, len=492/492/512
TCPv4 bad checksum from 02cf80d0:0050 to 2f991fc3:0572, len=294/294/314
TCPv4 bad checksum from 02cf80d0:0050 to 2f991fc3:0572, len=135/135/155
TCPv4 bad checksum from 02cf80d0:0050 to 2f991fc3:0555, len=492/492/512
addrconf_ifdown: device not found

These messages in 16 minutes of connection, so more or less just annoying
msgs, but they pop up in the last (or last two) devel releases. I'm sorry
I can't provide more infos, but if there is something I can do, tell me.
Is the last addrconf_ifdown a known problem ?

Ciao,
Riccardo.