From owner-freebsd-net@FreeBSD.ORG Thu Mar 25 16:50:38 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 2DA9C16A531; Thu, 25 Mar 2004 16:50:38 -0800 (PST) Received: from bes.amduat.net (bes.amduat.net [206.124.149.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id B542643D60; Thu, 25 Mar 2004 16:50:37 -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; Thu, 25 Mar 2004 16:50:36 -0800 From: "Jacob S. Barrett" To: Ruslan Ermilov Date: Thu, 25 Mar 2004 16:50:35 -0800 User-Agent: KMail/1.6.1 References: <200403251118.40718.jbarrett@amduat.net> <20040325234527.GC85417@ip.net.ua> In-Reply-To: <20040325234527.GC85417@ip.net.ua> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200403251650.35714.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: Fri, 26 Mar 2004 00:50:38 -0000 On Thursday 25 March 2004 03:45 pm, you wrote: > > Can you disable VLAN_HWTAGGING? > > Not without modifying if_nge.c, but it should be pretty trivial. As trivial as setting chaning: ifp->if_capabilities = IFCAP_HWCSUM | IFCAP_VLAN_HWTAGGING; to: ifp->if_capabilities = 0; This didn't solve the problem completely though. On the remote host I can now see tagged frames from the if_nge host, but the reply frames from the if_em host or not visible at all on the if_nge host (via tcpdump). tcpdump on if_em host: 16:41:28.741109 11:22:33:44:55:66 ff:ff:ff:ff:ff:ff 8100 60: 802.1Q vlan#2 P0 arp who-has 10.2.0.2 tell 10.2.0.1 16:41:28.741161 0:90:27:f4:58:1d 11:22:33:44:55:66 8100 60: 802.1Q vlan#2 P0 arp reply 10.2.0.2 is-at 0:90:27:f4:58:1d tcpdump on if_nge host: 16:41:27.079515 11:22:33:44:55:66 ff:ff:ff:ff:ff:ff 8100 46: 802.1Q vlan#2 P0 arp who-has 10.2.0.2 tell 10.2.0.1 ifconfig: nge0: flags=8843 mtu 1500 inet6 fe80::209:5bff:fe1a:7680%nge0 prefixlen 64 scopeid 0x2 ether 00:09:5b:1a:76:80 media: Ethernet 1000baseSX status: active ngeth0: flags=8843 mtu 1500 inet6 fe80::2a0:c9ff:feac:c55c%ngeth0 prefixlen 64 scopeid 0x6 inet 10.2.0.1 netmask 0xffffff00 broadcast 10.2.0.255 ether 11:22:33:44:55:66 script to setup VLAN: ifconfig nge0 up ngctl mkpeer nge0: vlan lower downstream ngctl mkpeer nge0:lower eiface vlan2 ether ngctl msg nge0: setpromisc 1 ngctl msg nge0: setautosrc 0 ngctl msg nge0:lower addfilter "{ vlan=2 hook=\"vlan2\" }" ifconfig ngeth0 link 11:22:33:44:55:66 up > ng_vlan(4) doesn't provide support for hardware VLAN tagging for output > frames -- it always emits ETHERTYPE_VLAN type Ethernet frames. Yeah, that is why I figured disabling VLAN_HWTAGGING might help. > > I am wondering if it is something to do VLAN_HWTAGGING. The if_em cards > > I have don't do it and work fine, but the if_nge cards don't work at all. > > What FreeBSD version you're seeing the panic on? I forgot to mention this was on CURRENT as of 3/24/2004. -- Jacob S. Barrett jbarrett@amduat.net www.amduat.net "I don't suffer from insanity, I enjoy every minute of it."