I think this setup has caused me more trouble than it is worth... I got
rid of TNOS today and have the Cluster working with the kernel AX25
stuff, I now have the ax25 parameter in the clx_par file set to none.
Local connects to my cluster are working great using the Linux ax25
kernel code. I will let you know if the garbage callsign problem shows
up again.
Now that I dumped TNOS I will need some help creating a AXIP link to the
node I get my CLX feed from.
I will post another message related to the problems I'm having creating
the AXIP link, maybe someone here can help me out with the ax25ipd
problem I'm having. Right now the link is down, so my local users are
not getting the spots that they were used to. :)
Using the kernel ax25 code will be best in the long run.
mg
-----Original Message-----
From: mqec@mail.dy.fi
<dfanuw@avtechpulse.com>
To: buj@migrationsverket.se <igxcyorb@xmcoinc.com>
Date: Wednesday, April 29, 1998 12:15 AM
Subject: Re: Another Garbage Call
>Dear Max,
>
>> I got another 'Garbage Call' connection this afternoon at NC7J, this
>> time it happened with a different user. I noticed that this guy
>> disconnected and then reconnected just fine.
>>
>...
>> ax25: NC7J
>
>This should be "none". Please give it a try. As I tried to explain
>yesterday, the ax25: config command in the clx_par is only for making
>CLX react directly on an AX25 socket connect request. The default
>nowadays is to go through ax25d.
>
>73 Ben, DL6RAI
>--
>Bernhard Buettner - Systemmanagement, LFK-FTE4 Telefon:
089/607-26921
>Email: zxqmig.agyyzgzdev@lufthoheit.net Fax:
089/607-22172
>