All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] traffic control advice (imq or not)
@ 2003-07-12  9:45 Adrian Ghioc
  0 siblings, 0 replies; only message in thread
From: Adrian Ghioc @ 2003-07-12  9:45 UTC (permalink / raw)
  To: lartc

Hi,

I have a central router linked with GRE tunnels with some 20+ remote routers
in a star topology fashion.
If I want to prioritize some flows in/out those GRE interfaces, what would
you recommmend:

1: Throwing all the traffic on the Central Router to an IMQ

iptables -t mangle -A PREROUTING -j IMQ --todev 0

# The GRE interfaces won't share traffic (duhh)
# selecting incoming/outgoing traffic with tc filter based on - src/dst and
other for specific flows
#                                                                           
          - only src/dst for default

advantages: - only the central router kernel should be patched with imq and
recompiled & tc patched with htb, centralised administration
disadvantages - all traffic has to travel through 2 queues, which I heard is
a bad thing for VoIP (which I plan to use)...

2: Creating per interface egress queues on all routers

advantages: - smaller delays
disadvantages - all the routers should have tc patched for htb, and the
configs spread on all routers

P.S. Maybe there are things that slipped my mind ...

Thank you all for your time,

Adi

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-07-12  9:45 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-07-12  9:45 [LARTC] traffic control advice (imq or not) Adrian Ghioc

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.