Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
| 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
09-28-2016, 03:05 PM
|
#1
|
|
LQ Newbie
Registered: Sep 2016
Posts: 5
Rep: 
|
iwconfig finds no wireless extensions, yet my Edimax EW-7811un can connect to internet
Hello,
I am running 4.4.6-gentoo on my desktop computer. I use a Edimax EW-7811un in order to connect to our router. However, there are times when my network randomly disconnects and I have to kill dhcpcd and rerun it in order to reach the internet again. This doesn't happen on my Windows 7 boot, so I know it's nothing to do with the hardware or my connection strength. Even stranger is although using dhcpcd and wpa_supplicant works, iwconfig cannot find a wireless extension.
I was wondering if anyone had a similar problem, and if so, if they managed to find a solution to this behaviour.
Cheers!
(P.S. I apologize if I have omitted any information required for context. This is my first time posting for help on a forum)
|
|
|
|
|
09-30-2016, 09:58 AM
|
#2
|
|
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,197
|
The contents of wpa_supplicant.conf would be interesting. Some distros have it in /etc/, others in /etc/wpa_supplicant/. Could we see it? Hide your passwords, of course.
Also while you're online, check & post the output of The error about 'no wireless extensions' may relate to a particular interface, not the box in general. |
|
|
|
|
09-30-2016, 03:56 PM
|
#3
|
|
Moderator
Registered: Mar 2008
Posts: 22,228
|
Hello and welcome to LQ.
I bought that online last year for maybe $9. As I recall I had to add in the driver for it. Did Gentoo supply the driver or did you add one in? Mine under Debian works flawless so far.
Also there might be some logs located that might offer clues. Usually under /var someplace.
|
|
|
|
|
09-30-2016, 06:47 PM
|
#4
|
|
Member
Registered: Sep 2003
Location: 19th moon ................. ................Planet Covid ................Another Galaxy;............. ................Not Yours
Posts: 705
Rep:
|
AFAIK, even if you are using something such as Portage/Emerge/etc., there are still what could be termed, package dependencies.
In other words, no matter how "magical"/helpful a tool like Portage may seem, there can still be problems with what some Human specified, or neglected to specify, as a dependency between packages. So an install of software may seem to work flawlessly, but something that is needed by the software that was installed, might actually be missing.
I once installed some software to handle a particular manufacturer's video hardware; during the install of software I'll just call A, there were dependencies included in A, on B and C; so all three things were installed.
Given the details of the situation, it should have been possible to keep B and C installed for other purposes, but remove A; when I tried that, things "broke". I discovered that there was actually a library bundled with A, which was needed by B and C, but no one had specified that B and C depend on A.
If nothing else solves the problem, you might want to check dependencies for whatever "wireless extension" it is, about which iwconfig is complaining.
Last edited by rigor; 09-30-2016 at 06:49 PM.
|
|
|
|
|
10-03-2016, 02:35 PM
|
#5
|
|
LQ Newbie
Registered: Sep 2016
Posts: 5
Original Poster
Rep:
|
Here's the wpa_supplicant.conf:
Code:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
network={
ssid="Zelda-II-Adventure-of-Linksys"
psk=****************
proto=RSN
key_mgmt=WPA-PSK
group=CCMP TKIP
pairwise=CCMP TKIP
priority=5
}
I activate my wireless network using the shell script below (to which I have added output files for debugging):
Code:
#output ifconfig -a before loading driver
ifconfig -a > ifconfig1.txt;
#load driver
modprobe rtl8192cu >;
sleep 2;
#output ifconfig -a after driver has been loaded
ifconfig -a > ifconfig2.txt;
#run wpa_supplicant and send debugging output to wpa_supplicant.txt
wpa_supplicant -B -i wlp0s20u2 -c /etc/wpa_supplicant/wpa_supplicant.conf -f wpa_supplicant.txt;
sleep 4;
#output ifconfig -a after wpa_supplicant has been running for 4 seconds
ifconfig -a > ifconfig3.txt;
#run dhcpcd on wireless interface
dhcpcd wlp0s20u2;
#
ifconfig -a > ifconfig4.txt;
Here's the output of ifconfig1.txt (before driver is loaded):
Code:
enp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 74:d4:35:0b:2a:bd txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 8 bytes 544 (544.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 544 (544.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sit0: flags=128<NOARP> mtu 1480
sit txqueuelen 1 (IPv6-in-IPv4)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Here's the output of ifconfig2.txt (after driver is loaded):
Code:
enp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 74:d4:35:0b:2a:bd txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 8 bytes 544 (544.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 544 (544.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sit0: flags=128<NOARP> mtu 1480
sit txqueuelen 1 (IPv6-in-IPv4)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp0s20u2: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 74:da:38:8f:70:90 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
The output of ifconfig3.txt (after wpa_supplicant is run):
Code:
enp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 74:d4:35:0b:2a:bd txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 11 bytes 850 (850.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 11 bytes 850 (850.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sit0: flags=128<NOARP> mtu 1480
sit txqueuelen 1 (IPv6-in-IPv4)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp0s20u2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::76da:38ff:fe8f:7090 prefixlen 64 scopeid 0x20<link>
inet6 2601:405:4400:4939:76da:38ff:fe8f:7090 prefixlen 64 scopeid 0x0<global>
ether 74:da:38:8f:70:90 txqueuelen 1000 (Ethernet)
RX packets 6 bytes 742 (742.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 13 bytes 1468 (1.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
The output of ifconfig4.txt (after dhcpcd is run on the wireless interface):
Are there supposed to be so many ipv6 addresses?
Code:
enp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 74:d4:35:0b:2a:bd txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 11 bytes 850 (850.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 11 bytes 850 (850.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sit0: flags=128<NOARP> mtu 1480
sit txqueuelen 1 (IPv6-in-IPv4)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp0s20u2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::76da:38ff:fe8f:7090 prefixlen 64 scopeid 0x20<link>
inet6 2601:405:4400:4939::5ebe prefixlen 128 scopeid 0x0<global>
inet6 2601:405:4400:4939:d2dc:27c2:c67a:2528 prefixlen 64 scopeid 0x0<global>
inet6 2601:405:4400:4939:76da:38ff:fe8f:7090 prefixlen 64 scopeid 0x0<global>
ether 74:da:38:8f:70:90 txqueuelen 1000 (Ethernet)
RX packets 11 bytes 1598 (1.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 21 bytes 2751 (2.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Last edited by samanthaAlison; 10-03-2016 at 02:45 PM.
|
|
|
|
|
10-03-2016, 02:43 PM
|
#6
|
|
LQ Newbie
Registered: Sep 2016
Posts: 5
Original Poster
Rep:
|
Here's the head of debugging file for wpa_supplicant:
Code:
Successfully initialized wpa_supplicant
rfkill: Cannot open RFKILL control device
wlp0s20u2: SME: Trying to authenticate with 84:00:2d:74:96:68 (SSID='Zelda-II-Adventure-of-Linksys' freq=2462 MHz)
wlp0s20u2: CTRL-EVENT-DISCONNECTED bssid=84:00:2d:74:96:68 reason=2 locally_generated=1
wlp0s20u2: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp0s20u2: Trying to associate with 84:00:2d:74:96:68 (SSID='Zelda-II-Adventure-of-Linksys' freq=2462 MHz)
wlp0s20u2: Associated with 84:00:2d:74:96:68
wlp0s20u2: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
wlp0s20u2: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
wlp0s20u2: WPA: Could not verify EAPOL-Key MIC - dropping packet
wlp0s20u2: Authentication with 84:00:2d:74:96:68 timed out.
wlp0s20u2: CTRL-EVENT-DISCONNECTED bssid=84:00:2d:74:96:68 reason=3 locally_generated=1
wlp0s20u2: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp0s20u2: SME: Trying to authenticate with 84:00:2d:74:96:68 (SSID='Zelda-II-Adventure-of-Linksys' freq=2462 MHz)
wlp0s20u2: Trying to associate with 84:00:2d:74:96:68 (SSID='Zelda-II-Adventure-of-Linksys' freq=2462 MHz)
wlp0s20u2: Associated with 84:00:2d:74:96:68
wlp0s20u2: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
wlp0s20u2: WPA: Key negotiation completed with 84:00:2d:74:96:68 [PTK=CCMP GTK=TKIP]
wlp0s20u2: CTRL-EVENT-CONNECTED - Connection to 84:00:2d:74:96:68 completed [id=0 id_str=]
wlp0s20u2: CTRL-EVENT-DISCONNECTED bssid=84:00:2d:74:96:68 reason=3 locally_generated=1
wlp0s20u2: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp0s20u2: SME: Trying to authenticate with 84:00:2d:74:96:68 (SSID='Zelda-II-Adventure-of-Linksys' freq=2462 MHz)
wlp0s20u2: Trying to associate with 84:00:2d:74:96:68 (SSID='Zelda-II-Adventure-of-Linksys' freq=2462 MHz)
wlp0s20u2: Associated with 84:00:2d:74:96:68
wlp0s20u2: CTRL-EVENT-DISCONNECTED bssid=84:00:2d:74:96:68 reason=3 locally_generated=1
wlp0s20u2: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp0s20u2: SME: Trying to authenticate with 84:00:2d:74:96:68 (SSID='Zelda-II-Adventure-of-Linksys' freq=2462 MHz)
wlp0s20u2: Trying to associate with 84:00:2d:74:96:68 (SSID='Zelda-II-Adventure-of-Linksys' freq=2462 MHz)
wlp0s20u2: Associated with 84:00:2d:74:96:68
wlp0s20u2: CTRL-EVENT-DISCONNECTED bssid=84:00:2d:74:96:68 reason=3 locally_generated=1
wlp0s20u2: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
And this is the dmesg output of the loading of the driver (and the activation of wpa_supplicant):
Code:
[ 680.603594] rtl8192cu: Chip version 0x10
[ 680.637239] rtl8192cu: MAC address: 74:da:38:8f:70:90
[ 680.637385] rtl8192cu: Board Type 0
[ 680.637580] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 680.637756] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[ 680.638018] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 680.638155] usbcore: registered new interface driver rtl8192cu
[ 680.639104] rtl8192cu 3-2:1.0 wlp0s20u2: renamed from wlan0
[ 682.828228] rtl8192cu: MAC auto ON okay!
[ 682.838966] rtl8192cu: Tx queue select: 0x05
[ 683.220326] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u2: link is not ready
[ 684.236509] wlp0s20u2: authenticate with 84:00:2d:74:96:68
[ 684.257535] wlp0s20u2: send auth to 84:00:2d:74:96:68 (try 1/3)
[ 684.289650] wlp0s20u2: authenticated
[ 684.290122] wlp0s20u2: associate with 84:00:2d:74:96:68 (try 1/3)
[ 684.335928] wlp0s20u2: RX AssocResp from 84:00:2d:74:96:68 (capab=0x431 status=0 aid=2)
[ 684.337114] wlp0s20u2: associated
[ 684.337272] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20u2: link becomes ready
[ 684.338704] cfg80211: Regulatory domain changed to country: US
[ 684.338848] cfg80211: DFS Master region: FCC
[ 684.338885] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 684.339286] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
[ 684.339532] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (N/A)
[ 684.339780] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
[ 684.340028] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)
[ 684.340276] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
[ 684.340521] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
|
|
|
|
|
10-03-2016, 02:48 PM
|
#7
|
|
LQ Newbie
Registered: Sep 2016
Posts: 5
Original Poster
Rep:
|
I've also seen through the wpa_supplicant log that the adapter is able to scan for other wireless networks.
I do have the driver compiled and loaded for my system, so I have no idea how to fix this. I'm going to try reinstalling the driver on the cd that came with the adapter and update if anything changes about the situation. :\
|
|
|
|
|
10-03-2016, 06:16 PM
|
#8
|
|
LQ Newbie
Registered: Sep 2016
Posts: 5
Original Poster
Rep:
|
UPDATE: I fixed the issue by using dkms to install rtl8912-fixes, and then running wpa_supplicant with the driver wext. Marking post as solved
|
|
|
|
|
10-04-2016, 02:53 AM
|
#9
|
|
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,197
|
Glad you're sorted.
|
|
|
|
All times are GMT -5. The time now is 04:27 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.
|
|
 Latest Threads
LQ News
|
|
