Bug #8806: HA sync : Starting captiveportal doesn't fire ipfw rules on slave, even if HA is enabled. - pfSense - pfSense bugtracker

Bug #8806

HA sync : Starting captiveportal doesn't fire ipfw rules on slave, even if HA is enabled.

Added by A FL over 2 years ago. Updated over 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Renato Botelho

Category:

Captive Portal

Target version:

2.4.4

Start date:

08/19/2018

Due date:

% Done:

100%

Estimated time:

Affected Version:

All

Affected Architecture:

All

Release Notes:

Default

Description

When a CP zone is enabled, slave does not start the captive portal (despite "enabled" setting appear checked on the slave):
One workaround to this is to manually start captiveportal on the slave by clicking "submit" on the salve cp settings, or by rebooting the slave.

I think it would be better to automatically start the slave if captiveportal sync is ensabled in System-> High Avaliablity settings

Associated revisions

Revision 7cab6335 (diff)
Added by Renato Botelho over 2 years ago

Fix #8806: Configure captive portal on secondary identical as master HA node

History

#1 Updated by Jim Pingle over 2 years ago

Target version set to 2.4.4

I wonder if this might be the same root cause as #8721

An XMLRPC sync used to trigger filter_configure via XMLRPC which handled refreshing a number of things on the secondary after a sync. It doesn't now, which may be the cause of these issues.