From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@vger.kernel.org
Subject: Re: Port-based routing with OpenVPN
Date: Wed, 26 Sep 2007 16:10:06 +0200 [thread overview]
Message-ID: <46FA683E.5030307@plouf.fr.eu.org> (raw)
In-Reply-To: <1190810998.6867.5.camel@laptop>
Mario Hülsegge a écrit :
>
> these 2 hints solved the problem, now all runs fine. i inserted a masq
> rule before, but without setting rp_filter
The kernel disables rp_filter by default, but the startup scripts
provided by some distributions enable it.
> (who would ever thought of THAT ;) ).
The practical answer is : anyone who experienced the problem once does.
Trust me.
The theoretical answer is : anyone using iproute should, because it is a
common issue documented in the Linux Advanced Routing & Traffic Control
HOWTO, and probably elsewhere. I myself hesitated to mention it and did
it only for completeness because it could not be the only cause of your
problem : tcpdump would have seen the replies even though the kernel had
dropped them.
prev parent reply other threads:[~2007-09-26 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 23:15 (unknown) "Mario Hülsegge"
2007-09-16 11:05 ` Port-based routing with OpenVPN Pascal Hambourg
2007-09-19 21:38 ` Mario Hülsegge
2007-09-25 22:14 ` Mario Hülsegge
2007-09-26 10:33 ` Pascal Hambourg
2007-09-26 12:49 ` Mario Hülsegge
2007-09-26 14:10 ` Pascal Hambourg [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=46FA683E.5030307@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=netfilter@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