Good afternoon,
Did some experimenting on a 64-bit machine today. SBBS compiled and does
not seg fault immediately even though SSH/TLS is allowed in the INI file.
So I think that maybe the cryptlib is not compatible with 32-bit linux machines?

I was never able to get the program to fire all the way, though. Using
sudo to start it, it complains that it does not have access to create
various directories and will not bind all of the ports. That later issue
is random... once it would not bind port 80 but bound 23 and 513... next
try, it bound 80 and 513 but not 23 or the ftp port. There were some other random ports unbound, but those were the ones I noticed. I did not change anything between attempts.

I have similar issues if I restart sbbs too soon after stopping it, or
having it seg fault, on the other machine. My assumption is that sbbs (or
the system) does not release the ports immediately. I waited quite a while before the second attempt mentioned above. I actually logged off, logged in
as myself, did some stuff, and logged back on as the bbs user.

All this was with a copy I pulled around Noon or so, EDT.

---
þ SLMR 2.1a þ "Mmmmmmmm.....chocolate."
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net:26
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: cryptlib and other issues
By: Dumas Walker to DIGITAL MAN on Sun May 20 2018 07:19 pm

Good afternoon,
Did some experimenting on a 64-bit machine today. SBBS compiled and does not seg fault immediately even though SSH/TLS is allowed in the INI file.
So I think that maybe the cryptlib is not compatible with 32-bit linux machines?

Okay, good info. Anyone else running 32-bit Linux with a recent SBBS build with SSH and/or TLS working okay?

I was never able to get the program to fire all the way, though. Using
sudo to start it, it complains that it does not have access to create various directories and will not bind all of the ports. That later issue
is random... once it would not bind port 80 but bound 23 and 513... next try, it bound 80 and 513 but not 23 or the ftp port. There were some other random ports unbound, but those were the ones I noticed. I did not change anything between attempts.

See http://wiki.synchro.net/faq:tcpip#bind for details.

digital man

Synchronet/BBS Terminology Definition #47:
SMB = Synchronet Message Base (e.g. smblib)
Norco, CA WX: 62.6øF, 74.0% humidity, 13 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.04-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Okay, good info. Anyone else running 32-bit Linux with a recent SBBS build with
SSH and/or TLS working okay?

Good. :)

See http://wiki.synchro.net/faq:tcpip#bind for details.

I did. I could not find anything with netstat, or that a reboot would fix.
FYI, the error is not a 13 (no access), it is 98, if that helps??

---
þ SLMR 2.1a þ "Buck McCoy?!? He was bigger than opium!"
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net:26
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: cryptlib and other issues
By: Dumas Walker to DIGITAL MAN on Tue May 22 2018 06:18 pm

Okay, good info. Anyone else running 32-bit Linux with a recent SBBS build with
SSH and/or TLS working okay?

Good. :)

See http://wiki.synchro.net/faq:tcpip#bind for details.

I did. I could not find anything with netstat, or that a reboot would fix.
FYI, the error is not a 13 (no access), it is 98, if that helps??

# grep 98 /usr/include/*/errno.h
/usr/include/asm-generic/errno.h:#define EADDRINUSE 98 /* Address already in use */

That means the port (on the specified network interface) is already in use.

Did you try adding REUSEADDR=1 to your ctrl/sockopts.ini file, like the FAQ said?

digital man

This Is Spinal Tap quote #16:
David St. Hubbins: I believe virtually everything I read...
Norco, CA WX: 58.6øF, 82.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.04-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

# grep 98 /usr/include/*/errno.h
/usr/include/asm-generic/errno.h:#define EADDRINUSE 98 /* Address already in use */

Neat! I need to try to remember this trick.

That means the port (on the specified network interface) is already in use.

Did you try adding REUSEADDR=1 to your ctrl/sockopts.ini file, like the FAQ said?

No because it was still in use after a reboot, so I don't think sbbs has
them in use. I *did* try the telnet trick that the FAQ mentions, though. The telnet and ftp ports refused connection, but port 80 did answer (I had
received the '98' on all three of them).

I was not able to see any of them active with a 'netstat' command but I
have to admit I am not 100% on what I am looking at in the output of that command. I suspect, but don't know, that apache may have been loaded
somehow by default. I can check that the next time I fire the system up.
Do you have any other tips on figuring out what might have 21 and 23 in use?

---
þ SLMR 2.1a þ A nudist wedding makes the best man easy to identify.
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net:26
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: cryptlib and other issues
By: Dumas Walker to DIGITAL MAN on Wed May 23 2018 06:40 pm

# grep 98 /usr/include/*/errno.h
/usr/include/asm-generic/errno.h:#define EADDRINUSE 98 /* Address already in use */

Neat! I need to try to remember this trick.

That means the port (on the specified network interface) is already in use.

Did you try adding REUSEADDR=1 to your ctrl/sockopts.ini file, like the FAQ said?

No because it was still in use after a reboot, so I don't think sbbs has them in use. I *did* try the telnet trick that the FAQ mentions, though. The telnet and ftp ports refused connection, but port 80 did answer (I had received the '98' on all three of them).

I was not able to see any of them active with a 'netstat' command but I
have to admit I am not 100% on what I am looking at in the output of that command. I suspect, but don't know, that apache may have been loaded somehow by default. I can check that the next time I fire the system up.
Do you have any other tips on figuring out what might have 21 and 23 in use?

Did you just just run 'netstat' with no arguments? You must include the -l or -a options to display listening ports:

-l, --listening
Show only listening sockets. (These are omitted by default.)

-a, --all
Show both listening and non-listening sockets.

Also, on Linux, you can include the -p option to display the PID/program name that owns the ports listed.

http://wiki.synchro.net/monitor:syslog recommends using the command 'netstat -nap' to monitor socket usage.

digital man

Synchronet/BBS Terminology Definition #34:
LF = Line Feed (ASCII 10, Ctrl-J)
Norco, CA WX: 65.0øF, 71.0% humidity, 6 mph NE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.04-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)