From Newsgroup: alt.bbs.synchronet
I'm puzzled. I joined DOVE-Net yesterday, successfully - I'm getting QWK packets of messages. Then I followed the instructions at http://wiki.synchro.net/module:dyndns
but I'm not able to connect to my BBS either by web or telnet. I can ping the DDNS hostname though (coffee.synchro.net) and it comes back with my
WAN (Internet) IP4 address, so it looks like DDNS is actually working.
I've forwarded TCP ports 21,22,23,80 and 513 in my router, which is a Linksys E-1200 v.2 running DD-WRT v.3.0-r31924 mega. I even tried putting
my PC in the DMZ. I've also disabled the firewall in PCLinuxOS, so I
should be wide open to the Internet at the moment (I'm not going to leave
it that way!) It's as though my services aren't binding to my external IP. (I can connect to my BBS via web by entering my internal LAN IP as the
URL.)
Any ideas?
I've forwarded TCP ports 21,22,23,80 and 513 in my router, which is a
To: charlie
Re: DDNS not working correctly By: charlie to alt.bbs.synchronet on
Fri Mar 02 2018 11:28 pm
From Newsgroup: alt.bbs.synchronet
I'm puzzled. I joined DOVE-Net yesterday, successfully - I'm getting
QWK packets of messages. Then I followed the instructions at http://wiki.synchro.net/module:dyndns but I'm not able to connect to
my BBS either by web or telnet. I can ping the DDNS hostname though (coffee.synchro.net) and it comes back with my WAN (Internet) IP4
address, so it looks like DDNS is actually working.
I've forwarded TCP ports 21,22,23,80 and 513 in my router, which is a Linksys E-1200 v.2 running DD-WRT v.3.0-r31924 mega. I even tried
putting my PC in the DMZ. I've also disabled the firewall in
PCLinuxOS, so I should be wide open to the Internet at the moment
(I'm not going to leave it that way!) It's as though my services
aren't binding to my external IP.
(I can connect to my BBS via web by entering my internal LAN IP as
the URL.)
Any ideas?
It could be that your router doesn't support hair-pinning, so you'd have
to use your local/private IP address to connect to your own servers in
that case.
Also see:
http://wiki.synchro.net/faq:tcpip#ports
There's a link there to a web page you can use to see what
servers/services you have open to the public Internet.
digital man
This Is Spinal Tap quote #13:
Nigel Tufnel: You can't really dust for vomit.
Norco, CA WX: 53.9°F, 86.0% humidity, 0 mph WSW wind, 0.00 inches
rain/24hrs --- Synchronet 3.17a-Win32 NewsLink 1.108
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
Thank you very much. That's indeed what's happening. I'd never heard of "hairpinning" but apparently my router doesn't support it as I am able to log onto my board's web interface from another IP using Tor browser.
Thanks for the port scan utility. It's very helpful. I wonder why it
shows that telnet on port 23 fails even though I have that port
forwarded?
The telnet service must be running as I can telnet into my
board locally (using my local internal LAN IP.)
Thank you very much. That's indeed what's happening. I'd never heard of
"hairpinning" but apparently my router doesn't support it as I am able
to log onto my board's web interface from another IP using Tor browser.
Okay, cool. It doesn't hurt to just use your local/private IP address
(or localhost) when logging on locally, though it can be pain
sometimes for web testing where URLs might use hostnames.
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 12:18:58 |
Calls: | 510 |
Messages: | 220575 |