On Sat, Nov 19, 2016 at 03:40:35PM -0500, Sam Tannous wrote:
> Ideally, I would like to just have *one* config file without the -i option
> and just specify a new "interfaces" (note the plural) option
> ("interfaces=swp1,swp2,...swpN") as the first line. Our CLI
> can create this file and then restart/reload hostapd as needed.
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.
> (The other features we plan to add are adding netlink awareness to the
> wired driver and
> adding an removing (layer2) filtering based on netlink messages and
> authentication
> status of particular stations. I've seen some filtering patches where
> this has been tried
> in the past. The plan is to use the linux tc filtering rules called
> from hostapd.
It would be interesting to see if something could be added to the
upstream version to get more functionality in this area.. I'm pretty
sure there are multiple implementations doing something like this, but
not very promising contributions to add that into hostap.git yet.
--
Jouni Malinen PGP id EFC895FA
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
