Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[twk3]

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)

[funchords]

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.

[twk3]

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.

[funchords]

Okay --- good tries ... hope the new one is better.

[twk3]

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.

[funchords]

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. 

[wannaplay]

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...

[wannaplay]

Problem was solved by reverting back to version 1.11

[twk3]

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)

[funchords]

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!

[twk3]

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.

[funchords]

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.)

[twk3]

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.

[funchords]

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. 

[netdevil]

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...