Bug #15740
openNAT uses unknown IP address
0%
Description
The SIP phone, communicating through pfSense, stops working from time to time.
Checking the state table it shows that the NAT translation, only for the phone, is happening to an IP address 84.230.48.58 which doesn't exist on the pfSense (probably an old WAN IP address). The PPPoE interface uptime is couple of hours, which there was a WAN IP address change recently.
NAT for all other connections are OK.
The real WAN IP address is 87.97.33.xx but the SIP packets from the phone are translated to 84.230.48.58
After disconnecting the phone for two minutes the faulty state cleared from pfSense. After connecting the phone again a new state has been created and the NAT is now happening with the correct IP address, and the phone is working again.
Netgate SG-2440 24.03-RELEASE
Basic Vanilla setup with no additional packages installed like siproxd.
There is only one host communicate to this remote IP:Port.
There is no 1:1 NAT and port randomization is enabled.
There is no static port configured.
So far I experienced incorrect NAT issue, which causes a SIP phone to stop working, at three locations, each with different pfSense hardware (1100, 4200, SG-2440) and with different SIP phone make and models.
Very similar case to https://redmine.pfsense.org/issues/15535 (incorrect NAT) but here we can't say that "If you use NAT in such a way that it would try to make two connections use the same conflicting information, it will fail to create a NAT state and the second connection will egress without NAT." Here the packets don't egress without NAT, the NAT is happening, but to an IP address which doesn't exist on the pfSense.
Files
Updated by dylan mendez 3 months ago
We need more information.
Are these two networks bridged? 192.168.0.0/24 and 10.10.3.0/24?
Updated by dylan mendez 3 months ago
Can you provide a status output of your firewall here?
https://nc.netgate.com/nextcloud/s/qpLyFbyx2cwokH8
https://docs.netgate.com/pfsense/en/latest/recipes/diagnostic-data.html
Updated by David G 3 months ago
There was a recent IP address change on the PPPoE interface to 78.131.44.xx, but the state was again kept using the previous ip address 87.97.33.xx so the phone stopped working.
I created and uploaded the diagnostic file. Please let me know if you haven't receive it.
Hopefully you can see all these happening in the uploaded diagnostic file.
Then I did the same trick, disconnected the phone's Ethernet for two minutes, the faulty state disappeared from pfSense, than I connected the phone again which created a new state with the correct IP PPPoE WAN IP address.
Updated by David G about 2 months ago
I provided all the information Dylan requested. Why did you change the status to Incomplete?
Updated by David G about 2 months ago
The dignostic files have been uploaded on the link provided.
Updated by dylan mendez 4 days ago
Based on this:
"There was a recent IP address change on the PPPoE interface to 78.131.44.xx, but the state was again kept using the previous ip address 87.97.33.xx so the phone stopped working."
This is not a bug.
Please see https://docs.netgate.com/pfsense/en/latest/config/advanced-networking.html#reset-all-states