From: Ross Skaliotis <ross@student.andover.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bandwidth limiting on packet size !
Date: Wed, 06 Mar 2002 17:33:51 +0000 [thread overview]
Message-ID: <marc-lartc-101543608917065@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101543470412247@msgid-missing>
I'm doing this in my setup. To match packet sizes, I use a filter that
looks at the 3rd byte in the ip header. The total length in the ip header
takes up two bytes, bytes 3 to 4 (or 2-3 if you're counting starting from
0 as you should when using a filter) for a maximum packet size of 65535.
My filter looks like the following:
tc filter add dev ppp0 parent 2:0 protocol ip prio 5 u32 match ip \
protocol 6 0xff match u8 0x00 0xff at 2 flowid 2:3
The second match does the following: It looks in the first byte of the two
byte field and matches 00 only. This means that the packet can only be big
enough to fill up on byte worth of data which equates to a size no greater
then 255 bytes. You can play around with it to get different values. It
seems to work fine for me.
Hope this helps,
-Ross Skaliotis
On Wed, 6 Mar 2002, Arindam Haldar wrote:
> hi all,
>
> i also wanted 2 know if someone has tried bandwidth limiting on packet
> size with tc and >>> WITHOUT USING IPTABLES !
> can anyone lend his expertise on the above pls...
> thanx in advance
>
> A.H
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-03-06 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 17:28 [LARTC] bandwidth limiting on packet size ! Arindam Haldar
2002-03-06 17:33 ` Ross Skaliotis [this message]
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-101543608917065@msgid-missing \
--to=ross@student.andover.edu \
--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.