Show Posts
1
18.1 Legacy Series / access port forward web sever from internal lan
« on: March 08, 2018, 05:47:32 pm »
Hi All,
New to opnsense and having a time figuring out how to access my web server internally on network. Here is my setup in a nutshell.
I am running latest stable opnsense. I have created port forward for both port 80 and 443 that redirects to local ip of my web server. I am using google dynamic dns to point my domain name to my public IP. This all works just fine and I can access the webserver from outside of my local network.
The problem is that I cannot access the web server using the fqdn on my internal network. I want to be able to access my web server by the same address in our our of my local network.
I have looked at the reflection / nat settings under: Firewall -> Settings -> Advanced.
When I check mark the boxes for (Reflection for 1:1) and (Sticky outbound NAT), I can access the web server locally as well as externally, but it is extremely slow. Like 30 plus seconds for a login that typically is milliseconds to respond.
It looks to me like a latency issue, but I am not sure. Any help would be appreciated.
Jodytek
New to opnsense and having a time figuring out how to access my web server internally on network. Here is my setup in a nutshell.
I am running latest stable opnsense. I have created port forward for both port 80 and 443 that redirects to local ip of my web server. I am using google dynamic dns to point my domain name to my public IP. This all works just fine and I can access the webserver from outside of my local network.
The problem is that I cannot access the web server using the fqdn on my internal network. I want to be able to access my web server by the same address in our our of my local network.
I have looked at the reflection / nat settings under: Firewall -> Settings -> Advanced.
When I check mark the boxes for (Reflection for 1:1) and (Sticky outbound NAT), I can access the web server locally as well as externally, but it is extremely slow. Like 30 plus seconds for a login that typically is milliseconds to respond.
It looks to me like a latency issue, but I am not sure. Any help would be appreciated.
Jodytek