Dangling socket on failed connection

[drboone]

This Pat connection attempt:

L[ax25]> connect seoc
2022/05/04 17:18:03 Connecting to W8CMN-2 (ax25)...
2022/05/04 17:18:05 Connected to W8CMN-2 (AX.25)
*** Failed to Connect
2022/05/04 17:18:10 Exchange failed: connection lost

whose packets look like this:

nino: fm KB8ZQZ to W8CMN-2 ctl SABM+ 17:18:03.775245 
nino: fm W8CMN-2 to KB8ZQZ ctl UA- 17:18:05.343934 
nino: fm W8CMN-2 to KB8ZQZ ctl I00+ pid=F0(Text) len 22 17:18:08.020993 
0000  *** Failed to Connect
nino: fm KB8ZQZ to W8CMN-2 ctl RR1- 17:18:08.038677 
nino: fm W8CMN-2 to KB8ZQZ ctl DISC+ 17:18:10.157056 
nino: fm KB8ZQZ to W8CMN-2 ctl UA- 17:18:10.177195 

leaves this dangling socket:

Active AX.25 sockets
Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
W8CMN-2    KB8ZQZ-0   ax0     LISTENING    001/000  0       0

Exiting pat interactive and restarting clears the dangling socket.

[martinhpedersen]

Thanks for the detailed report 😊

[martinhpedersen]

This was possibly fixed by b3b4be1, which will be included in the next release of Pat (>v0.12.1). Please report back once released. Thank you 🙂