Subj : Re: Modem/Dialup options for Mystic
To   : dejavu
From : Zip
Date : Thu Jun 18 2020 22:22:02

Hello dejavu!

On 17 Jun 2020, dejavu said the following...
 de> it out as see if it works for me, it looks like it was created for RHEL
 de> or CentOS from the directory names, I run Debian and I'm a little rusty

Actually it was created on a Debian 10.4 machine.

You will need the "liblockfile-bin" and "socat" packages installed and
perhaps something more.

 de> right now, after a long break and I'm not sure I could implement your
 de> code without requiring several stiff drinks and basic instructions.file
 de> :)

:)

Here you go:

1. Put the files in place, the paths are in the ZIP file.

2. chown root:staff /usr/local/sbin/modem-frontend.sh

3. chmod 0755 /usr/local/sbin/modem-frontend.sh

4. Rename the /etc/systemd/system/modem-frontend@ttyUSB0.service.d directory
to match some part of the name of your modem device, e.g. if your modem is
/dev/modem you might want to:
mv /etc/systemd/system/modem-frontend@ttyUSB0.service.d \
/etc/systemd/system/modem-frontend@modem.service.d

This is to allow for different configuration for different devices (modems),
if you have multiple modems.

5. Edit /etc/systemd/system/modem-frontend@<your modem device 
shortname>.service.d/local.conf:

5a. Set User= and Group= to a user on your system used for BBS stuff, i.e.
not a highly privileged user. You might even want to try User=nobody and
Group=nobody to see if that would work.

5b. Change the Environment=... lines to match your configuration, e.g.
specify your modem device, serial port speed and other stuff. The defaults
are under the "CONFIGURATION" heading in /usr/local/sbin/modem-frontend.sh;
you only need to set environment variables for the things you want to change.

NOTE: The modem init string needs to tell the modem to auto-answer;
modem-frontend.sh doesn't actually send an answer command (ATA).

6. Make systemd aware of your changes:
systemctl daemon-reload

7. Try starting it:
systemctl start modem-frontend@<your modem device shortname>
....e.g.:
systemctl start modem-frontend@modem

8. Check the output:
systemctl status modem-frontend@<your modem device shortname>
....e.g.:
systemctl status modem-frontend@modem

9. In case of failure, stop the service:
systemctl stop modem-frontend@<your modem device shortname>
....e.g.:
systemctl stop modem-frontend@modem
....and try to figure out what the error could be.

10. If all is OK, set the service to auto-start at boot time:
systemctl enable modem-frontend@<your modem device shortname>
....e.g.:
systemctl enable modem-frontend@modem

The systemd stuff is because Debian switched to systemd a while back instead
of using traditional /etc/init.d scripts for services.

It's good to know that modem-frontend.sh will complain about the incoming
RINGs as "unknown" (it is waiting for CONNECT); this is known and OK. :)

de> Also, I see in the script where it references a variable for the BBS's de>
IP and the BBS's port number, however I don't see any any of the files  de>
where that variable is defined.

The defaults are under the "CONFIGURATION" heading at the beginning of the
script, i.e. 127.0.0.1 as IP and 2323 as port.

If one doesn't set the environment variables BBS_HOST or BBS_PORT in the
systemd files the scripts uses the defaults.

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/04/21 (Linux/64)
 * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

.