lkml.org 
[lkml]   [1998]   [Dec]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: TCPv4 bad checksum in 2.1.131-ac8/9/10
If it is an ISP problem it's happening at more than one place.  My
kernel is 2.1.131 without any patches. I'm seeing the following using
dmesg (doesn't appear in /var/log/messages):

TCPv4 bad checksum from 205.138.126.6:006e to 208.154.157.147:041a,
len=1480/1480/1500

The first address is, among other things, the ISP DNS, the second
corresponds to a dialup link for my dynamic IP address.

On 18 Dec 1998, Paul Flinders wrote:

> Paul Flinders <paul@dawa.demon.co.uk> writes:
>
> > Is anyone else seeing bad checksums in recent kernels?
> >
> > I get a slew of
> >
> > TCPv4 bad checksum from 194.217.242.34:c1da to 194.222.0.39:0019, len=x/x/x+20
> >
> > when I pick up my mail (194.217.242.34 is one of my ISP mail machines).
> > Oddly I only see it to port 25 on my machine (I've just ftped the ac11
> > patches and a few other things with no problems) and I don't seem to have
> > lost any data so I'm wondering if it's a hardware problem but I've only
> > noticed it in the last 2 days (since I installed ac 8 or 9)
>
> At the moment the working theory is that this is a problem with my ISP
> (I see them when connected to Ascend kit but not 3Com)
>
> The only kernel change was to make them visible.
>
> Sorry for kicking up a fuss.


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

\
 
 \ /
  Last update: 2005-03-22 13:46    [W:0.069 / U:0.412 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site