From: Markku Savela <Markku.Savela@vtt.fi>
To: <netdev@vger.kernel.org>
Subject: rp_filter disabled (all = 0) and still get "martians"
Date: Tue, 17 Apr 2012 15:28:38 +0300 [thread overview]
Message-ID: <4F8D61F6.9090405@vtt.fi> (raw)
I've been trying to some IPsec with Click, and I thought
tunneling would be trivial: just enable forwarding
and disable rp_filters -- no such luck! I've
eth1: 192.168.0.14/24
tun0: 10.0.0.1/8
What tun0 basicly tries to do, is to add
dst 10.0.0.2 -> tun0 -> ...
... User space adds tunnel
... dst=192.168.0.15
... src=192.168.0.14
... and returns packet to tun0
-> tun0 -> expect it to be routed to eth1
But, I still get it dropped as martian, maybe
due to src address? (Routes fine if src is not
192.168.0.14, like 192.168.1.14).
[ 2801.224711] martian source 192.168.0.15 from 192.168.0.14, on dev tun0
Is there any way to disable this "feature"?
And, even better, it would be wonderful, if
specifying src=0.0.0.0 would automatically
fill in the correct source depending on the
final interface.
I'm doing this on
2.6.38-14-generic #58-Ubuntu SMP Tue Mar 27 18:48:46 UTC 2012 i686 i686
i386 GNU/Linux
reply other threads:[~2012-04-17 12:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F8D61F6.9090405@vtt.fi \
--to=markku.savela@vtt.fi \
--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).