From: "Geffrey Velásquez" <g_netfilter@netfids.com>
To: pasik@iki.fi
Cc: mgale@utilitran.com, netfilter@lists.netfilter.org
Subject: Re: Protecting against DoS
Date: Tue, 9 Dec 2003 14:20:09 -0500 (PET) [thread overview]
Message-ID: <36917.200.48.142.50.1070997609.squirrel@www.netfids.com> (raw)
In-Reply-To: <20031209171322.GE17221@edu.joroinen.fi>
Hum.. but what happen if the workstation is infected? the virus will do a
DoS to the user of the workstation, the firewall will block valid
connections.
> On Tue, Dec 09, 2003 at 10:06:50AM -0700, Michael Gale wrote:
>> Hello,
>>
>> You could try using a rate limit -- you could allow a machine to make
>> lets say 10 outbound
>> connections a second and then ...
>>
>> Depending on your network policy you could drop or log all other
>> outbound request.
>>
>
> This is what I'm planning to do.. and this is also the reason I was
> asking the questions in the original mail :-)
>
> -- Pasi Kärkkäinen
>
> ^
> . .
> Linux
> / - \
> Choice.of.the
> .Next.Generation.
next prev parent reply other threads:[~2003-12-09 19:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 15:43 Protecting against DoS 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 [this message]
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-11 8:04 ` bridge vlans in HP 2524 switch Computer Security
2004-01-26 10:45 ` Protecting against DoS Pasi Kärkkäinen
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 19:11 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
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=36917.200.48.142.50.1070997609.squirrel@www.netfids.com \
--to=g_netfilter@netfids.com \
--cc=mgale@utilitran.com \
--cc=netfilter@lists.netfilter.org \
--cc=pasik@iki.fi \
/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