Actions
Regression #15832
closedDDNS always resolves the public address using the default gateway
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
24.11
Release Notes:
Force Exclusion
Affected Version:
2.8.0
Affected Architecture:
Description
Reported on forum:
https://forum.netgate.com/topic/190842
- Create two DDNS entries, one set to WAN1 and another set to WAN2
- The IP address on the WAN2 interface/gateway must be a private IPv4 address.
- The cached IP address on the second entry using WAN2 shows the public IP address of WAN1.
Updated by Marcos M 23 days ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Fixed with 60ec37078eb9ed203a004f58e1eb94a7db6913fb.
This seems to be a regression in curl. More details:
https://github.com/curl/curl/issues/15553
Updated by Jim Pingle 22 days ago
- Status changed from Feedback to Resolved
Looks good on current snapshots.
Actions