One thing that I'm doing unusual.... I'm using TNOS as the TNC
interface. I noticed that the TNOS interface instructions are pretty
old. Has there been changes as to the proper way to make the connection
via TNOS? I would be interested in talking to someone that has had long
term sucess with the TNOS / hack interface.
I plan on getting rid of TNOS in a couple of months, but for now... I'm
going to keep it running until I can plan on the switch to the kernal
utilities. I need to time the change and re-creation of all my axip
links when I make the switch to the kernal utils, I need to do this, but
I still need to wait a few weeks or months before I take the time to
make the switch.
I'm really wondering if the garbage call is related to the TNOS mystery
interface. My clx_par file contains the following:
-----------
call: MyEncryptedCall # encrypted callsign string
[NC7J]
ax25: NC7J
vacuum: 360
#ssid: 0
tnc_dev: /dev/ptype
tnc_baud: 38400
-----------
I have ax25 built into the kernel, but I also have to use the clx_par
ax25 command to get things to work with TNOS, this is according to the
info. in the Admin Manual related to using CLX with TNOS.
One thing that is wierd, is the fact that I see kernel level ax25
connections when using the TNOS interface, output from 'netstat' shows:
Active AX.25 sockets
Dest Source Device State Vr/Vs Send-Q Recv-Q
K7UT-15 NC7J-0 ax0 ESTABLISHED 05/01 0 0
N7TR-15 NC7J-0 ax0 ESTABLISHED 06/05 0 0
W7CT-15 NC7J-0 ax0 ESTABLISHED 05/02 0 0
K7XB-15 NC7J-0 ax0 ESTABLISHED 00/02 0 0
N7KH-15 NC7J-0 ax0 ESTABLISHED 06/04 0 0
K7SX-15 NC7J-0 ax0 ESTABLISHED 02/03 0 0
K7JS-15 NC7J-0 ax0 ESTABLISHED 05/04 0 0
For the current users connected to my CLX cluster, I wouldn't expect the
kernel to see the AX25 connects, I thought CLX was doing all of the AX25
stuff when using the TNOS interface.
Here is the log output from the latest 'garbage callsign' connection....
KC7IAS caused this one:
Apr 28 23:10:55 ng7m syslog: kc7ias?@-15->[Connect]
Apr 28 23:10:55 ng7m syslog: usr_ctl/rpc_send.cc -> snd_ctl, 0 - 1/
T^F^Hlo^??4\
n^??m^^(): {@@@@@@@@@@@@}Hi om, This is nc7j, a Linux-PacketCluster node
runnin\
g CLX3.04. Last started: 28-Apr-1998 0406Z - Uptime: 0.19:04:30.
Cluster: 1 lin\
ks, 1 total nodes, 9 local users. <RPC: Can't encode arguments>
Apr 28 23:10:55 ng7m syslog: usr_ctl/rpc_send.cc -> mb_ctl, 0 -
3/h^A^E^Hh^A^E^\
H,n^??u!(): {@@@@@@@@@@@@}info/etc/motd<RPC: Can't encode arguments>
Apr 28 23:10:55 ng7m syslog: usr_ctl/rpc_send.cc -> mb_ctl, 0 -
3/h^A^E^Hh^A^E^\
H,n^??u!(): {@@@@@@@@@@@@}9999 mail/^?I^D^Hp}^E^Htu^D^H<RPC: Can't
encode argum\
ents>
Apr 28 23:10:55 ng7m syslog: usr_ctl/rpc_send.cc -> mb_ctl, 0 -
3/h^A^E^Hh^A^E^\
H,n^??u!(): {@@@@@@@@@@@@}batch/start/FI^D^Hp}^E^HP|^??<RPC: Can't
encode argum\
ents>
Apr 28 23:10:55 ng7m syslog: icl_com/us_ctrl.cc: Message is not correct
"PC16"/\
3 from nc7j.
Later on in the log....
Apr 28 23:19:32 ng7m syslog: kc7ias?@-15->:BYE^M
Apr 28 23:19:45 ng7m syslog: disconnect. byte = -1, errno =
107/Transport endpo\
int is not connected
Apr 28 23:19:45 ng7m syslog: kc7ias?@-15->:[Disconnect]
Any input would be appreciated.
Thanks everybody!
mg
-- Matthew George mailto:bnlinyr.iidsgz@vitkovice.cz mailto:terhi.victor@logonet.com NG7M