I've been googling for what ought to be a commonly sought server config recipe without luck and hope the group has some ideas -- for search terms if nothing else.
I'm evaluating a new ISP (Webpass, down in the Bay Area). They're fast and cheap, the latter in part because they don't pay for a public IP address for every customer. They wire buildings, and put everybody in the building behind a NATting router with a single public IP address. No ports are forwarded, so you can't SSH in from work when you forgot something or just want to see what that the kids are browsing. :-) It's new for broadband providers to be doing this, but colleges have been doing it for their dormitories for a decade. There must be solutions described out there. My proposed solution is to run an AWS instance (or some other cheap virtual host with a public IP address), install an openvpn server there, connect an openvpn client on my router to that server, and then configure the virtual host to forward all ports and protocols to the router via the openvpn tunnel. I think the cost of running the instance will be less than the difference between what Webpass and Comcast cost. And the Webpass people are much less rude. Has anybody seen, or can anybody find, a description of how to set this up? (The openvpn stuff's easy; port forwarding less so.) Alternatively, is there a better way to accomplish the same thing? Thanks, --Eric -- ****************************************************************************** * From the desktop of: Eric House, [email protected] * * Crosswords for Android now in beta: via Google Play or xwords.sf.net * ****************************************************************************** _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
