Hello!Synch
I have just got back into BBSing. I am an old SysOp from the dial up days and going through the learning curve of internet BBSing. I used to run
back in the late 80's and early 90's, before life got in the way. I've got Synch back up and can log on with SyncTERM and haven't started any customization yet. I do have a couple of questions:
1) I'm doing this through Manjaro Linux. I am trying to log onto the BBS through firefox locally, I get some sort of tp-link technologies log in page.
When I try through work, it can't resolve the address.
Does the Browser login only work with windows?
2) I am looking at me terminal and I am getting this login:wrong
9/25 21:24:34 term 0069 SSH connection accepted from 222.186.52.124 port 62458 9/25 21:24:37 term 0069 SSH session establishment failed
I am getting this from different addresses. Do I have something set up
and I am not letting someone in?
1) I'm doing this through Manjaro Linux. I am trying to log onto the BBS through firefox locally, I get some sort of tp-link technologies log in page.
That sounds like a router hairpinning issue. What happens when you try to goto http://localhost locally?
Re: Web Consoleto
By: Digital Man to Grease on Thu Sep 26 2019 02:51 am
1) I'm doing this through Manjaro Linux. I am trying to log onto the BBS through firefox locally, I get some sort of tp-link technologies log in page.
That sounds like a router hairpinning issue. What happens when you try
goto http://localhost locally?
I did the localhost, it works! So it must be something from between me and the outside world.
But you said you couldn't access the web server from the same computer when using your public hostname. That sounds like your router doesn't know howto
route back to your internal computer packets sent to your public IPaddress.
This router feature is known as hairpinning and not all routers support it. It doesn't really have anything to do with anyone else on the Internetbeing
able to access your web server. That would be a separate issue.
Re: Web Consoleanyone
By: Digital Man to Grease on Fri Sep 27 2019 09:43:03
But you said you couldn't access the web server from the same computer when using your public hostname. That sounds like your router doesn't know how to route back to your internal computer packets sent to your public IP address. This router feature is known as hairpinning and not all routers support it. It doesn't really have anything to do with
else on the Internet being able to access your web server. That would be a separate issue.
Could also be his ISP not allowing it. I used to be with Comcast, and they didn't allow hairpinning. Now have Google Fiber and there is no problem what-so-ever. :)
On 09-27-19 23:25, Digital Man wrote to Lupine Furmen <=-
That doesn't make any sense. Perhaps what you mean is the router
supplied by the ISP didn't support hairpinning. A hairpinned packet
never leaves your premises.
That doesn't make any sense. Perhaps what you mean is the router suppliedby
the ISP didn't support hairpinning. A hairpinned packet never leaves your premises.
Re: Web Consolesupplied
By: Digital Man to Lupine Furmen on Fri Sep 27 2019 23:25:23
That doesn't make any sense. Perhaps what you mean is the router
serverby the ISP didn't support hairpinning. A hairpinned packet never leaves your premises.
That is what I was told that it's called. I was trying to test my web
by using my domain name and I was not able to connect back to the same IP I was trying to connect FROM.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 233:20:37 |
Calls: | 6,624 |
Files: | 12,172 |
Messages: | 5,319,627 |