Zoli,
It looks to me as if the link to HA3PO is waiting for an ack from
him since he sent him (Q'd) packets to him and that is the state of things
at that time. But I gather it is happening all the time.
I think you may have a problem in /usr/local/fbb/system/port.sys
and that might cause this kind of thing.
On Sun, 6 Dec 1998, Zoltan (Zoli) Meszaros wrote:
> Hi all,
>
> 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.
>
I didn't know FBB was up to g. I am using e and it works so well I
don't want to upgrade.
> 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.
Yes it must be port.sys so here is mine. I have 2 ax.25 ports and
a special BPQ look netrom port called netbbs. And I telent to FBB if
desired. My file:
# FBB7.00
#
#
#Ports TNCs
2 4
#
# Interface 6 = Windows
# Interface 7 = TCPIP
# Interface 8 = TFWin.dll
# Interface 9 = LINUX
#
# LINUX : Address is logic name of the device if used (/dev/cua0)
#
#Com Interface Adress (Hex) Baud
1 9 **** 9600
2 9 e12 0 # e12 = 3602
#
# if LINUX MultCh field is :
# AX25 socket : logic name of the port in axports
# Maxframe: The maximum nb of frames the TNC will send at a time.
# NbFwd : Number of channels for OUTGOING forward at same time.
# MxBloc : Size of forward-block in kb.
#
# M/P-Fwd : Minute of the hour for start of forward, and period
# (how many minutes between each forward-start).
# Mode : One of these:
# B : BBS-mode.
# G : "Guest"-mode.
# U : Normal-mode.
# Type host-mode, one of these:
# D : WA8DED
# K : KAM hostmode.
# M : Telephone-modem.
# P : PK-232
# Q : BPQ v 4.x
# X : AF_AX25 Kernel Linux
# Addition: One of these letters can be used too:
# L : Send unproto beacon after each arriving mail.
# Y : Yapp allowed on this QRG.
# W : Gateway allowed TO this QRG.
# R : Read-Only acces.
# Freq. : Text to describe this port (max 9 characters, no space)
# Same number of lines as number of TNCs.
#
#TNC NbCh Com MultCh Pacln Maxfr NbFwd MxBloc M/P-Fwd Mode Freq
0 0 0 0 0 0 0 0 00/01 ---- File-fwd.
1 8 1 ax0 250 2 1 10 30/60 XUWY UHF port
2 2 1 ax1 250 4 1 10 00/60 XUWY VHF port
3 6 1 netbbs 250 4 1 10 15/60 XUWY BPQ look
4 8 2 0 250 5 4 1000 5/15 TUWY Telnet
#
# Special callsigns and modes for some channels.
#
#TNC Nbs Callsign-SSID Mode
#1 2 XXXXX-1 B
#
# End of file.
#
>
> If I stop solely XFBB, then device changes to "???" (three times question
> mark) in netstat response, but the rest of the line is the same. If I
> restart XFBB, then netstat keeps on showing "???" in device column for the
> stuck station.
>
> Below you find one such case, when HG8GL-0 is stuck here.
>
> So, any hint on what gives this? And what to do against? Or to get rid of
> such, except the reboot?
>
> Thanks for your help.
>
>
> #netstat --ax25
>
> Active AX.25 sockets
> Dest Source Device State Vr/Vs Send-Q Recv-Q
> HA3PG-0 HA5OB-0 ax3 RECOVERY 002/007 3780 0
> * HA5OB-0 ax3 LISTENING 000/000 0 0
> * HA5OB-0 scc3 LISTENING 000/000 0 0
> * HA5OB-0 ax1 LISTENING 000/000 0 0
> HG8GL-0 HA5OB-0 ax1 LISTENING 000/000 0 -196
>
>
> #cat /proc/net/ax25
>
> dest_addr src_addr dev st vs vr va t1 t2 t3 idle n2 rtt wnd
>paclen Snd-Q Rcv-Q Inode
> HA3PG-0 HA5OB-0 ax3 4 7 2 5 4/006 0/02 0/300 16/016 1/10 3 2
> 230 3780 0 146611
> * HA5OB-0 ax3 0 0 0 0 0/006 0/02 0/300 0/016 0/10 3 2
> 256 0 0 86074
> * HA5OB-0 scc3 0 0 0 0 0/005 0/01 0/300 0/016 0/10 2 7
> 256 0 0 86073
> * HA5OB-0 ax1 0 0 0 0 0/005 0/01 0/300 0/016 0/10 2 7
> 256 0 0 86071
> HG8GL-0 HA5OB-0 ax1 0 0 0 0 0/005 0/01 0/300 0/016 0/10 2 7
> 256 0 -196 0
>
>
> #axctl bbs hg8gl ha5ob -kill
>
> axctl: SIOAX25CTLCON: Transport endpoint is not connected
>
> (Note: "bbs" is the name of "ax1" device as per /etc/ax25/axports.)
>
>
> 73 , Zoli
>
> PS. Maybe I should drill a few holes big enough to make those stuck data
> flow out of the system? ;-)
>
> --------------------------------------------------------------
> Zoltan (Zoli) Meszaros AX25 : HA5OB @ HA5OB.HUN.EURO
> Budapest, Hunyadi ter 10. ampr-net : [EMAIL PROTECTED]
> H-1067 email : [EMAIL PROTECTED]
> HUNGARY WEB : http://www.qsl.net/ha5ob
>
>
Best wishes
- Karl F. Larsen, 3310 East Street, Las Cruces,NM (505) 524-3303 -
