This is probably a stupid question, but ...
Because of machine/logbook software limitations, I routinely use AX25
from Windows 98 to access a local node which is not only an AX25 box,
but also an interface to TCP/IP. If I go through the node to another
AX25 node and then to the DXCluster I get normal responses. The traffic
to/from the Cluster is definitely two-way. The node runs SuSE 6.2 and
seems to be very solid. (I use SuSE 6.4 for everything else).
Now if I go through the TCP/IP interface on the same node to a different
SuSE-based DXCluster, the traffic is one way. That means I can connect,
but after that nothing I send results in a response (that I can see)
from the Cluster, which in this case is running a version of DXSpider.
I can even be left apparently connected for hours after the Cluster
thinks I'm long gone. In other words, disconnects seem to go missing.
I am definitely on a list of users permitted to use this particular
AX25-TCP/IP interface node to reach the DXCluster, so why does the
interface apparently only work one way ??
Yes, I have asked the sysops of the Cluster and the AX25-TCP/IP node,
but it seems that between us we may be missing something obvious.
Any ideas I can pass on to the sysop(s) will be gratefully received.
73 John G3JAG
----------------------------------
E-Mail: John - G3JAG <[EMAIL PROTECTED]>
Date: 16-Jul-2000
Time: 22:01:31
This message was sent by XFMail 1.4.6-1
----------------------------------
