From: Brian White <bcwhite@precidia.com>
To: netdev@oss.sgi.com
Subject: rp_filter dropping things it shouldn't
Date: Wed, 05 Nov 2003 15:41:02 -0500 [thread overview]
Message-ID: <3FA9605E.2876B0D5@precidia.com> (raw)
Kernel: 2.4.20
Arch: i386
Dist: debian/testing
While experimenting with an automatic dial-backup system, we ended up with
the situation where we have two default routes, one to PPP with a metric
of 0 and one to ethernet with a metric of 1. The PPP route is brought
on-line when connectivity to a remote host is not possible over ethernet
but the default route over eth0 needs to remain so we can continue to check
that link.
The problem is that when we bind to eth0 to ping the remote host and a
reply does come back (thus indicating we can close the dial-backup link),
the ping reply is getting dropped by "rp_filter".
My guess is that rp_filter sees that the preferred default route is over ppp0
and thus assumes that packets should not be coming over eth0, which of course
they do since that is the interface/address the request was sent from.
Setting "rp_filter" to "0" for "eth0" fixed this problem.
Brian
( bcwhite@precidia.com )
-------------------------------------------------------------------------------
"A dollar saved is two dollars earned." -- Dave Chilton (The Wealthy Barber)
reply other threads:[~2003-11-05 20:41 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=3FA9605E.2876B0D5@precidia.com \
--to=bcwhite@precidia.com \
--cc=netdev@oss.sgi.com \
/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).