From: Michal Soltys <nozo@ziu.info>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: vlan interfaces and tc
Date: Mon, 11 Jun 2007 12:34:47 +0000 [thread overview]
Message-ID: <466D4167.4010101@ziu.info> (raw)
In-Reply-To: <1181561487.5881.36.camel@benve-laptop>
Christian Benvenuti wrote:
> Hi,
>
> [cut]
>
> Yes they are both allowed.
> This means, for example, that the traffic that originates from
> or that is addressed to a VLAN interface can potentially go through
> two independent QoS configurations.
> Depending on what you want to achieve, you may configure QoS
> only on the VLAN interface, only on the real interface, or
> on both.
>
> [cut]
>
Thanks for the answers. I've made some simple tests and there seems to
be one thing that doesn't work on virtual interfaces - classifying.
Whenever I used filters - u32, or fw paired with iptables' mark target,
or simply classify target - it was completely ignored on vlan interface,
while the same setup on real interface worked fine (if it wasn't going
through vlan earlier - look question below). So maybe queuing, despite
it's possible to set on vlan, shouldn't be used ? (it's weird a bit,
especially if someone wanted to have both disciplines at the same time).
One more question though - I've noticed that marks or direct classify
don't survive going through vlan interface (seems logical), so I can't
use them later on the real one. In the past someone asked it on the
list, and the answer was to use negative offsets with u32 filter,
looking for vlan tags in layer 2 header. It seems to work fine, but is
it actually safe to use ?
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-06-11 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 11:31 [LARTC] Re: vlan interfaces and tc Christian Benvenuti
2007-06-11 12:34 ` Michal Soltys [this message]
2007-06-11 16:39 ` Christian Benvenuti
2007-06-11 20:11 ` Michal Soltys
2007-06-11 20:40 ` Christian Benvenuti
2007-06-12 5:10 ` Stephen Hemminger
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=466D4167.4010101@ziu.info \
--to=nozo@ziu.info \
--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.