On Sun, 6 Dec 1998, Zoltan (Zoli) Meszaros wrote:
> This problem is similar to one already discussed before, I know, but as no
> solution was given, I try to put my case with as many details as I just
> can provide, and kindly ask the gurus to help me.
>
> Environment: Debian 2.0, kernel 2.0.36 (ie. I use kernel ax25),
> ax25-utils-2.1.42a.glibc, XFBB 7.00g tied direct to kernel ax25.
>
> The pain is, that sometimes a link got stuck and though it can't be seen
> from the application side (XFBB), it shows up in netstat --ax25. This
> prevents that station to connect again untill I reboot the whole system.
> No axctl kill helps, apparently no way to get rid of it but only
> restarting everything. The state of such a link seems always to be
> "LISTENING", while Recv-Q is -196.
Ok, as you said this seems to be the old problem that has been discussed
here quite a few times. Netstat reports the situation a bit wrong as the
socket is actually in "disconnected" state, not "listening" (actually
there is no "listening" state in linux ax.25...).
So far there is no known cure for this, other than switching to 2.1.x and
I doubt there will ever be much effort in tracing the bug down.
Kernel 2.2 is now tentatively scheduled to be released around Christmas so
for those of you with a little more experience I would really recommend
trying the new kernels. It would also be nice to find any possible bugs
before 2.2 is released and that won't happen if nobody uses the code.
--
--... Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ...--
