All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Egress shaping over multiple interfaces?
Date: Thu, 31 Oct 2002 16:06:08 +0000	[thread overview]
Message-ID: <marc-lartc-103608045422285@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103607410914000@msgid-missing>

On Thursday 31 October 2002 15:20, Martijn Klingens wrote:
> Hello,
>
> After reading the excellent HOWTO I got traffic shaping working nicely over
> ethernet devices on a test setup. I can't put this setup live though,
> because our main firewall has three 2mbit hdlc interfaces instead of a
> single device.
>
> We are using multipath routing using iproute2 nexthop at the moment, and
> that works fine for firewalling. But now I have a need for shaping and
> shaping only works over a single interface it seems and not over multiple
> interfaces.
Yes you can if you apply the needed patches to the kernel and iptables so you 
can use the imq device.  It's a virtual device and you can use the normal 
cbq/htb/tbf qdiscs on it.  You can redirect packets to it with iptables and 
you can do it from any interface you want and also from IN + OUT.  So you can 
create 1 imq device, redirect all packets that leaves hdlc0-2 and shape on 
that imq device.
IMQ link :
http://trash.net/~kaber/imq

> According to the HOWTO I can setup a teql device to bundle the hdlc0-2 into
> a single teql0 device, but that requires an extra combined IP address at
> both sides it seems.
The teql can only be used if you have a linux on both sides of the 2 links.

> The question is whether I can get away with setting up the teql device over
> the three hdlc IPs with an ip on the teql device that's either fake or one
> of our class C subnet (maybe even reuse the IP of the ethernet card on the
> other end), without having our provider to change their config.
>
> The round robin routing is not the problem, we have that working correctly
> for quite a while already, it's the fact that teql requires an extra IP
> which nexthop routing doesn't that bothers me a bit. And since this is a
> live router I am not going to take risks by messing with it without proper
> research...
>
> Is there any advice to give me here? Or do you need more information first?

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/

  reply	other threads:[~2002-10-31 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 14:20 [LARTC] Egress shaping over multiple interfaces? Martijn Klingens
2002-10-31 16:06 ` Stef Coene [this message]
2002-10-31 16:33 ` Martijn Klingens
2002-10-31 17:00 ` Stef Coene
2002-10-31 17:45 ` Hasso Tepper

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-103608045422285@msgid-missing \
    --to=stef.coene@docum.org \
    --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.