From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Simple Beginner Question - allocating 64k
Date: Thu, 07 Mar 2002 07:49:15 +0000 [thread overview]
Message-ID: <marc-lartc-101548743910073@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101546392202113@msgid-missing>
> Have an internet connection on eth0 - 64K
> so eth0 = 216.139.165.7
> and eth1 = 192.168.0.1
>
> have 4 pcs connected to a hub on eth1
> the pc's are 192.168.0.11 and 22 and 33 and 44
>
> I want to allocate 4kb to 192.168.0.11
> and 4kb to 192.168.0.22
> and 8kb to 192.168.0.33
> and 32kb to 192.168.0.44
>
> so this is a total of 48kb and the rest is used on the server 10.0.0.80
>
> Also - want to make sure that 192.168.0.11 never takes more than 4kb at
> any time.
>
> No fancy stuff like separating http and smtp and things.
>
> What's the simple most elegant way of doing this on eth1.
Create a HTB qdisc, add a ceiled class of 64K, add 5 classes with the
appropriated rate (4 for the LAN's : 4,4,8,32 kb and 1 for the server 16kb)
with ceil = 64kb. But ceil 192.68.0.11 to 4kbit. Mark the packets on eht1
for all ip's with a different mark and use the fw filter on eth0 to put the
traffic in the right class.
You can do the same with CBQ of you want. You need to patch the kernel
before you can use the HTB qdisc.
Stef
--
stef.coene@docum.org
More QOS info : http://www.docum.org/
Title : "Using Linux as bandwidth manager"
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-03-07 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 1:08 [LARTC] Simple Beginner Question - allocating 64k Carl Spies
2002-03-07 1:43 ` Carl Spies
2002-03-07 1:44 ` Greg Scott
2002-03-07 7:49 ` Stef Coene [this message]
2002-03-07 8:05 ` eth
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-101548743910073@msgid-missing \
--to=stef.coene@docum.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.