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.
Okay, good info. Anyone else running 32-bit Linux with a recent SBBS build with
SSH and/or TLS working okay?
See http://wiki.synchro.net/faq:tcpip#bind for details.
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?
# 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:
Did you just just run 'netstat' with no arguments? You must include the -l or -a options to display listening ports:
I am trying -lp. I may be very dense but I don't see any of the port numbers I am trying to use (21, 23, 80) anywhere in either list it produces.
Re: netstat
By: Dumas Walker to DIGITAL MAN on Thu May 24 2018 19:21:00
Here is a bit more... I just fired up sbbs in one window, and then did a 'netstat -lp' in another. Now, while sbbs is throwing the 98 errors in the first window, netstat now shows the services in question... telnet, ftp, etc... and shows them as being owned by sbbs.
Quitting sbbs in the first window causes those services to no longer appear on the netstat-lp list when it is executed a second time.
It almost seems like sbbs grabs the ports and then forgets it is the one that has them. :)
You have to use the -n option for it port numbers instead of service/protocol names (e.g. "21", instead of "ftp").
Is it possible you have duplicate network interfaces in your sbbs.ini file? What is your "Interface" value set to in your sbbs.in file?
You have to use the -n option for it port numbers instead of service/protocol names (e.g. "21", instead of "ftp").
Ahhh... now I see them! When SBBS is not running, only ports 22, 25, and
80 are engaged by other processes. 21 and 23 don't show up unless SBBS is running.
Is it possible you have duplicate network interfaces in your sbbs.ini file? What is your "Interface" value set to in your sbbs.in file?
The value in [Global] is set to "Interface=(blank)", which is the same as the setting on this board. It also shows up in other sections (ftp, services, etc.) and is also always blank.
Dumas Walker wrote to DIGITAL MAN <=-r
Did you just just run 'netstat' with no arguments? You must include the -l
-a options to display listening ports:
I am trying -lp. I may be very dense but I don't see any of the port numbers I am trying to use (21, 23, 80) anywhere in either list it produces.
One problem, since fixed, was that I was not running as su. :)
On the 32-bit machine sbbs is currently running on, I do get the
service name, like 'http', 'telnet', 'ftp', and they are all being used
by sbbs.
On the machine in question, the only one that shows up is http, and it
is indeed in use by apache2. telnet and ftp do not show up. Since the port number does not show up (in any human-readable form), I am not
sure if some other service has tied 21 and 23 up or not.
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 34:47:51 |
Calls: | 508 |
Messages: | 220015 |