All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Soltys <soltys@ziu.info>
To: Leonardo Uzcudun <uzcudunl@yahoo.it>
Cc: yao zhao <yao.development@gmail.com>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: VLAN 1 - Native
Date: Wed, 01 Feb 2012 20:26:53 +0100	[thread overview]
Message-ID: <4F2991FD.8090407@ziu.info> (raw)
In-Reply-To: <1328114680.76107.YahooMailNeo@web29019.mail.ird.yahoo.com>

On 12-02-01 17:44, Leonardo Uzcudun wrote:
> I'm sorry guys but i'm not understanding. Allow me to ask in a different way.
>
> I've a linux computer with 3 network cards (eth0, eth1 and eth2)
>
> eth0 is connected to a switch with vlans config.
> eth1 is connected to a network that has VID 1
> eth2 is connected to a network that has VID 101
>

Assuming you have:

eth0: 1u 101t
eth1: 1u
eth2: 101u

would this work for you ?:

ip link add link eth0 name eth0.101 type vlan id 101
ebtables -t broute -A BROUTING -i eth0 --vlan-id 101 -j DROP
brctl addbr br_vlan_1
brctl addbr br_vlan_101
brctl addif br_vlan_1 eth0 eth1
brctl addif br_vlan_101 eth0.101 eth2

ebtables should make 101 tagged traffic go through br_vlan_101 instead 
of br_vlan_1

I think there's also option for doing it with single bridge interface 
and some more complex ebtables rules, but the above if I didn't miss 
anything, should work fine.

  parent reply	other threads:[~2012-02-01 19:26 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 [this message]
2012-02-02  9:09                 ` Leonardo Uzcudun
2012-02-02  9:12                   ` Eric Dumazet
2012-02-02 12:17                     ` Michal Soltys
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=4F2991FD.8090407@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.