Bug #14597
open
Captive Portal: Allowed IPs are not working when config is inherited from earlier versions
0%
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 | ||
| Allowed-IP-old.JPG (59.1 KB) Allowed-IP-old.JPG | Allowed IPs inherited |
Updated by Jim Pingle over 1 year ago
Can you compare the config.xml contents from an older entry with a new entry to see what the difference is in the raw configuration? You can use the configuration history diff feature under Diagnostics > Backup & Restore to see what changed, for example, or just grab an entry from an older backup and compare to a current one.
Updated by Volker Werbus over 1 year ago
Hi Jim,
I already did.
The difference is the entry <dir>both</dir> is missing at the allowed IP. Looks like 2.6.0 and earlier did interpret the absence of this as “both directions” per default and 2.7.0 does not.
Best,
Volker