From: Dragan Simic <dsimic@urc.bl.ac.yu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] A small correction to LARTC (fwd)
Date: Thu, 16 Jan 2003 15:53:05 +0000 [thread overview]
Message-ID: <marc-lartc-104273186926588@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104272305013372@msgid-missing>
I had 2.4.x in mind when I wrote this about rp_filter values. In any case,
in the LARTC should be cleared out what applies to 2.2 branch, and what to
2.4 branch. It's true, in 2.2.23, there are three options (0,1,2); and
there are two options (0,1) in 2.4.20.
On Thu, 16 Jan 2003, Michael T. Babcock wrote:
> Dragan Simic wrote:
>
> >interface, but there should be, instead, "echo 1 > $i". Also, in
> >Documentation/networking/ip-sysctl.txt there are only two options
> >for rp_filter - 0 (RPF off) or 1 (RPF on).
>
> At various points in history there have been values of 0, 1 and 2
> available to mean different things. In my 2.2.14 source I have laying
> around, I see:
>
> rp_filter - INTEGER
> 2 - do source validation by reversed path, as specified in RFC1812
> ...
> 1 - (DEFAULT) Weaker form of RP filtering: drop all the packets
> ...
> 0 - No source validation.
--
.----------------------------------------------------------------------------.
| Pozdrav / Best Wishes, dsimic@urc.bl.ac.yu | LL The Choice of |
| Dragan Simic RS.BA Hostmaster | LL GNU |
| URC B.Luka / RSKoming.NET System/Network Admin | LLLL i n u x Generation |
`----------------------------------------------------------------------------'
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-01-16 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 13:26 [LARTC] A small correction to LARTC (fwd) Dragan Simic
2003-01-16 15:53 ` Dragan Simic [this message]
2003-01-16 21:52 ` Julian Anastasov
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=marc-lartc-104273186926588@msgid-missing \
--to=dsimic@urc.bl.ac.yu \
--cc=lartc@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