Building a reliable Winlink setup: client, modes, gateway selection and message handling
- Replies 2
- Views 56
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Dan 1 post
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
This thread is for pooling what a working Winlink Express setup needs, since the pieces are easy to configure in the wrong order. The aim is a station that works when the internet is down, not just one that works on a good day through Telnet.
Start with the account and the client. Winlink Express is the Windows client most people use. You enter your callsign and a Winlink password, and the system ties your mailbox to that callsign. Passwords are case-sensitive, and the account needs a working recovery address so a forgotten password does not become a problem during an exercise. Over RF the gateway issues a challenge and your client answers it, so the password is not sent in the clear. The first account setup and the channel list update both need internet, so do them before you need them.
Winlink Express treats each connection method as a session type: Telnet Winlink, Packet Winlink, VARA HF, VARA FM, ARDOP, Pactor, and the matching P2P types. Telnet reaches the Winlink system over the internet and is useful for testing your account, templates and message flow with no RF variables. Packet, VARA FM and the HF modes reach an RMS gateway (a radio station that relays traffic to and from the Winlink system). P2P skips gateways and the internet entirely, linking two stations directly.
Hardware splits into two families. Packet can use a hardware TNC or a software TNC fed by a sound card, and VARA and ARDOP are sound card modes. Pactor needs a dedicated modem, usually from SCS, and it is not a sound card mode. The questions I would like to compare notes on: which modes do you set up first, how do you decide between a gateway and P2P, and what do you check before trusting a station for an exercise?
For message handling, the Outbox, Sent Items and Drafts folders matter more than people expect. A message is not sent until it is posted to the Outbox and a session actually runs. Forms such as ICS-213 come from the template selector, open in a browser window, and attach structured data. The recipient needs a compatible Winlink client to see the form properly, otherwise they mostly see the text body. Does anyone have a clean pre-exercise checklist?
Link to comment
https://www.hamradiobase.com/forums/topic/10887-building-a-reliable-winlink-setup-client-modes-gateway-selection-and-message-handling/Share on other sites