Actually in Ubuntu the driver is cfg80211. what is the difference between 
nl80211?
should i make it as cfg80211 in configuration file. here is the 
configuration file. I didnt see 
any nl80211 when i give dmesg


#interface
interface=wlan1
# Select driver
driver=cfg82011
# Set access point name
ssid=myhotspot
# Set access point harware mode to 802.11g
hw_mode=g
# Set WIFI channel (can be easily changed)
channel=6
# Enable WPA2 only (1 for WPA, 2 for WPA2, 3 for WPA + WPA2)
wpa=2
wpa_passphrase=mypassword


Thanks
--M.Nithin

On Friday, August 1, 2014 11:55:58 AM UTC+5:30, Julian Calaby wrote:
>
> Hi Nithin, 
>
> On Fri, Aug 1, 2014 at 4:10 PM, Nithin Chakravarthy 
> <[email protected] <javascript:>> wrote: 
> > my wifi chipset is ap6210. But the same board with andrid os it is 
> working 
> > as AP 
>
> As you can see from the log, hostapd can't create a monitor mode 
> interface with that driver (it's not supported) and hostapd needs that 
> to do it's thing. 
>
> Android does things differently and (I believe) uses different drivers 
> so it doesn't have that restriction. 
>
> If you simply must have AP mode, I'd recommend getting a USB WiFi 
> stick that supports it. 
>
> Thanks, 
>
> Julian Calaby 
>
> > On Friday, August 1, 2014 10:49:42 AM UTC+5:30, Julian Calaby wrote: 
> >> 
> >> Hi, 
> >> 
> >> On Fri, Aug 1, 2014 at 3:03 PM,  <[email protected]> wrote: 
> >> > I have cubieboard2 running on ubuntu . wifi is working fine. But i 
> want 
> >> > turn it on as AP. Im doing it by using hostapd. But it is giving 
> these 
> >> > messages 
> >> > 
> >> > root@localhost:/# sudo hostapd -d /etc/hostapd/hostapd.conf 
> >> > 
> >> > Configuration file: /etc/hostapd/hostapd.conf 
> >> > nl80211: Add own interface ifindex 5 
> >> > Failed to create interface mon.wlan1: -95 (Operation not supported) 
> >> > nl80211: Failed to set interface wlan1 into AP mode 
> >> > nl80211 driver initialization failed. 
> >> > ELOOP: remaining socket: sock=4 eloop_data=0x2f0900 
> user_data=0x2f0ea8 
> >> > handler=0x28b9d 
> >> > ELOOP: remaining socket: sock=6 eloop_data=0x2f2848 user_data=(nil) 
> >> > handler=0x2e341 
> >> 
> >> Judging by this, your WiFi card doesn't support AP operation. 
> >> 
> >> Do you know what chipset it is? 
> >> 
> >> Thanks, 
> >> 
> >> -- 
> >> Julian Calaby 
> >> 
> >> Email: [email protected] 
> >> Profile: http://www.google.com/profiles/julian.calaby/ 
> >> .Plan: http://sites.google.com/site/juliancalaby/ 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "linux-sunxi" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to [email protected] <javascript:>. 
> > For more options, visit https://groups.google.com/d/optout. 
>
> -- 
> Julian Calaby 
>
> Email: [email protected] <javascript:> 
> Profile: http://www.google.com/profiles/julian.calaby/ 
> .Plan: http://sites.google.com/site/juliancalaby/ 
>

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to