From: Borut Mrak <b@aufbix.org>
To: lartc@vger.kernel.org
Subject: [LARTC] problems with vlans
Date: Wed, 07 Aug 2002 14:32:18 +0000 [thread overview]
Message-ID: <marc-lartc-102873082318080@msgid-missing> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi.
My setup:
P3 box, a few ethernet interfaces (eepro100) shaping traffic to some of my
customers. It's been working fine for more than a year. Each interface has a
root cbq qdisc with n (=num of customers) classes, u32 filters are used to
classify the packets according to src/dst addresses. These are the commands
used (taken from a perl script which parses a simple config file, therefore
the $ variables):
/sbin/tc qdisc add dev $device root handle $handle cbq bandwidth $bandwidth
avpkt 1000
/sbin/tc class add dev $device parent $rh{$device}0 classid $handle cbq
bandwidth 100mbit rate $bandwidth allot 1514 weight 100kbit prio 1 maxburst 1
avpkt 1000 bounded
/sbin/tc filter add dev $device parent $rh{$device}0 protocol ip prio 100 u32
match ip $direction $netblock flowid $handle
I tried moving this to a new machine using only 2 eepro100 interfaces and
using vlans (one port per customer is really quite expensive on an Extreme
switch :-), but suddenly the shaping stopped working as supposed.
For instance, I have a customers shaped to 512 kbps, but instead of that they
only get ~250 kbps. Changing the rate of the class does not make much
difference. Pushing it up to 2048kbps only changes the clients real bandwidth
to ~340 kbps. The kernel is stock 2.4.18, eepro100 driver is patched (one
line) to support VLANs and that's the only change from the old machine. Any
ideas? Shaping on a "normal" (non-vlan) interface seems to work OK.
BTW (offtopic), anyone knows of a more compact changelog for kernel 2.4.19? I
don't have time to read all the bk mumbo-jumbo, I only want to know the major
differences. 25MB diff scared me a little when it came out :-)
regards,
- --
Borut Mrak, b@aufbix.org
PGP: finger:b@aufbix.org
- ------------------------
"Great minds discuss ideas; Average minds discuss events; Small minds
discuss people."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj1RL3IACgkQRUVvbWYRhIJtGACgn146nxtpyLgCtGMel53sMABs
ipMAoLuCGikOJqGsdBW8jyzoFzXpyMXN
=4TQa
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-08-07 14:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-102873082318080@msgid-missing \
--to=b@aufbix.org \
--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.