You are not logged in.
Every so often, I will lose my wireless connection and am unable to connect again, using iwconfig and dhcpcd. It has nothing to do with the router, since all other devices function properly, with no disconnection at all. I am only ever able to connect the first time (using a script specified in rc.local) and after that, dhcpcd just fails.
I think it started happening after I installed kernel 2.6.24. I am using the rt61 drivers, I tried installing the newest drivers, but they didn't fix the problem.
dhcpcd outputs:
err, wlan0: timed out
warn, wlan0: using IPV4LL address 169.254.61.72
And messages from dmesg that may be telling:
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:16:01:8e:e6:ab
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: RX authentication from 00:16:01:8e:e6:ab (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:16:01:8e:e6:ab
wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
with
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
and
ADDRCONF(NETDEV_UP): wlan0: link is not ready
also occuring.
The script used to connect at start up is just:
#!/bin/bash
killall dhcpcd
ifconfig wlan0 up
iwconfig wlan0 essid 0016018EE6AA
iwconfig wlan0 key fede0fede0
dhcpcd -t 10 wlan0
so I don't think it can be anything to do with it.
Offline
I was getting a bit complacent since I hadn't run into the problem since I posted, but it happened again.
Anyone got any ideas?
Offline
Happened again.
Offline
This is becoming an annoying occurence now.
More error messages:
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:16:01:8e:e6:ab
wlan0: RX authentication from 00:16:01:8e:e6:ab (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:16:01:8e:e6:ab
wlan0: RX AssocResp from 00:16:01:8e:e6:ab (capab=0x411 status=0 aid=2)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: no IPv6 routers present
wlan0: switched to long barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
hda-intel: Invalid position buffer, using LPIB read method instead.
wlan0: switched to long barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to long barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to long barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to long barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to long barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to long barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to long barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to long barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to long barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to long barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: switched to short barker preamble (BSSID=00:16:01:8e:e6:ab)
wlan0: No ProbeResp from current AP 00:16:01:8e:e6:ab - assume out of range
Offline
Have you tried downgrading your kernel?
Offline
If your wireless router is set to "hide" the beacon your wifi will not work properly. I found that out the hard way having had similar symptoms to what you've posted.
Offline
The script used to connect at start up is just:
#!/bin/bash killall dhcpcd ifconfig wlan0 up iwconfig wlan0 essid 0016018EE6AA iwconfig wlan0 key fede0fede0 dhcpcd -t 10 wlan0
so I don't think it can be anything to do with it.
Correct me if I'm wrong, but you must bring your interface down before setting your wireless settings (essid, wep key, etc.):
#!/bin/bash
killall dhcpcd
ifconfig wlan0 down
iwconfig wlan0 essid 0016018EE6AA
iwconfig wlan0 key fede0fede0
dhcpcd -t 10 wlan0
dhcpcd should bring your interface up, so you don't have to do it manually.
Also, kernel 2.6.24 has the rt2x00 driver built in, so you must blacklist it if you want to compile and use the newest driver.
DkSoul
Offline
OK, I've done this. I'll give it a few days before I mark it as a success.
Thanks DkSoul.
Last edited by DarkJesus (2008-02-17 16:46:27)
Offline
I have your problem with rt73 driver.
Offline
Well, it doesn't disconnect by itself any more. However, if I disconnect for whatever other reason (like my modem being a bitch), then I still cannot reconnect.
At least it isn't so annoying any more.
Offline
Hi DarkJesus,
same problem here. Did you solve this? How?
Volker
Last edited by vooolker (2008-03-18 10:36:25)
Offline
I fixed it just last night.
The old rt61 drivers used to make an alias in /etc/modprobe.conf for ra0. Then when the newer versions would use wlan*, this line was also added. Since there were two lines in the modprobe.conf file aliasing to rt61, this is what caused the problems. So just delete or comment the old ra0 line and everything should work perfectly.
Good luck.
Offline
I think I also have to disable the ipv6 module, following the instructions on the wiki.
Offline
No, it's not the solution here.
Offline
Same problem with me... I'm using kernel module rt61pci and he recognizes my device as "wlan0" and is the only device configure in rc.conf.
Thus someone got the asnwer for the problem ?
Cheers
Linux / 4.18.5-ARCH / x86_64 / Intel I5-4460s / Intel® HD Graphics 4600 / MSI B85-G43 Gaming
Offline
hmm I am wondering if this could be effecting me I am not on any router but I did update to the newer kernal and I have been having internet problems. so do you think that it would be a good idea to blacklist rt2x00 or is it most likely a coincidence?
Last edited by Shadowmeph (2008-05-30 20:49:04)
Offline
I get a similar issue, and I'm using ndiswrapper.
And it happens only after being connected for 5 minutes, I can't perform a pacman -Syu.
Any ideas?
Some PKGBUILDs: http://members.lycos.co.uk/sweiss3
Offline
I get a similar issue, and I'm using ndiswrapper.
And it happens only after being connected for 5 minutes, I can't perform a pacman -Syu.Any ideas?
I guess you use ndiswrapper-1.53 together with kernel26-2.6.26-5. This pair of packages won't work together, due to a regression. You might consider downgrading ndiswrapper, following this thread. It worked for me so far, still it is a problematic issue, which will hopefully be solved with the release of kernel26-2.6.27.
celestary
Intel Core2Duo E6300 @ 1.86 GHz
kernel26
KDEmod current repository
Offline
Thanks a lot chaosgeisterchen, it worked
Some PKGBUILDs: http://members.lycos.co.uk/sweiss3
Offline