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 for Android: free password hash cracker in your pocket

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

Message-ID: <4DB4E94C.2060505@lwfinger.net>
Date:	Sun, 24 Apr 2011 22:23:56 -0500
From:	Larry Finger <Larry.Finger@...inger.net>
To:	Jeff Chua <jeff.chua.linux@...il.com>
CC:	lkml <linux-kernel@...r.kernel.org>, wlanfae@...ltek.com
Subject: Re: r8712u cannot set essid

On 04/24/2011 09:16 PM, Jeff Chua wrote:
> I'm having problem trying to set essid on the "Realtek RTL8188S WLAN
> Adapter" with the r8172u module on 2.6.39-rc4. There's no error. Just
> can't set.
>
>
> # dmesg ...
> r8712u: module is from the staging directory, the quality is unknown,
> you have been warned.
> r8712u: DriverVersion: v7_0.20100831
> r8712u: register rtl8712_netdev_ops to netdev_ops
> r8712u: USB_SPEED_HIGH with 4 endpoints
> r8712u: Boot from EFUSE: Autoload OK
> r8712u: CustomerID = 0x0000
> r8712u: MAC Address from efuse = 90:61:0c:01:8f:b0
> usbcore: registered new interface driver r8712u
> r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
> r8712u: 1 RCR=0x153f00e
> r8712u: 2 RCR=0x553f00e
>
> # iwconfig wlan1 essid "tryanything"
> # iwconfig wlan1
> wlan1     IEEE 802.11b  ESSID:""  Nickname:"rtl_wifi"
>            Mode:Ad-Hoc  Cell: Not-Associated   Bit Rate:0 kb/s
>            Sensitivity:0/0
>            Retry:off   RTS thr:off   Fragment thr:off
>            Encryption key:off
>            Power Management:off
>            Link Quality:0  Signal level:0  Noise level:0
>            Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>            Tx excessive retries:0  Invalid misc:0   Missed beacon:0

The code requires the interface to be up before the essid can be set. If you do 
it with the iwconfig command, you will see an error message.

I'm not sure if this is a reasonable requirement before allowing the essid to be 
set. Any thoughts?

Larry
--
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/