All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marius Cristian CONSTANTIN" <cchrism@sundy.cs.pub.ro>
To: lartc@vger.kernel.org
Subject: [LARTC] Bandwidth sharing...
Date: Sat, 13 Apr 2002 21:52:40 +0000	[thread overview]
Message-ID: <marc-lartc-101873474604697@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]

    I work as network administrator in a dept. from a bigger company, and I want to limit traffic in the night down to 160Kbit, without disrupting comunication with peers from the entire company. To make my self clear, the company has 2 class C networks, 1 for our dept, and the other for the rest of the company. So, I want to limit traffic to the Internet, but the traffic to the other class C won't be limited. Also another requirement is to limit all the day traffic like Morpheus, Kazaa, and stuff like that. The traffic should look like: internal to the company, no restriction. Peer2Peer traffic, 100Kbit day, 60Kbit in the night, Rest of the traffic not limited in the day, 160Kbit in the night. Also, if possible, traffic from the outside shouldn't be disturbed at all, any time (handled by root class).
    If I set the 130 class, without the TIME parameter, it won't limit the traffic in the night, despite the fact that the 130 class is a child for 128, which has the 160Kbit limit in the night and bounded. The 130 class has a sfq leaf, because I don't want a single user to hog the bandwidth.
    My questions are: why is the 130 class not limited to the bandiwidth of the parent? and second, should I do differently to get the same results?
    I've created several files with cbq.init like that:

root@mail:/etc/cbq# cat cbq-127.ourDept-AnotherDept 
DEVICE=eth0,100Mbit,10Mbit
RATE=100Mbit
WEIGHT=10Mbit
PRIO=1
BOUNDED=no
RULE=192.168.6.0/24,192.168.5.0/24
RULE=192.168.5.0/24,192.168.6.0/24

root@mail:/etc/cbq# cat cbq-128.ourDept-internet-total 
DEVICE=eth0,100Mbit,10Mbit
RATE=100Mbit
WEIGHT=10Mbit
LEAF=none
PRIO=6
BOUNDED=yes
TIME=20:00-06:00;160Kbit/16Kbit

root@mail:/etc/cbq# cat cbq-129.DSD-P2P            
DEVICE=eth0,100Mbit,10Mbit
RATE=120Kbit
WEIGHT=12Kbit
PRIO=8
PARENT=128
BOUNDED=yes
RULE=:1214
RULE=,:1214
RULE=:6346
RULE=,:6346
TIME=20:00-06:00;60Kbit/6Kbit

root@mail:/etc/cbq# cat cbq-130.ourDept-internet 
DEVICE=eth0,100Mbit,10Mbit
RATE=100Mbit
WEIGHT=10Mbit
PRIO=6
LEAF=sfq
PARENT=128
BOUNDED=no
RULE=192.168.5.0/24
RULE=192.168.5.0/24,
TIME=20:00-06:00;160Kbit/16Kbit



[-- Attachment #2: Type: text/html, Size: 3413 bytes --]

                 reply	other threads:[~2002-04-13 21:52 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-101873474604697@msgid-missing \
    --to=cchrism@sundy.cs.pub.ro \
    --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.