From: "Noah McNallie" <n0ah@n0ah.org>
To: linux-kernel@vger.kernel.org, "Alexander Clouter" <alex@digriz.org.uk>
Subject: Re: SNATed connections show as original ip in /proc/net/tcp
Date: Sun, 11 Jul 2010 11:11:59 -0400 [thread overview]
Message-ID: <op.vfopt9kclgimzx@win7> (raw)
In-Reply-To: <151pg7-26g.ln1@chipmunk.wormnet.eu>
On Sun, 11 Jul 2010 10:30:25 -0400, Alexander Clouter <alex@digriz.org.uk>
wrote:
> Noah McNallie <n0ah@n0ah.org> wrote:
>>
>> just as the topic describes.
>>
> Probably better to post this to netdev?
>
>> I'm currently doing SNAT to force some destination tcp ports to be
>> routed
>> through a specific route rather than the default route. To accomplish
>> this
>> I mark thoes packets with iptables, use 'ip' to specify marked packets
>> via
>> the specified route, and then use iptables to change their source
>> address.
>>
> SNAT'ing locally sourced traffic? That's pretty nasty.
>
> Look into using 'ip rule' and a second routing table.
>
> http://lartc.org/howto/lartc.rpdb.html
>
> You will still need use iptables/MARK to do L4 (tcp/udp/etc) policy
> routing though, however now you can dump the ugly SNATing.
>
> Cheers
>
ok i'll stick it there i must have missed that browsing mailing lists last
night... uhh as far as ip rule i am using that, that's how i match the
packets with the firewall mark that need to go out a specific interface
and to a specific route... i don't believe ip rule has any option to match
packets based on destination port and change their source address and
route them out any specific interface, or i'd be doing that all along as
that would be much better.
noah
next prev parent reply other threads:[~2010-07-11 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 9:10 SNATed connections show as original ip in /proc/net/tcp Noah McNallie
2010-07-11 14:30 ` Alexander Clouter
2010-07-11 15:11 ` Noah McNallie [this message]
2010-07-11 17:08 ` Alexander Clouter
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=op.vfopt9kclgimzx@win7 \
--to=n0ah@n0ah.org \
--cc=alex@digriz.org.uk \
--cc=linux-kernel@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