Internal IP to 2nd gateway
-
To be hoenst 2.0.2 is the latest and i am using it on other customer equipment. And its alright, i was on 2.0.1 for ages, but from my understanding there were bug fixes fixed in 2.0.2
Something else i thought of… Can you enable logging on the rule so it has a blue exclamation mark on it? And then try external access and see what the system firewall log says?
I would recommend a reinstall if you have rebooted and it hasnt come back online. I assume you have done loads of restarts on it before and its fine, up until now?
-
OK… Here We go again :)
I`ve just reinstalled PFSense and reconfigured all settings from scratch.
And now the conclusion:
1. I
ve noticed that whenever i create port forwarding from **WAN1** (Default GW) to the internal Lan Iam selecting as showed in the pic1 below:
I really don
t have reasonable explanation why… Ive just noticed that this set up works so I lived that way.All ports that are forwarded that way are working with no issues!
2. Whenever i try to create the same port forwarding but from WAN2 it is not working!
No Idea why…
3. Thanks to @craigduff "When you create a rule on the nat page "port forward" Right at the bottom there is an option for Filter rule association. This is what adds the rules."..
So I`ve made the respective changes to the port forwarding from WAN2 as shown on pic2 below:
And voila :) It`s just working :)
What I didn`t understand is why for WAN1 should be as per pic1 and for WAN2 as per pic2…
I really want to Thank @craigduff for his time and effort!
Respect!
-
No problem! It was my pleasure! I love Pfsense! Always will!