Skip to content

Instantly share code, notes, and snippets.

@eggy
Last active August 31, 2020 20:18
Show Gist options
  • Save eggy/f8a2775e10d52579c8e34f146db0ba1e to your computer and use it in GitHub Desktop.
Save eggy/f8a2775e10d52579c8e34f146db0ba1e to your computer and use it in GitHub Desktop.
ENiGMA½ BBS on a Raspberry Pi
ENiGMA½ BBS on a Raspberry Pi
Notes on setting up ENiGMA½ BBS and connecting it to a messaging network as a point node.
The notes assume you have setup the Raspberry Pi with ssh access.
My setup:
- Raspberry Pi, running raspbian fsxNet (21:4/143.1) “Eggy Pi BBS”
- Boss node is running Mystic BBS connected to fsxNet (21:4/143) “Eggy BBS”
ENiGMA½ BBS Side
On the Raspberry Pi setup ENiGMA½ BBS per github instructions:
curl -o- https://raw.githubusercontent.com/NuSkooler/enigma-bbs/master/misc/install.sh | bash
The script will automatically download and setup all the dependencies for ENiGMA½ BBS
To configure enigma-bbs, run the following from the enigma-bbs installation folder:
./oputil.js config new
This is a shortened version of getting it installed, please consult the enigma-bbs documentation for more details.
Follow enigma-bbs documentation on how to configure enigma-bbs for messaging networks.
If using the master, I had to fix a problem when using unzip, the beta branch has the issue completely resolved.
BINKD Side
Install and compile binkd from https://github.com/pgul/binkd
enigma-bbs my paths section
scannerTossers: {
ftn_bso: {
paths: {
outbound: /home/e/bbs/ftn_out/
inbound: /home/e/bbs/ftn_in/
secInbound: /home/e/bbs/ftn_secin/
reject: /home/e/bbs/packets/rejected/
retain: /home/e/bbs/packets/good/
}
}
I have created the following dirs based on enigma-bbs my paths:
mkdir -p /home/e/bbs/ftn_out
mkdir /home/e/bbs/ftn_in
mkdir /home/e/bbs/ftn_in_tmp
mkdir /home/e/bbs/ftn_secin
I also adjusted /var/log/binkd so that my user ‘e’ has write access to it
In my binkd.conf, I had to add an extra outbound folder to the outbound path defined in enigma-bbs’s scannerTossers::ftn_bso::paths, as enigma-bbs appends an outbound folder to its outbound path for legacy compatibility reasons. Below is a working binkd.conf
-------------------------------
# Number @ end is the root zone
domain fsxnet "/home/e/bbs/ftn_out/outbound" 21
# Our fsxNet address
address 21:4/143.1@fsxnet
sysname "Eggy Pi BBS"
location "Chicago, IL"
sysop "eggy"
nodeinfo 115200,TCP,BINKP
try 10
hold 600
send-if-pwd
log /var/log/binkd/binkd.log
loglevel 4
conlog 4
percents
printq
backresolv
inbound /home/e/bbs/ftn_secin
inbound-nonsecure /home/e/bbs/ftn_in
temp-inbound /home/e/bbs/ftn_in_tmp
minfree 2048
minfree-nonsecure 2048
kill-dup-partial-files
kill-old-partial-files 86400
prescan
#Primary BOS node
node 21:4/143@fsxnet -md bbs.eggy.cc:24554 XXXXXXX c
# our listening port (default=24554)
# use a different port for basic added security-ish (e.g. avoid generic scans)
iport 54554
pid-file /var/run/binkd/binkd.pid
# touch a watch file when files are received to kick of toss
flag /home/e/bbs/ftn_in/toss!.now *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa? *.pkt *.tic
# nuke old .bsy/.csy files after 24 hours
kill-old-bsy 43200
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment