Project

General

Profile

Actions

Bug #4674

closed

invalid state table entries after WAN IP change

Added by Daniel Haid over 6 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Rules / NAT
Target version:
Start date:
05/04/2015
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

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

states-bug.patch (1.22 KB) states-bug.patch Daniel Haid, 05/04/2015 08:53 AM
Actions #1

Updated by → luckman212 over 6 years ago

Interesting workaround! I will have to try this myself as we've had similar problems with SIP devices & Asterisk.

Actions #2

Updated by Kill Bill almost 5 years ago

Can someone look into this? Sounds to me like the ordering here is indeed just wrong.

Actions #3

Updated by slu - almost 5 years ago

SIP behind pfSense with changing WAN IP address is with this bug impossible.
I must delete every day the old states.

Actions #4

Updated by Jim Pingle over 2 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.

Actions #5

Updated by Jim Pingle over 2 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #6

Updated by Jim Pingle about 2 years ago

  • Target version changed from 2.5.0 to 2.4.5
Actions #7

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.

Actions

Also available in: Atom PDF