Project

General

Profile

Actions

Bug #16117

open

DYNDNS using the wrong source interface if Firewall State Policy is set to Interface Bound States

Added by Marcelo Cury 11 months ago. Updated about 10 hours ago.

Status:
Ready To Test
Priority:
Normal
Assignee:
-
Category:
Dynamic DNS
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.x
Affected Architecture:
amd64

Description

pfSense 2.7.2, all patches applied.
DYNDNS provider -> DUCKDNS
Default gateway of the firewall is a Gateway group in which WAN1 is the primary (TIER 1) and WAN2 is the backup (TIER2).
Firewall State Policy is set to Interface Bound States

DYNDNS configuration:
Interface to monitor: WAN2
Interface to send update from: WAN2

What is happening:
WAN1 IP address is being updated for the DYNDNS.

What should happen:
WAN2 IP address should be updated for the DYNDNS.

What actions I did to fix the issue ?

Changed Firewall State Policy is set to Interface Bound States to Floating States.
This fixed the issue.

Actions #1

Updated by Marcelo Cury 11 months ago

Just a fix to this section:

What actions I did to fix the issue ?

Changed Firewall State Policy from Interface Bound States to Floating States.
This fixed the issue.

Actions #2

Updated by Marcos M 11 months ago

  • Status changed from New to Ready To Test

Please re-test on 2.8.0-BETA - there have been various fixes related to the issue.

Actions #3

Updated by Marcelo Cury 11 months ago

Hello Marcos, thanks for answering.

I'll try to simulate that in my lab, I'll install a new NIC in my server to map that with libvirt.
But I can't do it right now, too busy lately unfortunately.

As soon as I have some free time, I'll test and update here.

Thanks.

Actions #4

Updated by Manuel Carrera about 10 hours ago

Hello, my ticket #16716 has been closed as a duplicate of this one. It seems this is indeed the same problem, except I haven't meddled with this "Firewall State Policy" setting for now.

Considering this problem is still happening on pfSense Plus 25.11.1, I think you can change this ticket back as not resolved.

Of course if you need to do some tests, I can do that.

Actions

Also available in: Atom PDF