On Wed, 2016-06-08 at 08:29 -0700, Ali Nematollahi wrote:
> I can rebuild again but doesn't my current log say:
>
> Supported interface modes:
>
> * IBSS
>
> * managed
>
> * AP
>
> * AP/VLAN
>
> Doesn't it mean it supports ap mode and it was built with ap support?
>
Yeah, that means the *driver* is built with AP mode support. My latest
email was that wpa_supplicant wasn't built with AP mode support. The
driver only provides some mechanisms to put the card into AP mode, but
the supplicant itself (or hostapd) is what actually makes AP mode work.
So you need to make sure wpa_supplicant is built with CONFIG_AP=y too.
Dan
> On Jun 7, 2016 2:13 PM, "Dan Williams" <dcbw redhat com> wrote:
>
> >
> > On Tue, 2016-06-07 at 13:00 -0700, Ali Nematollahi wrote:
> > >
> > > I've been using AP mode for over a year with the same set up. I
> > > use
> > > many
> > > commands to set it up but it has been working perfectly fine.
> > > Here is
> > > the
> > > output you requested:
> > I misread the error message; it's not from the kernel, but from
> > wpa_supplicant. Your supplicant hasn't been built with AP mode
> > support, so you'll need to rebuild it with CONFIG_AP=y in the build
> > config. NM is supposed to detect that the supplicant doesn't have
> > that
> > support, but I guess that's not working for some reason.
> >
> > Dan
> >