Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] packet shaping bridge
Date: Mon, 09 May 2005 22:26:14 +0000	[thread overview]
Message-ID: <427FE386.5050308@dsl.pipex.com> (raw)
In-Reply-To: <427A4932.7000002@ckua.org>

Jason Bath wrote:
> Thanks!  Adding the filter to the root was the trick.  From the various 
> documentation I was reading I had the impression that the filter needed 
> to be added to the sub-classes - 1:1 and so forth.  I presume that's 
> only appropriate when you have leaves below 1:1.
> 
> Anyhow, the trick now is figuring out how I want to configure things 
> with two of these bridges in mind.  The topology would look like this:
> 
> Switch-bridge/filter-WAN router--Remote WAN router-bridge-remote switch
> 
> Now with 1.5Mbit/s with the potential for 2mbit/s I was thinking of 
> limiting each bridge at 1Mbit/s. I didn't want to limit at 750kbit/s 
> because if you're doing a big file transfer, you're going to suffer and 
> besides, the ratio of download to upload is in favour of the download 
> The streaming audio devices are set up for 128kbit/s MPEG-layer3.  So 
> we're looking at dedicating a minimum of 150kbit/s which can double or 
> more if I'm having congestion problems.
> 
> Now here's an interesting idea.  Let me know if it's possible or not. Is 
> it possible for me to create a bridge between the two linux boxes so it 
> physically looks like
> 
> eth0 eth1 --WAN--  eth1 eth0
> 
> but virtually you are going
> 
> eth0 ------- eth0
> 
> The reason I ask this is so I can create an awareness between the two 
> bridges as to how much traffic is actually going through the pipe so I 
> may optimize it to its fullest.
> 
> I suppose that it could be done via snmp or spanning-tree?

I don't know if that will work - if you can shape on both ends just do 
egress shaping on the WAN facing interfaces. You'll need to back off a 
bit to allow for link overheads, but it will be alot nicer than doing it 
all from one end.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2005-05-09 22:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 16:26 [LARTC] packet shaping bridge Jason Bath
2005-05-05 21:58 ` Jason Bath
2005-05-05 22:20 ` Andreas Klauer
2005-05-05 22:51 ` Andy Furniss
2005-05-06 17:49 ` Jason Bath
2005-05-09 22:26 ` Andy Furniss [this message]

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=427FE386.5050308@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox