Print

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

[smlunatick]

You might want to try inSSIDer instead.

[boldt]

yeah, I had to borrow a laptop last night to run the netstumbler test (I wish it ran on an Intel 5300!). I digress, there were a LOT more networks then I remember seeing last time, but there were still quite a few openfrequencies/channels.

Here were the frequencies in use last night:
1,6,8,9,10,11

So I set my DIR-655 to "wireless channel" 4 (I thought a good one right in the hole of open freq) last night before I crashed:

The phrase "[INFO] Wireless restart" entry appears in the log file 1718 times since the time I changed the frequency to 4 and now!

[INFO] Tue Mar 17 15:38:45 2009 Above message repeated 1 times
[INFO] Tue Mar 17 15:38:37 2009 Wireless link is up
[INFO] Tue Mar 17 15:38:27 2009 Wireless link is down
[INFO] Tue Mar 17 15:38:26 2009 Wireless restart
[INFO] Tue Mar 17 15:38:26 2009 Disconnect all stations
[INFO] Tue Mar 17 15:38:26 2009 All Wireless shut down
[INFO] Tue Mar 17 15:38:24 2009 Wireless restart

Anyone else have any thoughts or suggestions?

[bluenote]

You are running 1.22 but is it the latest beta?  (b05)
I don't know that that beta is any better for wireless, but it was a lot better for several other bugs I was experiencing so its worth a try.

The only thing I can think to suggest at this point is to simplify the wireless to just one device for a bit and see what happens.  (aside from simplifying the wireless config as much as possible which I assume you have already done) ... ie: play the disable everything game

Cory

[boldt]

yes I am running 1.22 b05.

I have to admit that I am running out of things to try, options and patience.

I have restored my antique Linksys WAP back into production for the time being.

I suppose that after going through two of these units, that I will have to blame my environment for these issues. It would be nice however if there was something in the logs that provided some sort of clue as to the reasons for these restarts!?!?!

If anyone has any other suggestions on other things to try please let me know.

[MichaelL]

boldt,

I have had the same wireless restart issues that you are seeing.  I found that when I changed the Transmit Power from High to Medium or Low, the restarts went away.  My guess is that the receiver is either susceptible to reflections (which would have a higher amplitude on the High setting) and the geometry of my environment is producing an above average number OR there is an elevated internal noise level with the transmitter at full power that is hammering the receiver. 

I don't think I have had any wireless restarts since setting the Transmit Power to Low.

- Mike

[ckraft]

I've given up. I just don't have the time to work my poor piece of equipment (A2 model). My DIR-655 kept "freezing" and I had to turn it off and on again throughout the day. When I called support, we proceeded to turn down performance (e.g. gigabit transmit rate...or something like that down to 10 mbps). This stopped the problem for a while but it started cropping up again. Hoping the new Cisco/Linksys works now (although I hear it too has had a rash of overheating problems).

Sometime I think there is room for a premium vendor that just gets things right - maybe not the first to market but when they release...it works. 

[EddieZ]

I've given up. I just don't have the time to work my poor piece of equipment (A2 model). My DIR-655 kept "freezing" and I had to turn it off and on again throughout the day. When I called support, we proceeded to turn down performance (e.g. gigabit transmit rate...or something like that down to 10 mbps). This stopped the problem for a while but it started cropping up again. Hoping the new Cisco/Linksys works now (although I hear it too has had a rash of overheating problems).

Sometime I think there is room for a premium vendor that just gets things right - maybe not the first to market but when they release...it works. 

Sorry to hear your bad experience (either a flawed device or bad network settings on your part, whatever...). But it would be presumtious to take your experience as THE bar for vendor qualification. I have no issues and it performs better than all models/vendors tried before. And I'm not Dlink 

[razzle]

I have an A2 version and did not have any problems until I installed the latest update and tried to run shareport and then the drops started.  Uninstalled shareport and put older firmware back in and still constant drops.  Hard to believe things were running great and then a firmware upgrade and nothing but problems.  Re-installed my old Netgear router and no problems.  I am fixing to start the debugging trying things mentioned and if this does not work time something will be thrown away and a new router search will begin.  Hard to believe with these problems that D-Link is not doing more to resolve issues.

[EddieZ]

I have an A2 version and did not have any problems until I installed the latest update and tried to run shareport and then the drops started.  Uninstalled shareport and put older firmware back in and still constant drops.  Hard to believe things were running great and then a firmware upgrade and nothing but problems.  Re-installed my old Netgear router and no problems.  I am fixing to start the debugging trying things mentioned and if this does not work time something will be thrown away and a new router search will begin.  Hard to believe with these problems that D-Link is not doing more to resolve issues.

Apparently these issue do not affect the majority of users. Reflashing helps 9/10 times. A bad upgrade or downgrade (and restoring the saved config since we're all lazy  ) can cause these issues. So reflash the firmware, reset to factory default and build up the config again. This will solve the issues.

[momcat1]

After too many hours troubleshooting, I think I may have resolved the frequent reboots for my DIR-655. I have firmware 1.21. I have an external HD that was setup to run Mionet. I have disabled Mionet and have the drive mapped to each computer on the network. Apparently, Mionet randomly polled to an external server. I'm told the IP was somewhere in France. Each time it did this first my laptop connection to the router would disable, then when I reinstated that by disabling and re-enabling in network settings, the router would close the connection to the modem, and shut itself off. It's been 4 days now since I disabled Mionet, and the router has not shut itself off once.

[frumpy_uk]

I'll start a separate thread as well but since google throws this one up I'll share here too : I found that a cheap HDMI cable was the source of my frequent (30-40 times daily) wireless restarts.

If your router lives near a HDMI cable, you might want to experiment by disconnecting the HDMI (and taking it a long way away if you're superstitious!) and then monitoring your connection.

I replaced my cheap HDMI cable and I no longer see frequent restarts (although I still get one or two every couple of days).


I hope that helps someone - it took me 3 full days of researching and trial and error to isolate the issue with mine.

Like others here, I must say that the old and cheap linksys WRT54 I swapped in temporarily while experimenting was not affected by this HDMI cable.


cheers
Paul