From owner-freebsd-hackers Fri Jun 21 10:19:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25541 for hackers-outgoing; Fri, 21 Jun 1996 10:19:16 -0700 (PDT) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA25534 for ; Fri, 21 Jun 1996 10:19:12 -0700 (PDT) Received: from tav.kiev.ua (tav-sita.sita.kiev.ua [193.124.50.39]) by ref.tfs.com (8.7.5/8.7.3) with SMTP id KAA00305 for ; Fri, 21 Jun 1996 10:18:40 -0700 (PDT) Received: (from helg@localhost) by tav.kiev.ua (8.6.12/8.6.12) id UAA04703; Fri, 21 Jun 1996 20:03:23 +0300 Date: Fri, 21 Jun 1996 20:03:23 +0300 From: Oleg N Panashchenko Message-Id: <199606211703.UAA04703@tav.kiev.ua> To: grog@lemis.de (Greg Lehey) Cc: hackers@freebsd.org Subject: Re: IP question: who should return ENOBUFS? Organization: Maxis Labs X-Newsreader: TIN [version 1.2 PL2] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199606201803.UAA19421@allegro.lemis.de> you wrote: : I've just spent a fair amount of time trying to figure out why our : ISDN software jams up if it can't establish a connection. The : symptoms are that if you can't establish a connection before a certain : number of packets have been sent, the whole interface just returns: : === root@freebie (/dev/ttyp0) /sys/netinet 11 -> ping 192.109.197.38 : PING 192.109.197.38 (192.109.197.38): 56 data bytes : ping: sendto: No buffer space available : ping: wrote 192.109.197.38 64 chars, ret=-1 : ping: sendto: No buffer space available I have seen exactly the same behaviour with Digiboard driver. There was reliable way to reproduce it: ping -f any.non-local.host And see nothing except of 'No buffer space available' until restarting the interface. Adding a call of linesw[].l_start() in appropriate place in driver code closed the problem. Oleg