Project

General

Profile

Actions
Copy link

Regression #12617

closed

Dynamic DNS client updates using a private IP address when it cannot determine the public IP address

Added by Steve Wheeler over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Viktor Gurov
Category:
Dynamic DNS
Target version:
2.6.0
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.

Actions
Copy link

Also available in: Atom PDF