Packet Radio SSID and Alias convention

SSIDs

SSIDs are used to identify separate services running under the same call sign. For example, you may have a node, a BBS, and a chat server all running on your home packet station. All three can’t operate as exactly the same call, so an SSID is added on the end to differentiate between them.

There isn’t a fixed convention on which services should use which SSID, but as a group, it would be helpful if we had a “standard” we used, just for clarity. It doesn’t really matter what the standard is, as long as we document it, and stick to it.

With that in mind, I would like to propose the following :

  • M7GMT – Your “raw” call sign without an SSID (this implies -0). Your personal terminal. Use when you connect to other systems, are having a chat, etc.
  • M7GMT-1 – BBS (mailbox). This is somewhat of a convention already, with many TNC’s in-built mailbox defaulting to -1.
  • M7GMT-3 – Chat
  • M7GMT-5 – Node

We can use SSIDs 1 to 15, so if there are other services that several stations run (e.g. DX Cluster), we can add a new line here to keep things organised.

Aliases

Aliases are used as a “friendly name” for packet stations, allowing you to connect without having to remember whch SSID you need. For example, my node currently has the alias WYMOND (for Wymondham), so you could connect by typing either connect M7GMT-5 or connect WYMOND.

Aliases can be up to 6 characters, and should be unique on the packet network. The idea is for these to be memorable, so I would be interested in your feedback on the following formats:

  1. WAVExxWAVE followed by a 2 letter ID. First letter is first letter of city/town/village. Second letter is type: D for digipeater, N for node, B for BBS, and C for chat. Examples:
    • WAVEWD:MB7NAF = Wymondham Digipeater
    • WAVEAN:M7GMT-5 = Attleborough Node
  2. WAVxxxWAV followed by a 3 letter ID. As option one, but this allows an extra character for station ID, which would help prevent potential clashes as the network grows. Examples:
    • WAVBCC:GB7MSX-3 = Burgh Castle Chat
    • WAVWYD:MB7NAF = WYmondham Digipeater
    • WAVATN:M7GMT-5 = ATtleborough Node
  3. TWxxxxTW followed by a 4 letter ID. This allows even more flexibility for the station ID, but is perhaps less clear that they are all associated. Examples:
    • TWBUCC:GB7MSX-3 = BUrgh Castle Chat
    • TWWYMD:MB7NAF = WYMondham Digipeater
    • TWATTN:M7GMT-5 = ATTleborough Node

Discuss

Again, what we settle on is less important than sticking to the standard. I would love your feedback on this, other formats to consider, and so on.

Happy packeting!

Our first packet net

It’s been talked about for a long time, but we’ve finally set a date for our first packet net; Saturday 17th September at 20:00 – 144.950FM.

With so few of us within simplex range of each other, digipeating will be essential, so please make sure this is enabled in your TNC if you’re taking part. The more stations we can get involved, the better this will work, so if your station is packet-capable, please dust off your TNC and join in.

Stations confirmed so far:

  1. M0XTF Tony – Bungay
  2. M0VCX John – Watton
  3. M1MIT Tim – Norwich
  4. M5MSX Martin – Gt. Yarmouth
  5. M7GMT Rik – Attleborough

As this will be the first attempt, we’ll be figuring out who can hear who, and exactly how paths should be configured, but if all goes well, this could become a regular thing, perhaps alternating with a 2m JS8 net. We could call it SaturDATA. 🙂

GB7ZAH – On air testing

Our second packet station (GB7ZAH) switched on today for full testing. This has been a long time coming and joins GB7MSX in the East of Norfolk. There will be periods where the station may not be available while we change configs in the backend.

A huge thanks to Martin M5MSX for his help with configuration hits, and M7GMT for testing on air.

The next step is to get MB7NAF (M1MIT) node on the air.

If you’d like to use either GB7MSX/GB7ZAH you can connect via 1200Baud AX.25 on 144.950NFM.