D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: funchords on November 29, 2008, 07:56:00 PM
-
This sequence occurred today (bottom to top):
[INFO] Sat Nov 29 10:51:14 2008 Wireless link is up
(...22 seconds...)
[INFO] Sat Nov 29 10:50:52 2008 Wireless link is down
[INFO] Sat Nov 29 10:50:52 2008 Wireless restart
[INFO] Sat Nov 29 10:50:52 2008 Disconnect all stations
[INFO] Sat Nov 29 10:50:52 2008 All Wireless shut down
[INFO] Sat Nov 29 10:50:50 2008 Wireless restart
[INFO] Sat Nov 29 10:48:14 2008 Blocked incoming TCP connection request from 71.XXX.XXX.123:37786 to 71.XXX.XXX.228:135
I have no idea what prompted the restart. The log is not helpful.
-
I have the same problem several times a day. And have been trying to narrow down why mine is restarting for weeks. Still working on it. But having a reason in the logs would certainly help.
-
I have the same problem several times a day. And have been trying to narrow down why mine is restarting for weeks. Still working on it. But having a reason in the logs would certainly help.
A poster on the DSLReports forum has suggested that UPnP being on has something to do with it in his case. In this specific case, I did get the router showing up as part of "Router Discovery" in SSDP about that time -- that's also a UPnP function. Figuring out a reproducible sequence to find and fix this bug would be awesome.
-
Please give detailed info on the environment that the router is operating in. Any other 2.4ghz devices in that area?
-
My log displays the same wireless restart message but only once a day when I start up my wired desktop. The desktop is using two nVidia Nic cards that are teamed together (2 nics looks like 1). It never did it until I started using this new board with the dual nics built in and doesn't do it when I have the 2 nics operating as single connection (Not-teamed).
Do you have a nVidia board that is wired to the router?
-
Mine happenes for serveral reasons.
It would happen whenever my blackberry decided to switch from the wifi to the cell tower, the wireless would restart several times in a row.
By placing my blackberry in a DMZ I have eliminated that.
I am still seeing random wireless restarts several times a day with no problem logged. It usually happens while a ftp transfer starts, or a IM client connects, or while my email client starts pulling emails.
To the point were you can see it disconnect as you perform the action.
I am also getting a full router restart about once a day.
-
Please give detailed info on the environment that the router is operating in. Any other 2.4ghz devices in that area?
Nothing in the same room. I'm the 2nd floor unit in a multi-family apartment complex. There's plenty of wi-fi around, and neighbors probably have all the baby monitors, cordless phones, and etc..
That question got me to thinking, though, that I am using dynamic channel selection. Maybe its hopping away from something (tho it ought to log it!!) I'll set it to something static and see what happens. (Changed -- from Auto to Channel 1 as scans show it's the most vacant, also changed Auto Width 20/40 MHz to 20 -- there's no way I'm going to get 40 MHz in an apartment complex). Well see if that stabilizes it.
The device is on a plastic shelf more than 6 inches from any wall or nearby object.
Do you have a nVidia board that is wired to the router?
No, thanks for that. This is two ethernet ports on one card?
It would happen whenever my blackberry decided to switch from the wifi to the cell tower, the wireless would restart several times in a row.
By placing my blackberry in a DMZ I have eliminated that.
I am still seeing random wireless restarts several times a day with no problem logged. It usually happens while a ftp transfer starts, or a IM client connects, or while my email client starts pulling emails.
That's quite a list but nothing jives. That reproducible aspect of ftp or email would be interesting to nail. Thanks, though.
-
funchords- my nics are hardwired to the motherboard and there are 2 of them.
-
Hmm, here's a thought. Let's say you have the router in mixed mode. You have devices in multiple categories. So I have N, G, and B devices. My B device is a cell phone that isn't always here. I remove the B device from the network by walking away. The router does a wireless restart to jump into mixed G and N mode instead of Mixed B G and N. But while it restarted my G device is no longer connected, it jumps into N mode. Restarts. Then my G device tries to connect, jumps back to mixed N and G mode, restarts.
To me it looks more obvious for my setup than what I have been thinking. I will finish my current test and then test this out.
Even though their aren't any deauthentifications, my cell loses the wifi when it gets out of range, and might not actually deauthenticate.
-
Since disabling Auto Channel and disabling 20/40 MHz Auto width to 20 MHz, I haven't had a wireless restart. I'll post back if I do, but I think we're on to something here.
-
Hello guys,
seems I am experiencing the same problem since I (foolishly) enabled 20/40 Auto. Before it was running relatively stable - I have now set it on g-only, 20MHz and static channel.
The annoying thing is that the log does not "log" anything about it - the network connection of the laptop just disappears on the laptop side. And it won't reconnect afterwards, needs a system restart (running Ubuntu 7.10).
I also believe you're onto something... I have a feeling that this is the last DLink Router I will ever have possessed ... every day there are new surprises... have had several routers, never had any problems... UNTIL NOW.
-
I did my test in Mixed N and G mode with channel width set to 20 and disabled auto channel
This did not fix my problems
I have now thrown it into Mixed G and B and set the trans rate to 54
I noticed my connection reported going from 108 Mbps to 54 Mbps. Which made me realize that the connection was actually managing to use the Atheros Super G aspect of my Atheros wireless. (I hadn't realized I was reporting 108 before) So maybe the Super G is what's causing some problems for me. I'll test that after I finish this current test.
I'll let you guys know. I think we might be getting close.
EDIT:When forcing a change in modes, you notice the logs report a "Wireless link is up." But no restart, and the nodes never lose connection. I just find it interested that we can't make the router reproduce a wireless restart... or rather, have no need to when changing settings.
EDIT2:
That failed, Testing in G only mode
-
48 hours logged -- no "wireless restart" messages --
from Status/Device Info:
Wireless Radio : Enabled
802.11 Mode : Mixed 802.11n and 802.11g
Channel Width : 20MHz
Channel : 1
Secondary Channel : ??? (this line is hidden but shows up in cut-paste)
WISH : Active
Wi-Fi Protected Setup : Enabled/Configured
SSID List
Network Name (SSID) Guest MAC Address Security Mode
funchords No XX:XX:XX:XX:XX:XX WPA/WPA2 - Personal
From Wireless Network:
Enable Auto Channel Scan : (unchecked)
Transmission Rate: Best (Auto)
Channel Width: 20 MHz
Visibility Status: Visible
-
I managed to make it 18hrs with my last one. Then a restart.
I'm now attempting the same settings as funchords, with super G unchecked on my adapter settings. (only difference is that I have WPS turned off)
EDIT:Nope, that is very unstable for me. (I dunno if it's the mixed mode that is, or using "Best transmision rate" instead of a set one) I am back on set rate, G only, no super G, and this time I have disabled WISH
we'll see how it goes
-
Still going strong on my end. Anything on your client-side logs (Event Viewer) that coincides with your restart?
"Best transmision rate" instead of a set one
I'd be surprised if its this -- in fact, a set transmission rate might cause wireless restarts by design for all I know. A restart is generally a watchdog function, if processes stop responding or error counts climb too high, and the device has no other alternatives, it's supposed to restart. (Similar to why we reboot computers when there is nothing else we can try -- a rebooted system is better than a locked up one and actually may resolve one-time problems.)
Leaving this at auto gives the wireless the option of lowering the rate instead of waving the white flag. If I seriously suspected it was related to that setting and wanted to test the theory, I would fix it at some medium to low rate that is universally supported -- like 11.
-
Event viewer just says that my nic authenticated right after. No warnings or errors other than that listed.
One thing to note is that for mine, it usually restarts several times in a row before anything authenticates. I am about to do a test with none of my devices authenticated. And see if the router still restarts the wireless. At which point I will exchange it for a new one and hope it's not my radioactive body blocking signals again. ;)
I did a quick ping to see if I could force a restart (cause 90% of my restarts have an ICMP 8 packet blocked about 2 minutes before the restart, but none close enough for me to think it's the cause)
But if the all devices off comes back clear, I am going to do an error load test. I will block an outgoing port, and then attempt to flood the router. See if I can at least force a restart... if not, it shouldn't be an error load problem. Gives me one more thing to eliminate.
(EDIT: On another note... I can only manage the router from one of my computers, the others give me a: "502 Bad Gateway : Apache/2.0.55 (Unix) DAV/2 Server at 192.168.0.1 port 80" just something interesting. Maybe it's because I'm already authenticated on the other one. Just another interesting quirk I've found)
-
Event viewer just says that my nic authenticated right after. No warnings or errors other than that listed.
One thing to note is that for mine, it usually restarts several times in a row before anything authenticates. I am about to do a test with none of my devices authenticated. And see if the router still restarts the wireless. At which point I will exchange it for a new one and hope it's not my radioactive body blocking signals again. ;)
I did a quick ping to see if I could force a restart (cause 90% of my restarts have an ICMP 8 packet blocked about 2 minutes before the restart, but none close enough for me to think it's the cause)
ICMP 3 or 8? I wouldn't expect 8.
But if the all devices off comes back clear, I am going to do an error load test. I will block an outgoing port, and then attempt to flood the router. See if I can at least force a restart... if not, it shouldn't be an error load problem. Gives me one more thing to eliminate.
(EDIT: On another note... I can only manage the router from one of my computers, the others give me a: "502 Bad Gateway : Apache/2.0.55 (Unix) DAV/2 Server at 192.168.0.1 port 80" just something interesting. Maybe it's because I'm already authenticated on the other one. Just another interesting quirk I've found)
Ooops! That's not from the DIR-655! (It doesn't run Apache, nor Unix.) All the others give you this? Do you have another 192.168.0.1 on your network? Try changing the DIR-655 to another IP safely outside of the DHCP-assignment range.
-
NVM about the 192.168.0.1, those other nodes are using a proxy I guess. (It isn't setup in the device, but the opera browser on them appears to proxy through an opera server, must be a bug, being that private addresses shouldn't be proxied or something, dunno)
Unfortunately, I'm gettting these restarts even while there are no nodes connected, according to the logs. I disconnected everything for two hours, and in the logs there is a restart 1 hr after everything was disconnected. (I had switched back to the Mixed N and G mode cause I seem to have a lot of problems with it)
It doesn't appear to be other AP interference, there are no others on channel 1, the closest being on channel 6.
I'm not sure what else could be interfering... I know that cell reception is crap in this apartment, which is one of the reasons why I am using wifi on my blackberry for calls.
I think I might go ahead and get an RMA, grab a new one, see if that fixes things.
-
Okay --- good tries ... hope the new one is better.
-
I thought I had a 30 day return, looks like it was only 15. I guess I'm stuck with this one until I buy a new one.
I guess I'll keep messing around with it, see what happens.
-
I thought I had a 30 day return, looks like it was only 15. I guess I'm stuck with this one until I buy a new one.
I guess I'll keep messing around with it, see what happens.
If you're in the USA, you probably have a 1 year mfr. warranty. Call Tech Support, let them suggest a few things and if they don't work out, you can exchange it.
I'm beginning to get a "bad hardware" vibe in your case.
-
I'm having a simular problem. Everything was fine until this morning, wireless is acting up. Get this wireless restart problem all the time. I've got no idea whats causing it and what changed from yestoday to today. I haven't touched the router in weeks...
-
Problem was solved by reverting back to version 1.11
-
Yeah, I think mine might be a hardware issue, it had to be shipped accross the ocean, so who knows what's going on.
Unfortunately, both my gf and I have to work from home some days of the week. (Our company has outgrown it's office, and it is currently moving) So I will have to pick up a new router before I can ship this one away.
I love the 655 other than this one issue.
My router came with firmware 1.20, which I had problems with, so I upped to 1.21. Maybe I will try 1.11 before I buy a new one. (And before that, I will try the known bug... I will actually turn off DNS Relay - should have done this before)
EDIT: DNS Relay off, still disconnecting. Haven't tried 1.11 yet, BUT, some interesting development today. I have a set of amplfied computer speakers that I left on last night, the 1/8 inch adapter is just resting on a counter. My blackberry running on wifi is on the same counter about a foot away. Every once in a while I will hear a very distinct set of noised from the speakers. These noises are consistant with my wireless restarts. One thing to note is that these noises appear to occur right before my blackberry loses connection. But it isn't for another 30 seconds that the router usually actually manages to disconnect the rest of the nodes. Also, the router doesn't restart every time the noises occur, but the noises occur evertime the router restarts.
This led me to the blackberry support forums. Where I have heard this:
Not only Belkin routers, but any routers that aren't plain B or G routers seem to cause problems, draft N, anything with speed enhancing features. If your Linksys isn't plain Jane 802.11g, that might be the cause. Not sure about 4.5.0.52, but some OS also weren't so great for wifi.
I have the lastest OS for my BB. I will open up a support topic over there as soon as I'm 100% convinced the blackberry is causing the problem. (Because it doesn't explain why the wireless restarted with no devices connected)
-
I have a set of amplfied computer speakers that I left on last night, the 1/8 inch adapter is just resting on a counter. My blackberry running on wifi is on the same counter about a foot away. Every once in a while I will hear a very distinct set of noised from the speakers. These noises are consistant with my wireless restarts. One thing to note is that these noises appear to occur right before my blackberry loses connection. But it isn't for another 30 seconds that the router usually actually manages to disconnect the rest of the nodes. Also, the router doesn't restart every time the noises occur, but the noises occur evertime the router restarts.
Some multi-band cell phones throw an awful lot of spectrum when they change modes or re-home. You can hear this in nearby speakers, in very tinny-sounding pulses with the rhythm similar to a horse gallup.
http://www.freesound.org/download/18596/18596_dobroide_20060425.cellphone.interference.flac
(or go to http://www.freesound.org/samplesViewSingle.php?id=41003 and log in)
or
http://media.freesound.org/data/41/sounds/41003__andriala__Cell_phone_interference.mp3
(or http://www.freesound.org/samplesViewSingle.php?id=18596 and log in)
You can hear how much trash these put out -- they're the bane of electronics everywhere!
-
Yep, that's the sound.
But I can't determine whether the phone is restarting the router, or if the router is disconnecting the phone, and it's making sounds as it picks up the tower. I will continue and find out what I can.
-
Awesome, that's a significant clue!
Can people with this problem power off and then power on your wireless phone a few times, and see if doing so causes the "restarting wireless" entry to be created?
Reply back with your phone model and the result.
I tried Samsung SCH-i760 (Verizon Wireless) which is CDMA-based, 3 cycles on and off and no restarts were noted in the log. (I live in a complex, so my restarts might be associated with a neighbor's GSM phone.)
-
No luck, I can't seem to force the restart. Phone is Blackberry Pearl 8120. It makes the noises when the disconnect occurs (as it switches from using the wifi to using EDGE). So the disconnect causes the symptom.
(I am still seeing restarts while I don't have any devices connected.)
EDIT:
One intersting thing is that in my logs my devices are deauthenticating about once every two minutes. And then authenticating again. (I don't notice any drops on my devices)
[INFO] Thu Dec 11 16:41:26 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx7 secured and linked
[INFO] Thu Dec 11 16:41:26 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx7 associated
[INFO] Thu Dec 11 16:41:26 2008 Above message repeated 1 times
[INFO] Thu Dec 11 16:41:00 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx7 secured and linked
[INFO] Thu Dec 11 16:41:00 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx7 associated
[INFO] Thu Dec 11 16:41:00 2008 Above message repeated 1 times
[INFO] Thu Dec 11 16:40:10 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx7 secured and linked
[INFO] Thu Dec 11 16:40:10 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx7 associated
[INFO] Thu Dec 11 16:40:10 2008 Above message repeated 1 times
[INFO] Thu Dec 11 16:39:55 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx7 disconnected for reason: Authentication Failed
[INFO] Thu Dec 11 16:39:53 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx7 associated
[INFO] Thu Dec 11 16:39:51 2008 Above message repeated 3 times
[INFO] Thu Dec 11 16:39:24 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx9 disconnected for reason: Received Deauthentication
[INFO] Thu Dec 11 16:39:14 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx7 secured and linked
[INFO] Thu Dec 11 16:39:14 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx7 associated
[INFO] Thu Dec 11 16:39:14 2008 Above message repeated 1 times
[INFO] Thu Dec 11 16:39:14 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx9 secured and linked
[INFO] Thu Dec 11 16:39:14 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx9 associated
[INFO] Thu Dec 11 16:39:14 2008 Above message repeated 1 times
[INFO] Thu Dec 11 16:39:06 2008 Uma: Wireless system with MAC address xxxxxxxxxxxxx9 disconnected for reason: Received Deauthentication
Is that just normal router behaviour as it updates WPA2 or something? My logs are full of these, I haven't really been paying attention to them. As they don't seem to have any effect on my ability to browse/download stuff.
-
No, that's not normal, although it is related to WPA. I'm surprised its not having an effect, sooner or later -- the spec says that ends that can't agree ought to eventually lock one another out. Fixing it should be easy -- (power down, power up) restart both ends of that connection and it should be cleared.
-
That's very similar to what it looked on my network - and neither my wife nor I have a cell phone! However, after limiting the WLAN to -g- only and selecting a fixed channel (11) tt seems to be working relatively stable right now.
I think that the source of the problem is NOT your cell phone but that the source is somewhere else and the noises are just an effect of the deauthentification-madness of the router... but that's just my two cents...
-
I'm thinking Fixed channel is what's fixing it. :D
As an experiment, I'll put mine back in auto and see what happens over the next day or two.
-
Hmm, I already know moving to wireless g only mode reduces my restarts. (And I'm already on fixed chan)
I also decided to see what if those authentications were actually effecting my network. I started pinging my router, and I get a timeout a couple times a minute. So the WPA seems to be having some fun with my network.
I'm getting this authentication/deauthentication problem with all devices on my network. I agree with netdevil, I don't think my phone is the cause.
My new test will be using WPA1, see what happens.
EDIT: The first thing I tried was to use WPA2 only, (AES). Both this and the TKIP for WPA2 left my devices unable to connect. (must not be able to use WPA2)
I am currently trying WPA only with AES
EDIT2: No longer having auth/deauth issues. Internet browsing load times have noticably decreased on image intense sites. The other thing I did was change the Group Key Update Interval to be a full day.
Too soon to tell if this will also fix my restart issues, but my log file is sure getting smaller and easier to read.
-
If you want to experiment between WPA/WPA2 (or WEP or None), after making that change on your DIR-655 (or any AP), then go to your wireless devices, wipe out their saved settings for your access point, reboot the wireless device, and then associate like you would with a brand-new access point.
This advice cannot hurt, since it doesn't do anything but match the current settings at worst. However, it won't help you connect a WPA-only or a TKIP-only network device to a WPA2-only network.
If this helps, it's because after you changed the DIR-655, the wireless device remembered the previous connection and security parameters which were no longer valid. Following that process creates and saves a new, clean, correct set of parameters reflecting the recent change you made to your wireless network.
Note: If you do have trouble connecting up to a WPA and/or WPA2 network with these steps, its possibly because the AP has the wireless device in an 802.1X lockout or blacklist, earned by too many prior authentication failures. To clear the lockout, repeat the above steps and remove power/restore power to the Access Point right after you reboot the wireless device. If you don't have access to the AP's power, then leaving the affected device offline for a little over an hour or two should also expire the lockout (that's a guess, I don't know where D-Link's thresholds are set).
-
Aye, my laptop cannot connect when set to WPA2 only mode. But it can in WPA only mode. If I put it into both mode, I can connect, but my devices deauthenticate and reauthenticate every few minutes.
I also haven't fixed my wireless restart. I just got another one now, the difference this time, is that with the current settings it only happens once. Previous restarts often restarted several times back to back before any devices were authenticated.
-
Okay, to be clear --
If you're in WPA/WPA2 mode, and you've wiped out your computer's saved settings for your access point, rebooted the computer and router, and then associated like you would with a brand-new access point, you still get the authentication/deauthentication cycle?
Which wireless NIC do you have? Are you on the latest drivers and OS updates?
-
I have an atheros super G card on a toshiba laptop. Running Windows XP SP3.
When I first got the router, I could only connect while it was open or in WEP and not in any mode that included n (including mixed modes). I updated the card firmware to the most recent, that was about a month ago. Then I was able to connect to the router while it was in WPA and while in a mixed mode with n.
And yes, after completely clearing wifi profiles for the wifi on the laptop, and resetting the router, I still get auth/deauth events as soon as I switch into WPA2 + WPA and no connection when using just WPA2. I get these events from the laptop, and from my blackberry. I have not seen a deauth on my wii though, yet. But it's not always on.
From the first day that I got my laptop working on the network, I have been seeing log events every 30sec-2min. I wasn't seeing a performance hit, so I just thought it was normal.
Now that I'm using WPA only, I'm only seeing log events every 30min - 1hr.. and they're just ICMP 8 packets being blocked, or transmission sequence errors.
-
Interesting, thanks!
-
OK - mine works better but still not good. Yesterday my wife's laptop disconnected and would not log back on even after several reboots. I had to reboot the router, only then would the laptop be able to log back on - only to be immediately disconnected again. Another attempt to register in the network and it worked again. Here's the log from Ubuntu 7.10 - the router does NOT log any useful data...!
Dec 12 13:33:03 wika-laptop kernel: [ 9582.272000] wlan0: Initial auth_alg=0
Dec 12 13:33:03 wika-laptop kernel: [ 9582.272000] wlan0: authenticate with AP XX:XX:XX:XX:XX:XX
Dec 12 13:33:03 wika-laptop kernel: [ 9582.472000] wlan0: authenticate with AP XX:XX:XX:XX:XX:XX
Dec 12 13:33:03 wika-laptop kernel: [ 9582.672000] wlan0: authenticate with AP XX:XX:XX:XX:XX:XX
Dec 12 13:33:04 wika-laptop kernel: [ 9582.872000] wlan0: authentication with AP XX:XX:XX:XX:XX:XX timed out
Dec 12 13:33:05 wika-laptop kernel: [ 9583.872000] wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 12 13:33:08 wika-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Dec 12 13:33:17 wika-laptop kernel: [ 9595.868000] wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 12 13:33:19 wika-laptop kernel: [ 9597.868000] wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 12 13:33:19 wika-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Dec 12 13:33:30 wika-laptop last message repeated 2 times
Dec 12 13:33:33 wika-laptop kernel: [ 9611.860000] wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 12 13:33:34 wika-laptop NetworkManager: <info> Activation (wlan0/wireless): association took too long (>60s), failing activation.
Dec 12 13:33:34 wika-laptop NetworkManager: <info> Activation (wlan0) failure scheduled...
Dec 12 13:33:34 wika-laptop NetworkManager: <info> Activation (wlan0) failed for access point (KeinZugangFuerFremde)
Dec 12 13:33:34 wika-laptop NetworkManager: <info> Activation (wlan0) failed.
Dec 12 13:33:34 wika-laptop NetworkManager: <info> Deactivating device wlan0.
[.... NEXT DAY .... The same. After rebooting the router the following appeared:]
Dec 13 09:38:49 wika-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 13 09:38:50 wika-laptop kernel: [ 2413.800000] wlan0: Initial auth_alg=0
Dec 13 09:38:50 wika-laptop kernel: [ 2413.800000] wlan0: authenticate with AP XX:XX:XX:XX:XX:XX
Dec 13 09:38:50 wika-laptop kernel: [ 2413.800000] wlan0: RX authentication from XX:XX:XX:XX:XX:XX (alg=0 transaction=2 status=0)
Dec 13 09:38:50 wika-laptop kernel: [ 2413.800000] wlan0: authenticated
Dec 13 09:38:50 wika-laptop kernel: [ 2413.800000] wlan0: associate with AP XX:XX:XX:XX:XX:XX
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: RX AssocResp from XX:XX:XX:XX:XX:XX (capab=0x431 status=0 aid=1)
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: associated
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
Dec 13 09:38:50 wika-laptop kernel: [ 2413.808000] wlan0: association frame received from XX:XX:XX:XX:XX:XX, but not in associate state - ignored
Dec 13 09:38:50 wika-laptop kernel: [ 2413.880000] wlan0: RX WEP frame with unknown keyidx 1 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:50 wika-laptop kernel: [ 2414.032000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:50 wika-laptop kernel: [ 2414.132000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:50 wika-laptop kernel: [ 2414.236000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:51 wika-laptop kernel: [ 2414.876000] wlan0: RX WEP frame with unknown keyidx 1 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:51 wika-laptop kernel: [ 2415.260000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:51 wika-laptop NetworkManager: <debug> [1229186331.962856] nm_device_802_11_wireless_update_bssid(): Roamed from BSSID 00:00:00:00:00:00 to XX:XX:XX:XX:XX:XX on wireless network 'XXXXXXXX'
Dec 13 09:38:52 wika-laptop kernel: [ 2415.464000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:52 wika-laptop NetworkManager: <debug> [1229186332.042796] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'KeinZugangFuerFremde'
Dec 13 09:38:52 wika-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Dec 13 09:38:52 wika-laptop kernel: [ 2415.876000] wlan0: RX WEP frame with unknown keyidx 1 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:53 wika-laptop kernel: [ 2416.828000] wlan0: RX WEP frame with unknown keyidx 0 (A1=00:14:85:df:74:54 A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:54 wika-laptop kernel: [ 2418.132000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:54 wika-laptop kernel: [ 2418.432000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:55 wika-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Dec 13 09:38:56 wika-laptop NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'KeinZugangFuerFremde'.
Dec 13 09:38:56 wika-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 13 09:38:56 wika-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Dec 13 09:38:57 wika-laptop NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Dec 13 09:38:57 wika-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Dec 13 09:38:57 wika-laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface wlan0
Dec 13 09:38:57 wika-laptop dhclient: wmaster0: unknown hardware address type 801
Dec 13 09:38:57 wika-laptop kernel: [ 2421.096000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:58 wika-laptop kernel: [ 2421.504000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:58 wika-laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface wlan0
Dec 13 09:38:58 wika-laptop dhclient: wmaster0: unknown hardware address type 801
Dec 13 09:38:59 wika-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Dec 13 09:39:00 wika-laptop kernel: [ 2424.168000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:00 wika-laptop kernel: [ 2424.268000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:02 wika-laptop kernel: [ 2426.112000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:06 wika-laptop kernel: [ 2430.108000] printk: 1 messages suppressed.
Dec 13 09:39:06 wika-laptop kernel: [ 2430.108000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:07 wika-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Dec 13 09:39:07 wika-laptop dhclient: DHCPOFFER from 192.168.0.1
Dec 13 09:39:07 wika-laptop dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 13 09:39:11 wika-laptop kernel: [ 2435.124000] printk: 1 messages suppressed.
Dec 13 09:39:11 wika-laptop kernel: [ 2435.124000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:13 wika-laptop dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 13 09:39:16 wika-laptop kernel: [ 2440.140000] printk: 1 messages suppressed.
Dec 13 09:39:16 wika-laptop kernel: [ 2440.140000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:24 wika-laptop kernel: [ 2448.128000] printk: 3 messages suppressed.
Dec 13 09:39:24 wika-laptop kernel: [ 2448.128000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:25 wika-laptop kernel: [ 2449.152000] printk: 1 messages suppressed.
Dec 13 09:39:25 wika-laptop kernel: [ 2449.152000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:28 wika-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Dec 13 09:39:28 wika-laptop dhclient: DHCPOFFER from 192.168.0.1
Dec 13 09:39:28 wika-laptop dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 13 09:39:28 wika-laptop dhclient: DHCPACK from 192.168.0.1
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.197.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: New relevant interface wlan0.IPv4 for mDNS.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Registering new address record for 192.168.0.197 on wlan0.IPv4.
Dec 13 09:39:28 wika-laptop NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface wlan0
Dec 13 09:39:28 wika-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Dec 13 09:39:28 wika-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Dec 13 09:39:28 wika-laptop dhclient: bound to 192.168.0.197 -- renewal in 38570 seconds.
Dec 13 09:39:28 wika-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.host_name
Dec 13 09:39:28 wika-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain
Dec 13 09:39:28 wika-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers
Dec 13 09:39:28 wika-laptop NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon:
Dec 13 09:39:28 wika-laptop NetworkManager: <info> address 192.168.0.197
Dec 13 09:39:28 wika-laptop NetworkManager: <info> netmask 255.255.255.0
Dec 13 09:39:28 wika-laptop NetworkManager: <info> broadcast 192.168.0.255
Dec 13 09:39:28 wika-laptop NetworkManager: <info> gateway 192.168.0.1
Dec 13 09:39:28 wika-laptop NetworkManager: <info> nameserver 192.168.0.1
Dec 13 09:39:28 wika-laptop NetworkManager: <info> domain name 'XX.XXXXXXXX.net'
Dec 13 09:39:28 wika-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Dec 13 09:39:28 wika-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Dec 13 09:39:28 wika-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Withdrawing address record for 192.168.0.197 on wlan0.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.197.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Interface wlan0.IPv4 no longer relevant for mDNS.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.197.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: New relevant interface wlan0.IPv4 for mDNS.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Registering new address record for 192.168.0.197 on wlan0.IPv4.
Dec 13 09:39:29 wika-laptop NetworkManager: <info> Clearing nscd hosts cache.
Dec 13 09:39:29 wika-laptop NetworkManager: <WARN> nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))
Dec 13 09:39:29 wika-laptop NetworkManager: <info> Activation (wlan0) successful, device activated.
Dec 13 09:39:29 wika-laptop NetworkManager: <debug> [1229186369.699975] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'XXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Dec 13 09:39:29 wika-laptop NetworkManager: <info> SWITCH: terminating current connection 'wlan0' because it's no longer valid.
Dec 13 09:39:29 wika-laptop NetworkManager: <info> Deactivating device wlan0.
Dec 13 09:39:29 wika-laptop dhclient: There is already a pid file /var/run/dhclient.wlan0.pid with pid 6006
Dec 13 09:39:29 wika-laptop dhclient: killed old client process, removed PID file
Dec 13 09:39:29 wika-laptop dhclient: wmaster0: unknown hardware address type 801
Dec 13 09:39:29 wika-laptop dhclient: wmaster0: unknown hardware address type 801
Dec 13 09:39:29 wika-laptop NetworkManager: <info> Activation (wlan0) Finish handler scheduled.
Dec 13 09:39:29 wika-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Dec 13 09:39:29 wika-laptop dhclient: DHCPRELEASE on wlan0 to 192.168.0.1 port 67
Dec 13 09:39:29 wika-laptop avahi-daemon[4761]: Withdrawing address record for 192.168.0.197 on wlan0.
Dec 13 09:39:29 wika-laptop avahi-daemon[4761]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.197.
Dec 13 09:39:29 wika-laptop avahi-daemon[4761]: Interface wlan0.IPv4 no longer relevant for mDNS.
Dec 13 09:39:29 wika-laptop kernel: [ 2453.356000] NET: Registered protocol family 10
Dec 13 09:39:29 wika-laptop kernel: [ 2453.356000] lo: Disabled Privacy Extensions
Dec 13 09:39:29 wika-laptop kernel: [ 2453.356000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 13 09:39:29 wika-laptop ntpdate[6077]: can't find host ntp.ubuntu.com
Dec 13 09:39:29 wika-laptop ntpdate[6077]: no servers can be used, exiting
Dec 13 09:39:30 wika-laptop NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed
Dec 13 09:39:30 wika-laptop NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed
Dec 13 09:39:30 wika-laptop kernel: [ 2454.180000] wlan0: deauthenticate(reason=3)
As mentioned above, after that I registered again and it connected me.
Maybe that gives any clues?
-
Looks to me like there is something wrong with your connection manager. For one, it lies:
Dec 12 13:33:34 wika-laptop NetworkManager: <info> Activation (wlan0/wireless): association took too long (>60s), failing activation.
^ Based on the times, network manager did not wait 60 seconds, and for authentication, network manager didn't even wait a single second before timing out. I don't think this is your problem though.
Dec 13 09:39:29 wika-laptop NetworkManager: <WARN> nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))
^ Do you have nscd installed? This shouldn't be your problem either, but it is something to check out.
Basically, I'm not smart enough to figure it out, based on those logs. One thing I would try if I were you, would be to try and use http://wicd.sourceforge.net/ instead of network manager, and see if you get the same problem.
-
OK - mine works better but still not good. Yesterday my wife's laptop disconnected and would not log back on even after several reboots. I had to reboot the router, only then would the laptop be able to log back on - only to be immediately disconnected again. Another attempt to register in the network and it worked again. Here's the log from Ubuntu 7.10 - the router does NOT log any useful data..
That's lockout behavior. Was this network WPA/WPA2 at some point and is now WEP?
-
@twk3 - Thanks, I'll take a look at that.
@funchords: No, it's still WPA only which seems to work more stable. Haven't tried WEP yet.
I am not sure what this is. Sometimes it kicks her out of a Skype session and she'll be locked out if that's what it is.
Right now I am just waiting for OpenSuse11.1 to be available for download then I'll install that and see if it's getting any better (wanted to switch to Ubuntu 8.04 which ran fine as a LiveCD but the installation would always crash when it started to write files to the harddisk ??? ).
EDIT: OK, I installed WICD and the connection rate is much better, can't really say all too much about stability so far. What I noticed, however, is that my logs are filling up with 'CTS Protection enabled/disabled' messages like crazy (every 1-3 sec) and something about a 'printk message suppressed.' I guess for more detailed analyses I'll wait for the new OpenSuse-installation.
Edit2: Still getting errors and the connection disconnects after a while (WICD reports its still up but nothing gets transferred; router log does not report anything; system log reports an error, which I will post later). For some reason I still think that the router is involved in this somehow...
-
I have been connected with fedora 8 all this week, and the restarts have still been occuring. Just eliminates my software on windows from being the cause. Though, as far as I can tell, it seems to restart when nothing is connected as well.
Whether it's the router, my laptop wireless card, or my blackberry... I still don't know.
-
I have been connected with fedora 8 all this week, and the restarts have still been occuring. Just eliminates my software on windows from being the cause. Though, as far as I can tell, it seems to restart when nothing is connected as well.
And that's still on fixed channel 1? Have you tried 11?
-
I made these changes yesterday as per D-Link tech support and I havent had a wireless restart yet, and it's been almost a full 24 hours
>Make sure UPnP and Muticast streaming are disabled.
>Change wireless channel to 10
>Change beacon period to 80
>Change RTS threshold to 2100
>Change Fragmentation threshold to 2100
>Change DTIM interval to 5
-
Try reflashing the firmware.
-
I've reflashed the firmware several times. I'm trying the settings suggested by Rimtech.
EDIT: The new settings have not stopped my wireless restarts.