Joining a hub

This page is for sysops who want their callers to play the games on a Door Hub. You need three things: an account from the hub, the connector running on your BBS machine, and a door entry on your BBS that sends callers to the connector.

• A BBS that can open an outgoing RLogin connection for a caller. Synchronet does this with doorhub.js. Mystic does it with the IR menu command. See Mystic and other BBS programs for others.
• The connector for your system, from the downloads: doorhub-connector for Linux (x64 or arm64, such as a Raspberry Pi with a 64-bit system) or doorhub-connector.exe for 64-bit Windows.
• Outgoing internet access to the hub's SSH port (2022 unless the hub says otherwise). Nothing needs to be opened on your router: the connector only makes outgoing connections, and it listens only on your own machine.

Ask the hub's sysop for an account. Tell them:

• your BBS name, and
• the system tag you'd like: 2 to 8 letters or digits, for example KAL. It appears in front of your callers' names on the hub ([KAL]Heisenberg), so pick one people will connect with your board.

For the Kalgoorlie Door Hub, email slaterm@theiguru.au.

The hub sends you a filled-in doorhub-connector.ini. It holds your hub password. Keep it on the BBS machine only, readable by the BBS account only.

Put the connector and its ini in a folder on the BBS machine and run it as a service. The connector has the steps for Linux and Windows and explains every setting.

• Synchronet: copy doorhub.js to your mods folder and add a door. See Synchronet set-up.
• Mystic and others: see Mystic and other BBS programs.

You can add one entry that shows the hub's game menu, and entries that go straight into one game. Ask the hub for its list of game codes. The Kalgoorlie Door Hub's codes are on the Door Hub start page.

1. Check the connector is running and listening. Linux: ss -ltn | grep 9998. Windows: netstat -an | findstr 9998.
2. Log on to your BBS and pick the hub entry. You should see “Connecting to the Door Hub, please wait …” and then the hub menu or the game.
3. The connector's log shows each session:

2026/11/09 10:42:32 Connected to hub hub.example.com:2022
2026/11/09 10:42:32 [KAL]Heisenberg connected to hub, door: "lord"
2026/11/09 10:57:47 [KAL]Heisenberg disconnected

If something goes wrong, see Troubleshooting.

• On the hub your callers are [TAG]Name. On the hub's door BBS, which the games see, they appear as Name (TAG), because Synchronet doesn't allow user names starting with [.
• Names may be up to 30 characters and may not contain [ or ].
• The first time a caller connects, the hub remembers their password (made by doorhub.js and kept in their user properties). If a different password arrives later for the same name, the hub refuses it. That stops a new caller who takes an old name on your board from playing as the old caller. If you rebuild your user base, ask the hub sysop to reset the affected players.
• The hub may limit how many of your callers play at once (10 by default). Extra callers see a “try later” message.

Door Hub and DoorParty don't share anything and can run on the same BBS. DoorParty's connector usually uses port 9999, so Door Hub's examples use 9998.

To join more than one Door Hub, run one connector per hub, each with its own folder, ini and local_port. On Linux give each its own systemd unit. On Windows the service name is fixed in 0.1.0, so run the second connector some other way, for example from a scheduled task at start-up.

Stop and remove the connector (sudo systemctl disable –now doorhub-connector on Linux, or doorhub-connector.exe service remove on Windows), delete its folder and doorhub.js, remove the door entry, and let the hub's sysop know so they can remove your account.