From: Andrew Beverley <andy@andybev.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter@vger.kernel.org, Pandu Poluan <pandu@poluan.info>
Subject: Re: Routing locally generated traffic on fwmark
Date: Thu, 29 Sep 2011 18:46:11 +0100 [thread overview]
Message-ID: <1317318371.26402.292.camel@andybev-desktop> (raw)
In-Reply-To: <alpine.LNX.2.01.1109291934450.25670@frira.zrqbmnf.qr>
On Thu, 2011-09-29 at 19:35 +0200, Jan Engelhardt wrote:
> On Thursday 2011-09-29 19:28, Andrew Beverley wrote:
>
> >On Thu, 2011-09-29 at 12:28 +0200, Jan Engelhardt wrote:
> >> On Thursday 2011-09-29 08:51, Andrew Beverley wrote:
> >> >> iptables -A OUTPUT -t mangle -d 89.16.176.81 -j MARK --set-mark 0x800
> >> >> ip rule add fwmark 0x800/0xffff table T2
> >> >> ip route add table T2 default dev ppp1 via 94.30.127.76
> >> >
> >> >I've also added the following, which makes no difference:
> >> >
> >> >iptables -t nat -A POSTROUTING -o ppp1 \
> >> > -j SNAT --to-source 109.224.134.110
> >>
> >> Of course it makes no difference, because SNAT is applied after routing.
> >> ("POST" "ROUTING", see?)
> >
> >Yes, but in my case the SNAT still needed applying. The problem was that
> >although the packets were being routed via the second interface, they
> >were still being sent from the original IP address of the first
> >interface. Therefore, packets were being returned to the first
> >interface, making it look as if the second interface wasn't being used.
>
> Well, that's why one should use tcpdump -i ethX, rather than tcpdump -i
> any :-)
Yep, I learn something every time ;-)
prev parent reply other threads:[~2011-09-29 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 22:20 Routing locally generated traffic on fwmark Andrew Beverley
2011-09-29 6:51 ` Andrew Beverley
2011-09-29 7:32 ` Pandu Poluan
2011-09-29 7:53 ` [SOLVED] " Andrew Beverley
2011-09-29 8:29 ` Pandu Poluan
2011-10-02 13:11 ` Ed W
2011-09-29 10:28 ` Jan Engelhardt
2011-09-29 17:28 ` Andrew Beverley
2011-09-29 17:35 ` Jan Engelhardt
2011-09-29 17:46 ` Andrew Beverley [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=1317318371.26402.292.camel@andybev-desktop \
--to=andy@andybev.com \
--cc=jengelh@medozas.de \
--cc=netfilter@vger.kernel.org \
--cc=pandu@poluan.info \
/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