Quote:
Originally Posted by Red Squirrel
The issue is if your ISP blocks port 80 you can do all the port redirecting you want in your internal network, you still won't be able to have something listen to port 80 on the outside. (or any port).
You could listen to port 81 and redirect to port 80 internally, but then users still have to type :81 in the url.
|
Actually not true, if an ISP blocks port 80, I can use a DNS web redirection.
EG
Dynamic DNS service such as noip.com is able to create an A record that points to an IP address, then create a web redirect that points to that A record plus port, such as:-
Dynamic host name =
http://name1.noip.org pointing to WANIP
Dynamic host, web redirect
http://name.noip.org pointing to
http://name1.noip.org:12080
Thus when the url
http://name.noip.org is entered the actual address is
http://name1.noip.org:12080 which actually the dynamic DNS service translates it to
http://WANIP:12080 so that means nobody has to use the port suffix in the url,,,, then when data is sent on port 12080 which is then routed via my router to the server LANIP (192.168.0.100) on port 12080, iptables within the server reroutes (redirects) port 12080 to port 80 where my Apache server is listening on, so it wouldn't matter if the ISP blocks port 80, I can use the url
http://name.noip.org without using the port suffix and it does work, and because owncloud script updater is hard coded to use port 80, this method of redirection does work for the updater script.
As an example, I'm using the same method on this url:-
http://my-web.no-ip.net/downloads except the virtual host that's serving that site is actually running on my home server, on a port other than 80,,,, and there's no adding the port to the url.
