From: Brian Capouch <brianc@palaver.net>
To: netfilter@lists.netfilter.org
Subject: iptables NAT with "policy routing?"
Date: Thu, 22 Jan 2004 01:49:08 -0500 [thread overview]
Message-ID: <400F7264.1080201@palaver.net> (raw)
I have had to temporarily use a table-based route for one of my networks
for administrative reasons, e.g.
> ip rule from 192.168.1.0/24 lookup table temp
Then
> ip route add default via 192.168.127.1 dev eth0 table temp
I have standard iptables NAT rules for a host on that network:
iptables -t nat -A POSTROUTING -s 192.168.1.10 -j SNAT --to-source A.B.C.D
iptables -t nat -A PREROUTING -d A.B.C.D -j DNAT --to-destination
192.168.1.10
**********
I suspect though, that this mode of routing (as opposed to using the
"regular" table via "route add default") is somehow hosing my iptables NAT?
At least sniffing the egress interface now shows the traffic heading out
with its NATted address of 192.168.1.10.
Newbie here, I guess. Can someone help/enlighten?
Thx.
B.
next reply other threads:[~2004-01-22 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 6:49 Brian Capouch [this message]
2004-01-27 1:47 ` iptables NAT with "policy routing?" Harald Welte
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=400F7264.1080201@palaver.net \
--to=brianc@palaver.net \
--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.