All of lore.kernel.org
 help / color / mirror / Atom feed
From: Technical Support <support@bluenorthernsoftware.com>
To: netfilter@vger.kernel.org
Subject: "new not syn" packets.. false positive?
Date: Wed, 3 Jun 2009 23:19:36 -0500	[thread overview]
Message-ID: <200906032319.36957.support@bluenorthernsoftware.com> (raw)

Using Linux kernel 2.6.26 and iptables with this rule....

iptables -A bad_tcp_packets -p tcp ! --syn -m state --state NEW -j DROP

...a certain group of known reputable sites have a copious number of packets 
dropped by that rule.  A capture of a conversation with one of those sites 
via Wireshark indicated that the following was the offending packet...

TCP      [TCP Window Update] http > 58666 [ACK] Seq=1 Ack=1 Win=1049248 Len=0 
TSV=1194040538 TSER=2055704

While this group of known sites accounts for 99% of all packets stopped by 
the 'new not syn' rule above, they suggest that it's a problem in our 
firewalling or TCP.implementation.  Their sites are a client/server operation 
where remote clients connect to their servers irregularly to send and receive 
data via HTTP.  I suspect the problem  lies somewhere in their server 
software, but knowing just enough about networking to be mildly dangerous I 
can't say that with any authority.  If the above infomation is pertinent, or 
if further data from the sniffer or kernel log would be useful, please let me 
know and I'll provide what I can. Thanks in advance.

Chuck Logan

             reply	other threads:[~2009-06-04  4:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04  4:19 Technical Support [this message]
2009-06-04 12:36 ` "new not syn" packets.. false positive? Paul Evans
  -- strict thread matches above, loose matches on Subject: below --
2009-06-05  9:16 Technical Support

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=200906032319.36957.support@bluenorthernsoftware.com \
    --to=support@bluenorthernsoftware.com \
    --cc=netfilter@vger.kernel.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.