From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Ralf Spenneberg <lists@spenneberg.org>
Cc: "Geffrey Velásquez" <g_netfilter@netfids.com>,
Netfilter <netfilter@lists.netfilter.org>
Subject: Re: Protecting against DoS
Date: Tue, 09 Dec 2003 13:41:53 -0500 [thread overview]
Message-ID: <1070995313.1869.28.camel@jasiiitosh.nexusmgmt.com> (raw)
In-Reply-To: <1070993798.18225.96.camel@kermit>
On Tue, 2003-12-09 at 13:16, Ralf Spenneberg wrote:
> Hi,
>
> Am Die, 2003-12-09 um 19.01 schrieb John A. Sullivan III:
> > > > echo 1 > /proc/sys/net/ipv4/tcp_syncookies -- if you have not compiled
> > >
> > >
> > > Is that valid for forwarded packets? or only destinated to the firewall?
> This is valid only for local packets.
>
> > We have avoided using these /proc settings for just that concern - that
> > they are mostly for the gateway itself and not for the devices being
> > protected by it whether it is anti-spoofing with rp_filter or protecting
> > against syn_floods. Is this assumption of ours true? Thanks, all - John
> Actually it depends. Most just concern local packets, but
> rp_filter and accept_source_route for example tests for all packets.
>
>
> Cheers,
>
> Ralf
Ah, very interesting. Yes, we do disable source route and we disable
redirects through /proc on our gateways but I thought (in my ignorance)
that rp_filter only affected traffic to the gateway. So you are saying
that if rp_filter=1 and a packet comes into the gateway on eth0 bound
for an address on the other side of eth1 but not the address bound to
eth1 and has a source address of some device on eth0, that rp_filter
will drop the packet before it ever gets to netfilter?
To take it a step further, if rp_filter=2 and a packet come into the
gateway on eth0 bound for an address on the other side of eth1 but not
on a network directly connected to eth1 and has a source address that is
from a network that is either directly or indirectly connected to eth1,
rp_filter will drop the packet before it gets to netfilter? This
actually seems a bit strange since the network on the other side of eth0
is indirectly connected to eth1 but I'm not quite sure what rp_filter=2
means.
Thanks - John
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
next prev parent reply other threads:[~2003-12-09 18:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 19:11 Protecting against DoS Geffrey Velásquez
2003-12-09 18:01 ` John A. Sullivan III
2003-12-09 18:16 ` Ralf Spenneberg
2003-12-09 18:41 ` John A. Sullivan III [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 15:43 Pasi Kärkkäinen
2003-12-09 16:02 ` Michael Gale
2003-12-09 16:28 ` Pasi Kärkkäinen
2003-12-09 16:40 ` Michael Gale
2003-12-09 16:51 ` Pasi Kärkkäinen
2003-12-09 17:06 ` Michael Gale
2003-12-09 17:13 ` Pasi Kärkkäinen
2003-12-09 19:20 ` Geffrey Velásquez
2003-12-09 20:10 ` Arnt Karlsen
2003-12-10 16:53 ` Pasi Kärkkäinen
2004-01-11 1:50 ` Peter Frischknecht
2004-01-26 10:45 ` Pasi Kärkkäinen
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=1070995313.1869.28.camel@jasiiitosh.nexusmgmt.com \
--to=john.sullivan@nexusmgmt.com \
--cc=g_netfilter@netfids.com \
--cc=lists@spenneberg.org \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox