I have been looking into VLANS on some switches. Apparently on these
switches, a host can only be a member of two vlans if it is 802.IQ
compliant (or have 2 NIC's, one into each vlan). Its not clear from the
docs whether the OS has to be 802.IQ compliant or if its an attribute of
the NIC.
Anyway is Linux 802.IQ compliant? Is Linux 2.2 or just 2.4.
How long has 802.IQ been around and how widespread is it. Is Solaris
compliant. How about NT/ Win 2000.
Robert Cohen
TLTSU, Australian National University.
On Fri, 17 Nov 2000, Robert Cohen wrote:
> Anyway is Linux 802.IQ compliant? Is Linux 2.2 or just 2.4.
> How long has 802.IQ been around and how widespread is it. Is Solaris
> compliant. How about NT/ Win 2000.
See http://vlan.sourceforge.net/ and
http://scry.wanfear.com/~greear/vlan.html for two implementations for
Linux.
Peter
--
Peter Svensson ! Pgp key available by finger, fingerprint:
<[email protected]> ! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF
<[email protected]> !
------------------------------------------------------------------------
Remember, Luke, your source will be with you... always...
On Fri, Nov 17, 2000 at 07:37:04PM +1100, Robert Cohen wrote:
> I have been looking into VLANS on some switches. Apparently on these
> switches, a host can only be a member of two vlans if it is 802.IQ
> compliant (or have 2 NIC's, one into each vlan). Its not clear from the
> docs whether the OS has to be 802.IQ compliant or if its an attribute of
> the NIC.
Oh, you mean IEEE 802.1q VLAN trunking protocol ?
> Anyway is Linux 802.IQ compliant? Is Linux 2.2 or just 2.4.
> How long has 802.IQ been around and how widespread is it. Is Solaris
> compliant. How about NT/ Win 2000.
The baseline Linux is not, but there has been external development
activity to create patches supporting vlan-trunk interfacing.
In fact TWO separate patches, which now do share some code:
http://scry.wanfear.com/~greear/vlan.html
http://vlan.sourceforge.net/
I have seen VLAN trunking implemented at some network cards for
Solaris (gigabit cards mainly), similar is propably true for
the windows world. Common thing there is that the DRIVER creates
an illusion of having gazillions of network devices, each plain
simple ethernet device.
Linux is slightly different from that model by having generalized
802.1q frame PROTOCOL processing layer which isn't bound to any
particular network device driver. For upper protocols also Linux
VLAN code supplies an illusion of ethernet device per each VLAN
sub-interface.
Linux is slowly getting its network drivers capable to support 802.1q
enlarged ethernet frames, but those are still few and far in between.
> Robert Cohen
> TLTSU, Australian National University.
/Matti Aarnio