From owner-freebsd-net@FreeBSD.ORG Sat Mar 27 08:48:40 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FF2916A4CE; Sat, 27 Mar 2004 08:48:40 -0800 (PST) Received: from bes.amduat.net (bes.amduat.net [206.124.149.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83BEF43D2D; Sat, 27 Mar 2004 08:48:39 -0800 (PST) (envelope-from jbarrett@amduat.net) Received: from [10.0.0.236] ([10.0.0.236]) (AUTH: LOGIN jbarrett, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bes.amduat.net with esmtp; Sat, 27 Mar 2004 08:48:38 -0800 From: "Jacob S. Barrett" To: Ruslan Ermilov Date: Sat, 27 Mar 2004 08:48:37 -0800 User-Agent: KMail/1.6.1 References: <200403251118.40718.jbarrett@amduat.net> <20040327074205.GA32984@ip.net.ua> <200403270753.53476.jbarrett@amduat.net> In-Reply-To: <200403270753.53476.jbarrett@amduat.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200403270848.37996.jbarrett@amduat.net> cc: freebsd-net@freebsd.org Subject: Re: Disabling VLAN_HWTAGGING X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Mar 2004 16:48:40 -0000 On Saturday 27 March 2004 07:53 am, Jacob S. Barrett wrote: > Well with a new "correct" MAC that pings go back and forth just fine now. > I will back out all my changes and see if they still work with the hardware > tagging/detagging enabled. OK, with the hardware support re-enabled the frame now enters the driver. It is detected as VLAN frame and sent to VLAN_INPUT_TAG. The frame is then delivered via lower hook to the ng_vlan where it doesn't match the vlan tag so it goes out the nomatch hook. I guess with the VLAN tag stripped from the frame that ng_vlan can't match it. Is this the expected behavior with ng_vlan? I can just comment out the VLAN stripping line in the driver if it is the expected behavior. That isn't a big deal really. I haven't done a whole lot with the network interface drivers other than a few minor fixes here and there, but would it be hard to add some sort of flag to enable/disable the tag stripping via ifconfig? I was thinking that could be down through a "linkx" flag right? If the driver got the say "link1" it would down the interface, set clear the stripping config bits, and then re-up the interface. Or would this be better handled by a sysctl option? Does that sound safe and do-able? -- Jacob S. Barrett jbarrett@amduat.net www.amduat.net "I don't suffer from insanity, I enjoy every minute of it."