All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Bonser <george@thebackrow.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] I know there must be a way ...
Date: Wed, 12 Dec 2001 20:10:49 +0000	[thread overview]
Message-ID: <marc-lartc-100818790803816@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100810869803719@msgid-missing>

> Ok - I missed this. So we have this
>                                                        A
>                                                      /
>   [ your network ]  - [ linux machine ] - [ router ]
>                                                      \

Or possibly this:                       A
                                      /
    [ my network ] - [ linux machine ]
                                      \
                                        B

> The Linux machine also has a full view and knows where traffic will go.
>
> But the router does its own routing?

I currently do not have a linux box in the path. I have two GigE links to
Provider-A and a GigE link to provider-B.  Each GigE terminates on an
Extreme Summit 1i layer 2/3 switch. What I currently do is have each of
these units peer with internal BGP to a linux box running Zebra. I use it
to set the policies and aggregate everything into one single routing table
that I pass to a router just outside the firewall.  The effect there is
to provide that router with the best next hop for traffic so it goes to
the  router associated with the egress link without having to peer with
all  three of the routers. The linux box acts as a route server but is not
in the traffic path.

But enough of that ...

What I really need is a different kind of policing filter. Rather than one
that sets a maximum bandwidth, I need one where I can set a MINIMUM
bandwidth and something that will pull traffic from another queue to keep
it at that minumim

OR

A filter that can query ANOTHER queue's rate monitor and reclassify
traffic into that queue whenever the target queue's traffic rate is below
some configurable number.

It is probably going to involve writing something new. I really do not see
a way to do it yet with the pieces I see.  I am going to do some more
reading over the weekend and see what I can come up with before I start
hacking on stuff, I really hate reinventing wheels.



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

      parent reply	other threads:[~2001-12-12 20:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 22:10 [LARTC] I know there must be a way George Bonser
2001-12-11 23:00 ` bert hubert
2001-12-11 23:19 ` bert hubert
2001-12-12 20:10 ` George Bonser [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=marc-lartc-100818790803816@msgid-missing \
    --to=george@thebackrow.net \
    --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.