On Fri, Oct 30, 2015 at 08:59:51PM +0530, Krishna Chaitanya wrote: > When STA-VIF is connected to AP: Channel 10 > > with p2p_oper_channel=1, using p2p_connect with go_intent=15, the > Group is starting in channel 10 even though the driver is MCC capable. p2p_oper_channel parameter should not be used for any production use case. If you want to specify the operating channel, use the freq=<MHz> argument with P2P_CONNECT. > So we have added "p2p_ignore_shared_freq" to the config file, still > the same behavior is seen. That should work if you specify the operating channel with the P2P_CONNECT command. > What is the ideal solution? > > 1) Change wpas_p2p_setup_freqs to take cfg->op_channel as highest priority. No, p2p_oper_channel configuration parameter should not be used for anything. The only potentially acceptable change would be to remove it completely from wpa_supplicant, but I don't want to do that since it may break parsing of existing configuration files. > 2) Make the pref_freq 0 (similar thing is done for invite case), but > still the op_channel in config file is not honored. > 3) Make the pref_freq=cfg->op_channel. 4) Use the documented (wpa_supplicant/README-P2P) freq parameter to p2p_connect. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
