Hi, short form: groups (either persistent or not) are added to an assumedly wrong interface if issued via dbus. if done via control interface, groups are added as expected. I have a test setup of 3 mac80211_hwsim radios (wlan0-2). In this scenario I use wlan0 and wlan2. Mesh0 is added to wlan0 with the command "iw phy phy1 interface add mesh1 type mp". wpa_cli reports: > interface Available interfaces: wlan2 wlan0 p2p-dev-mesh0 mesh0 Mesh0 network: network={ ssid="meshssid" mode=5 frequency=2437 key_mgmt=SAE psk="meshpassword" } Case 1: using wpa_cli: I select interface wlan0 and create a group via p2p_group_add. Group appears in wlan0 network list. Scanning using wlan2 shows both the mesh network and the newly created group. Case 2. using dbus. I get object path for interface wlan0 via "GetInterface" (resulting in /fi/w1/wpa_supplicant1/Interfaces/3). I issue a GroupAdd or ADDPersistentGroup. wpa_cli reports the groups under mesh0. Debug output confirms: dbus: fi.w1.wpa_supplicant1.Interface.P2PDevice.AddPersistentGroup (/fi/w1/wpa_supplicant1/Interfaces/3) [a{sv}] dbus: Register persistent group object '/fi/w1/wpa_supplicant1/Interfaces/1/PersistentGroups/1' [...] dbus: fi.w1.wpa_supplicant1.Interface.P2PDevice.GroupAdd (/fi/w1/wpa_supplicant1/Interfaces/3) [a{sv}] wpa_dbus_dict_open_read: start reading a dict entry dbus: Register group object '/fi/w1/wpa_supplicant1/Interfaces/1/Groups/wL' Groups are added under /fi/w1/wpa_supplicant1/Interfaces/. Is it intended so? I see that control interface and dbus handlers are completely different. Any help is welcome, Thanks, Viktor _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap