[LARTC] linux newbie

2004-08-31 Thread arya sby
hi all,
i am newbie in linux, i would like to ask u about some manual or step-by-step website about htb or others bandwidth manager, thanx before it
		Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!

[LARTC] Citrix and QoS

2004-08-31 Thread rsenykoff

Thanks to all the content from the archives
and the HOWTO, I've got a QoS bridge running, based off the Dante script
http://www.compsci.lyon.edu/mcritch/dante/  --> http://www.compsci.lyon.edu/mcritch/dante/shape.sh.eth0

While we are experiencing a marked improvement
in Citrix consistency, I still feel there is room for improvement. Citrix
sends a LOT of small packets. It is basically a very thin stream. The only
thing I can really see benefitting us more would be to break up large packets
so that Citrix packets don't wait for large packets to complete sending.
 We also run H323, and QoS has helped immensely in eliminating dropped
packets and interference between H323 and the more important (lower priority)
Citrix class.

Would lowering the MTU size be safe
in order to force packets to be fragmented? What kind of negative impacts
should I expect / look for with this? I'm not sure what the packet size
our H323 units use... I guess I could use Ethereal to check it out. May
depend on settings as well.

Any comments appreciated.

Thanks!

[LARTC] limiting the bandwidth for *each* ip in some class

2004-08-31 Thread firestarter
hello all, i got my htb running and controlling my
bandwidth right, but i have a doubt.

i configured HTB to limit my class 192.168.0.0/24 to
128kbit. but i want 128kbit for *each* machine on this
class, and not for the entire class. when 2 machines
in 192.168.0.0/24 are downloading one file, they share
the 128kbit bandwidth between them, using 64kbit for
each. why i can get all machine on this class using
128kbit without share this link?

thanks 





___
Yahoo! Acesso Grátis - navegue de graça com conexão de qualidade! 
http://br.acesso.yahoo.com/
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


Re: [LARTC] netem usage example

2004-08-31 Thread Stephen Hemminger
On Tue, 31 Aug 2004 17:49:06 +0200
[EMAIL PROTECTED] wrote:

> I'm trying to setup a netem delay with no luck (using iproute2-2.6.8,
> compilation broke during arpd compile, so I use the
> tc binary in the tc/ subdir, there's also a q_netem.so there).

Just take arpd out of the Makfile if you don't need it.

> kernel is 2.6.8.1, compile with CPU cycle counter as time reference.
> I was using sch_delay of 2.6.7 happily with something like:
> tc qdisc add dev eth0 root 1: delay latency 1ms rate 35M
> now I use:
> tc qdisc add dev eth0 root netem latency 1ms
> and it complain about "unknown qdisc netem"

Netem is built as separate shared library, it expects to
be in /usr/lib/tc/q_netem.so

> 
> do you have usage example with the new netem "scheduler"?

See new website:
http://developer.osdl.org/shemminger/netem
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


[LARTC] WRR problem and other things

2004-08-31 Thread Paweł Staszewski



Hello 
 
 
I have problem with wrr and more than 1300 
classes
when i try to add qdisc like:
 
tc qdisc add dev imq1 parent 1:21 handle 1000: wrr 
dest ip 1512 0
 
then i have a message like:
RTNETLINK answers: Cannot allocate 
memory
 
And some other problem:
When I do more than 2048 filters I have message 
like:
 
 
Classes:
tc class add dev imq1 parent 1:1 classid 
1:9 htb rate 1024kbit ceil 2048kbit
..
tc class add dev imq1 parent 1:1 classid 
1:10 htb rate 1024kbit ceil 2048kbit
...
...
...

tc class add dev imq1 parent 1:1 classid 
1:2048 htb rate 1024kbit ceil 2048kbit
tc class add dev imq1 parent 1:1 classid 1:2049 htb rate 1024kbit ceil 
2048kbit
tc class add dev imq1 parent 1:1 classid 1:2050 htb rate 1024kbit ceil 
2048kbit
 
 
Filters:
tc filter add dev imq1 parent 1:0 protocol ip prio 2 u32 match ip 
dst 1.1.1.1 flowid 1:9
..
tc filter add dev imq1 parent 1:0 protocol ip prio 2 u32 match ip 
dst 1.1.1.1 flowid 1:10
...
...
...
tc filter add dev imq1 parent 1:0 protocol ip prio 2 u32 match ip 
dst 1.1.1.1 flowid 1:2048
RTNETLINK answers: File exist
tc filter add dev imq1 parent 1:0 protocol ip prio 
2 u32 match ip dst 1.1.1.1 flowid 1:2049
RTNETLINK answers: File exist

tc filter add dev imq1 parent 1:0 protocol ip prio 
2 u32 match ip dst 1.1.1.1 flowid 1:2050
RTNETLINK answers: File exist
 
So classes are added corectly but filters not. WHY  
 
Please help me
 
Regards
Paweł Staszewski


[LARTC] Finally: A working case of two adsl load balance

2004-08-31 Thread favero
First of all i wanna thanks Christoph Simon for the support. 
Only after his reply to my email i could see the real solution to 
the problem (Valeu mesmo cara... me ajudou pra caramba! 
Fico te devendo essa!) :) 
Here is what i learned in a month of research: 
I tried A LOT of things to do load balance, including the one at 
LARTC homepage. The only tutorial that REALLY works in my 
case is the Christoph Simon at http://www.ssi.bg/~ja/nano.txt 
Maybe LARTC can replace the erroneous tutorial at 
http://lartc.org/howto/lartc.rpdb.multiple-links.html with the 
nano.txt. 
I will not write a tutorial, first of all cause my english is very 
bad. Second because the nano.txt tutorial can do the trick. I 
will just give some hints i used here. 
First of all the load balance DOESN´T work without the Julian 
Anastasov route patch. You can get it at: 
http://www.ssi.bg/~ja/#routes So don´t be lazy, get the kernel 
source code, aplly the patch and compile the kernel. 
Pay attention to your nat configuration. In the first attempt I 
had problems cause i forgot to mask the nated ips on the 
postrouting table (this command is the last on my example 
below). 
I used the ip adress of the external interface, not the mask 
for the external network (nano.txt tutorial gives the 2 
options...) 
Be sure that you don´t have a default route on your main 
table. If u have any, delete it! 

I have a linux box with: 
- Kernel 2.6.3 with Julian Anastasov patch to kernel 2.6.0-
2.6.3 http://www.ssi.bg/~ja/routes-2.6.0-test11-10.diff 
- iproute2-ss010824 
- 4 ethernet cards: 
eth0 - internal lan ip range 192.168.1.x 
eth1 - internal lan ip range 192.168.2.x 
eth2 (ppp0) - external adsl with 600 Kb/sec down and 300 
Kb/sec up 
eth3 (ppp1) - external adsl with 600 Kb/sec down and 300 
Kb/sec up 
I have nat and my 2 lan access the internet using the linux 
box as gateway. 
I run 2 rp-pppoe daemon, one for each adsl connection. 
ppp0 ip: 200.101.233.120 
ppp0 gateway: 200.138.225.254 
ppp1 ip: 201.3.219.70 
ppp1 gateway: 201.3.196.254 

Here is the commands i use: 

#table main with priority 50, the highest one 
ip rule add prio 50 table main
#table 201 
ip rule add prio 201 from 201.3.219.70 table 201
ip route add default via 201.3.196.254 dev ppp1 src 
201.3.219.70 proto static table 201
ip route append prohibit default table 201 metric 1 proto static
#table 202 
ip rule add prio 202 from 200.101.233.120 table 202
ip route add default via 200.138.225.254 dev ppp0 src 
200.101.233.120 proto static table 202
ip route append prohibit default table 202 metric 1 proto static
#table 222 
ip rule add prio 222 table 222
ip route add default table 222 proto static nexthop via 
201.3.196.254 dev ppp1 nexthop via 200.138.225.254 dev 
ppp0
#essential masquerade option 
iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -j 
MASQUERADE 
iptables -t nat -A POSTROUTING -s 192.168.2.0/24 -j 
MASQUERADE 

Here is the route output: 

[EMAIL PROTECTED] root]# route
Tabela de Roteamento IP do Kernel
Destino Roteador MáscaraGen. Opções Métrica Ref Uso Iface
200.138.225.254 * 255.255.255.255 UH 0 0 0 ppp0
201.3.196.254 * 255.255.255.255 UH 0 0 0 ppp1
192.168.2.0 * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo

Here is the ip route list output for the 4 tables (main, 201, 
202, 222): 

