AGW Packet Engine interfaces

The AGW Packet Engine (AGWPE) is a program created by George Rossopoylos, SV2AGW. It is a Windows application intended to share a TNC across a local area network, and that application can be downloaded at SV2AGW.com.

While George has stated that it is not OK to reverse-engineer and emulate his protocol, there are several packages that do exactly that for systems other than Windows. These include Direwolf and ldsped.

Each of these programs creates a server that listens on a TCP/IP port for client connections, then serves packet radio data to each client from whatever interfaces are connected to the server.

Xastir is able to use any AGWPE-compatible server as an interface for packet data.

Setting up an AGWPE interface

• Activate on Startup?: Should this interface be turned on when Xastir is launched?
• Allow Transmitting?: Can we send data to this interface?
• Host: the host on your LAN that is running the AGWPE-compatible server
• Port: The TCP/IP port on which the AGWPE server is listening (defaults to 8000)
• Pass-code: Some AGWPE servers can be configured to require a pass code to connect. Enter it here if you need one.
• Reconnect on NET failure?: If the connection to the server is dropped for some reason, should we keep trying to reconnect?
• Transmit RadioPort: If the server has multiple radio ports, which one should this interface refer to?
• IGate options: Determine whether or not to gate radio traffic to or from the internet. Do not enable unless you understand the implications of running an IGate and are willing to take responsibility for everything that runs through it.
• UnProto Paths: The paths your transmitted packets should take through the RF environment. WIDE2-2 is a safe default unless you have special needs.