Added a Gateway - Created a blackhole!
-
Maybe an RTFM issue (though I have) but I was hoping to get some perspective on how PFSense routing works (coming from a guy who designs large scale routed networks and probably shouldn't have made this mistake).
I have a 2.4.5 based home setup (mostly WAN+LAN) but have a bunch of routers internally and need to add some static routes on the LAN side. If the PFsense FW was a normal router, and I wanted a route to 192.168.100.0/24 I'd just add it to the routing table with the appropriate GW.
I took this approach, added a LAN side GW and a corresponding static route, and instead of just adding this route, PFSense decided to change my 0/0 route to this new GW and shunt all my outbound to my internal LAN router and create a nice outage until I was able to deduce what it had done.
Why is it doing this? To add a LAN based static route, do I need to add a static 0/0 route or hit some setting to prevent it from being over written? Either I did something really wrong here process wise (seems not according to docs) or the routing approach here is really non-intuitive?
P
-
@badfish57
In system/routing/gateways you can select the default gateway.I'm unsure how the 'automatic' selection determines which one is default
-
Thanks, I did notice that and set the WAN_DHCP to default yet as soon as I add the new GW it becomes the default. I assume I can set the weight of the new one lower and that might help. Need to wait till evening to try again.