Messages in this thread | | | Date | Wed, 25 Mar 1998 19:25:06 -0500 | From | Aaron Tiensivu <> | Subject | Re: "Greased TCPenguin" |
| |
> 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 > >TCPv4 bad checksum from 130.155.198.47:03ff to 130.155.191.26:03fd, len=32/32 > >TCPv4 bad checksum from 130.155.198.47:0448 to 130.155.191.26:1770, len=32/32 > >TCPv4 bad checksum from 130.155.198.47:0201 to 130.155.191.26:03ff, len=20/20
> 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?). > > I think that also because _I_ never seen that messages over an ethernet.
Some people have noted that it might be due to VJ Compression. I used to get those messages every once in a while under 2.0.x while running a busy quake server on ethernet. I wrote it off as modem spoo..
But, the interesting note.. same setup, now under pre-2.1.91, I haven't had any of these messages.
Sooo.. I think it's a bit of a toss-up.
-- Easter has been cancelled this year. They've found the body.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |