From owner-freebsd-hackers Mon Jul 13 03:18:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09860 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 03:18:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09855 for ; Mon, 13 Jul 1998 03:18:41 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id KAA08973; Mon, 13 Jul 1998 10:18:21 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA27248; Mon, 13 Jul 1998 12:18:19 +0200 (MET DST) Message-ID: <19980713121819.08980@follo.net> Date: Mon, 13 Jul 1998 12:18:19 +0200 From: Eivind Eklund To: "Larry S. Lile" , hackers@FreeBSD.ORG Subject: Re: Still having problems with my driver :( References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Larry S. Lile on Sat, Jul 11, 1998 at 03:47:07PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I limited this to -hackers only, as it isn't really a tokenring problem. On Sat, Jul 11, 1998 at 03:47:07PM -0400, Larry S. Lile wrote: > > I still cannot get the upper network layers to respond to incoming > packets. I even hacked tcpdump to make sure that I was no wrecking > the packets as I took them off the wire. > > 15:29:58.698564 arp who-has anatok tell blastok (0:0:83:2d:9f:35) > hardware #6 > 15:29:59.588735 cyntok > anatok: icmp: echo request > 15:30:00.590438 cyntok > anatok: icmp: echo request > tcpdump: WARNING: compensating for unaligned libpcap packets > (^- anybody know how to fix this?) > 15:30:03.499586 cyntok.1054 > anatok.telnet: S 3037285377:3037285377(0) > win 16384 > 15:30:09.271262 cyntok.1054 > anatok.telnet: S 3037285377:3037285377(0) > win 16384 > 15:30:09.702343 arp who-has anatok tell blastok (0:0:83:2d:9f:35) > hardware #6 > > The only messages I got indicating anything at all is wrong were > these when I ifconfig the card up for the first time after a > reboot. > > Jul 10 22:21:33 anarchy routed[69]: ignore RTM_ADD without gateway > Jul 10 22:21:33 anarchy routed[69]: Send bcast sendto(tok0, > 10.0.0.255.520): No buffer space available > Jul 10 22:21:33 anarchy routed[69]: write(rt_sock) RTM_ADD 10.0.0.0/24 > --> 10.0.0.1: File exists > > Any ideas what might be wrong, or could someone please look at my > code and help me figure this out. If ping -f gives the same "no buffer space available", it probably originate here (around line 333 in netinet/ip_output.c): /* * Verify that we have any chance at all of being able to queue * the packet or packet fragments */ if ((ifp->if_snd.ifq_len + ip->ip_len / ifp->if_mtu + 1) >= ifp->if_snd.ifq_maxlen) { error = ENOBUFS; goto bad; } If this is the case, it is due to your driver not pulling packets off the output queue (or not doing it fast enough). What to do about it depend on the internals of your driver. The 'file exists' comes from an already existing route being overwritten - that part of it shouldn't be a problem, I think. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message