From: Claus Fischer <claus.fischer@clausfischer.com>
To: linux-kernel@vger.kernel.org
Subject: Spoof protection with redundant routes
Date: Mon, 8 Apr 2002 22:02:15 +0200 [thread overview]
Message-ID: <20020408220215.A1987@clausfischer.com> (raw)
I have a box with two redundant CIPE tunnels to a
remote network 10.36.x.x.
Routing table:
Destination Gateway Genmask ... Iface
...
10.36.1.12 0.0.0.0 255.255.255.255 UH 0 0 0 cipcb3
10.36.1.11 0.0.0.0 255.255.255.255 UH 0 0 0 cipcb1
10.36.0.0 10.36.1.12 255.255.0.0 UG 0 0 0 cipcb3
10.36.0.0 10.36.1.11 255.255.0.0 UG 0 0 0 cipcb1
...
Now when a packet comes in from 10.36.2.2 on cipcb1, the
spoof protection kills it, since the outgoing packet would
take the route via cipcb3 which is first. I didn't quite
expect that initially.
- Is that known and by design?
- Is that the desired behaviour?
- Is there some possibility to change that?
- Do I have a choice other than to turn off rp_filter?
Claus
--
Claus Fischer <claus.fischer@clausfischer.com>
http://www.clausfischer.com/
next reply other threads:[~2002-04-08 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 20:02 Claus Fischer [this message]
[not found] <20020408220215.A1987@clausfischer.com.suse.lists.linux.kernel>
2002-04-08 20:23 ` Spoof protection with redundant routes Andi Kleen
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=20020408220215.A1987@clausfischer.com \
--to=claus.fischer@clausfischer.com \
--cc=linux-kernel@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