From: Andrew Beverley <andy@andybev.com>
To: "Ethy H. Brito" <ethy.brito@inexo.com.br>
Cc: netfilter@vger.kernel.org
Subject: Re: shaping vlans - revisited
Date: Sat, 05 Feb 2011 02:10:24 +0000 [thread overview]
Message-ID: <1296871824.1616.14.camel@andybev> (raw)
In-Reply-To: <20110204142417.30dbe5fa@pulsar.inexo.com.br>
On Fri, 2011-02-04 at 14:24 -0200, Ethy H. Brito wrote:
> On Fri, 04 Feb 2011 14:24:05 +0000
> Andrew Beverley <andy@andybev.com> wrote:
>
> > On Fri, 2011-02-04 at 12:05 -0200, Ethy H. Brito wrote:
> > > On Fri, 04 Feb 2011 02:59:16 +0000
> > > Andrew Beverley <andy@andybev.com> wrote:
> > >
> > >
> > > > Stupid question - can you not just attach your qdisc to the vlan
> > > > interface and mark the traffic on the vlan interface as well, as if
> > > > it was eth1?
> > >
> > > You mean "tc qdisc add dev vlanX ..." + "iptables ... -j IPMARK ..." ??
> > >
> > > No. This must not be done. I have now 6 vlans (3 for IPv4 and 3 for
> > > IPv6) each pair to one ISP. The only way I know (if you guys know
> > > another way, please advise) to shape *_global_* aggregated traffic for
> > > each client is to attach to eth1 an not to individual vlans.
> > >
> >
> > Could you use an IFB device? Or possibly even IMQ?
>
> IFB??
>
> it may be a good way out.
> Do you know any discussion list or forum for it?
This list is probably a good place to start. There doesn't seem to be a
huge amount of information around for it, but I got a good response from
the author when I contacted him with a question a while back.
Andy
next prev parent reply other threads:[~2011-02-05 2:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 17:29 Fw: shaping vlans - revisited Ethy H. Brito
2011-02-03 18:50 ` Andrew Beverley
2011-02-03 20:01 ` Ethy H. Brito
2011-02-04 2:59 ` Andrew Beverley
2011-02-04 7:43 ` Marek Kierdelewicz
2011-02-04 14:05 ` Ethy H. Brito
2011-02-04 14:24 ` Andrew Beverley
2011-02-04 16:24 ` Ethy H. Brito
2011-02-05 2:10 ` Andrew Beverley [this message]
2011-02-05 12:46 ` Marek Kierdelewicz
2011-02-05 14:42 ` Ethy H. Brito
2011-02-05 14:52 ` Marek Kierdelewicz
2011-02-05 16:32 ` Ethy H. Brito
2011-02-05 16:41 ` Marek Kierdelewicz
2011-02-05 23:26 ` Ethy H. Brito
2011-02-04 3:28 ` Jan Engelhardt
2011-02-04 3:42 ` Grant Taylor
2011-02-04 14:06 ` Ethy H. Brito
2011-02-05 13:56 ` Ethy H. Brito
-- strict thread matches above, loose matches on Subject: below --
2011-02-03 15:38 Ethy H. Brito
2011-02-03 15:46 ` Marek Kierdelewicz
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=1296871824.1616.14.camel@andybev \
--to=andy@andybev.com \
--cc=ethy.brito@inexo.com.br \
--cc=netfilter@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