[EMAIL PROTECTED] root]# ip route list table main
200.138.225.254 dev ppp0 proto kernel scope link src 
200.101.233.120
201.3.196.254 dev ppp1 proto kernel scope link src 
201.3.219.70
192.168.2.0/24 dev eth1 scope link
192.168.1.0/24 dev eth0 scope link
127.0.0.0/8 dev lo scope link
[EMAIL PROTECTED] root]# ip route list table 201
default via 201.3.196.254 dev ppp1 proto static src 
201.3.219.70
prohibit default proto static metric 1
[EMAIL PROTECTED] root]# ip route list table 202
default via 200.138.225.254 dev ppp0 proto static src 
200.101.233.120
prohibit default proto static metric 1
[EMAIL PROTECTED] root]# ip route list table 222
default proto static
nexthop via 200.138.225.254 dev ppp0 weight 1
nexthop via 201.3.196.254 dev ppp1 weight 1

And that´s all! I have a working and very well balanced 
system. I´m getting combined download speed of 120 Kb/sec 
running multiple simultaneous downloads (p2p, html, ftp, etc), 
40 kb/sec simultaneous upload speed. I can play online 
games without problems. MSN/ICQ remains connected all the 
time using the same ip address. No packet loss problems.The 
two 600/300 lines really looks very similar to a 1200/600 line. 
It´s really wonderful. 
I hope this can help someone. The load balance isn´t so hard 
to do when you know which commands you really need. I did 
it, why can´t you do it too? :) 
Fernando Favero 
[EMAIL PROTECTED]
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


[LARTC] netem usage example

2004-08-31 Thread philippe . strauss
I'm trying to setup a netem delay with no luck (using iproute2-2.6.8,
compilation broke during arpd compile, so I use the
tc binary in the tc/ subdir, there's also a q_netem.so there).
kernel is 2.6.8.1, compile with CPU cycle counter as time reference.
I was using sch_delay of 2.6.7 happily with something like:
tc qdisc add dev eth0 root 1: delay latency 1ms rate 35M
now I use:
tc qdisc add dev eth0 root netem latency 1ms
and it complain about "unknown qdisc netem"

do you have usage example with the new netem "scheduler"?

thanks
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


Re: [LARTC] RE: [LARTC] Load Balance simply doesn´t work...

2004-08-31 Thread JasonB
Hello, 

>From the looks of it you have the IP Network incorrect, You need to set
this to your Network... for example .. 

ip route add 23.215.4.0/26 dev eth2 src 23.215.4.61 table T2

23.215.4.0 is the network address, because 23.215.4.1 is my gateway for
this interface (Router). If you still have a hard time with it .. You
can post your Netmask and GW and I should be able to figure it out for
you. There may be a way to do it from your IP address, but I had
subnetting and aren't very good at it :) 



ip route add 212.71.142.210/29 dev eth1 src 212.71.142.210 table 10

On Tue, 2004-08-31 at 11:02, Marc-Christian Petersen wrote:
> On Thursday 26 August 2004 15:06, Marcos Schonfeld wrote:
> 
> Hi Marcos,
> 
> > ip route add $P1_NET dev $IF1 src $IP1 table 10
> > ip route add default via $P1 table 10
> > ip route add $P2_NET dev $IF2 src $IP2 table 20
> > ip route add default via $P2 table 20
> >
> > ip route add $P1_NET dev $IF1 src $IP1  # This may be not necessary
> > ip route add $P2_NET dev $IF2 src $IP2  # This may be not necessary
> >
> > ## ip route add default via $P1  ## You don't have to set this default
> > gw, because you'll be routing accross this gateway instead of doing
> > load-balance
> >
> > ip rule add from $IP1 table T1
> > ip rule add from $IP2 table T2
> 
> shouldn't this be table 10 and table 20? :)
> 
> anyway, I have a problem settings this up. I get:
> 
> 
> ip route add 212.71.142.210/29 dev eth1 src 212.71.142.210 table 10
> RTNETLINK answers: Invalid argument
> 
> ip route add default via 212.71.142.209 table 10
> ip route add 61.212.57.152/29 dev eth2 src 61.212.57.152 table 20
> ip route add default via 61.212.57.153 table 20
> 
> ip route add 212.71.142.210/29 dev eth1 src 212.71.142.210
> RTNETLINK answers: Invalid argument
> 
> ip route add 61.212.57.152/29 dev eth2 src 61.212.57.152
> RTNETLINK answers: File exists
> 
> ip rule add from 212.71.142.210 table 10
> ip rule add from 61.212.57.152 table 20
> 
> strace from 1st RTNETLINK invalid argument:
> 
> 
> controllen=0, msg_flags=0}, 0) = 36
> dup(2)  = 4
> fcntl64(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
> fstat64(4, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
> 0x4b3ed000
> _llseek(4, 0, 0xb8526df0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
> write(4, "RTNETLINK answers: Invalid argum"..., 36) = 36
> close(4)= 0
> munmap(0x4b3ed000, 4096)= 0
> brk(0)
> 
> any idea what I am doing wrong?
> 
> Thanks alot.

___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


Re: [LARTC] RE: [LARTC] Load Balance simply doesn´t work...

2004-08-31 Thread Marc-Christian Petersen
On Tuesday 31 August 2004 17:02, Marc-Christian Petersen wrote:


> ip route add 212.71.142.210/29 dev eth1 src 212.71.142.210 table 10
> RTNETLINK answers: Invalid argument

blubber bleh silly me. I implemented ipcalc.pl in my brain now ;)

-- 
ciao, Marc
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


Re: [LARTC] RE: [LARTC] Load Balance simply doesn´t work...

2004-08-31 Thread Marc-Christian Petersen
On Thursday 26 August 2004 15:06, Marcos Schonfeld wrote:

Hi Marcos,

> ip route add $P1_NET dev $IF1 src $IP1 table 10
> ip route add default via $P1 table 10
> ip route add $P2_NET dev $IF2 src $IP2 table 20
> ip route add default via $P2 table 20
>
> ip route add $P1_NET dev $IF1 src $IP1  # This may be not necessary
> ip route add $P2_NET dev $IF2 src $IP2  # This may be not necessary
>
> ## ip route add default via $P1  ## You don't have to set this default
> gw, because you'll be routing accross this gateway instead of doing
> load-balance
>
> ip rule add from $IP1 table T1
> ip rule add from $IP2 table T2

shouldn't this be table 10 and table 20? :)

anyway, I have a problem settings this up. I get:


ip route add 212.71.142.210/29 dev eth1 src 212.71.142.210 table 10
RTNETLINK answers: Invalid argument

ip route add default via 212.71.142.209 table 10
ip route add 61.212.57.152/29 dev eth2 src 61.212.57.152 table 20
ip route add default via 61.212.57.153 table 20

ip route add 212.71.142.210/29 dev eth1 src 212.71.142.210
RTNETLINK answers: Invalid argument

ip route add 61.212.57.152/29 dev eth2 src 61.212.57.152
RTNETLINK answers: File exists

ip rule add from 212.71.142.210 table 10
ip rule add from 61.212.57.152 table 20

strace from 1st RTNETLINK invalid argument:


controllen=0, msg_flags=0}, 0) = 36
dup(2)  = 4
fcntl64(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat64(4, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x4b3ed000
_llseek(4, 0, 0xb8526df0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(4, "RTNETLINK answers: Invalid argum"..., 36) = 36
close(4)= 0
munmap(0x4b3ed000, 4096)= 0
brk(0)

any idea what I am doing wrong?

Thanks alot.

-- 
ciao, Marc

___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


[LARTC] ANNOUNCE: Linux QoS Library (LQL) 0.5.0

2004-08-31 Thread Dan Siemon
The Linux QoS Library (LQL) provides a GPL licensed, GObject based C API
to manipulate the network queueing disciplines, classes and classifiers
in the Linux kernel. LQL does not use the TC command as a back-end.
Instead, LQL communicates with the Linux kernel via Netlink sockets the
same way TC does.

0.5.0   2004-08-30
-
* Initial public release.
* I wanted to get 100% API doc coverage and a lot more testing
  done before I made a public release but I decided to go with
  the release early, release often strategy.
* 86% API documentation coverage. A lot of the undocumented API is
  for the U32 classifier implementation which I am not that fond of. I
  think this API will change quite a bit.
* What LQL really needs is much more testing in larger applications.
* I make absolutely no promises that any of the API will be stable. I
  expect the API to change as larger programs are built with it and
  new limitations (and bugs) are found.

Please see http://www.coverfire.com/lql/ for more information.

Download:
http://www.coverfire.com/lql/download/lql-0.5.0.tar.gz

-- 
OpenPGP key: http://www.coverfire.com/files/pubkey.txt
Key fingerprint: FB0A 2D8A A1E9 11B6 6CA3  0C53 742A 9EA8 891C BD98

___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/