I hit a problem, and I need to roll back around december 2024 to fix my bug. I telnet to my G8BPQ node and try connecting to unknown station, the packet is OK. VE2YAG>TEST SABM 15 bytes.
If I try to connect to know station (station in node list) on radio port, the KISS packet seem corrupted, 35 bytes insteed of 15 bytes for SABM. Ihex dump the kiss packet to see what wrong, the packet have valid adressing: VE2YAG>VA2AIG-1 but control byte and PID seem corrupted.
As you see in capture, control byte (15e bytes) is 0xBF invalid control byte and PID is 0x82 (NETrom pid is 0xCF) And anyway, SABM do not have a PID, only for I ou UI frame. packet is too big of 20 bytes.
24.82 and 24,75 have this bug, roll back randomly far enough to 6.0.24.52 fix them problem.
I hit a problem, and I need to roll back around december 2024 to fix my bug. I telnet to my G8BPQ node and try connecting to unknown station, the packet is OK. VE2YAG>TEST SABM 15 bytes.
If I try to connect to know station (station in node list) on radio port, the KISS packet seem corrupted, 35 bytes insteed of 15 bytes for SABM. Ihex dump the kiss packet to see what wrong, the packet have valid adressing: VE2YAG>VA2AIG-1 but control byte and PID seem corrupted.
As you see in capture, control byte (15e bytes) is 0xBF invalid control byte and PID is 0x82 (NETrom pid is 0xCF) And anyway, SABM do not have a PID, only for I ou UI frame. packet is too big of 20 bytes.
24.82 and 24,75 have this bug, roll back randomly far enough to 6.0.24.52 fix them problem.