I can access my local webserver using the 192.168.0.* address, but using the webdomain that points to the no-ip that points to that doesn’t work, though it does on a pc or phone outside of the local network.
since it happens on the windows/linux and mac boxes in my house i’m going to ssume there’s a router issue (some googling suggested nat which can’t be edited on a sky router but the guy had a pretty specific setup)
there wouldn’t be an opensuse-specific config i can edit somehow would there? or some non-nat router port forwarding? i can access it using a proxy and i’m sure the prism guys love reading my portfolio website but the ads are doing my head in
but if it can’t be done it can’t be done, may as well ask first
malcolmlewis wrote:
> Hi
> A quick way is just to add it into the hosts file on the windows and
> linux machines;
>
> Code:
> --------------------
>
> 192.168.0.xxx www.somewebsite.com
>
> --------------------
Right but that just short-circuits the routing so it doesn’t really test
access using the external address. If that was all that was wanted then
accessing it directly using the 192 address would be sufficient.
To diagnose what is stopping it working, I would suggest using
You can not access your web server in your LAN from outside the LAN if you did not configure your router to transfer any incoming request to port 80 on the router to that particular system in your LAN.
The IP addresses in your LAN are private addresses and can not be used from the Internet. You have instead one IP address from the Internet, your router (BTW that is also the address that should get a name attached in the Internet DNS server(s) when you want to reach it from the Internet by hostname).
And the router then does address translation from your router’s Internet address to your private address.
Evey router make/type has his own interface to configure this, thus we can not tell you exectly what to do.
hcvv wrote:
> You can not access your web server in your LAN from outside the LAN if
> you did not configure your router to transfer any incoming request to
> port 80 on the router to that particular system in your LAN.
The OP’s original post explicitly says that they CAN reach the server
from nodes outside the LAN. So that part works. the bit that doesn’t is
routing from the LAN out to the Internet and then back to the web server.
Not all routers can perform “hairpin routing” ie your packets go to your DG and without leaving the device are routed back to the physical network they came from(which theoretically and often is possible because the packets are routed through the external interface of a multi-homed device).
The most sure way to do what is requested is to either connect through a remote proxy (on the Internet) or connect through a remote Host using a VPN.
I’ll give this a try; testing even using the 192.* address wont work as some redirects specifically point to the external address which then fails (some auto phpbb3 stuff). The firewall already forwards port 80 to this machine, so i’ll give this host file stuff a go, testing is horrible on a phone ha…
…aaand yes that works!
ps. sorry to the other mods in the thread, i should’ve been clearer that connectivity is fine, i’m just testing new functionality
That would work for me, if I were running a web server. The equivalent works for SSH.
That’s because my home router happens to support loopback (a different meaning of loopback than “127.0.0.1”).
Many home routers do not support this. If you have a home router that does not support it, then you will have to use the 192.168.. address, and do something with your hosts file or run a local DNS so that the hostname will be mapped to the private IP when used in your network.
