Strange beahviors in 2.6 release

[Clouseau]

I have now seen in two 2.6 version firewall a situation where you can log in to GUI normally but you just cant change settings. I have now one unit that was able to generate internal CA authority certificates but not server sertificates at all. Usually this is trivial few minutes task but here it just does not do anything.

I have also major issues to asign new interface. I managed to assingn interface but I can give a IP or activate the interface.

This is extreamly strance as I have close to 50 these kind of firewall in use. This symphtom has come up with 2.6 release. Looks like it can't write to disk ?? Or could this corrupt the file system so that it just won't allow any changes to files?

I also had one 2.6 firewall that did not follow any firewall rule I made. It allowed all trafic out to the Internet even I had only Anti-Lockout rule in the interface??

Now I'm strugeling with one where I can't greate server sertificate and activate interface with any ip's.

Never ever seen like this in any version of pfSense history

[Cool_Corona]

2.6 seems broke in very fundamental ways.

I have stayed on 2.5.2 since the first 3 FW's I updated all had weird behaviour and MultiWAN and VLAN's are not working.

[jimp]

There isn't enough information to go on here, there aren't any known issues that match what you describe exactly.

Are you certain your users aren't set with the privilege that denies config changes? It's a common error people make when setting up users and groups to select the entire list, which also includes the privilege which denies them the ability to change the configuration.

Check the system log and see if it's logging any errors when you try to make changes.

It's also possible you have a hardware problem. Some SSDs and similar media can fail into a read-only state where they won't persistently store changes.