All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Smietanowski stefan@hanse.com
To: lartc@vger.kernel.org
Subject: [LARTC] Multiple interfaces?
Date: Mon, 08 Jan 2001 23:17:40 +0000	[thread overview]
Message-ID: <marc-lartc-98373940416840@msgid-missing> (raw)

<PRE>Hi!

Correct me if I'm wrong, but this works:

internet --- linux machine with iproute2 controlling bandwidth ---
machines behind it getting bandwidth controlled.

With &quot;control&quot; is limit/prioritization, etc.

&quot;---&quot; is a connection of some sort connected to the linux box.

That should work as it does here :)

Now, is it possible for &quot;---&quot; to be for example a 802.1q VLAN (using for
example Ben Greear's 802.1Q implementation)?

If so, cool, that's wanted.. :)

Now to the problem.

Let's look back to my not-so-complex example and make it slightly more
complex.

Is there ANY way to get THIS to work? :

internet --- linux w/ iproute2 --- one net
                        |
                        |
                        |
                  some other net

And handle bandwidth management between those 2 ports?

I've been looking and looking and I see no solution to it, due to that
the top qualifier discipline is on top of the interface and not on top
of &quot;top box&quot;.

Or am I reading it wrong?

Any suggestions?

Why I'd want that is actually to use VLAN 802.1Q to a capable switch so
that it really is just inet --linux--switch,
physically but the cable to the switch carries the various VLANS and
bandwidth manages them together as if they were the same interface on
the linux box, which they in a sence are but .. not.. :)

Hopefully this isn't too weird described. If you have questions what the
hell I mean, ask.

// Stefan


</PRE>

             reply	other threads:[~2001-01-08 23:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 23:17 Stefan [this message]
2001-01-09  8:27 ` [LARTC] Multiple interfaces? josdg

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-98373940416840@msgid-missing \
    --to=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.