From: Petr Pisar <petr.pisar@atlas.cz>
To: netfilter@lists.netfilter.org
Subject: Re: Not NATed packets
Date: Sun, 23 Apr 2006 22:35:13 +0200 [thread overview]
Message-ID: <e2goe1$f34$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0604231700330.6204@tank.eu.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
lukas@tank.eu.org wrote:
> I have strange problem with NAT.
Me too.
> I have kernel 2.6.14.7-5 and iptables-1.3.3-6@2.6.14.7_5 and I use nat
Tested with 2.6.11 and 2.6.16.4.
> NAT configuration is simple but some packets are not NATed - on my
> public interface packets with source address of my internal (NATed)
> network appears and i have no clue what is wrong.
I have very simple rules too. nat/PREROUTING is empty and
nat/POSTROUTING contains only one rule with MASQUARADE target on
interface with public IP (Policies are ACCEPT). I don't use ROUTE target
anywhere.
> 16:30:39.015880 IP (tos 0x0, ttl 127, id 28594, offset 0, flags [DF],
> proto: TCP (6), length: 40) 10.10.10.104.3689 > 83.29.48.50.6881: F,
> cksum 0x1623 (correct), 3885889894:3885889894(0) ack 3151418643 win 65535
Exactly. I can see only FIN packets which are not translated. After
looking into conntrack table, I think MASQ ignores FIN packets that are
missing in conntrack table (Is it INVALID or NEW state?).
Very strange behaviour have counters too. These strange packets are not
loggable after MASQ rule. It seems like a bug.
- -- Petr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFES+UBuR4f4nEwzHIRArlUAKCQ9d9+f8bpcsboqoJOih6zndijEACfWOcV
E/15jUu11M4BE0mfuZztTtk=
=h4uY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-04-23 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 15:04 Not NATed packets lukas
2006-04-23 20:35 ` Petr Pisar [this message]
2006-04-24 9:55 ` lukas
2006-05-04 20:35 ` Pascal Hambourg
2006-04-29 18:44 ` Petr Pisar
2006-04-29 19:15 ` Petr Pisar
2006-05-04 22:22 ` Pascal Hambourg
2006-05-05 17:26 ` Petr Pisar
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='e2goe1$f34$1@sea.gmane.org' \
--to=petr.pisar@atlas.cz \
--cc=netfilter@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.