> Andi Kleen writes:
> > Richard Gooch <rgooch@atnf.CSIRO.AU> writes:
> >
> > > Andrea Arcangeli writes:
> > > > On Tue, 24 Mar 1998, Richard Gooch wrote:
> > > >
> > > > >Something still not right:
> > > > >
> > > > >TCPv4 bad checksum from 130.155.198.47:03ff to 130.155.191.26:03fd, len=32/32/52
> > > > >TCPv4 bad checksum from 130.155.198.47:03ff to 130.155.191.26:03fd, len=32/32/52
> > > > >TCPv4 bad checksum from 130.155.198.47:0448 to 130.155.191.26:1770, len=32/32/52
> > > > >TCPv4 bad checksum from 130.155.198.47:0201 to 130.155.191.26:03ff, len=20/20/4
> > > >
> > > > I read messages such us this a lot of times but I never related it to a
> > > > possible TCP bug, I always think that the ppp/slip is a poor connection
> > > > and can miss something (we use checksum for that cases no?).
> > >
> > > My modem link has compression and error checking, so in theory I have
> > ^^^^^^^^^
> > (but your serial cable between computer and modem hasn't), also note
> > that theory and practice often differ. Another possibility is that
> > the packets got corrupted further down the link.
>
> The modem cable is properly shielded. The serial link runs at 115 k.
> Is this really likely?
With an internal v.34 modem, I get a few of those errors:
Dec 4 16:53:59 dennis1 kernel: TCPv4 bad checksum from 207.219.98.1:d9aa
to 155.135.1.24:0014, len=24/24/44
Dec 5 01:18:44 dennis1 kernel: TCPv4 bad checksum from 209.67.19.99:0050
to 155.135.1.24:51b0, len=20/20/40
Dec 5 01:18:57 dennis1 kernel: TCPv4 bad checksum from 209.67.19.99:0050
to 155.135.1.24:51b9, len=20/20/40
Dec 5 01:21:00 dennis1 kernel: TCPv4 bad checksum from 209.67.19.99:0050
to 155.135.1.24:5259, len=20/20/40
Dec 14 15:05:16 dennis1 kernel: TCPv4 bad checksum from 204.181.3.203:0050
to 155.135.1.29:086b, len=874/874/894
Dec 14 15:05:45 dennis1 kernel: TCPv4 bad checksum from 204.181.3.203:0050
to 155.135.1.29:086d, len=1165/1165/1185
Dec 31 13:58:32 dennis1 kernel: TCPv4 bad checksum from
206.184.214.34:0014 to 155.135.1.22:0831, len=1480/1480/1500
Dec 31 14:45:03 dennis1 kernel: TCPv4 bad checksum from
206.184.214.34:0014 to 155.135.1.22:0832, len=1480/1480/1500
Mar 25 23:41:58 dennis1 kernel: TCPv4 bad checksum from
208.147.140.18:0017 to 155.135.1.35:08b6, len=20/20/40
I'm using ppp 2.3.3, a 2.1.72 kernel, and glibc 2.0.6. On the other end
of the PPP connection is an Intel v.34 modem and a Cisco 7000
communications server.
___
Trevor Johnson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu