From: Simon Stemplinger <Simon.Stemplinger@gmx.de>
To: lartc@vger.kernel.org
Subject: [LARTC] Filter for large packets?
Date: Fri, 24 Jan 2003 09:43:53 +0000 [thread overview]
Message-ID: <marc-lartc-104340156315484@msgid-missing> (raw)
Hi,
i am using the wondershaper script on a DSL-router-firewall combination
for several LAN clients. My Problem is that the port based filter rules
dont match bulk traffic satisfyingly, because many file sharing programs
allow to use custom ports. Usually a few connections that is not
recognized as bulk are enough to fill up the 1:20 queue and slow down
www and other normal traffic. Can anyone tell me a filter rule that
matches Packets greater that a certain number of bytes. I think
classifying outgoing packets > 512 or 1024 bytes as bulk should help
here. Do you think this is a good idea, or am i missing something?
What would be a good size threshold to separate normal from bulk traffic?
regards,
Simon
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-01-24 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 9:43 Simon Stemplinger [this message]
2003-01-24 17:38 ` [LARTC] Filter for large packets? Simon Stemplinger
2003-01-24 17:39 ` Stef Coene
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-104340156315484@msgid-missing \
--to=simon.stemplinger@gmx.de \
--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.