netdev - Re: 802.1Q support?

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:	Mon, 12 Jan 2009 22:46:57 +0200
From:	Matti Aarnio <matti.aarnio@...iler.org>
To:	Robin Getz <rgetz@...ckfin.uclinux.org>
Cc:	netdev@...r.kernel.org
Subject: Re: 802.1Q support?

On Mon, Jan 12, 2009 at 11:48:26AM -0500, Robin Getz wrote:
> I'm trying to understand the "standard" way to control a switch which
> supports VLAN.

"Standard" way would be to telnet to it, and issue IOS commands..
(or any other variant of things.)

> Pick any one of:
>  
> Infineon XWAY ADM6999 (eight-port 10/100 plus one MII) 
> http://www.infineon.com/cms/en/product/channel.html?channel=ff80808112ab681d0112ab68ce8d0043
>  
> Micrel MS8993M (2 port 10/100 plus one MII)
> http://www.micrel.com/_PDF/Ethernet/ks8993m_pb.pdf 
>  
> Broadcom BCM5325E (five port 10/100 plus one MII)
> http://www.broadcom.com/collateral/pb/5325E-PB00-R.pdf
>  
> Realtek (five port 10/100 plus one MII) 
> http://www1.futureelectronics.com/doc/REALTEK%20SEMICONDUCTOR/Realtek%20Semiconductor%20RTL8306SD-GR.pdf
>  
> They all have multiple MAC/PHYs which are exposed to the wire, and a
> single MII interface - which normally connects directly to a SOC's MII/MAC.
> 
> I would have thought that there would be separate drivers for these in the 
> phylib, but I didn't find anything that looked like it would work.
> (or expose the right interface (all the vendor specific VLAN registers) so
> I can program them properly from userspace)...
> 
> It is possible to hack up the specific EMAC driver to do everything, but
> that doesn't seem like the right way to do it...

In Linux Kernel there is VLAN support - but that happens well inside the 
network stack, not at network card drivers.

Doing something similar to what  vconfig tool does is definitely an option.
Doing it with vconfig ?   Probably not.  Layering problem, you see.

> Any pointers appreciated.
> Thanks.

/Matti Aarnio
--
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