Hi Ben, Your patch works like a charm. The hostapd problem is fixed. Thanks, Ann On Fri, Mar 25, 2016 at 5:55 PM, Ann Lo <annlo.tech@xxxxxxxxx> wrote: > This is excellent information. > > Thanks, > Ann > > On Fri, Mar 25, 2016 at 5:49 PM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: >> On 03/25/2016 05:24 PM, Ann Lo wrote: >>> >>> Hi Ben, >>> >>> Thanks for your information and suggestion. Using -dd option, there >>> are more information from hostapd, including: >>> >>> nl80211: Beacon set failed: -16 (Device or resource busy) >>> >>> Further investigation result is that this happens in the following >>> scenario: >>> 1) hostapd runs OK at channel 36 using 80 MHz width. >>> 2) wpa_supplicant (using the same radio) tries to connect to a remote >>> AP on channel 36 using 20 MHz width. >>> 3) hostapd is restarted at this point. >>> 4) When hostapd comes up again, it gets the above error. >>> 5) At this point, wpa_supplicant connects successfully. >>> >>> The radio requires AP and client using the same channel. Does this >>> mean that the channel width must be the same? >> >> >> Channel width does not need to be the same, but the primary channel >> must be. >> >> You probably need a patch I put into hostapd to force not switching >> the primary channel when running multiple interfaces on a single radio. >> >> https://github.com/greearb/hostap-ct/commit/cd25b893c97da95b5b7cda0e61ea7bcf5355bc16 >> >> >> Thanks, >> Ben >> >> -- >> Ben Greear <greearb@xxxxxxxxxxxxxxx> >> Candela Technologies Inc http://www.candelatech.com >> _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
