DNAT. You map one/more ports from your router exposed on internet to ip:port of the local app.
However, http/https ports are already used on routers to offer an admin web GUI. It’s technically possible to circumvent this with some ad-hoc firewall rules, but it depends if the router admin UI let’s you do that.
Exactly, they aren’t exposed outside. That’s why you can “potentially” add rules to route request from the outside to an internal host:port, even 80/143. On the LAN you would still able to connect to router admin.
Yes, you can definitely connect manually through telnet (I did it back in the old days). The only problem is it will not stay connected too much, because you should also reply to server's PINGs at regular time intervals otherwise you'll get disconnected.
> This could have been avoided, but the time to avoid it was perhaps in the early 2000s.
there were protests, from Seattle '99 until Genova '01, where many different groups merged into a single protest agaist that kind of globalization. but after 9/11 everything almost vanished in the name of worldwide anti-terrorism.
The terrorists won on 9/11 not because they directly did much damage but because they got America to shoot itself in the foot. This was just one of many things our government's response ruined, unfortunately.
