From: Technical Support <support@bluenorthernsoftware.com>
To: netfilter@vger.kernel.org
Subject: Re: "new not syn" packets.. false positive?
Date: Fri, 5 Jun 2009 04:16:59 -0500 [thread overview]
Message-ID: <200906050417.00552.support@bluenorthernsoftware.com> (raw)
Paul Evans replied:
> 'not syn' packets are any TCP packets that don't contain the SYN flag.
> "NEW" packets are ones for which conntrack cannot find an existing
> entry in the conntrack table.
Thanks, Paul. I guess with all that said the question I still have is, is it
safe to assume that there is a problem on the remote end, given that with
virtually every contact with those sites, at least one packet is always
dropped per the 'new not syn' rule? Or is it still possible that, regardless
of the frequency of the dropped packets from those sites, that there still
could be a 'legitimate' cause for it to happen? I'm just trying to get out
of being the damp middle-man in a whizzing contest between the clients and
the mighty keepers of the servers. :) Thanks for the reply and info!
Chuck Logan
next reply other threads:[~2009-06-05 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 9:16 Technical Support [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-04 4:19 "new not syn" packets.. false positive? Technical Support
2009-06-04 12:36 ` Paul Evans
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=200906050417.00552.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).