Actions
Regression #12617
closed
Dynamic DNS client updates using a private IP address when it cannot determine the public IP address
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
22.01
Release Notes:
Default
Affected Version:
2.6.0
Affected Architecture:
All
Description
Under some conditions the dyndns up client can send a private IP address even though 'Use public IP' is set.
For example:
Nov 24 01:01:31 fw1 php[64738]: rc.dyndns.update: phpDynDNS: updating cache file /conf/dyndns_wan_rfc2136_'my.dyndns.name'_ns1.netgate.com.cache: 192.168.1.5
That firewall is behind NAT and should never send it's local interface IP.
That was tested in the current 22.01 snapshot at the time but we have seen it in AWS in recent snaps.
Updated by Viktor Gurov over 2 years ago
Updated by Jim Pingle over 2 years ago
- Status changed from New to Pull Request Review
- Assignee set to Viktor Gurov
Updated by Viktor Gurov over 2 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
Applied in changeset 070fb1a8868bdb780952d2d3532a6059c97bd677.
Updated by Jim Pingle over 2 years ago
- Subject changed from DynDNS client can update using a private IP to Dynamic DNS client updates using a private IP address when it cannot determine the public IP address
Updating subject for release notes.
Updated by Viktor Gurov over 2 years ago
same fix for DynDNS (non-RFC2136):
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/538
Updated by Jim Pingle over 2 years ago
- Status changed from Feedback to Pull Request Review
Updated by Viktor Gurov over 2 years ago
- Status changed from Pull Request Review to Feedback
Applied in changeset 1fa4c4731bca54652becfb6737bdc3ea8851d6b7.
Actions