From: Anders Westrup <anders@barbanet.com>
To: Neal Stephenson <neal@bakerst.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: solved it (at lest for me) "MASQUERADE: Route sent us somewhere else."
Date: Fri, 9 Jan 2004 10:46:39 +0100 [thread overview]
Message-ID: <20040109094639.GD3073@taket.barbanet.com> (raw)
In-Reply-To: <1073620346.17985.26.camel@moran.bakerst.org>
Hi,
I have another solution to the same problem. I also use multiple external
interfaces and select outgoing interface via:
ip rule add from IP/range lookup TABLE
With 2.4.23 iptables -j MASQUERADE stopped working, reporting:
MASQUERADE: Route sent us somewhere else.
In my case the solution was to change my masquerade rule
iptables -t nat -A POSTROUTING -o IF -s IP/range -j MASQUERADE
to SNAT instead:
iptables -t nat -A POSTROUTING -o IF -s IP/range -j SNAT --to-source EXT-IP
With this config everything works as before 2.4.23.
regards
Anders Westrup
On Thu, Jan 08, 2004 at 10:52:26PM -0500, Neal Stephenson wrote:
> Hi,
>
> I figured out my routing problems which were causing
>
> MASQUERADE: Route sent us somewhere else.
>
> messages from the kernel. I use iptables to masquerade and mangle
> packets so with the advanced router features i can send it out
> appropriate interfaces (i.e. web traffic out my residential ISP service
> not my commercial ISP service). See the earlier thread on this for more
> info (Subject 2.4.23 masquerading broken?). I got a useful reply from
> Martin Josefsson who suggested that ipt_MASQUERADE could no longer find
> the input-interface anymore. Upon further investigation and it seems all
> the rules with iif or from in them no longer work (at least for me). So
> rules like the following will cause the error in post 2.4.22 kernels.
>
> ip rule add pri 420 from IP lookup TABLE
>
> I now use exclusively rules of the form
>
> ip rule add pri 420 fwmark MARK table TABLE
>
> and mark all packets needing special routing with mangling rules such as
>
> iptables -t mangle -A PREROUTING -s IP -j MARK --set-mark MARK
>
> this seems to prevent the problem. Don't know what changed in the
> kernel.
>
> Neal
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
--------------------------------------------
Anders Westrup <anders@barbanet.com>
echo '[lddx%Px/dsnK<b]dsb203953535806376680189225555sn[ln128]sdx' | dc
prev parent reply other threads:[~2004-01-09 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 3:52 Neal Stephenson
2004-01-09 9:46 ` Anders Westrup [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=20040109094639.GD3073@taket.barbanet.com \
--to=anders@barbanet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neal@bakerst.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
all inboxes | Powered by JetHome®