Project

General

Profile

Actions

Bug #14597

open

Captive Portal: Allowed IPs are not working when config is inherited from earlier versions

Added by Volker Werbus 10 months ago. Updated 10 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Captive Portal
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.0
Affected Architecture:
SG-1100, amd64

Description

Hi PFSense developers,

we are running 200+ locations with PFSense, varoius hardware, various versions. We did a major update last nite in about 50% of the locations and noticed that some allowed IPs where not working properly in the captive portal. See screenshots attached.
Those IPs were inherited from config file generated initially on version 2.3.1 and we noticed that the two "direction arrows" were not shown. This was not a problem until the recent update. If we delete those IPs and type them in again, the arrows are showing and everything works.


Files

Allowed-IP-new.JPG (58.3 KB) Allowed-IP-new.JPG Allowed IPs deleted and typed in again Volker Werbus, 07/21/2023 08:12 AM
Allowed-IP-old.JPG (59.1 KB) Allowed-IP-old.JPG Allowed IPs inherited Volker Werbus, 07/21/2023 08:12 AM
Actions

Also available in: Atom PDF