From: Patrick McHardy <kaber@trash.net>
To: Ingo Oeser <netdev@axxeo.de>
Cc: netdev@vger.kernel.org
Subject: Re: Funny Routing change since 2.6.16.x
Date: Thu, 08 Feb 2007 17:32:24 +0100 [thread overview]
Message-ID: <45CB5098.3020107@trash.net> (raw)
In-Reply-To: <200702081652.31527.netdev@axxeo.de>
Ingo Oeser wrote:
> Patrick McHardy schrieb:
>
>>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?
We have a netfilter Wiki now at wiki.netfilter.org. You could add
the first entry :)
prev parent reply other threads:[~2007-02-08 16:32 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
2007-02-08 16:32 ` Patrick McHardy [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=45CB5098.3020107@trash.net \
--to=kaber@trash.net \
--cc=netdev@axxeo.de \
--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).