[lkml]   [1996]   [Sep]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.0.18 -> MASQ: failed TCP/UDP checksum
Date said:
} I got this in my /var/log/kernel file today. These were generated
} when a Windows for Workgroups client was using Netscape Navigator
} through masquerading. I use masquerading a lot and have never seen
} this one before. My external connection is through PPP; the internal
} client is connected via thinnet (each using NE2k's).

They mean that the incoming data packet was corrupt - or at least it
failed its checksum. The masq code used to just rewrite the packet
headers and force the checksum to be right (thus falsely validating
corrupt data), it now drops corrupt packets on the floor and
generates that kernel message.

It should probably do something else - update the error counts on the
interface?, inform in a more useful fashion?, not fill up the syslog!

Basically if its occaisional then ignore the message.
If its regular then the other end may be broken.
If its regular and distributed over many hosts start checking your
ethernet or other net connections!


[ - Unix Applications Engineer ]
[ *Views expressed here are personal and not supported by PLAnet* ]
[ PLAnet Online : The White House Tel : +44 113 251 6012 ]
[ Melbourne Street, Leeds LS2 7PS UK. Fax : +44 113 2345656 ]

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