From: Ben Clewett <B.Clewett@roadrunner.uk.com>
To: "Sadanapalli, Pradeep Kumar (MED, TCS)" <Pradeep.Sadanapalli@med.ge.com>
Cc: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: How to configure iptables to block a land attack?
Date: Mon, 17 Mar 2003 09:18:56 +0000 [thread overview]
Message-ID: <3E759300.2030707@roadrunner.uk.com> (raw)
In-Reply-To: <2DE78F33FFE0D3118C0200508B94F9CA19420E49@uswaumsx08medge.med.ge.com>
Asking for a 'standard iptables configuration for all the common
attacks' is asking for a lot!!!
There are many way of setting up a firewall, and you have to take into
account how it will work. Including DNS, Email, NAT, NAPT, Routing
protocols, ICMP options, DNZ's etc...
Also it depends what you have compiled into your kernel for what options
area available to you. A 'standard' set may fail because of this and
leave you unwittingly vunerable! Compiling everything there is into
your kernel is not the correct answer here.
Even worse, there are considerations of load, logging, QoS...
Maybe you want a VPN as well, or backup routs when primary failes...
For instance my 'standard' set, which has taken me six months to
produce, has nearly a 1000 rules, thirty or so flags, very complex
logging, QoS, VPN support, using MySQL to post-store and analyse the logs...
I started by reading 'Linux Firewalls' (second edition) from Ziegler,
New Riders. This has a selection of common iptables setups you can copy
and edit the way you want...
Alternativelly, use something like SuSE or Redhat which has it's own
'standard set' built in. :)
Good luck...
Ben
Sadanapalli, Pradeep Kumar (MED, TCS) wrote:
> Hi Friends,
> Can anyone tell me how should I configure my IPTABLES Firewall to block
> a LAND ATTACK?
> I am new to firewalling..I am running RedHat Linux 8.0 and iptables.
>
> Can anyone send me a standard iptables configuration for all the common
> attacks?
> I would like to know what are all the common atacks and explaination
> about them.
> Can you direct me to some good link where I can find information on this
> topic?
>
> Thanks and Regards,
> Pradeep
>
>
>
> -----Original Message-----
> From: terry white [mailto:twhite@aniota.com]
> Sent: Friday, March 14, 2003 2:18 AM
> To: linux-admin
> Subject: RE: how to minimize/maximize/restore an open window in linux
> ...
>
>
> on "3-13-2003" "Sadanapalli, Pradeep Kumar (MED, TCS)" writ:
>
> : I am using RedHat linux 8.0 . I am running KDE .
>
> ... that is the install i'm running on one of my machines.
>
> i just checked, and when a window is open, 'left' click on the '-'
> at
> the "top right" of that window, and it disappears into a 'pane' at the
> bottom of the desktop. 'left' click that, and it reappears ...
>
>
next prev parent reply other threads:[~2003-03-17 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 21:34 How to configure iptables to block a land attack? Sadanapalli, Pradeep Kumar (MED, TCS)
2003-03-15 14:25 ` terry white
2003-03-17 9:18 ` Ben Clewett [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-15 17:43 Tace
2003-03-15 18:40 ` terry white
2003-03-15 19:42 ` Glynn Clements
2003-03-17 21:37 Sadanapalli, Pradeep Kumar (MED, TCS)
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=3E759300.2030707@roadrunner.uk.com \
--to=b.clewett@roadrunner.uk.com \
--cc=Pradeep.Sadanapalli@med.ge.com \
--cc=linux-admin@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 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.