From: Michael Schwartzkopff <ms@sys4.de>
To: netfilter@vger.kernel.org
Subject: Source NAT in POSTROUTING chain for locally generated packets
Date: Tue, 26 Aug 2014 08:38:32 +0200 [thread overview]
Message-ID: <1613016.CfItKYvQAW@nb003> (raw)
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
Hi,
For some special reasons I want to alter the IP address of outgoing packets
that are generated locally to a secondary IP address on my machine. For a test
I use the udp/echo service. Without any rules a tcpdump looks like this:
192.168.56.101 is the primary address of the echo server and 192.168.56.16 is
the secondary address of the interface.
08:24:04.063987 IP 192.168.56.1.48462 > 192.168.56.16.echo: UDP, length 6
08:24:04.064522 IP 192.168.56.101.echo > 192.168.56.1.48462: UDP, length 6
So I add the iptables rule:
iptables -t nat -I POSTROUTING -p udp -s 192.168.56.101 --sport 7 \
-j SNAT --to-source 192.168.56.16
now tcpdump shows that no answer packet is sent out any more:
08:24:16.851095 IP 192.168.56.1.55362 > 192.168.56.16.echo: UDP, length 6
With iptables -t nat -L POSTROUTING I can see that the rule is hit since the
counter increases. Also a iptables TRACE shows me that the rule is hit. No
filter appears in the TRACE log.
Any ideas where the packet vanished?
Mit freundlichen Grüßen,
Michael Schwartzkopff
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next reply other threads:[~2014-08-26 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 6:38 Michael Schwartzkopff [this message]
2014-08-28 22:08 ` Source NAT in POSTROUTING chain for locally generated packets Pascal Hambourg
2014-08-31 12:05 ` Michael Schwartzkopff
2014-08-31 14:19 ` Michael Schwartzkopff
2014-08-31 15:33 ` Pascal Hambourg
2014-08-31 15:42 ` Michael Schwartzkopff
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=1613016.CfItKYvQAW@nb003 \
--to=ms@sys4.de \
--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.