All web traffic suddenly being redirected to internal web server
-
What nat rules do you have? Can you give us an output of```
pfctl -sn -
This is quite common with misconfigured NAT rules, see here:
http://doc.pfsense.org/index.php/Why_does_enabling_NAT_Reflection_break_web_surfing%3F
-
Hi thanks for all your help. I just confirmed that the nat rule for port 80 is correctly configured with external address.
the print out of pfctl -sn is huge, I don't know how to capture the entire print. I have attached a screen print of my nat page:
 -
My guess you are having problem with your web-server.
-
You have two port forwards on the "zon" interface that have an external address of 0.0.0.0 for port 80.
That may also be an issue.
-
You have two port forwards on the "zon" interface that have an external address of 0.0.0.0 for port 80.
That may also be an issue.
Could you explain how this might be related to NAT on WAN interface?
-
Could you explain how this might be related to NAT on WAN interface?
It's not related to NAT on WAN, it's related to NAT reflection, which is a big ugly mess and could easily do this. :-)
-
Could you explain how this might be related to NAT on WAN interface?
It's not related to NAT on WAN, it's related to NAT reflection, which is a big ugly mess and could easily do this. :-)
Oh… I did not see anything about nat redirection in initial post and supposed this web-site fails for outside people -)
-
He didn't say it, but if you look at the link I posted earlier, it's the #1 cause of this exact issue.
-
Hey guys thanks so much for your help. The zon interface is my wan2 which this moment is down.
The webserver is accesabile from outside, and everything else is accessible from lan (ie. email, ping, traceroute), it really only seems to be port 80 that gets redirected to the webserver. What gets me is that system was up for 2 months and never had an issue, until this morning.
I also doubled checked the nat rule for port 80 to the webserver and is setup with external address.
-
You seem to be missing the real point here. If you have NAT reflection enabled, shut it off.
If that fixes the problem, then you still have an incorrectly specified port forward somewhere.
-
Hi thanks again. I shut off nat reflection, and now everything is fine, so obviously than I have a mis-configured port 80 somewhere. Why would this turn up now after 2 months of no problems?
-
It may be related to that second WAN that you said was just shut off, or some other cause. Somehow it's trying to reflect any external address instead of a specific one.
NAT Reflection is evil :)
