Skip to contentSkip to conversation

Multiple interfaces?

LARTC Stefan Smietanowski [email protected] 2 participants 2 messages Jan 8, 2001 – Jan 9, 2001

lore
Share & tools
lore

Stefan Smietanowski [email protected]

author
#0 lore 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>

#1 lore raw

<PRE>On Tue, 9 Jan 2001, Stefan Smietanowski wrote:

&lt;snip&gt;
&gt;<i> Is there ANY way to get THIS to work? :
</I>&gt;<i>
</I>&gt;<i> internet --- linux w/ iproute2 --- one net

</I>&gt;<i>                         |
</I>&gt;<i>                         |
</I>&gt;<i>                         |

</I>&gt;<i> some other net
</I>&gt;<i>
</I>&gt;<i> And handle bandwidth management between those 2 ports? </I>&gt;<i>
</I>&gt;<i> I've been looking and looking and I see no solution to it, due to that </I>&gt;<i> the top qualifier discipline is on top of the interface and not on top </I>&gt;<i> of &quot;top box&quot;.
</I>&gt;<i>
</I>&gt;<i> Or am I reading it wrong?
</I>
I came to the same conclusion, i guess you are wright ...

&gt;<i> Any suggestions?
</I>
use the &quot;Ingress policer qdisc&quot; ?

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

I haven't done it yet myself, but i guess one should use the Ingress policer qdisc on the &quot;inet&quot; interface. Unfortunately he howto is not giving a lot of info on that issue.

Is there someone out there who has some experience with this ?

Greetings,
jos

</PRE>