From: "\"Oleg A. Arkhangelsky\"" <sysoleg@yandex.ru>
To: Alex <mysqlstudent@gmail.com>
Cc: Jan Engelhardt <jengelh@medozas.de>, netfilter@vger.kernel.org
Subject: Re: Analyzing DNAT traffic
Date: Sat, 05 Mar 2011 18:18:06 +0300 [thread overview]
Message-ID: <514701299338286@web59.yandex.ru> (raw)
In-Reply-To: <AANLkTikUyPPHcUv9XRPBmyUDX1SQO-SSvyS-d09VutGt@mail.gmail.com>
05.03.2011, 18:13, "Alex" <mysqlstudent@gmail.com>:
> The last two are just regular requests for access to facebook from
> another PC on the internal network.
This packets can be out-of-order or duplicate packets with FIN flag.
They are not connected to any conntrack entry, so there is no way
to do NAT transformation for them.
--
wbr, Oleg.
next prev parent reply other threads:[~2011-03-05 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 20:13 Analyzing DNAT traffic Alex
2011-03-05 8:19 ` "Oleg A. Arkhangelsky"
2011-03-05 14:23 ` Alex
2011-03-05 14:38 ` Jan Engelhardt
2011-03-05 15:12 ` Alex
2011-03-05 15:17 ` Jan Engelhardt
2011-03-05 15:18 ` "Oleg A. Arkhangelsky" [this message]
2011-03-05 23:33 ` Alex
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=514701299338286@web59.yandex.ru \
--to=sysoleg@yandex.ru \
--cc=jengelh@medozas.de \
--cc=mysqlstudent@gmail.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