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:	Wed, 01 Feb 2012 16:23:10 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Leonardo Uzcudun <uzcudunl@...oo.it>
Cc:	yao zhao <yao.development@...il.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: VLAN 1 - Native

Le mercredi 01 février 2012 à 15:14 +0000, Leonardo Uzcudun a écrit :
> Yes, all those points are clear. My question is: can i do anything in
> the linux side (i can't change the switch config) to make the traffic
> on vlan 1 to function?
> 
> Example: how do those linux-wifi-access points that support vlans are
> able to have VLAN 1 and other vlans?

eth0 will receive your "untagged" traffic, exactly if you had no vlan
config on your machine.

eth0 will send your "untagged" traffic, exactly if you had no vlan
config on your machine.

If "eth0" name doesnt please you, you can rename it to eth0.1 or
eth0.untag


ip link set dev eth0 name eth0.untag



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