FOX Relay — field guide

For an introduction and current availability, start with the FOX Relay overview. This guide describes the current Avalonia source; an older installed test build may not include every feature. Use the installation instructions supplied with the build Tom invited you to test.

Getting connected

1. Select a saved site/device, choose a recent connection, or open a new connection.
2. Pick SSH, Telnet, Rlogin or Serial and enter the relevant target or serial settings.
3. Check the destination, credentials and connection options before connecting.
4. Review host-key prompts and connection-security information rather than accepting an unexpected identity automatically.
5. Keep separate device work in its own session tab. A disconnected retained tab is not a live session.

Network sessions need reachability and authorized credentials. Serial needs a compatible adapter, driver, port and device settings. On Linux or macOS, local permissions can prevent opening a serial device even when the adapter is listed.

Security indicators and older equipment

Legacy SSH algorithms require explicit opt-in. The negotiated connection determines the indicator:

• Green: SSH algorithms with no flagged practical break.
• Yellow: legacy cryptography with a reduced security margin.
• Orange: broken cryptography; treat the connection as no more private than Telnet.
• Red: unencrypted network traffic, including protocols such as Telnet.

A green indicator is not a security certification for the device. Telnet, Rlogin and plain FTP do not protect traffic from someone who can observe the network path. Serial is a separate, physical connection. Compatibility still depends on the device and transport; no connection method guarantees access to every device.

Sites, credentials and history

Saved sites keep related devices together. Recent successful connections and session logs serve different purposes: history helps you reconnect, while logging retains terminal output according to your options.

Passwords belong in the saved-site/credential controls, not Scratch Pad or command history. Secure storage depends on the operating system and access to its secret service. On macOS, Relay uses Keychain to protect its local credential storage; do not confuse that with AirWitness's different Wi-Fi passphrase behavior. An unavailable or denied secret store is not permission to fall back to a plaintext password file.

Treat exported site packages, logs, command macros and device output as potentially sensitive. Review what is included before sharing them.

Files and commands

Each session can expose the supported file tools: SFTP Explorer, FTP Transfer and serial XModem. They need their own working transport and device support; opening a terminal does not prove a file-transfer service is available.

Review a command macro before sending it. A saved command may change a device configuration; the name of a macro is not a guarantee that it only reads information.

Plugins

Use Plugin Manager for the plugins offered to your test build. LLDP Mapper, Switch Health and configuration tools each have their own target selection and supported vendor/command sets.

Inspect targets, credentials and command previews. A discovered LLDP neighbor is evidence of what the device reported, not an automatic authorization to rename ports or write configuration. A health result describes completed checks and available evidence, not a general certification of the switch.

Plugin behavior can require access to a real device, appropriate credentials and permissions. Developer sample plugins are not part of the normal tool catalog.

Scratch Pad and preferences

Scratch Pad holds local working notes independently of saved sites. Dock or float it as the task requires. Notes are not an encrypted credential vault or automatically a complete audit record.

Terminal options include font, scrollback and keyboard behavior. Logging and credential persistence have their own settings; check these when moving between test builds or operating systems.

Installation and updates

Relay is invitation-only. Use the package and instructions supplied to you, and use Help → Check for Updates for the update path supported by your installed build. Do not substitute an older development package or infer public availability from an update feed.

Windows, Linux and Apple Silicon Mac packaging differ. Follow the actual installer supplied with the package rather than generic instructions to bypass operating-system warnings. Stop and ask Tom if a downloaded package has an unexpected publisher, signature or warning.

Removing the application and removing its saved user data are different actions. Keep a backup of the data you need before moving machines or performing a clean removal.

Questions and test feedback: admin@airwitness.net.