Currently, enabling or disabling client isolation feature requires manual configuration change and is thus reverted any time configuration is generated by the WebUI. There should be a checkbox to set this in a more comfortable way.
I do not see any reason why this is a feature...
I consider client isolation quite useful as it prevents malware from spreading in internal networks, hackers attacking other devices in the same wifi network, and so on. For these systems with WLAN I administer, I use to enable it via command line, but this is not very comfortable. So I do not see any reason why not adding a switch for it - it will not harm anything. :-)
Forum post on how to do this: https://forum.ipfire.org/viewtopic.php?f=22&t=12274&p=79070&hilit=client+isolation#p79070
Created attachment 656 [details] Proposed patch for wlanap.cgi
https://patchwork.ipfire.org/patch/2155/
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=5b4464a94478059ceebf266bc31dee4a4ba18fac This needs to be implemented in IPFire 3.x, too.
https://blog.ipfire.org/post/ipfire-2-23-core-update-131-is-available-for-testing
https://blog.ipfire.org/post/ipfire-2-23-core-update-131-released