Date: Sat, 22 Jun 1996 13:16:26 +0200 (MET DST) From: grog@lemis.de (Greg Lehey) To: helg@tav.kiev.ua (Oleg N Panashchenko) Cc: hackers@FreeBSD.ORG (FreeBSD Hackers) Subject: Re: IP question: who should return ENOBUFS? Message-ID: <199606221116.NAA14679@allegro.lemis.de> In-Reply-To: <199606211703.UAA04703@tav.kiev.ua> from "Oleg N Panashchenko" at Jun 21, 96 08:03:23 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Oleg N Panashchenko writes: > > 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. Yup. That's the problem. > Adding a call of linesw[].l_start() in appropriate place in driver code > closed the problem. I'd consider that a workaround. We need to change the congestion avoidance algorithm to something that works. In the meantime, this "bug fix" in ip_output must be removed. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606221116.NAA14679>