Request preparation

• I used an AI assistant to help structure this request
• I checked for existing issues covering the same feature

What would you like?

What

Add an Authorization Code (password) input field to the TGXL, PGXL, and
Antenna Genius connection configuration dialogs in AetherSDR. This field is
required when connecting to these devices over a direct WAN/internet connection
without a VPN.

Currently AetherSDR only supports LAN auto-discovery for all three devices,
with no way to enter the Auth Code that the 4O3A API requires for authenticated
remote connections.

Why

The 4O3A remote connection protocol for the TGXL (TCP port 9010), PGXL, and
Antenna Genius requires an Auth Code that is set on each device during local
LAN setup. When operating remotely without a VPN — using direct port forwarding
from the router to the device — the client must present this Auth Code to
authenticate.

Without a field to enter this credential in AetherSDR, remote operation of all
three devices is impossible unless the operator runs a full VPN between the
remote PC and the shack LAN. This is a significant barrier for operators who
use SmartLink for the FLEX radio but prefer not to run VPN infrastructure just
to control these accessories.

Real-world scenario this blocks today:

• FLEX-8600M operated via SmartLink from a remote location ✅
• TGXL at the shack — cannot connect remotely without VPN ❌
• PGXL at the shack — cannot connect remotely without VPN ❌
• Antenna Genius at the shack — cannot connect remotely without VPN ❌

How Other Clients Do It

The 4O3A Windows application handles this with a Remote Devices
configuration panel where the operator enters:

• Remote WAN IP address or hostname
• TCP port (device-specific)
• Authorization Code (set on the device during initial local setup)

Once saved, the app connects directly over the internet using the Auth Code
for authentication. SmartSDR for Windows does not expose this natively —
operators using SmartSDR remotely with TGXL/PGXL/AG must use the separate
4O3A Windows app alongside it, or run a VPN.

AetherSDR has the opportunity to be the first single application to handle
FlexRadio + TGXL + PGXL + Antenna Genius remote operation natively without
requiring any external tools or VPN.

Suggested Behavior

In the TGXL applet settings, PGXL applet settings, and Antenna Genius
applet settings, add a Remote Connection section to each:

When Remote mode is selected:

1. AetherSDR skips LAN broadcast discovery entirely
2. Connects directly to the specified host:port over TCP
3. Sends the Auth Code as part of the 4O3A API handshake
4. Stores the Auth Code securely in the AetherSDR settings
   (obfuscated or OS keychain — not plaintext)

The Auth Code field should follow the same masked input pattern already used
for SmartLink credentials in AetherSDR.

Example interaction:

1. Operator opens TGXL applet → Settings
2. Switches mode to Remote
3. Enters shack WAN IP, port 9010, Auth Code
4. Clicks Connect → AetherSDR authenticates and TGXL applet becomes fully
   operational from the remote location — no VPN required
5. Same process repeated independently for PGXL and Antenna Genius applets

Protocol Hints

• TGXL remote TCP port: 9010
• PGXL remote TCP port: needs verification from 4O3A API docs
• Antenna Genius remote TCP port: needs verification from 4O3A API docs
  (ports for 4O3A devices are in the 9010–9015 range)
• Auth Code is passed during the TCP handshake as part of the published
  4O3A LAN API — same authentication mechanism across all three devices
• Integration points in AetherSDR: existing TgxlModel, PgxlModel, and
  AG connection classes — this is additive, not a redesign
• No FlexLib or SmartSDR protocol involvement — entirely client-to-device TCP

Additional context:

This is a functional blocker for remote operators, not a convenience feature.
Any operator running a remote shack with TGXL, PGXL, or Antenna Genius and no
VPN infrastructure cannot use these devices at all through AetherSDR today.
The 4O3A Windows app already solves this — AetherSDR needs parity.

Checked for existing issues — no duplicate found covering remote Auth Code
support for TGXL, PGXL, or Antenna Genius.