invalid state table entries after WAN IP change
This is similar to Bug #1629. I have a SIP client behind pfsense 2.2.2. When the WAN IP changes, there is a state table entry with the old IP, and the SIP client can not register anymore.
I suspect that this happens because the SIP client continuously generates packets, so that one could arrive between pfSense_kill_states and filter_configure_sync. My patch reverses the order of the two functions and seems to work, but I do not know whether this will introduce other problems.
Updated by Jim Pingle almost 2 years ago
- Status changed from Feedback to Resolved
No feedback from OP or previous commenters, and at least with a quick test here it appears to be doing the right thing now compared to the previous code.
Can revisit if people still encounter issues.