====== Mystic and other BBS programs ======

Any BBS program that can make an outgoing RLogin connection can use the [[doorhub:connector|connector]]. Set up the connector exactly as for Synchronet; only the door entry is different.

===== What the connector expects =====

An RLogin connection to ''local_interface:local_port'' (normally ''127.0.0.1:9998'') with the fields in the order Synchronet and SyncTERM use:

^ RLogin field ^ What to send ^
| client user name | the caller's hub password. Any string, but it must stay the same for that caller. |
| server user name | the caller's name. The connector adds ''[TAG]''. |
| terminal type | the game code (for example ''lord''), or blank for the hub menu |

===== Mystic =====

//Not yet tested with Door Hub; reports welcome.//

Add a menu item with the command **IR** (outbound RLogin) and data like:

<code>
/addr=127.0.0.1 /port=9998 /user=@USER@ /pass=hubpass /term=lord
</code>

  * Mystic sends the password first, which is the order the connector expects.
  * Use ''/term='' with a game code, or leave it out for the hub menu.
  * With a fixed ''/pass'' every caller has the same hub password. That's fine: the hub only uses it to check that a returning name is the same person from your board.
  * The menu editor and IR options are described in the [[http://wiki.mysticbbs.com/|Mystic wiki]].

===== Using the rlogin program =====

If your BBS can run a Linux command for a door, the system ''rlogin'' program works too, the same way DoorParty's Mystic script does it:

<code bash>
rlogin -p 9998 -l "CallerName" localhost
</code>

''rlogin'' sends your Linux user name as the hub password (so every caller has the same one) and no game code, so callers get the hub menu. A terminal type can be passed with ''TERM=lord rlogin ...'' on systems whose rlogin sends ''$TERM''.

===== Other software =====

If your BBS can only telnet out, it can't use Door Hub directly: the hub needs the caller's name, which telnet doesn't carry. Ask on your BBS software's support channels about outbound RLogin, or contact the hub's sysop.