From: Eric Dumazet <eric.dumazet@gmail.com>
To: Leonardo Uzcudun <uzcudunl@yahoo.it>
Cc: yao zhao <yao.development@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: VLAN 1 - Native
Date: Wed, 01 Feb 2012 18:21:21 +0100 [thread overview]
Message-ID: <1328116881.1882.14.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <1328114680.76107.YahooMailNeo@web29019.mail.ird.yahoo.com>
Le mercredi 01 février 2012 à 16:44 +0000, Leonardo Uzcudun a écrit :
> 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
>
> I've the following configuration:
>
> ip addr add 0.0.0.0 dev eth0
> ip link set eth0 up
> ip link add link eth0 name eth0.1 type vlan id 1
> ip link add link eth0 name eth0.101 type vlan id 101
> ip addr add 0.0.0.0 dev eth0.1
> ip addr add 0.0.0.0 dev eth0.101
> ip link set eth0.101 up
> ip link set eth0.1 up
> brctl addbr br_vlan_1
> brctl addbr br_vlan_101
> brctl addif br_vlan_1 eth0.1 eth1
> brctl addif br_vlan_101 eth0.101 eth2
> ip addr add 0.0.0.0 dev br_vlan_1
> ip addr add 0.0.0.0 dev br_vlan_101
> ip link set br_vlan_1 up
> ip link set br_vlan_101 up
>
>
> with this setup, the traffic on VID 101 is working fine. The devices
> across the switch and eth2 communicate each other but, the devices on
> VID 1 don't communicate with those connected to eth1
>
> If I remove eth0.1 and add eth0 to br_vlan_1 i have the opposite
> situation:
> the traffic on VID 101 is NOT working. The devices across the switch
> and eth2 DO NOT communicate each other
> but, the devices on VID 1 communicate with those connected to eth1. Of
> course on br_vlan_1 i'm getting the VID 1 traffic AND the VID 101....
This might work on recent kernels, please try them.
This is netdev list, after all ;)
next prev parent reply other threads:[~2012-02-01 17:21 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 [this message]
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
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=1328116881.1882.14.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox