From: "George Peverill" <gpeverill@ns.sympatico.ca>
To: lartc@vger.kernel.org
Subject: [LARTC] Bandwidth Nazi'ing revisited
Date: Wed, 19 Mar 2003 11:19:28 +0000 [thread overview]
Message-ID: <marc-lartc-104807298618692@msgid-missing> (raw)
After about a week or more of enjoying a sensible amount of bandwidth on
our
network (after limiting the rate/ceiling of one particular ip on our
network)
I noticed that the rules I had been given weren't infallable, something
was
wrong. For some reason our internal samba traffic (eth1) was also
limited to the rate/ceiling
of my bandwidth throttling script [see below]
It does indeed limit his bandwidth to a max of 60kbps/sec (which is
wonderful) but somehow
its also limiting our samba traffic to 60kbp/sec also (we only notice it
in one direction
also (from our server 192.168.0.1 (eth1 interface ip) -> any of our ip's
192.168.0.x).
Any idea why it seems to be applying this rule to everyones traffic as
it leaves the server on eth1 ?
We seem to have full internet download bandwidth (which would be traffic
on eth0(about 300k/s) but
no internal traffic only passing thru eth1.
#!/bin/bash
/sbin/tc qdisc del dev eth0 root
/sbin/tc qdisc del dev eth1 root
/sbin/tc qdisc add dev eth1 root handle 1: htb default 10
/sbin/tc class add dev eth1 parent 1: classid 1:1 htb rate 100Mbps ceil
100Mbps burst 2k
/sbin/tc class add dev eth1 parent 1:1 classid 1:10 htb rate 90Mbps ceil
100Mbps burst 2k prio 0
/sbin/tc class add dev eth1 parent 1:1 classid 1:11 htb rate 60kbps ceil
60kbps burst 2k prio 7
/sbin/tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 match ip
dst 192.168.0.65 classid 1:11
/sbin/tc qdisc add dev eth0 root handle 1: htb default 10
/sbin/tc class add dev eth0 parent 1: classid 1:1 htb rate 10Mbps ceil
10Mbps burst 2k
/sbin/tc class add dev eth0 parent 1:1 classid 1:10 htb rate 9.9Mbps
ceil 10Mbps burst 2k prio 0
/sbin/tc class add dev eth0 parent 1:1 classid 1:11 htb rate 60kbps ceil
60kbps burst 2k prio 7
/sbin/tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip
src 192.168.0.65 classid 1:11
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-03-19 11:19 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-104807298618692@msgid-missing \
--to=gpeverill@ns.sympatico.ca \
--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.