From: Michal Soltys <soltys@ziu.info>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Leonardo Uzcudun <uzcudunl@yahoo.it>,
yao zhao <yao.development@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: VLAN 1 - Native
Date: Thu, 02 Feb 2012 13:17:17 +0100 [thread overview]
Message-ID: <4F2A7ECD.2050909@ziu.info> (raw)
In-Reply-To: <1328173972.2279.1.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
On 02.02.2012 10:12, Eric Dumazet wrote:
> Le jeudi 02 février 2012 à 09:09 +0000, Leonardo Uzcudun a écrit :
>> Hello Michal:
>>
>> It is working on kernel 3.0.0-15 Ubuntu. I've just to modify the
>> ebtables command as:
>> ebtables -t broute -A BROUTING -i eth0 -p 802_1Q --vlan-id 101 -j DROP
>> (protocol is a must when you use --vlan-id)
>>
>>
>> I'll test it on kernel 2.6.32-5 Debian
>>
>>
>> Just last question,in the case i should implement this kind of
>> configuration in a kernel 2.6.31, should i backport/patch anything? is
>> it a bad idea (running it on 2.6.31)?
>
> This is going to be tough.
>
Btw, this (ebtables broute drop) method has been mentioned in bridge-nf
faq for ages (through most/all 2.6 kernels at least) - and for the very
purpose of directing tagged/not tagged traffic to proper bridge
interfaces. Shouldn't 2.6.31 be pretty safe in that regard ?
Or did you mean backporting/patching part ?
> The point of Jesse Gross (and others) work was exactly to permit better
> vlan/bridge integration/stacking.
>
Just to be sure - are those patches in any way changing / deprecating /
conflicting with ebtables approach ?
next prev parent reply other threads:[~2012-02-02 12:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1328095366.10975.YahooMailNeo@web29004.mail.ird.yahoo.com>
2012-02-01 11:24 ` VLAN 1 - Native Leonardo Uzcudun
2012-02-01 13:04 ` Eric Dumazet
[not found] ` <CADDf=MQ8EYEtOO2e5NJLrW0DKDz5xCBEBwuY6rxNu4Cybq=kKQ@mail.gmail.com>
2012-02-01 14:57 ` yao zhao
2012-02-01 15:05 ` Eric Dumazet
2012-02-01 15:14 ` Leonardo Uzcudun
2012-02-01 15:23 ` Eric Dumazet
2012-02-01 16:25 ` yao zhao
2012-02-01 16:44 ` Leonardo Uzcudun
2012-02-01 17:21 ` Eric Dumazet
2012-02-01 17:25 ` yao zhao
2012-02-01 18:14 ` Ben Hutchings
2012-02-01 20:52 ` yao zhao
2012-02-01 21:01 ` Eric Dumazet
2012-02-01 22:01 ` Leonardo Uzcudun
2012-02-01 19:26 ` Michal Soltys
2012-02-02 9:09 ` Leonardo Uzcudun
2012-02-02 9:12 ` Eric Dumazet
2012-02-02 12:17 ` Michal Soltys [this message]
2012-02-02 16:33 ` Jesse Gross
2012-02-02 12:10 ` Benny Amorsen
2012-02-02 12:53 ` Eric Dumazet
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=4F2A7ECD.2050909@ziu.info \
--to=soltys@ziu.info \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=uzcudunl@yahoo.it \
--cc=yao.development@gmail.com \
/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.