Bug #1629 - will a fix make it for 2.2?
-
https://redmine.pfsense.org/issues/1629 (invalid state table entries after WAN IP change)
This is one of the oldest bugs that I am tracking - wondering if anyone knows whether a fix was in the works for 2.2 or if this can is getting kicked to 2.3. I have a few Asterisk boxes behind pfSense firewalls that I have to manually restart after WAN failovers, so I am hoping for a fix one day!
-
I downloaded and am testing for this reason as well.
So far so good but its early days.
-
Edit: removed pointless quote, apparently what I wrote and what got posted were two very different things.
Sum total: 1. I've been tracking this bug forever 2. Thanks, Chris!
-
I committed what will likely be a fix for this issue earlier, it'll be in all 29th and newer snapshots. See my comment here for info on how to enable it:
https://redmine.pfsense.org/issues/1629#note-62I'll add a GUI option under System>Advanced if my testing works as expected. It's available to manually enable for those who want to try it.
-
I had this problem through the 2.1.x series, but have not yet seen it since I started running 2.2alpha. Good to know the option is available if needed, and nice that it's in the config file.
Can this replace the existing GUI option for state killing when a gateway goes down (system - advanced - miscellaneous)?
-
Can this replace the existing GUI option for state killing when a gateway goes down (system - advanced - miscellaneous)?
No, those are two completely separate things. Your IP may not change when a gateway goes down, and your gateway may not go down when your IP changes.