All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Heffner <jheffner@psc.edu>
To: netfilter-devel@lists.netfilter.org
Subject: What to do with malformed l4proto packets?
Date: Thu, 05 Apr 2007 18:11:55 -0400	[thread overview]
Message-ID: <4615742B.3040708@psc.edu> (raw)

We have someone on the end of a DSL line that seems to be 
non-deterministically corrupting some of his packets (a rate of ~1e-5) 
in a way that causes the TCP checksum to fail.  While he hopes to get 
this situation remedied, the immediate problem is that his connections 
that go through our firewall are getting reset every time a corrupted 
segment is received.

AFAICT, what's happening is that tcp_error() finds the TCP checksum 
wrong, returning -NF_ACCEPT back up to nf_conntrack_in(), which quits 
and sends NF_ACCEPT back up.  So we have a TCP packet not associated 
with a connection, so our firewall rules send back a RST.

So, the question is: is there any reason to ACCEPT TCP segments with 
known bad checksums?

Thanks,
   -John

             reply	other threads:[~2007-04-05 22:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 22:11 John Heffner [this message]
2007-04-07 16:34 ` What to do with malformed l4proto packets? Ross Vandegrift

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4615742B.3040708@psc.edu \
    --to=jheffner@psc.edu \
    --cc=netfilter-devel@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.