Project

General

Profile

Actions

Bug #14829

closed

Multi-WAN Dynamic DNS does not fail over when preferred WAN loses link

Added by Georgiy Tyutyunnik 10 months ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Dynamic DNS
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.09
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

Link down for main WAN does trigger GW group failover to secondary WAN, but doesn't trigger DynDNS updatedns event.
System logs for the link up - link down attached


Files

syslogsDynDNS.txt (26.8 KB) syslogsDynDNS.txt Georgiy Tyutyunnik, 10/02/2023 03:37 PM

Related issues

Related to Bug #14626: Multi-WAN IPsec does not fail over when preferred WAN loses linkResolvedJim Pingle

Actions
Actions #1

Updated by Georgiy Tyutyunnik 10 months ago

  • Related to Bug #14626: Multi-WAN IPsec does not fail over when preferred WAN loses link added
Actions #2

Updated by Jim Pingle 10 months ago

  • Assignee set to Jim Pingle
Actions #3

Updated by Georgiy Tyutyunnik 10 months ago

  • File deleted (syslogsDynDNS.txt)
Actions #5

Updated by Jim Pingle 10 months ago

  • File 1087.diff added
  • Subject changed from DynDNS failover not triggered from losing WAN link in multiWAN scenario to Multi-WAN Dynamic DNS does not fail over when preferred WAN loses link
  • Status changed from New to Pull Request Review
  • Target version set to 2.8.0
  • Plus Target Version set to 23.09

I have a fix for this coming, but it needs more testing.

Internal MR is https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/1087

Diff to test via system patches is attached.

Actions #6

Updated by Jim Pingle 10 months ago

  • File deleted (1087.diff)
Actions #7

Updated by Jim Pingle 10 months ago

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

Updated by Danilo Zrenjanin 9 months ago

  • Status changed from Feedback to Resolved

Tested against:

23.09.b.20231013.0600

It works as expected.

I am marking this case resolved.

Actions #9

Updated by Jim Pingle 9 months ago

  • Target version changed from 2.8.0 to 2.7.1
Actions

Also available in: Atom PDF