From: Nigel Kukard <nkukard@lbsd.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Bandwidth limiting
Date: Mon, 08 Apr 2002 23:51:48 +0000 [thread overview]
Message-ID: <marc-lartc-101830994728684@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216959@msgid-missing>
hrmmm, ok after trying out "tc" for the last week i've noticed it is
not even nearly as powerfull as netfilter.
is still have the same problem with dropping packets as i did before,
it seems to break some connections (i'm not dropping SYN packets, or
any ones which are in state NEW), only those related & established.
is there anything i shouldn't drop?, like specific combinations of
flags? would it be better if i dropped every second packet when a limit
is exceeded rathat than everything?
i really need advice on this :(
Regards
Nigel
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-04-08 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 0:00 [LARTC] Bandwidth limiting Thomas
2000-11-22 16:35 ` Thomas
2000-11-22 23:35 ` Thomas
2002-04-08 23:51 ` Nigel Kukard [this message]
2002-04-09 12:44 ` Stef Coene
2002-04-09 12:52 ` Nigel Kukard
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=marc-lartc-101830994728684@msgid-missing \
--to=nkukard@lbsd.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 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.