9 messages in org.freebsd.freebsd-hackersRe: IP question: who should return EN...| From | Sent On | Attachments |
|---|---|---|
| Greg Lehey | Jun 20, 1996 11:03 am | |
| Nate Williams | Jun 20, 1996 11:45 am | |
| Dennis | Jun 20, 1996 2:06 pm | |
| David Greenman | Jun 20, 1996 2:43 pm | |
| Greg Lehey | Jun 21, 1996 12:50 am | |
| Greg Lehey | Jun 21, 1996 6:36 am | |
| Oleg N Panashchenko | Jun 21, 1996 10:03 am | |
| Greg Lehey | Jun 22, 1996 4:16 am | |
| David Greenman | Jun 22, 1996 5:33 pm |
| Subject: | Re: IP question: who should return ENOBUFS? | |
|---|---|---|
| From: | Greg Lehey (gr...@lemis.de) | |
| Date: | Jun 22, 1996 4:16:06 am | |
| List: | org.freebsd.freebsd-hackers | |
Oleg N Panashchenko writes:
In article <1996...@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