I am still working on the problem. I am now trying to install a stock 2.2.18 + vlan 1.0.0 on a PC (previously it was an embedded system) to make some tests on the kernel. However I a am using a NIC 3Com with the driver 3c59x which need to be patch to work with vlan. My problem is that the patch available on the candela website concerns a recent version of the driver. Does someone have a patch for the 3c59x driver included in the 2.2.18 ? ps: I would like to try the 2.4.1 kernel so if a patch is also needed I will soon need it. -----Message d'origine----- De : vlan-bounces@xxxxxxxxxxxxxxx [mailto:vlan-bounces@xxxxxxxxxxxxxxx] De la part de Perriot, Cedric Envoy? : lundi 7 f?vrier 2005 11:47 ? : vlan@xxxxxxxxxxxx Objet : RE: [VLAN] kernel 2.2.18 + vlan patch around july 2001 first I got linux on both end. And I am receiving untagged frames (because the cisco switch removed the tag) so obviously the frame is going to eth0. How could i make it going to eth0.0 or being used by eth0 instead of being dropped ? >From what i see If we declared a vlan on the linux it only accept >tagged frames in this vlan. But this is problematic with the cisco switches because we cannot declared a vlan 0 in the switch so it will always remove the tag. any news ? ced -----Message d'origine----- De : Perriot, Cedric Envoy? : jeudi 3 f?vrier 2005 09:00 ? : vlan@xxxxxxxxxxxx Objet : RE: [VLAN] kernel 2.2.18 + vlan patch around july 2001 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. So, are the frames dropped because the interface eth0 is not configured (no ip,...)? And what about configuring eth0 and eth0.0 with the same IP. what are the consequences ? thank you for your help cedric -----Message d'origine----- De : vlan-bounces@xxxxxxxxxxxxxxx [mailto:vlan-bounces@xxxxxxxxxxxxxxx] De la part de Ben Greear Envoy? : mercredi 2 f?vrier 2005 18:09 ? : Linux 802.1Q VLAN Cc : vlan@xxxxxxxxxxxx Objet : Re: [VLAN] kernel 2.2.18 + vlan patch around july 2001 Perriot, Cedric wrote: > Maybe I am just misusing the vlan functionnality. My goal is to use > 802.1p without 802.1q to do so I would like to get a vid = 0. I don't think VLAN-0 is going to work, and at the very least, you cannot use .1p w/out using .1q as the headers are one and the same. Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com _______________________________________________ Vlan mailing list Vlan@xxxxxxxxxxxx http://www.lanforge.com/mailman/listinfo/vlan _______________________________________________ Vlan mailing list Vlan@xxxxxxxxxxxx http://www.lanforge.com/mailman/listinfo/vlan
