On Tue, 2025-04-01 at 21:03 -0400, Greg Wooledge wrote: > On Tue, Apr 01, 2025 at 17:52:55 -0700, Van Snyder wrote: > > The server is on the LAN side of the router (192.168.1.65). It's > > not in > > the DMZ. My server isn't running Apache ACLs or iptables or TCP > > wrapper. The router is running a firewall. I've forwarded WAN-side > > ports 23, 80 and 443 to my server, and another non-22 WAN-side port > > to > > port 22 on my server. > > > > I can view pages from my server on itself or other computers in my > > house using 192.168.1.65 (the LAN side of the router), but not > > 47.229.8.99 (the WAN side of the router). > > OK, so just to be clear: > > 1) Your internal computer is running a web server on ports 80 and > 443. > 2) Your internal computer's IP address is 192.168.1.65. > 3) Your router's external IP address is 47.229.8.99. > 4) You've told your router to forward port 80 to 192.168.1.65 port > 80. > > > Maybe my server isn't listening for telnet. I installed telnet and > > telnetd, but "systemctl start telnetd" said there's no such thing. > > DO NOT install telnetd!!
Thanks for the advice. I removed it. > OK, with that out of the way: > > hobbit:~$ telnet 47.229.8.99 80 > Trying 47.229.8.99... > telnet: Unable to connect to remote host: No route to host > > I cannot reach your router's external IP address from here. You'll > want to verify that this is the correct IP adderss, and if it is, > figure out why it can't be routed-to from the outside world. # nslookup vandyke.mynetgear.com Server: 192.168.1.1 Address: 192.168.1.1#53 Non-authoritative answer: Name: vandyke.mynetgear.com Address: 47.229.8.99 nslookup vandyke.mynetgear.com Server: 192.168.1.1 Address: 192.168.1.1#53 Non-authoritative answer: Name: vandyke.mynetgear.com Address: 47.229.8.99 It looks like I get name service from my router.
