Re: [LARTC] Configuration of CBQ

["Awie" <awie@eksadata.com>]

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

Stef,

Thanks for your advise, it should be a better idea than mine.

Anyway, how can I make that config? Here I attach my config, but I think it
is still not a correct one.

Thx & Rgds,

Awie

----- Original Message -----
From: "Stef Coene" <stef.coene@docum.org>
To: "Awie" <awie@eksadata.com>; <lartc@mailman.ds9a.nl>
Sent: Sunday, April 27, 2003 11:25 PM
Subject: Re: [LARTC] Configuration of CBQ


> On Sunday 27 April 2003 16:52, Awie wrote:
> > All,
> >
> > I plan to config my network by using CBQ (Attached the configuration
> > files). I want to do a packet prioritization instead traffic shaping
> > (perhaps in the future I will need it).
> >
> > The result that I want :
> >
> > 1. HTTP gets the 1st priority
> > 2. SMTP and some other packet get the 2nd
> > 3. FTP gets the 3rd
> >
> > Should I configure the "priority default"? (I did it in Cisco router,
last
> > time)
> >
> > Your answer is very appreciated. Many thanks for your help.
> What do you mean with priority??  Do you mean that all HTTP traffic should
be
> send first?  If you do, then you a big download can kill all FTP or SMTP
> traffic.  To prevent this, you have to shape the traffic.
>
> Isn't it better to say that http can always use at least 60% of the link?
If
> there is no other traffic, HTTP can use 100%.  Ftp can use 100% traffic,
but
> of there is other traffic, it will fal back to 10.
>
> So something like this:
> HTTP : 60 %
> SMTP : 30 %
> FTP : 10 %
>
> Traffic that can use a higher priority is real-time traffic like telnet,
ssh
> or traffic that needs low delays like ACK.
>
> Stef
>
> --
>
> stef.coene@docum.org
>  "Using Linux as bandwidth manager"
>      http://www.docum.org/
>      #lartc @ irc.oftc.net
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>

[-- Attachment #2: cbq-4.ftp --]
[-- Type: application/octet-stream, Size: 94 bytes --]

DEVICE=eth0
RATE=100Kbit
WEIGHT=10Kbit
PRIO=7
RULE=:20,192.168.1.0/24
RULE=:21,192.168.1.0/24

[-- Attachment #3: cbq-3.misc --]
[-- Type: application/octet-stream, Size: 1112 bytes --]


DEVICE=eth0
RATE=100Kbit
WEIGHT=10Kbit
PRIO=6

#Windows Media Player.
RULE=:1755,192.168.1.0/24

#SMTP
RULE=:25,192.168.1.0/24

#Real Player uses TCP port 554, for UDP it uses different ports,
#but generally RealAudio in UDP doesn't consume much bandwidth.
RULE=:554,192.168.1.0/24
RULE=:7070,192.169.1.0/24

#Napster uses ports 6699 and 6700, maybe some other?
RULE=:6699,192.168.1.0/24
RULE=:6700,192.168.1.0/24

#Audiogalaxy uses ports from 41000 to as high as probably 41900,
#there are many of them, so keep in mind I didn't list all of
#them here. Repeating 900 nearly the same lines would be of course
#pointless. We will simply cut out ports 410031-41900 using
#ipchains or iptables.
RULE=:41000,192.168.1.0/24
RULE=:41001,192.168.1.0/24

#continue from 41001 to 41030
RULE=:41030,192.168.1.0/24

#Some clever users can connect to SOCKS servers when using Napster,
#Audiogalaxy etc.; it's also a good idea to do so
#when you run your own SOCKS proxy
RULE=:1080,192.168.1.0/24

#Add any other ports you want; you can easily check and track
#ports that programs use with IPTraf
#RULE=:port,192.168.1.0/24

[-- Attachment #4: cbq-2.eth0 --]
[-- Type: application/octet-stream, Size: 83 bytes --]


DEVICE=eth0,100Mbit,10Mbit
RATE=100Kbit
WEIGHT=10Kbit
PRIO=5
RULE=192.168.1.0/24