Hi Jouni, I don't necessarily need a config file if hostapd_cli can do the following: enable/disable interface (for wired) and modify radius attributes. >From what I could find, it seems to only be used to show various mibs, collect station information, and so on. Perhaps I need to modify some configs and recompile? How would I do the following?.... 1. Enable driver wired for say eth1, also disable EAP wired listening on eth3 2. Set a radius IP auth address 10.10.10.10, same for accounting, set auth and acct ports. 3. Monitor a port for authentication (I think this is easy enough to just detect when EAP completes with success or failure). 4. Detect link up/down so I can add/remove filtering on ports. I could probably do this outside hostapd but it would be nice to be able to control this via hostapd_cli. Thanks, Sam On Sat, Nov 19, 2016 at 4:49 PM, Jouni Malinen <j@xxxxx> wrote: > Do you need to even use a configuration file? hostapd control interface > can be used to dynamically add and remove interfaces, set configuration > parameters for those interfaces, and enable/disable interfaces. That's > what I would be using if there is any need for dynamic operations > instead of trying to stop and restart the process. > _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
