Putting my pfSense Home Lab on an Extender
-
@the_director Actually it is OK if they are on separate breakers, they just have to be in the same phase in the panel. In other words, they need to be on the same vertical row.
-
Ok, if you have a static route and no NAT then you need a firewall rule on the pfSense WAN to allow traffic from 192.168.1.X to 192.168.5.X. Otherwise it will just be blocked there.
Also make sure the pfSense WAN does not have 'block private networks' set since that traffic is from a private subnet
Steve
-
@robh-0 Really! Ok then I may need to give this a try!
-
Thanks @stephenw10! Haven't had much time to play around with this (some unfortunate life events have been underway), but should get some thing this week! Ill test out all your suggestions and update the thread.
-
So I got a little time tonight to play around with it, but unfortunately still getting blocked. Below are some screenshots.
Even though I (believe) I set the firewall to all anything though, its still blocking it, which makes no sense to me.
The pfSense firewall rules:
The pfSsense firewall logs:
Current NAT settings:
-
Hmm, that certainly seems like it should pass with that allow all rule on WAN.
Do you see any alerts in the GUI?
Go to Status > Filter Reload and reload the filter with the button there. Make sure it loads cleanly without any errors.
Steve
-
@stephenw10 will do when I get home from work this evening
-
@stephenw10 This is what I get from the Filter Reload:
-
Looks fine. And you are still seeing blocked traffic in the firewall log on WAN like that?
-
@stephenw10 So if I try to access 192.168.5.6 (an iDrac that sits behind the pfSense box) I get "192.168.5.6 took too long to respond." but I dont see the firewall logging anything like it did before (see below). The 5.6 address is perfectly accessable by a laptop sitting behind the pfSense box, and the laptop can access the external web just fine.
