¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

TCP Master/Slave question


 

John,
?
As the TCP-SLAVE side of a connection I assumed that I would never initiate a connection. I am seeing the following:
?
13:35:48T N5MDT-13>N4NVD-3 Port=2 <XID C P> 2=21 3=22a486 RX Paclen=256 RX Window=7?
?
I have different ports for AXUDP (port 1) and AXTCP (port 2.)
The above line is obviously the Port 2 Monitor and it looks to me like it is a connection request being initiated by me.? However, I am seeing a similar line to a well established and connected AXTCP link to N3HYM.
?
?
Now, earlier today, I switched N4NVD from TCP (port 2) back to UDP (port 1) and restarted.? The UDP route is stable using port 1.? However, I am still seeing the above line in the port 2 monitor.
?
So, what exactly is the XID packet?? When should I expect to see these cease for N4NVD?
?
The axipcache1.cfg file contains only port 1 connections.? I do not see a port 2 cache file. Is there one that I can empty to stop these XID packets to N4NVD sooner than letting it time out on its own?
?
?
Thanks
--
73,
Mark, N5MDT
Montgomery, Texas
?
?
?


 

Those packet finally stopped at 56 past the hour.? They continued for 30 minutes and through several restarts.
?
Still curious about the XID packets.? It seems to be a change from previous versions.
?
?
73,
Mark, N5MDT
Montgomery, Texas
?
?
?


 

¿ªÔÆÌåÓý

Yes, that is a recent change to AXTCP/UDP. An XID is sent before the SABM to attempt to negotiate an ax.25 V2.2 connection. If the other send replies with an XID response a SABM is then sent. AXTCP Master/Slave only selects which end established the TCP connection, not which end opens the ax.25 link.


On 20/05/2025 15:18, Mark Taylor wrote:

Those packet finally stopped at 56 past the hour.? They continued for 30 minutes and through several restarts.
?
Still curious about the XID packets.? It seems to be a change from previous versions.
?
?
73,
Mark, N5MDT
Montgomery, Texas
?
?
?