Bug 11974

Summary: hostapd: make client isolation configurable via WebUI
Product: IPFire Reporter: Peter Müller <peter.mueller>
Component: ---Assignee: Peter Müller <peter.mueller>
Status: CLOSED FIXED QA Contact:
Severity: Balancing    
Priority: Will affect an average number of users    
Version: 2   
Hardware: all   
OS: All   
See Also: https://bugzilla.ipfire.org/show_bug.cgi?id=12027
Attachments: Proposed patch for wlanap.cgi

Description Peter Müller 2019-01-22 17:38:27 UTC 
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.
Comment 1 Michael Tremer 2019-01-22 17:39:17 UTC 
I do not see any reason why this is a feature...
Comment 2 Peter Müller 2019-01-22 20:00:05 UTC 
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. :-)
Comment 3 Peter Müller 2019-01-24 15:49:59 UTC 
Forum post on how to do this: https://forum.ipfire.org/viewtopic.php?f=22&t=12274&p=79070&hilit=client+isolation#p79070
Comment 4 Peter Müller 2019-03-08 19:44:02 UTC 
Created attachment 656 [details]
Proposed patch for wlanap.cgi
Comment 5 Peter Müller 2019-03-16 14:21:29 UTC 
https://patchwork.ipfire.org/patch/2155/
Comment 6 Peter Müller 2019-03-18 16:03:51 UTC 
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=5b4464a94478059ceebf266bc31dee4a4ba18fac

This needs to be implemented in IPFire 3.x, too.