From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: shaping vlans - revisited
Date: Thu, 03 Feb 2011 21:42:59 -0600 [thread overview]
Message-ID: <4D4B75C3.2060007@riverviewtech.net> (raw)
In-Reply-To: <20110203180118.62970fb1@pulsar.inexo.com.br>
On 2/3/2011 2:01 PM, Ethy H. Brito wrote:
> One extra detail is: this setup was working (just as it is for eth0)
> until two weeks ago when then we created the vlans and splited the
> traffic among them.
Once the traffic is in side of a VLAN tag (on the raw device), filters
will not match the traffic the say way that it did. - Try applying
your filters to the VLAN sub-interface.
This is because the traffic is no longer IP traffic in side of Ethernet
SNAP frames, but rather VLAN tagged frames that contain Ethernet SNAP
frames.
Are you wanting to give one VLAN on a given raw interface more priority
than another?
Grant. . . .
next prev parent reply other threads:[~2011-02-04 3:42 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
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 [this message]
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=4D4B75C3.2060007@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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 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.