From owner-freebsd-questions@FreeBSD.ORG Thu Apr 10 01:22:59 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C889937B401; Thu, 10 Apr 2003 01:22:59 -0700 (PDT) Received: from kazi.fit.vutbr.cz (kazi.fit.vutbr.cz [147.229.8.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CBF043F93; Thu, 10 Apr 2003 01:22:58 -0700 (PDT) (envelope-from cejkar@fit.vutbr.cz) Received: from kazi.fit.vutbr.cz (localhost [127.0.0.1]) by kazi.fit.vutbr.cz (8.12.9/8.12.9) with ESMTP id h3A8MqYF031781 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Apr 2003 10:22:52 +0200 (CEST) Received: (from cejkar@localhost) by kazi.fit.vutbr.cz (8.12.9/8.12.5/Submit) id h3A8Mp2J031776; Thu, 10 Apr 2003 10:22:51 +0200 (CEST) X-Authentication-Warning: kazi.fit.vutbr.cz: cejkar set sender to cejkar@fit.vutbr.cz using -f Date: Thu, 10 Apr 2003 10:22:51 +0200 From: Cejka Rudolf To: Mike Hogsett Message-ID: <20030410082251.GA28336@fit.vutbr.cz> References: <200304091941.h39JfSwX025768@quarter.csl.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200304091941.h39JfSwX025768@quarter.csl.sri.com> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: luigi@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: nge driver & VLAN support X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 08:23:00 -0000 Mike Hogsett wrote (2003/04/09): > If I `tcpdump' nge0 I see vlan tagged frames, but all the vlan numbers are > wrong. On the Cisco I manually pruned the `vlans allowed on trunk' down > to vlans 505 and 800. Vlan 505 packets show up in the tcpdump output of > nge0 as vlan 2305 and vlan 800 packets show up in the output as vlan 256. > > If anyone can offer any insight into my problem, or offer further ways to > diagnose the problem I would greatly appreciate it. It seems that you have the same problems as we had in the past with em driver. Here is my posting without any response to Bill Paul, hope it helps (the other possible buggy drivers are bge, nge, txp and gx, because they all call vlan_input_tag()): ... I think that I saw some related VLAN commits by you, Luigi, can you help, please? Or do you know anybody else? -- Date: Thu, 27 Feb 2003 18:04:38 +0100 From: Cejka Rudolf To: Bill Paul Subject: Re: cvs commit: src/sys/dev/fxp if_fxp.c if_fxpreg.h if_fxpvar.h Bill Paul wrote (2003/02/26): > Modified files: > sys/dev/fxp if_fxp.c if_fxpreg.h if_fxpvar.h > This chip has hardware VLAN support as well. I hope to enable > support for this eventually. Hello, are you really interested in hardware VLAN support? If so, please look at kern/46405 - it seems that drivers with implemented hardware VLAN support does not work correctly if there is packet priority != 0. It has been fixed in em driver by Prafulla Deuskar (kern/45907 and kern/46028), but according to sources it seems that other drivers with hardware VLAN support still does not work and it seems that there is nobody interested to fix VLAN support in FreeBSD. Or please can you tell me, who else from kernel developers is really interested in VLAN support? There is function vlan_input_tag() with parameter "t" and I think that it is expected to be "VLAN Tag" containing ID and Priority and drivers do it in this way (except for em driver, which masks VLAN ID from VLAN Tag thanks to fix from Prafulla). However, we think that it should be fixed directly in vlan_input_tag() function and this function should mask VLAN ID from VLAN Tag inside itself - but it does not do it. Thank you very much. -- Rudolf Cejka http://www.fit.vutbr.cz/~cejkar Brno University of Technology, Faculty of Information Technology Bozetechova 2, 612 66 Brno, Czech Republic