Perriot, Cedric wrote: > What I meant was i want the switch to look at the priority without looking > at the vlan. > I know that the priority belong to the 4 bytes added by the 802.1q but the > standards says: > > about frames: > > <"3.6 Frame: A unit of data transmission on an IEEE 802 LAN MAC that conveys > a protocol data unit (PDU) > between MAC Service users. There are three types of frame; untagged, > VLAN-tagged, and priority-tagged."> > I would like to use the last one. > > <" The null VLAN ID. Indicates that the tag header contains only > user_priority > information; no VLAN identifier is present in the frame. This VID value > shall not > be configured as a PVID or a member of a VID Set, or configured in any > Filtering > Database entry, or used in any Management operation.. "> > > and talking about vlan equipment: > > <"All implementations shall support the use of all VID values in the range 0 > through their defined maximum > VID,"> > > If i add a vlan 0 to the interface eth0 I get a new interface eth0.0 > I am wondering where the untagged frames are dropped. >>From what i saw the frames will never reach the vlan code because the > ethernet type field will be 8000 instead of 8100. Is Linux generating VLAN frames with the type set to 8000, or is your other network equipment? I'll have to create a VID of zero and poke around with a sniffer tomorrow... > So, are the frames dropped because the interface eth0 is not configured (no > ip,...)? If it's a tag with a VLAN header, then the VLAN code should get the packet regardless of the IP addresses. If it has no VLAN tag, then the VLAN code will never get it...and then it would go to the ethX interface. > And what about configuring eth0 and eth0.0 with the same IP. what are the > consequences ? Same as configuring eth0 and eth1 with the same IP I imagine... Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com
