On Sun, 2015-12-27 at 11:31 +0800, 邢冲 wrote:
Does connman has any plan to use hostapd for AP mode? any try or
ConnMan does not have any plans to use hostapd for AP mode. ConnMan is
implementing the host side of things so it will need to have
wpa_supplicant up and running in order to connect to WiFi networks. It
implements decent tethering capabilities that a laptop or phone user can
be assumed to be able to control. But ConnMan does not try to be a
router device; therefore it lacks some of the more advanced and exotic
configuration capabilities of a router.
For a client end device MAC address filtering looks like a nuisance.
It's very hard to have a decent API for it, not mention digging out the
MAC address for various WiFi devices or believing that any UI using user
should be able to figure out why some devices suddenly can connect while
others can't. Besides, it does not give any extra security in the first
place as the MAC address can be changed by an attacker.
In general the wpa_supplicant/hostapd split is somehting you need to
take up on the hostapd mailing list. After all it would be simpler for
everybody if there were just one well-maintained daemon with a properly
functioning D-Bus API.