Very interesting testing that I did yesterday on this issue. I run pat on raspberry pi 3B+ Kernel 5.15.84-v7+
I'm one of the guys that gets this message
2023/01/25 06:44:17 Connecting to AE4ML-10 (ax25)...
2023/01/25 06:44:17 Unable to establish connection to remote: address already in use
My kernel information
pi@pat-mbx:~ $ hostnamectl
Static hostname: pat-mbx
Icon name: computer
Machine ID: a5eca8118bed467c91eca99db51e5b45
Boot ID: 6cb60b7a9a7e41829b2d0501aa3c2de2
Operating System: Raspbian GNU/Linux 11 (bullseye)
Kernel: Linux 5.15.84-v7+
Architecture: arm
I get 1 transmission and then a failure, or so I thought.
I have the luck of 4 RMS gateways in the region that are accessible either direct or via a hop or 2.
My test was this . I rebooted the pi and send the first to my closest gateway. The initial message went perfectly. and then the second one failed. I didn't reboot or restart services.
I resent the message to a second gateway via 1 hop and it worked. I created a second message and sent it to the same gateway and it failed. I repeated this process to the third and fourth gateways all with the same behavior . The first message works and the second message fails.
This tells me atleast with the failure I can still send my message via a second or third route. but why does it hold the last known gateway in a state of already in use ? with no ability to send a message via that path ?