netdev - Re: Problem with VLANs and via-velocity driver

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]

Message-ID: <4AFD4595.1070904@e-teleport.net>
Date:	Fri, 13 Nov 2009 12:40:05 +0100
From:	Séguier Régis <rseguier@...eleport.net>
To:	Patrick McHardy <kaber@...sh.net>
CC:	Kevin Shanahan <kmshanah@...enchant.net>, netdev@...r.kernel.org
Subject: Re: Problem with VLANs and via-velocity driver

Patrick McHardy a écrit :
>
>>> There's some special-casing for VID 0 in velocity_init_cam_filter().
>>> Does "ip link add link eth0 type vlan id 0" make any difference?
>>> If not, does "ip link set eth0 promisc on"?
>>>   
>>>       
>> When we patch the driver to support multiple vlan, we decide to use the
>> vlan 0 to desactivate the vlan filtering.
>>     
>
> Why? The usual behaviour is to receive both tagged and untagged
> frames.
>   
We decide this with françois as an alternative to desactivate the NIC 
vlan filtering instead of creating a modul parameter.
The vlan id 0 need to be created but not necessary activate.

In september 2008, we had a discution about exactly the same problem.
You speak about the possibility of an ALLVLAN device flag.

I think i proposed a patch to desactivate NIC vlan filtering when we are 
in promisc mode but not used.
-- 
Régis Séguier
--
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