From: Ingo Oeser <netdev@axxeo.de>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org
Subject: Re: Funny Routing change since 2.6.16.x
Date: Thu, 8 Feb 2007 16:52:31 +0100 [thread overview]
Message-ID: <200702081652.31527.netdev@axxeo.de> (raw)
In-Reply-To: <45CA09F2.6050700@trash.net>
Hi Patrick,
Patrick McHardy schrieb:
> Ingo Oeser wrote:
> > Patrick McHardy schrieb:
> >
> >>My guess is that you're using MASQUERADE on ppp0, which since 2.6.14
> >>doesn't exclude locally generated packets anymore, so it translates
> >>them to the primary ppp0 address. For replies it works because NAT
> >>is already set up for the incoming packet, without masquerading.
> >
> >
> > Your guess is right! Thanks for that hint. Do you have any idea, how to
> > restore the old behavior?
> >
> > I have to, because the ISP cannot assign a different local address
> > and have problems with the new behavior, because that IP adress is an MX entry
> > and the VPN gateway address for several third party vendor tunnels.
> > So changing that is quite an effort.
>
>
> Since these packets already have the proper source address chosen
> by routing, there is no need to NAT them anymore. So the easiest
> fix is to exclude them manually from masquerading based on the
> address.
Just did that (iptables -t nat -I POSTROUTING -s $SRCADDR -o ppp0 -j ACCEPT)
and it works without any problems.
Many thanks for your very fast help! I'm very happy now :-)
Do you know any good place, where this can be documented?
Best regards
Ingo Oeser
next prev parent reply other threads:[~2007-02-08 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 16:56 Funny Routing change since 2.6.16.x Ingo Oeser
2007-02-07 17:07 ` Patrick McHardy
2007-02-07 17:16 ` Ingo Oeser
2007-02-07 17:18 ` Patrick McHardy
2007-02-08 15:52 ` Ingo Oeser [this message]
2007-02-08 16:32 ` Patrick McHardy
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=200702081652.31527.netdev@axxeo.de \
--to=netdev@axxeo.de \
--cc=kaber@trash.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).