Hello, Context: I am working on some automation which involves wpa_supplicant and NetworkManager. My symptoms are that NetworkManager always creates a p2p device (seen in `nmcli dev`), which I would like to avoid for automation purposes. NetworkManager does this because wpa_supplicant says that the wlan device has P2P capabilities. My initial understanding was that I could avoid that by setting p2p_disabled=1 in wpa_supplicant config. However, this flag does not apply to newly-created interfaces. So when NetworkManager recreates the interface, the 'disabled' check always evaluates to false, which causes the 'p2p' flag to be set when NetworkManager examines it through dbus. This is the relevant part: https://w1.fi/cgit/hostap/tree/wpa_supplicant/dbus/dbus_new_handlers.c#n3538 I experimented a bit with wpa_cli as well - I don't see a way to configure wpa_supplicant to never advertise p2p capabilities for newly-created interfaces * `wpa_cli set p2p_disabled 1` sets `wpa_s->conf->p2p_disabled` which is checked in the dbus handler, but newly-created interfaces obviously don't inherit that flag * `wpa_cli p2p_set disabled 1` sets `wpa_s->global->p2p_disabled` which is not checked in the dbus new handler linked above (I'm also not sure if it can be set through a config file) I am likely misunderstanding a few things (I am entirely new to this code base) - but am wondering whether there is a way to achieve what I want? I am unsure whether wpa_supplicant really is working as expected. Maybe the solution would simply be to have NetworkManager have its own p2p_disabled setting instead of relying entirely on wpa_supplicant. Any advice welcome Thanks! _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
