linux-kernel - Re: r8712u cannot set essid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Apr 2011 19:14:15 +0800
From:	Jeff Chua <jeff.chua.linux@...il.com>
To:	Larry Finger <Larry.Finger@...inger.net>
Cc:	lkml <linux-kernel@...r.kernel.org>, wlanfae@...ltek.com
Subject: Re: r8712u cannot set essid

On Mon, Apr 25, 2011 at 12:32 PM, Jeff Chua <jeff.chua.linux@...il.com> wrote:

Larry,

Saw this post from you about putting the r8712u into "ap mode" below ...

Larry Finger | 27 Jan 15:39
> Re: unable to put RTL8192SU in master mode
> Master mode with r8712u has not been tested. The driver I started with has a
> configuration parameter that enables "AP mode". I kept that in, but I do not
> know if it works.

Here's what I tried, but not sure if this is the correct way to put
into AP mode ...

# modprobe r8712u network_mode=4

Then, I ran ...

# wpa_supplicant -d -D hostap -i wlan0 -c /etc/wpa42.conf

wpa_driver_hostap_set_wpa: enabled=1
...
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
...
wlan0: AP mode support not included in the build

Is wpa_supplicant saying the r8172u is not in AP mode?

Regarding setting essid I posted earlier, it seems the ssid can be set
when wlan0 is "associated" to an AP. But, not set if not associated.
With IBSS mode, there's no association to begin with, so the SSID
can't be set. Make sense?

Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/