All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adrian Ghioc" <adrian.ghioc@deltadr.ro>
To: lartc@vger.kernel.org
Subject: [LARTC] traffic control advice (imq or not)
Date: Sat, 12 Jul 2003 09:45:13 +0000	[thread overview]
Message-ID: <marc-lartc-105800342211720@msgid-missing> (raw)

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/

                 reply	other threads:[~2003-07-12  9:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-105800342211720@msgid-missing \
    --to=adrian.ghioc@deltadr.ro \
    --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.