All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Netfilter Developers <netfilter-devel@lists.netfilter.org>
Subject: rp_filter
Date: Fri, 27 Dec 2002 16:11:14 -0500	[thread overview]
Message-ID: <20021227211113.GK677@ns> (raw)

[-- Attachment #1: Type: text/plain, Size: 949 bytes --]

Hey all,

  Can we *please* move the rp_filter cruft into the firewalling code
  proper?  I've had yet another friend come to me asking for help after
  fighting with his iptables setup for 6 hours trying to get it to work
  to discover the whole problem was rp_filter getting in the way.  If
  rp_filter was part of the actual firewalling code where it should be
  people wouldn't run into this stupid problem.

  rp_filter is an obscure option that only the poor souls who ran into
  it know about.  I've met people who have implemented it all by hand in
  iptables because they didn't know it existed, and then didn't entirely
  trust it.  The people who need the option (those who actually run
  routers or firewalls) know they need it and will take care of having
  it enabled in their firewalling code, for most people (desktop users 
  and whatnot) it's useless anyway because they've only got one
  interface.

  	Stephen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2002-12-27 21:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27 21:11 Stephen Frost [this message]
2002-12-28  8:46 ` rp_filter Patrick Schaaf
2002-12-29 17:28   ` rp_filter Stephen Frost
2002-12-28  9:17 ` rp_filter Patrick Schaaf
2003-01-08 12:38   ` rp_filter Roberto Nibali
  -- strict thread matches above, loose matches on Subject: below --
2018-07-13 15:23 rp_filter Leroy Tennison
2018-07-13 16:23 ` rp_filter Grant Taylor
2018-07-13 16:26 ` rp_filter Jay Vosburgh
2018-07-13 18:03 ` rp_filter Leroy Tennison
2018-09-04 10:11 ` rp_filter Anton Danilov

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=20021227211113.GK677@ns \
    --to=sfrost@snowman.net \
    --cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.