Skip to content

Give a login that reaches a KISS TNC its own exception type #246

Closed

Description

@gx1400

Since 0.4.0-alpha.4 (7bb2078, #232), AprsIsClient fails a login straight away when a line contains FEND (0xC0), which means the other end is a KISS TNC, such as Dire Wolf's port 8001. It throws a plain LoginException. An app can only tell this apart from any other failed login by reading the English message.

AprsMap needs this to show "That's a KISS TNC: add it as a TNC source" instead of "Server unreachable" (its gap G32).

Scope: a LoginException subclass, for example KissTncLoginException. That follows LoginRejectedException, which is also a LoginException, so existing catch (LoginException) code keeps working. The failure should also reach AprsIsConnection's state events as that type. This adds to the public API only; behaviour is unchanged.

Done when:

  • the AprsIsClientTests case for a login that reaches a KISS TNC checks the exception's type, not its message;
  • the new type is listed in PublicAPI.Unshipped.txt.

AprsMap priority 3: nice to have for 0.5.0.

Activity

  1. added this to the 0.5.0-alpha.1 milestone on Oct 17, 2026
  2. added
    enhancementNew feature or request
    blocks: AprsMapBlocks an AprsMap feature issue; see its milestone in APRS-NET/AprsMap
    priority: lowDo if time allows; can move to a later milestone
    on Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    blocks: AprsMapBlocks an AprsMap feature issue; see its milestone in APRS-NET/AprsMapenhancementNew feature or requestpriority: lowDo if time allows; can move to a later milestone

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions