Project

General

Profile

Actions

Regression #12617

closed

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

Added by Steve Wheeler 5 months ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Dynamic DNS
Target version:
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 #2

Updated by Jim Pingle 5 months ago

  • Status changed from New to Pull Request Review
  • Assignee set to Viktor Gurov
Actions #3

Updated by Viktor Gurov 5 months ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions #4

Updated by Jim Pingle 5 months 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.

Actions #6

Updated by Jim Pingle 5 months ago

  • Status changed from Feedback to Pull Request Review
Actions #7

Updated by Viktor Gurov 5 months ago

  • Status changed from Pull Request Review to Feedback
Actions #8

Updated by Jim Pingle 3 months ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF