Max found a good name for this phenomenon!
I think it has to do with CLX's ability to directly serve the connect
request to an AX.25 socket. In a nowadays Linux installation, the
AX.25 utilities come with a program named ax25d. This is a so-called
meta-daemon which is responsible to start up different programs
depending on which SSID is being called. A similar application is
the program inetd which runs in every Unix system and depending on
which port number was connected, starts up a different service program.
When CLX was started, this program (ax25d) did not exist and gthe
design was so that every connect request was directly served by CLX.
Later, when people started putting several things on one node, we
created a special configuration switch, the "ax25:" command, to
supress CLX serving that port. This is activated by putting
ax25: none
into your clx_par file.
What seems to happen is that both ax25d and CLX try servicing the
connect request (in a special condition, because it normally seems to
work) and so the "garbage connection" is somehow created.
So please try to follow Angel's suggestion and actively disable
the AX25 support in the config file. Let's see if the theory is
true.
73 Ben, DL6RAI (@work)
-- Bernhard Buettner - Systemmanagement, LFK-FTE4 Telefon: 089/607-26921 Email: xxdd@kerailya.tunkki.fi Fax: 089/607-22172