iGate

Bridge RF packets to and from the APRS Internet System

An iGate (Internet Gateway) connects your local RF APRS network to the worldwide APRS-IS (APRS Internet System). Graywolf supports bidirectional gating — forwarding packets from RF to the internet and from the internet back to RF.

RF → APRS-IS (Connection)

iGate RF to APRS-IS tab showing server, port, callsign, and passcode settings
Connection settings for the APRS-IS network

The first tab configures the APRS-IS connection used for both directions. When enabled, graywolf connects to an APRS-IS server and gates eligible RF-heard traffic up to the internet.

FieldDefaultDescription
Enable iGate Off Master switch for the iGate
APRS-IS Server rotate.aprs2.net APRS-IS server hostname
Port 14580 APRS-IS server port
Callsign Login callsign (e.g., N0CALL-5)
Passcode -1 APRS-IS passcode. -1 = receive-only (no TX to IS).

The APRS-IS passcode authenticates your station for sending data to the network. Use -1 for a receive-only iGate that monitors APRS-IS without contributing. To generate a valid passcode, use an APRS passcode calculator with your callsign (without SSID).

APRS-IS → RF

iGate APRS-IS to RF tab showing server filter and gating rules
Server filter and IS→RF gating rules configured for a single station

The second tab controls what you receive from APRS-IS and what gets gated to RF. There are two layers of filtering:

Both layers are needed because APRS-IS filter syntax cannot express everything the gating rules can. For example, there is no server-side filter for “messages addressed to a specific callsign” — you would need to pull all messages (t/m) and filter locally with a Message Dest rule.

APRS-IS Server Filter

The APRS-IS Server Filter field is the filter string sent to the APRS-IS server at login. If left empty, no packets are received.

IS → RF Gating Rules

Rules are evaluated in Priority order (lower = first). The first matching rule decides whether the packet is allowed or denied. If no rule matches, the packet is denied.

FieldDescription
Type Match type: Callsign, Prefix, Message Dest, or Object
Pattern Value to match against (e.g., NW5W-12, W5)
Action Allow or Deny
Priority Evaluation order (lower = evaluated first)

IS→RF gating transmits on the air. Only enable this if you have a valid amateur radio license, proper PTT and channel configuration, and understand the impact on your local APRS channel. A misconfigured IS→RF gate can flood a busy frequency.

Example: Gate a Single Station

To gate only packets from NW5W-12 to RF, set the APRS-IS Server Filter to b/NW5W-12 (so APRS-IS only sends you that station’s packets) and add a gating rule to allow them through:

APRS-IS Server Filter: b/NW5W-12

Type:     Callsign
Pattern:  NW5W-12
Action:   Allow
Priority: 100

Simulation Mode

Simulation mode lets you test your iGate configuration without actually connecting to APRS-IS or transmitting. Packets that would be gated are logged instead. Toggle it via POST /api/igate/simulation or the web UI.

Use simulation mode when first setting up your iGate to verify that filters are working as expected before going live.

Automatic Behaviors

The iGate automatically handles several edge cases:

API Reference

MethodEndpointDescription
GET/api/igate/configGet iGate settings
POST/api/igate/configUpdate iGate settings
GET/api/igate/statusReal-time connection status and counters
POST/api/igate/simulationToggle simulation mode
GET/api/igate/filtersList RF filter rules
POST/api/igate/filtersCreate a filter rule
PUT/api/igate/filters/{id}Update a filter rule
DELETE/api/igate/filters/{id}Delete a filter rule