Bug #4674
closedinvalid state table entries after WAN IP change
100%
Description
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.
Files
→L Updated by → luckman212 over 11 years ago
Interesting workaround! I will have to try this myself as we've had similar problems with SIP devices & Asterisk.
KB Updated by Kill Bill over 9 years ago
Can someone look into this? Sounds to me like the ordering here is indeed just wrong.
S- Updated by slu - over 9 years ago
SIP behind pfSense with changing WAN IP address is with this bug impossible.
I must delete every day the old states.
JP Updated by Jim Pingle about 7 years ago
- Category set to Rules / NAT
- Assignee set to Jim Pingle
- Target version set to 2.5.0
Looking at /etc/rc.newwanip it does appear to make more sense to configure before killing the old states.
JP Updated by Jim Pingle about 7 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset commit:86e6e0bcffcbb988dc7f80ac0aed25cad28d79eb.
JP Updated by Jim Pingle almost 7 years ago
- Target version changed from 2.5.0 to 2.4.5
JP Updated by Jim Pingle over 6 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.