netdev - Re: VLAN 1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 2 Feb 2012 09:09:01 +0000 (GMT)
From:	Leonardo Uzcudun <uzcudunl@...oo.it>
To:	Michal Soltys <soltys@....info>
Cc:	yao zhao <yao.development@...il.com>,
	Eric Dumazet <eric.dumazet@...il.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: VLAN 1 - Native

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)?

Thanks again.

BR,

Leo



----- Messaggio originale -----
Da: Michal Soltys <soltys@....info>
A: Leonardo Uzcudun <uzcudunl@...oo.it>
Cc: yao zhao <yao.development@...il.com>; Eric Dumazet <eric.dumazet@...il.com>; "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Inviato: Mercoledì 1 Febbraio 2012 20:26
Oggetto: Re: VLAN 1 - Native

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.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html