LARTC - May 2004 - RV: RV: LATENCY PROBLEMS

I thought of creating an htb class for each user, but as you said I
haven''t
got enough bw to do soo.

That’s why my setup only has 5 classes with WRR queues so I get sure each
user doesn’t affects the other users. On top of that I have an iplimit to a
maximum of 15 parallel connections per user.

So I get the following conclusions:
	A) change link
	B) upgrade to kernel 2.6 and use l7 filtering

Eventhough.. anyone suggesting alternative solutions?


-----Mensaje original-----
De: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] En
nombre de Andreas Klauer
Enviado el: sábado, 15 de mayo de 2004 1:54
Para: lartc@mailman.ds9a.nl
Asunto: Re: [LARTC] RV: LATENCY PROBLEMS

Am Friday 14 May 2004 23:59 schrieb Jason Boxman:
> > Anyway - even if I weren''t using IPP2P, P2P traffic
wouldn''t really
> > matter since I put all traffic into user classes. So the only person
> > who''s suffering would be the P2P user. And I don''t
really care about
> > that. ;-)
>
> Interesting.  How did you accomplish that?
It''s nothing special. Each user gets his/her own HTB class. No matter
what
kind of traffic the user generates (Interactive, P2P, ...), it
shouldn''t
affect the other users. This works well in small networks. It wouldn''t 
work well if I had to create 500 classes for a ADSL line, because the 
guaranteed rates per user would be too low.
> So right now each user is getting a prio disc?
It looks like this:
http://www.metamorpher.de/files/fairnat_ipp2p.png
(warning, big image: ~5000x2000 pixels)
Blue = qdisc, Green = class; Blue arrow = filter.

Please note that 1:3 is a class for local LAN traffic. 
The other are user classes.

Every user gets a prio qdisc with 4 bands (4th band for P2P, everything 
else gets classified by the TOS priomap). The prio leafs get SFQ on top.
Don''t know if that actually makes sense, but it works well for me.

Andreas
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

GoMi wrote:
>I thought of creating an htb class for each user, but as you said I
haven''t
>got enough bw to do soo.
>
>That’s why my setup only has 5 classes with WRR queues so I get sure each
>user doesn’t affects the other users. On top of that I have an iplimit to a
>maximum of 15 parallel connections per user.
>
>So I get the following conclusions:
>	A) change link
>	B) upgrade to kernel 2.6 and use l7 filtering
>
>Eventhough.. anyone suggesting alternative solutions?
>  
>

At risk of sounding blunt. What''s your problem? Can you not do some 
monitoring on the router and find out exactly what is happening?

Try looking at your bandwidth usage. For example, throttle bandwidth 
right back, and then look at the actual line usage - if it''s maxing out
then you know that for some reason the throttling is being defeated. 
Consider whether it''s incoming or outgoing that is maxing out (you know
that incoming is harder to throttle).

Also, since it''s an adsl connection the overhead calculations for the 
line are significantly out, especially if you have many small packets on 
your network. It could be that the ATM overhead is eating up bandwidth? 
Try the patch suggested a few days ago?

I think if you can find out what is happening then it would be easier to 
design a fix?

Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/