pfSense

The Apply Changes button is being shown too early in the workflow.
PR https://github.com/pfsense/pfsense/pull/3058 should fix that, and hopefully clarify the message text so that it is clear that the user needs to adjust the assigned interfaces and save. Then use the Apply Changes button that is shown after saving.

Phillip Davis wrote:

The Apply Changes button is being shown too early in the workflow.
PR https://github.com/pfsense/pfsense/pull/3058 should fix that, and hopefully clarify the message text so that it is clear that the user needs to adjust the assigned interfaces and save. Then use the Apply Changes button that is shown after saving.

The way it worked in 2.2.X was when you hit apply changes it saved and rebooted the pfsense at the same time. When you have a interface mismatch you will most likely be changing the interface and/or IP your accessing the pfsense from. So the workflow how you have it would require you to hit save, re-access the pfsense using the new IP/Interface, then hit apply changes. An Apply changes that saves and reboot is more desirable.

"The way it worked in 2.2.X was when you hit apply changes it saved and rebooted the pfsense at the same time."

Hmmm - I had a quick look at the back-end processing code from 2.2.* before making that fix above. The code seems the same on 2.2.* and 2.3.* but maybe I missed something in how it used to work?

I am not in a position to do any realistic test of this at the moment. Maybe Chris or someone from ESF can check out what used to happen and what is now happening?