I feel the linux VLAN package is a minimal implementation. It provides you with Virtual Interfaces, you can make a virtual NIC interface for each VLAN that is configured in the nearby switch - provided, you have a trunk link with the switch - that means, your card received tagged frames. With the virtual interfaces, per VLAN, you can make bridges or you can run servers on top of it. regards jojan -----Original Message----- From: Csaba P?csai [mailto:Csaba.Pocsai@xxxxxxxxx] Sent: Tuesday, September 28, 2004 11:59 AM To: Linux 802.1Q VLAN Subject: RE: [VLAN] vlan & osi-model HI, Just to make the thing clear. Is it true that vlan package of linux does only the tagging. There is no any VLAN table which shows which packet can go to where? I also tried VLAN and I recognized that I have to use one of the following: iptables ->> VLAN layer 3 to separate the different VLANS depending on subnets briging ->> VLAN layer 1 (port based) simply placing the interfaces in different briges. ???? (maybe iptables but only reduced) -->> VLAN layer 2 for MAC VLANs. How you do this things?! Thanks Csaba -----Original Message----- From: vlan-bounces@xxxxxxxxxxxxxxx [mailto:vlan-bounces@xxxxxxxxxxxxxxx]On Behalf Of Vishwas Manral Sent: Tuesday, September 28, 2004 8:58 AM To: Linux 802.1Q VLAN Subject: RE: [VLAN] vlan & osi-model Hi Jojan, I would restate what Ben has said "port-based VLANs work simply because the equipment knows which port the VLAN comes in on and uses that information to know that the traffic belongs to a particular VLAN." There is nothing to do with Layer-1 etc. Thanks, Vishwas -----Original Message----- From: vlan-bounces@xxxxxxxxxxxxxxx [mailto:vlan-bounces@xxxxxxxxxxxxxxx] On Behalf Of JOJAN Sent: Tuesday, September 28, 2004 10:14 AM To: 'Linux 802.1Q VLAN' Subject: RE: [VLAN] vlan & osi-model AFAIK, these are not official names. Layer <n> VLAN is really a layer 2 solution, but it depends on some layer <n> feature to make decision on what to do with a packet. These rules apply only for those packets which are untagged. When they enter the switch, the switch has to TAG it before making a decision as to which all ports the frame has to be forwarded. If the switch has Layer3 configurations, those rules are taken first - then comes layer 2 configurations then comes layer 1 configurations. Layer3 VLAN is named so because it examines the Layer3 packet for input to the rules e.g., IP subnet Layer2 VLAN is named so because it examines the layer2 features for input to the rule e.g., MAC address, Frame Type Layer1 VALN is named so because it checks the physical features - the port thru which it entered the switch Hope this is clear. regards jojan -----Original Message----- From: Lars Reimann [mailto:lar@xxxxxxxxxxx] Sent: Monday, September 27, 2004 5:06 PM To: Linux 802.1Q VLAN Subject: [VLAN] vlan & osi-model hi all, i've a short question about the different vlan operating modes. everywhere it says: layer 1 VLAN, layer 2 VLAN, layer 3 VLAN, layer 4-7 vlan. my question is, if vlan layer 1 really corresponds to "OSI-Model Layer 1 " VLAN? i do understand that layer 2 vlan works with mac-addresses like osi-model layer 2, and layer 3 vlan inspects ip-adresses for example forming vlans per subnet. but i cannot imagine how per-port vlan works on layer1. can anyone help? _______________________________________________ Vlan mailing list Vlan@xxxxxxxxxxxx http://www.lanforge.com/mailman/listinfo/vlan ------------------------------------------------------------------------ --- "This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken upon this e-mail is strictly prohibited and may be unlawful." ------------------------------------------------------------------------ --- _______________________________________________ Vlan mailing list Vlan@xxxxxxxxxxxx http://www.lanforge.com/mailman/listinfo/vlan _______________________________________________ Vlan mailing list Vlan@xxxxxxxxxxxx http://www.lanforge.com/mailman/listinfo/vlan --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.767 / Virus Database: 514 - Release Date: 9/21/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.767 / Virus Database: 514 - Release Date: 9/21/2004 _______________________________________________ Vlan mailing list Vlan@xxxxxxxxxxxx http://www.lanforge.com/mailman/listinfo/vlan --------------------------------------------------------------------------- "This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken upon this e-mail is strictly prohibited and may be unlawful." ---------------------------------------------------------------------------
