Thanks for all the tips on good web hosts for my BBS!
I went with OVHCloud because I like the way they advertised their prices. (No hourly jargon!)
I set myself up with Ubuntu 18.04 & VestaCP. I got my BBS domain configured properly (I'm able to serve web pages) and now I'm almost ready to run the BBS on there.
I got stuck on something though: I ran MIS server, but when I try to connect with a telnet client it doesn't connect. There's nothing in the mis log either. The mis screen remains unchanged when I try to connect, so something is up. Does it seem like I don't have my port open? (23?)
I tried to open it up like this:
sudo ufw allow 23/tcp
(But that didn't work - I still couldn't connect.)
It seems like the port is open - what else can I check?
Thanks.
--- Mystic BBS/QWK Gate v1.12 A47 2020/11/23 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (77:1/100)
I got stuck on something though: I ran MIS server, but when I try to connectwith a telnet client it doesn't connect. There's nothing in the
mis log either.The mis screen remains unchanged when I try to connect,
so something is up.Does it seem like I don't have my port open? (23?)
Make sure it's bound to port 23? netstat -anp|grep :23 shoudl do it.
If it's not installed then ss -tulwn|grep :23
I had to run sudo ./mis daemon for it to listen on port 23.
I believe you need to be root to run servers on ports < 1024 if I'm not mistaken. Not sure if that's the case here?
sudo ufw allow 23/tcp
sudo ufw allow 23/tcp
After this, you still have to reload ufw to make the change take effect.
Thanks for all the tips on good web hosts for my BBS!
I went with OVHCloud because I like the way they advertised their prices. (No hourly jargon!)
I set myself up with Ubuntu 18.04 & VestaCP. I got my BBS domain configured properly (I'm able to serve web pages) and now I'm almost ready to run the BBS on there.
I got stuck on something though: I ran MIS server, but when I try to connect with a telnet client it doesn't connect. There's nothing in the mis log either. The mis screen remains unchanged when I try to connect, so something is up. Does it seem like I don't have my port open? (23?)
I tried to open it up like this:
sudo ufw allow 23/tcp
(But that didn't work - I still couldn't connect.)
It seems like the port is open - what else can I check?
Thanks for that tip - When I tried to reload it, I found out that "Firewall not enabled." So now I'll assume that my problem isn't a firewall issue.
BTW, running on port 23 is dangerous for the simple fact that it runs as root.There are ways around it such as using capabilities, but the
easiest would beto use iptables and redirect port 23 to something like 10023. That allows youto run your bbs on both 10023 as a non-root user, and port 23 by using a safeiptables redirection.
"Firewall not enabled." So now I'll assume that my problem isn't a firewall issue.
Maybe 'sudo tail -F /var/log/syslog` while you try to telnet in and see whatlog lines are revealed?
I'm new to VestaCP. I just noticed that I have the website files (in a public_html folder) within the admin folder. Could it be that Mystic's server (mis) is unable to respond because Mystic can't do sudo commands?
Sorry, I'm an admitted lamer. But I think that eventually one of these clues are going to get me back up and running.
If Mystic failed to bind to port 23 (and other low ports) you'd see it in Mystic logs. Have you looked there?
Do we know if mis is actually listening on 23?
Maybe try:
netstat -l -n -p --inet
BTW, running on port 23 is dangerous for the simple fact that it runs as root.There are ways around it such as using capabilities, but the
MIS binds the ports immediately on execute and then drops root access using setGID and setUID to the owner of the binaries. So the idea is if you start it as sudo, it should immediately bind the ports (even before the servers are loaded) and then run as the group/user assigned to the binaries.
Unless root specifically owns the binaries then it should not even allow you to run as root if you try.
MIS binds the ports immediately on execute and then drops root access u setGID and setUID to the owner of the binaries. So the idea is if you it as sudo, it should immediately bind the ports (even before the serve are loaded) and then run as the group/user assigned to the binaries.
BTW, running on port 23 is dangerous for the simple fact that it runs as root. There are ways around it such as using capabilities, but the easiest would be to use iptables and redirect port 23 to something like 10023. That allows you to run your bbs on both 10023 as a non-root user, and port 23 by using a safe iptables redirection.
This also works for ssh, and other protocols.
BTW, running on port 23 is dangerous for the simple fact that it runs as root. There are ways around it such as using capabilities, but the
easiest would be to use iptables and redirect port 23 to something like 10023. That allows you to run your bbs on both 10023 as a non-root user, and port 23 by using a safe iptables redirection.
Nelgin,
If one was to set up an iptables rule to redirect traffic from Port 23 to Port 2323, where synchronet is listening, will synchronet still receive the IPA of the outside system attempting to make the connection, or will it receive the IPA of the system where the iptables rule resides?
Does that answer change if the machine where the iptables rule resides, and where synchronet is running, are the same system?
| Sysop: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 60 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 02:57:56 |
| Calls: | 516 |
| Files: | 6,996 |
| Messages: | 289,384 |