Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello
I am having difficulties getting RTL8188CUS working on Debian 7.8 (wheezy) LXDE on an old HP zv5112EA laptop.
It looks to me that the WiFi dongle is recognized but it can not connect to AP. After 3 days of tests I have no conclusion.
I am posting some command results which may be useful. Any help would be much appreciated.
Code:
$uname -a
Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.65-1+deb7u2 i686 GNU/Linux
$ sudo iwconfig
lo no wireless extensions.
wlan1 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr=2347 B Fragment thr:off
Encryption key:off
Power Management:off
eth0 no wireless extensions.
Code:
$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp
#home wifi
auto wlan1
iface wlan1 inet dhcp
wpa-ssid SKARM_2.4GHz
wpa-psk XXXXXXXX (<- 8 digits)
Code:
$ cat /etc/wpa_supplicant/wpa_supplicant.conf
update_config=1
ctrl_interface=/var/run/wpa_supplicant
# default eapol_version=1
eapol_version=2
ap_scan=1
fast_reauth=1
country=GR
# psk: WPA preshared key; 256-bit pre-shared key
# The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e.,
# 32 bytes or as an ASCII passphrase (in which case, the real PSK will be
# generated using the passphrase and SSID). ASCII passphrase must be between
# 8 and 63 characters (inclusive).
# This field is not needed, if WPA-EAP is used.
# Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys
# from ASCII passphrase. This process uses lot of CPU and wpa_supplicant
# startup and reconfiguration time can be optimized by generating the PSK only
# only when the passphrase or SSID has actually changed.
#sudo wpa_passphrase SKARM_2.4GHz (here goes my 8 digits)
network={
ssid="SKARM_2.4GHz"
scan_ssid=1
key_mgmt=WPA-PSK
#psk="XXXXXXXX" (here are the above 8 digits)
psk=xxxxxxxxx...xxxxxxxxxx (here are 64 hex digits)
}
Code:
$sudo cat /var/log/syslog
Mar 21 18:25:33 debian wpa_supplicant[1742]: wlan1: Failed to initiate AP scan
Last edited by SkarmoutsosV; 03-21-2015 at 11:35 AM.
Reason: Syntactic correction
$ ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
link/ether 00:02:3f:21:27:01 brd ff:ff:ff:ff:ff:ff
3: wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT qlen 1000
link/ether 04:8d:38:37:3e:1e brd ff:ff:ff:ff:ff:ff
$ sudo rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Actually syslog is full of two kind of messages the one is about AP scan as I posted earlier
and the second is dhclient which fails to get an IP. I suppose the latter is expected with no AP association.
Code:
$sudo grep wlan1 /var/log/syslog
debian dhclient: DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 3
Anyway, Head_on_a_Stick, thank you for your effort.
Any other suggestions are welcome.
Code:
$ sudo dmesg|grep wlan1
[ 10.920801] udevd[368]: renamed network interface wlan0 to wlan1
[ 17.655755] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 4320.333857] ADDRCONF(NETDEV_UP): wlan1: link is not ready
Last edited by SkarmoutsosV; 03-21-2015 at 01:31 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.