Access wan portforwarded address from lan
Im trying to access WAN ip from inside the lan network, but only to be greeted with : err_connection_timed_out.
The wan IP has portforwarded an lan web server.
Accessing wan IP outside the lan network works perfectly.
Currently i have tried this guide
Nat reflection mode for portforwarded : Pure Nat
Enable NAT reflection for Nat1:1 : Ticked
Enable automatic outbound NAT for Reflection : Ticked.
Under firewall>Nat : Port forward
Interface WAN, Protocol TCP, source , source ports des.address : WAN . Dest port : 80, NAT IP : webserver local IP (10.x.x.x)
And why do you not just access your webserver via its lan IP 10.x.x.x (why are you hiding rfc1918 address?)
Cause if its single user only, it would be easy, but there are multiple users and hard to make them remember the address. "Now everyone please login to 10.0.4.119 and upload your file to the dedicated location"
Why would they not just use the name of said server? Be it either the machines fqdn on your local domain. Or just a simple host override to point the public fqdn to the servers 10.0.4.119 address.
I think i stated the issue wrongly. So this is how i wish the system to work :
We have a domain name bought and point to our WAN IP.
We have a local web server working inside our network.
When people who are within our local network type the domain name to their browsers, they arent forwared to the web server.
When people who are outside our local network type the domain name to their browsers, they are forwarded to the web server correctly.
When i type the local ip into the browser, the webpage is opened correctly.
So what am i asking now is to, how to make it so people who are within our local network can access the webpage the same way as others can from outside.
"how to make it so people who are within our local network can access the webpage the same way as others can from outside."
With a simple host override that says hey public fqdn when your inside the network resolve to your rfc1918 address of the server. This takes 5 seconds to setup and don't have to worry about going through the firewall just to be reflected back inside via a hairpin, etc.
The link you provided - just use method2, split dns.