Telnet login receives invalid callsign.

[R1BLH]

Telnet login receives an invalid callsign when attempting to log in. An underscore "_" is prepended to the callsign, causing the session to terminate, and an error entry with the reason "invalid callsign" appears in the security log.

[AI3I]

I'm sorry you're experiencing this; I'll work on reproducing and fixing...thank you!

[R1BLH]

I'm sorry you're experiencing this; I'll work on reproducing and fixing...thank you!

links (to R1BLH)
Ave Obs Ping Next Filters
Callsign Type Started Uptime RTT Count Int. Ping Iso? In Out PC92? Address
OE3XHQ-1 DXSP 16-Mar-2026 0526Z 5d 2h 55m 0.04 2 300 287 Y 89.185.97.27
R1BET-1 DXSP 16-Mar-2026 0526Z 5d 2h 55m 0.00 2 300 297 Y 81.200.146.29
R1BLH-2 DXSP 21-Mar-2026 0814Z 7m 19s 999.00 1 300 17 local
R5ACQ-1 DXSP 16-Mar-2026 0526Z 5d 2h 55m 0.02 2 300 297 Y 95.84.184.191
RC3C-2 DXSP 16-Mar-2026 0526Z 5d 2h 55m 0.01 2 300 287 Y 81.25.49.85
R1BLH de R1BLH-1 21-Mar-2026 0821Z dxspider >

I think that RTT issue of the connection to the pyCluster (R1BLH-2) has the same reason.

[AI3I]

Telnet login now strips telnet IAC negotiation bytes before validating the entered callsign, which fixes the invalid leading-character/garbled login path. There is direct regression coverage for the sanitized login-line path. Closing as resolved in the current tree.