From owner-freebsd-net Tue Aug 28 23:33:48 2001 Delivered-To: freebsd-net@freebsd.org Received: from hirogen.kabelfoon.nl (hirogen.kabelfoon.nl [62.45.45.69]) by hub.freebsd.org (Postfix) with ESMTP id 8C01B37B406 for ; Tue, 28 Aug 2001 23:33:37 -0700 (PDT) (envelope-from pblok@inter.NL.net) Received: from ntpc (kf-pij-tg01-426.dial.kabelfoon.nl [62.45.89.172]) by hirogen.kabelfoon.nl (Postfix) with SMTP id EFF8C7CD2; Wed, 29 Aug 2001 08:33:35 +0200 (CEST) Reply-To: From: "Peter Blok" To: "'Mike Tancsa'" , "'Garrett Wollman'" Cc: Subject: RE: Runt frames = broken VLAN ? Date: Wed, 29 Aug 2001 08:29:09 +0200 Message-ID: <001001c13053$e9ea74c0$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <5.1.0.14.0.20010828160054.01accec0@marble.sentex.ca> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Mike, et al. I had the panic too. The problem is the order of initialization. It only happened when you compile NETGRAPH support in the kernel instead of using it as a module. When initialize netgraph a little bit later it works fine. In netgraph.h there is a macro called NETGRAPH_INIT. I have changed the SI_ORDER_ANY to SI_ORDER_LAST or SI_SUB_PSEUDO to something else (I can't remember). I am using the module. I'll check on this today and get a proper answer. Peter -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Mike Tancsa Sent: Tuesday, August 28, 2001 22:11 To: Garrett Wollman Cc: freebsd-net@FreeBSD.ORG Subject: Re: Runt frames = broken VLAN ? At 12:54 PM 8/28/01 -0400, Garrett Wollman wrote: >< said: > > > Can anyone tell me why the VLAN code might be causing my switches (ciscos) > > to see a lot of runt frames when the interface is in 802.1q trunking > mode ? > >It's possible that the Cisco is (bogusly, IMHO) trying to enforce the >Ethernet minimum frame length on the *de*capsulated frames. If you >send a frame that's less than 60 octets long, it gets encapsulated >(adding another four octets) and then padded by the interface up to 64 >octets. After the encapsulation is removed by the receiver, the frame >appears to only be 60 octets long. > >I'd call it a Cisco bug. The minimum frame length in Ethernet arises >from the electrical parameters of the original CSMA/CD Ethernet >design; what matters is the number of clocks the transmitter is >active, not the length of the payload. If its a Cisco bug, would it not manifest it self consistently ? On other ports, I have a 3620 and another catalyst both in 802.1q trunking mode, but I dont see any runt frames there. Also, who is the VLAN maintainer these days ? I ran into a panic that I thought was netgraph related, but Archie Cobbs thinks it might be in the VLAN code. I filed a PR on the issue http://www.freebsd.org/cgi/query-pr.cgi?pr=30149 I saved the debug kernel as well as the core dump in case its needed, but the problem is easy enough to repeat. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message