Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Roy-Magne Mo <rmo@sunnmore.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] pps limit ?
Date: Thu, 31 Aug 2006 10:35:32 +0000	[thread overview]
Message-ID: <44F6BB74.30307@sunnmore.net> (raw)
In-Reply-To: <20060830140726.GA24152@ldc.net>

Dmytro O. Redchuk wrote:
> Hello, list members,
> 
>   can i limit pps rate with linux? How?
> 
>   -m limit does not fit, as i understood: it can help with low rates only
>   (is that true? any suggestions?)

This is probably better achieved at the switch level. If this is for 
stopping viruses and DoS-attacks, then it's better to stop the traffic 
as close to the source as possible.

-- 
Roy-Magne Mo

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-08-31 10:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30 14:07 [LARTC] pps limit ? Dmytro O. Redchuk
2006-08-30 15:22 ` Kajetan Staszkiewicz
2006-08-31  6:06 ` Dmytro O. Redchuk
2006-08-31 10:35 ` Roy-Magne Mo [this message]
2006-08-31 11:03 ` Dmytro O. Redchuk

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=44F6BB74.30307@sunnmore.net \
    --to=rmo@sunnmore.net \
    --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