Right, your wlan0 seems to be sitting there but not joining the network. The driver etc looks ok so far. You're down to wpa_supplicant, protocols, & dhcp.
1. Os the psk in wpa_supplicant.conf passed through wpa_passpgrase? You get an output to paste into wpa_supplicant.conf Code:
bash-4.3$ wpa_passphrase My_ESSID My_Password Code:
wpa_supplicant -c/path/to/wpa_supplicant.conf -i wlan0 -Dwext >> some.log && dhcpcd wlan0 >>some.log |
Quote:
Quote:
Code:
[root@darkmoon:log] # wpa_supplicant -c/etc/wpa_supplicant.conf -i wlan0 -Dwext >> /var/log/bk.log && dhcpcd wlan0 >> /var/log/bk.log Code:
Feb 9 22:22:05 darkmoon kernel: [95066.510646] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3) Code:
Feb 9 22:22:05 darkmoon kernel: [95066.279479] brcmfmac: power management disabled Code:
[root@darkmoon:log] #cat /var/log/bk.log |
On that output, the software looks ok, and you have driver or firmware trouble. One thing to try is that there's another -D option for wpa_supplicant, e.g. nl802.11. That's easy.
The messier bit is getting a driver & firmware your system agrees with, especially as you're Arm based & not x86. I think there's a big endian/little endian thing going on between those 2. If that doesn't sort it, and you get drivers that work for others & not you, we might end up calling the hardware dud. Ebay has usb wifi modules that plug into usb & provide wifi. I think you need the usbnet kernel module. I got one for the RasPi 1 I had, and it worked like a dream. |
@ slackist,
Sorry, been busy, I note that your system sets up wlan0 and that you have setup your essid, After that have you run ifconfig wlan0 up and then iwlist wlan0 scan? If you did and get a list of networks including your own then may I suggest that you forget about wpa supplicant et.al. and try using wicd. Wicd does not require you to have wpa supplicant configured, nor does network manager for that matter, but I find wicd easier to use. Just be sure that you have removed any entries you may have made in /etc/rc.d/rc.inet1.conf or wicd will not work. I never bothered with wpa supplicant so I'm not sure what you should do with that but probably it too would need any configs to be removed. |
Quote:
Quote:
|
This may be a wicd configuration problem.
That happened to me on an install to a bananapro. I had first gotten the pro up and running with a wired connection to my lan. When I then tried to configure to wireless with configs known to be correct it just rolled around. It turned out that wireless was turned off in wicd. I was able to connect once I turned it on. I was in an x session via ssh when I did it and don't remember exactly how now. Here's a link that might give you some ideas http://www.linuxquestions.org/questi...ff-4175475544/ I remember at the time I found some other references to this problem and solution so have a look. |
May I chime in some?
tcpdump can rely some of the 802 frame headers Also aircrack-ng might help a bit If not, alone the RTFMing of the respective chapters of said apps might shed a light of the culprits? IIRC the problem is the immature driver/firmware of the wifi MAC, so reading the module source might help even But before anything: /sbin/modinfo <module of ours> Would yield a clue? |
maybe this solves your problem ....
https://debianforum.de/forum/viewtop...142749#p935640 # /etc/modprobe.d/regdomain.conf options cfg80211 ieee80211_regdom=[your_country_code] have phun :) |
I'm not confident that will sort it as his wifi is puking on normal setup instructions. At the risk of repeating myself from post #20
Quote:
|
Reminds me of the days of ACX100 and how it got from a patch to mainline :)
My bet: kernel side (=not ready yet). Remedy: try upgrade kernel until it works? |
I believe I'm having a very similar issue. My Raspberry Pi was connecting to a WiFi network for months without issue. About a week ago it suddenly stopped and will not associate with the AP.
`iwlist wlan0 scan` shows the network is available: Code:
Cell 02 - Address: D6:D9:19:9A:00:5A /etc/network/interfaces contents: Code:
# interfaces(5) file used by ifup(8) and ifdown(8) /etc/wpa_supplicant/wpa_supplicant.conf contents: Code:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev When I run `wpa_supplicant -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf` I receive this error: Code:
Successfully initialized wpa_supplicant |
If the config hasn't changed since the problems began, I would leave them. They look believeable.
What else happened around the same time as the problems? Kernel update? Software update? That's where to look. You also can specify more authentication methods than just ccmp. I believe one of them is going out (don't remember which), but you can hedge your bets there. If that fails, I would start reinstalling packages, and finally suspect hardware. |
Thanks, @business_kid.
It could have been a software and/or kernel update. I try to keep the PI updated. What packages do you suggest that I reinstall? Can you point me to where I could learn about other authentication methods other than ccmp? |
I would first disable WPA altogether and see if you can connect with dhcpcd. If you succeed, that clears the rest of it. Reinstall WPA supplicant
Man wpa_supplicant.conf provides info. |
Hello together,
maybe offtopic, but just a really stupid idea, which should be checked: Move the Raspberry more near to the Router Rationale: Some years in the past I got an issue with RPI2 and USB-WLANstick, I dont remember much details, but after hours of trying to connect and finding out the issue I fixed it as follows: Setup was: RPI2, WLAN accesspoint configured S2-smartphone tries to connect Network (SSID of the RPI) showed up on the smartphone, all seemed fine, but from my seat (3m away from the router) I got always "Authentication failed". Once moving the Smartphone near to the Raspberry all worked fine ...:-) just an idea, ignore if it does not help Good job, thank you really much for your deep analysis above! It gave me some more hints how to analyze issues with the WLAN! best regards Uwe PS: I currently have got the same issue like above, in a few days I will move the RPI setup to the 1st floor, where the router resides ... maybe it helps for me :-) |
All times are GMT -5. The time now is 03:38 AM. |