From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@vger.kernel.org
Subject: Re: force specific interface / late DNAT
Date: Mon, 11 Oct 2010 13:17:09 +0200 [thread overview]
Message-ID: <4CB2F235.90208@plouf.fr.eu.org> (raw)
In-Reply-To: <20101011101013.66800@gmx.net>
Hello,
mad_stuff@gmx.de a écrit :
>
> I've some strange requirements for my setup: my box (2.6.24) holds a
> bunch of outgoing ppp-connections (ppp0-ppp15) but all of these use the
> same IP subnet (192.168.1.0/24; 192.168.1.100 is my side, and
> 192.168.1.1 is the IP of the server on the other side; so in the end,
> I've got 16 ppp-devices with IP 192.168.1.100 belonging to completely
> different networks).
>
> Now I want to connect (SFTP using OpenSSH) to some servers (IP:
> 192.168.1.1 each) on the oposite sides, so I thought about NAT to make
> this mess a bit handier:
Is this one same server or different servers with the same address ?
> -> I had the following idea to distinguish the different connections
> for userspace programs: for each device pppX create an alias pppX:1 with
> IP 10.0.X.2/24 so that I can connect to 10.0.10.1 if I want to talk to
> 192.168.0.1 connected via ppp10 and 10.0.9.1 if I want to use
> 192.168.0.1 connected via ppp9 etc.
Yo do not have to create IP aliases ; you can just add routes. This
saves the SNAT/MASQUERADE operation.
ip route add 10.0.X.1 dev pppX
> So I added two rules:
>
> iptables -t nat -A OUTPUT -o ppp9 -d 10.0.9.1 -j DNAT --to-destination 192.168.0.1
> iptables -t nat -A POSTROUTING -o ppp9 -j MASQUERADE
>
> But this doesn't work since after applying the DNAT rule the routing
> decision is changed
You can use -j MARK in mangle/OUTPUT and advanced routing (ip rule add
fwmark) to force routing via the correct interface.
prev parent reply other threads:[~2010-10-11 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 10:10 force specific interface / late DNAT mad_stuff
2010-10-11 11:17 ` Pascal Hambourg [this message]
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=4CB2F235.90208@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--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.