2/13 09:56:36 ftp 0003 !ERROR 13 binding FTP Server socket to port 21
Do I have to manually configure sbbs.ini?
or is there a configuration like in windows that I can run 1st?
2/13 09:56:36 ftp 0003 !ERROR 13 binding FTP Server socket to port
21
Permission denied. You're not root, so you can't bind to ports < 1024.
You can start as root and have it switch afterward to the User and Group specified in the [Unix] section of sbbs.ini.
You could just run it as root, but probably shouldn't.
You could configure services to bind to ports > 1024 and just start as a normal user. Forwarding rules in your firewall could allow you to redirect traffic from 'standard' external ports to wherever your BBS is listening.
1st time I installed Synchronet on my Raspberry PI I got an error so I wiped my OS and restarted from scratch.
This time I was able to build synchronet with no errors.
when I try to run sbbs here is what I get.
2/13 09:56:36 ftp 0003 !ERROR 13 binding FTP Server socket to port 21
2/13 09:56:36 ftp 0003 Will retry in 15 seconds (1 of 2)
2/13 09:56:36 mail 0005 !ERROR 13 binding SMTP Server socket to port 25 2/13 09:56:36 mail 0005 Will retry in 15 seconds (1 of 2)
2/13 09:56:36 web Synchronet Web Server Revision 1.646
2/13 09:56:36 web Compiled Feb 13 2018 08:12:37 with GCC 6.3.0
Do I have to manually configure sbbs.ini?
or is there a configuration like in windows that I can run 1st?
There are ways to bind to ports <= 1024 for non-root processes in Linux. The setcap tool can give an executable permission to do so. https://www.jumpingbean.co.za/blogs/mark/run-application-port-below-1024-l
Do I have to manually configure sbbs.ini?
or is there a configuration like in windows that I can run 1st?
2/13 09:56:51 term 0004 !ERROR 13 binding Telnet Server socket to port 23 2/13 09:56:51 term 0004 Will retry in 15 seconds (2 of 2)
2/13 09:56:51 srvc 0006 !ERROR 13 binding NNTP socket to port 119
2/13 09:56:51 srvc 0006 Will retry in 15 seconds (2 of 2)
2/13 09:56:52 web 0007 !ERROR 13 binding Web Server socket to port 80
2/13 09:56:52 web 0007 Will retry in 15 seconds (2 of 2)
[Threads: 7 Sockets: 5 Clients: 0 Served: 0 Errors: 0] (?=Help): q
There are ways to bind to ports <= 1024 for non-root processes in Linux. The setcap tool can give an executable permission to do so. https://www.jumpingbean.co.za/blogs/mark/run-application-port-below-1024-l inux
I ran it with sudo.2/13 09:56:36 ftp 0003 !ERROR 13 binding FTP Server socket to port
21
Permission denied. You're not root, so you can't bind to ports < 1024.
You can start as root and have it switch afterward to the User and Group specified in the [Unix] section of sbbs.ini.
Re: Raspberry PI synchronet problems
By: echicken to Denn on Tue Feb 13 2018 01:01 pm
2/13 09:56:36 ftp 0003 !ERROR 13 binding FTP Server socket to port
21
Permission denied. You're not root, so you can't bind to ports < 1024.I ran it with sudo.
I am using raspian stretch where normally I would use Ubuntu.
You can start as root and have it switch afterward to the User and Group specified in the [Unix] section of sbbs.ini.
I was going to look more into the wiki but its down right now (sigh).
There are ways to bind to ports <= 1024 for non-root processes in
Linux. The setcap tool can give an executable permission to do so.
https://www.jumpingbean.co.za/blogs/mark/run-application-port-below-
1024-l inux
I will look into it, the setup runs fine but I was assuming I could run the Console using sudo but I am missing something I guess.
I will look into it, the setup runs fine but I was assuming I could
run the Console using sudo but I am missing something I guess.
You could run the console with sudo.. But I think it would be generally bad practice to run public-facing servers as root. If someone somehow gains shell access to your system through the server, you wouldn't want them having root privileges due to the process running as root.
You could run the console with sudo.. But I think it would be
generally bad practice to run public-facing servers as root. If
someone somehow gains shell access to your system through the
server, you wouldn't want them having root privileges due to the
process running as root.
afaik, SUDO only binds the ports, then the software is handed back to the user specified in sbbs.ini or cmdline.
sudo is a program that runs a program as root in Linux (sudo is short for "superuser do"). That's my understanding of it, unless there's more to it.
I was going to look more into the wiki but its down right now (sigh).
No, it's up. I just hit from hundreds of miles away. <shrug>
afaik, SUDO only binds the ports, then the software is handed back
to the user specified in sbbs.ini or cmdline.
sudo is a program that runs a program as root in Linux (sudo is short for "superuser do"). That's my understanding of it, unless there's more to it.
You could run the console with sudo.. But I think it would be generally bad practice to run public-facing servers as root. If someone somehow gains shell access to your system through the server, you wouldn't want them having root privileges due to the process running as root.
I will look into it, the setup runs fine but I was assuming I could
run the Console using sudo but I am missing something I guess.
You could run the console with sudo.. But I think it would be
generally bad practice to run public-facing servers as root. If
someone somehow gains shell access to your system through the
server, you wouldn't want them having root privileges due to the
process running as root.
afaik, SUDO only binds the ports, then the software is handed back to the user specified in sbbs.ini or cmdline.
Re: Raspberry PI synchronet problems
By: Nightfox to KK4QBN on Wed Feb 14 2018 14:49:13
sudo is a program that runs a program as root in Linux (sudo is short for "superuser do"). That's my understanding of it, unless there's more to it.
I may have heard it wrong but I thought I heard Rob say at one time that sbbs was setup to bind the ports with sudo, then revert back to regular user privelidges, as I say "afaik" I may be completely wrong.
user specified in sbbs.ini or cmdline.
I kind of figured it must be a setup item I missed in sbbs.ini
the linux config is mainly at the very bottom of sbbs.ini. but I suggest reading it from top to bottom.
I may have heard it wrong but I thought I heard Rob say at one time
that sbbs was setup to bind the ports with sudo, then revert back to
regular user privelidges, as I say "afaik" I may be completely wrong.
No, that's right.
user specified in sbbs.ini or cmdline.
I kind of figured it must be a setup item I missed in sbbs.ini
It's trying to load the console but the wiki dose'nt show how to set the varible that I can see, I might have somehow missed it :)
Does Synchronet linux ver load with a console the same a windows Synchronet?
Synchronet Console for Linux Version 3.17a Copyright 2016 Rob Swindell
!SBBSCTRL environment variable not set, using default value: /sbbs/ctrl
!ERROR 2 (No such file or directory) opening /sbbs/ctrl/sbbs.ini
Using default initialization values
!ERROR 2 changing directory to: /sbbs/ctrl
Loading configuration files from /sbbs/ctrl
!ERROR Loading Configuration Files: 2 (No such file or directory) opening /sbbs/ctrl/main.cnf
like I said.. even though I have set these vairables up like ALL FAQS have shown me to, SBBS still cannot pick the env var up.. under debian.
Does Synchronet linux ver load with a console the same a windows
Synchronet?
By default, no. The Linux SBBS runs at the console, although I remember seeing a (GTK?) GUI sbbs monitor for Linux that I think was meant to be similar to the SBBS GUI console for Windows. I run the Windows version though (I've only tried the Linux version a few times for testing), so I don't remember all the details.
afaik, SUDO only binds the ports, then the software is handed back to the >KK> user specified in sbbs.ini or cmdline.
sudo is a program that runs a program as root in Linux (sudo is short for "superuser do"). That's my understanding of it, unless there's more to it.
Sounds like a problem with your script. What if you just type this (no script): export SBBSCTRL=/sbbs/ctrl && /path/to/scfg
or
export SBBSCTRL=/sbbs/ctrl && /path/to/sbbs
Re: Raspberry PI synchronet problems
By: KK4QBN to Denn on Thu Feb 15 2018 14:43:43
like I said.. even though I have set these vairables up like ALL FAQS have shown me to, SBBS still cannot pick the env var up.. under debian.
I even tried what was suggested in the wiki
SBBSCTRL=/sbbs/ctrl && export SBBSCTRL and still:
kk4qbn@kk4qbn:/sbbs/exec$ ./runsbbs
[sudo] password for kk4qbn:
Synchronet Console for Linux Version 3.17a Copyright 2016 Rob Swindell
!SBBSCTRL environment variable not set, using default value: /sbbs/ctrl
this is in ~/.profile ~/.bash.profile AND in the script I use to run the SBBS console app. so the env var is actually set in the same term sbbs is being run in RIGHT before it is being run and still don't work.
to make SCFG work right I either have to run /sbbs/exec/scfg /sbbs/ctrl
or cd on /sbbs/ctrl and run ../exec/scfg
it's crazy.. it should be working but will not..
Correct, but my understanding of how synchronet works is that it "hands back" control of the bbs to the user account once it is done using the sudo user to bind the ports.
DM will probably correct me here. :)
Sounds like a problem with your script. What if you just type this (no script): export SBBSCTRL=/sbbs/ctrl && /path/to/scfg
or
export SBBSCTRL=/sbbs/ctrl && /path/to/sbbs
?
just sbbs wont load till I fix the binding errors
(no script): export SBBSCTRL=/sbbs/ctrl && /path/to/scfg
or
export SBBSCTRL=/sbbs/ctrl && /path/to/sbbs
Ok, that pulled scfg up, no issues, put it in a script and now working flawlessly as is sbbs.. but still wondering why it will not work machine wide.. I'll keep fooling around with the profile files, etc.. until it gets fixed.
Al wrote to Nightfox <=-
That has always been my understanding. Mystics MIS server is run by
"sudo ./mis" so it can bind the ports but all the files it creates are owned by the user who owns MIS. I think MIS may have been written to operate that way.
Yes, Mystic is able to run as the owner of the files in its home directory. Synchronet uses a more traditional approach, where to user to run as after binding ports is specified in a configuration file (sbbs.ini).
KK4QBN wrote to Vk3jed <=-
Re: Re: Raspberry PI synchronet problems
By: Vk3jed to Al on Sat Feb 17 2018 08:16:00
Yes, Mystic is able to run as the owner of the files in its home directory. Synchronet uses a more traditional approach, where to user to run as after binding ports is specified in a configuration file (sbbs.ini).
It can be specified on commandline too.
Al wrote to Vk3jed <=-
I have run sbbs daemonized before but I always ran it as root.
Maybe the sudo method would work?
Re: Raspberry PI synchronet problems
By: Digital Man to KK4QBN on Thu Feb 15 2018 03:45 pm
Sounds like a problem with your script. What if you just type this (no script): export SBBSCTRL=/sbbs/ctrl && /path/to/scfg
or
export SBBSCTRL=/sbbs/ctrl && /path/to/sbbs
?
I typed that, the varible works but I still get binding errors I will work on it this weekend, I think I may just need to set stuff up in sbbs.ini
Once I get it all figured out using the command line I will make a script to load it all at startup.
Yes, Mystic is able to run as the owner of the files in its home directory. Synchronet uses a more traditional approach, where to user to run as after binding ports is specified in a configuration file (sbbs.ini).
It can be specified on commandline too.
I haven't looked into that option.
KK4QBN wrote to Tony Langdon <=-
./sbbs -unUSERNAME -ugUSERGROUP -hnHOSTNAME
think you can do a ./sbbs -? or /? for help
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 88:25:06 |
| Calls: | 2,069 |
| Calls today: | 2 |
| Files: | 11,134 |
| Messages: | 946,757 |