[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: aprsd config problem? More info...



More info thru observations, thus better(?) honed questions.

> Problem(s): aprsd won't...

1) stream output to it's ports (as config'd in aprsd.conf);
2) close its' connections

Using netstat, I can see that aprsd leaves data waiting on the socket:

Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp      124      0 192.168.1.5:10151       192.168.1.2:3152
CLOSE_WAIT
tcp      124      0 192.168.1.5:10151       192.168.1.2:3187
CLOSE_WAIT
tcp      124      0 192.168.1.5:10151       192.168.1.2:3156
CLOSE_WAIT
tcp      124      0 192.168.1.5:10151       192.168.1.2:3205
CLOSE_WAIT
tcp        0      0 192.168.1.5:ssh         192.168.1.2:3090
ESTABLISHED
tcp        0      0 192.168.1.5:ssh         192.168.1.2:3106
ESTABLISHED
tcp        0      0 192.168.1.5:ssh         192.168.1.2:3089
ESTABLISHED
tcp        0      0 192.168.1.5:ssh         192.168.1.2:3201
ESTABLISHED
tcp      124      0 192.168.1.5:10151       192.168.1.2:3190
CLOSE_WAIT
tcp      124      0 192.168.1.5:10151       192.168.1.2:3143
CLOSE_WAIT
tcp      124      0 192.168.1.5:10151       192.168.1.2:3161
CLOSE_WAIT
tcp      124      0 192.168.1.5:10151       192.168.1.2:3177
CLOSE_WAIT
tcp      124      0 192.168.1.5:10151       192.168.1.2:3194
CLOSE_WAIT
tcp      124      0 192.168.1.5:10151       192.168.1.2:3149
CLOSE_WAIT
tcp        0      0 192.168.1.5:ssh         192.168.1.2:3129
ESTABLISHED
tcp      124      0 192.168.1.5:10151       192.168.1.2:3182
CLOSE_WAIT
tcp      124      0 192.168.1.5:10151       192.168.1.2:3167
CLOSE_WAIT

The remote app (UIView\telnet) opens the socket, recieves the initial
history dump, then waits for more data till a timeout, were it sets
FIN_WAIT_2 and finally cleans up the abandoned socket.

aprsd appears to "lose touch" with the socket after dumping the history (or
local beacon). Thus the process is stranded till CLOSE_WAIT times out,
afterwhich the the owning process (aprsd) finally dissolves. Connections are
made at a rate greater than the CLOSE_WAIT timeouts, so ultimately, the
server loses resources.

Could I have missed some subtle config in my kernel compile?

Could networking be misconfig'd such that an initial connection is
successful, but the connections become lost (some struct corruption or
something)?

Thanks for any thoughts,

Rick

Original msg below>>>

> -----Original Message-----
> From: Rick Bolen [mailto:rbolen@carolina.rr.com]
> Sent: Wednesday, March 10, 2004 6:37 PM
> To: Debian Hams
> Subject: aprsd config problem?
>
>
> Hello all,
>
> I wrote regarding this awhile back, but my install was too
> cobbled to tshoot. I've since re-installed Woody, compiled a
> custom kernel with AX.25 protocol support, reinstalled the
> libax25, ax25-tools, ax25-apps and reinstalled aprsd.
>
> I still suffer the same problem I had with the previous install,
> i.e., aprsd won't stream output to it's ports (as config'd in aprsd.conf).
>
> -If I telnet (from localhost or remote) to the non-history and
> raw ports, I get only my server's beacon returned once only.
>
> -If I telnet (from localhost or remote) to ports w/history, I get
> the history dump as of the time of socket connect, but no further
> data streams out.
>
> -My aprs client sw, UI-View32, is config'd to mainport (10151).
> When it connects, it gets the history dump, but no further data
> until its' timout, and then it reconnects (same behavior whether
> the client officially "logs in" or not). This reconnect results
> in another "aprsd -d" process being spawned (as indicated by ps
> -aux). The STAT of all "aprsd -d" processes remain "S"
> (Sleeping). The number of aprsd processes will increase into the
> hundreds as re\connections occur).
>
> -All the while, "listen" displays a constant incoming stream of
> aprs data from the port.
>
> Hardware config:
> Via Eden 5000
> 10\100 NIC
> TNC X(kiss only)->/dev/ttyS0
>
> Relevent config data is as follows:
>
> axports:
> aprs2m  KG4OFO-13       9600    255     2       144.390 MHz (APRS
> 1200bps on air)
>
> ax25.init (per www.febo.com):
> /usr/sbin/kissattach /dev/ttyS0 aprs2m 44.71.36.65
> /usr/sbin/kissparms -p aprs2m -f no -l 50 -r 32 -s 320 -t 320
> /sbin/ifconfig ax0 broadcast 44.71.36.127 netmask 255.255.255.192
> /sbin/ifconfig ax0 arp mtu 256 up
> /sbin/route add -net 44.71.36.64 irtt 4000 ax0
>
> /etc/ax25# ifconfig
> ax0       Link encap:AMPR AX.25  HWaddr KG4OFO-13
>           inet addr:44.71.36.65  Bcast:44.71.36.127  Mask:255.255.255.192
>           UP BROADCAST RUNNING  MTU:256  Metric:1
>           RX packets:558 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:10
>           RX bytes:41439 (40.4 KiB)  TX bytes:254 (254.0 b)
>
> eth0      Link encap:Ethernet  HWaddr 00:40:63:CC:0A:CE
>           inet addr:192.168.1.5  Bcast:255.255.255.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:1141 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1196 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:115839 (113.1 KiB)  TX bytes:136042 (132.8 KiB)
>           Interrupt:11 Base address:0xe800
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> /etc/ax25# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref
>   Use Iface
> 44.71.36.64     *               255.255.255.192 U     0      0
>     0 ax0
> 192.168.1.0     *               255.255.255.0   U     0      0
>     0 eth0
> default         192.168.1.1     0.0.0.0         UG    0      0
>     0 eth0
>
>
> Anyone understand what the problem and solution is to this? It's
> driving me crazy.
>
> Thanks,
> Rick - kg4ofo




Reply to: