From: Sorin Panca <sorin.panca@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: network flood imunity
Date: Wed, 21 Dec 2005 15:09:12 +0200 [thread overview]
Message-ID: <43A953F8.2040907@gmail.com> (raw)
In-Reply-To: <43A94A49.60506@vip.cybercity.dk>
Mogens Valentin wrote:
> Sorin Panca wrote:
>
>> Hi!
>> I have a network with no natting and i would linke to develop a rule set
>> for flood protection of some windows stations. Recently one station was
>> flooded while it was powered off (for me this is a uncomprehensible
>> situation / act)..
>
>
> Ehh? Flooded while powered off? Says who? Your ISP? If they can see
> YOUR IP getting spoofed (while powered off), they -may- have a
> problem with overlapping custumer IP's; I've seend that before :)
Tell taht to my boss! :) As far as he is concerned that flood is my
fault and the ISP is always right... And I should do something for that
matter. (That is why I asked you guys.)
>
>> My ISP added a filter against my station and I can't
>> acces the internet on it now. The server is running kernel 2.4.22-10mdk
>> with mandrake-<some.version> and iptables-1.2.8. I tried to replace it
>> (the server) but due to unknown reasons, I failed three times. And I
>> gave up.
>> If someone has an ideea of how can I protect the server in this
>> configuration against floods, I would be very happy to learn.
>
>
> I havne't got time for rule examples, but you may find the following
> /proc settings quite helpful:
>
> # Disable ICMP echo-request to broadcast addresses (Smurf
> amplifier):
> echo "1" >/proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
>
> # Enable syn-cookies (prevent syn-flood attacks):
> echo "1" >/proc/sys/net/ipv4/tcp_syncookies
>
> # Reduce number of possible SYN Floods:
> echo "1024" >/proc/sys/net/ipv4/tcp_max_syn_backlog
>
> # Enable defrag error protection:
> echo 1 > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses
>
> # Enable time-wait assassination hazards in tcp (RFC 1337):
> echo "1" >/proc/sys/net/ipv4/tcp_rfc1337
>
> # Prevent remote digging of OS-type and uptime (RFC1323):
> #echo "1" >/proc/sys/net/ipv4/tcp_timestamps # enable
> timestamps
> echo "0" >/proc/sys/net/ipv4/tcp_timestamps # disable
> timestamps
>
> # Disable RFC2018 TCP Selective Acknowledgements:
> echo 0 > /proc/sys/net/ipv4/tcp_sack
>
>
>
> # Sourcerouting and spoofing:
> for i in /proc/sys/net/ipv4/conf/*; do
> # Drop all source-routed packets:
> echo "0" >$i/accept_source_route
>
> # Deactivate normal ICMP redirect accept/send:
> echo "0" >$i/accept_redirects
> echo "0" >$i/send_redirects
>
> # Activate secure ICMP redirects (send only?) (on by
> default):
> echo "1" >$i/secure_redirects
>
> # Enable ingress + egress source-address verification
> (prevent spoofing):
> #echo "0" >$i/rp_filter # disable
> echo "1" >$i/rp_filter # enable
> done
>
> # Log spoofed, source routed and redirect packets:
> #echo 1 >/proc/sys/net/ipv4/conf/all/log_martians
> echo 0 >/proc/sys/net/ipv4/conf/all/log_martians
>
>
I'll try these. Thank you!
next prev parent reply other threads:[~2005-12-21 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 11:57 network flood imunity Sorin Panca
2005-12-21 2:09 ` ludi
2005-12-21 13:04 ` Sorin Panca
2005-12-21 12:27 ` Mogens Valentin
2005-12-21 13:09 ` Sorin Panca [this message]
2005-12-21 15:33 ` TheGesus
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=43A953F8.2040907@gmail.com \
--to=sorin.panca@gmail.com \
--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 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.