Re: ebtables and IMQ

me athome <any_junk-/[email protected]>
Newsgroups gmane.linux.network.bridge.ebtables.devel
Message-ID <[email protected]>
Nick,

First let me say that iptables works for me but it
also works for other scenarios where you can now use
either ebtalbes or iptables.

The reason I think ebtables should be used is that I
don’t use any IP.
I have several Ethernet bridges which I rate limit to
a specific bandwidth. I don’t care about any IP since
I limit based on input interfaces (VLANs in my case);
the key is that I rate limit more than one interface
to a specific rate. As you know TC will only work on
one interface so if I want to aggregate more than one
such that for example eth0.500+eth0.501+eth0.502
ingress rate limited to 1Mbps I need to use iptables
to redirect these interfaces to imq0 and do the TC on
imq0. Since there is not IP involved and it is based
purely on the bridge/interface I think ebtables would
make more sense.

Ron.



--- Nick Fedchik <[email protected]> wrote:
> Hello me athome,
> Monday, December 9, 2002, 20:47:26, you wrote:
> ma> Is anybody working on making IMQ a target in
> ebtables?
> IMHO - nobody.
> ma> IMQ (intermediate queuing device) is very useful
> for
> ma> traffic shaping
> (http://luxik.cdi.cz/~patrick/imq/).
> ma> I am using it now with iptables and bridge-nf
> but
> And it's all right?
> ma> it would make more sense to use ebtalbes...
> What the sense to use it in the ebtables?
> AFAIK it's depends on ip/tc utils usage,
> therefore it depends on IP, not on ethernet frames.
> 
> -- 
> Best regards,
> Nick Fedchik FNM3-RIPE  mailto:[email protected]
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.