From: Yevgeny Kosarzhevsky <deza50293@tut.by>
To: netfilter@vger.kernel.org
Subject: SNAT problem
Date: Sun, 22 Aug 2010 21:35:34 +0300 [thread overview]
Message-ID: <4C716DF6.3040602@pisem.net> (raw)
Hi,
I have the issue with incorrect SNAT.
I have two interfaces, let's say ppp0 - x.x.x.x, ppp1 - y.y.y.y ppp0 is
a default gateway.
I use some command to change routing to IP z.z.z.z via ppp1:
ip ro ad to z.z.z.z dev ppp1
I have SNAT rules for both interfaces, however, I notice with tcpdump
that outgoing packets are still using x.x.x.x instead of y.y.y.y IP,
though packets are being sent with the correct interface (ppp1)
I have shut down ppp0 and removed SNAT rule for it, but outgoing packets
are still showing x.x.x.x IP. Even, ip ro fl cache didn't help.
Is there anything I am doing wrongly? I suppose this is some unwanted
behaviour.
warp:~# uname -a
Linux warp 2.6.32-5-686 #1 SMP Thu Aug 12 13:38:27 UTC 2010 i686 GNU/Linux
next reply other threads:[~2010-08-22 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 18:35 Yevgeny Kosarzhevsky [this message]
2010-08-22 21:12 ` SNAT problem Pascal Hambourg
[not found] ` <4C8C9C9C.2010005@pisem.net>
2010-09-13 9:10 ` Pascal Hambourg
-- strict thread matches above, loose matches on Subject: below --
2009-07-01 10:00 Manu
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=4C716DF6.3040602@pisem.net \
--to=deza50293@tut.by \
--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