Print

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

[funchords]

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.

[twk3]

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.

[funchords]

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. 

[Lycan]

Please give detailed info on the environment that the router is operating in. Any other 2.4ghz devices in that area?

[davevt31]

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?

[twk3]

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.

[funchords]

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.

[davevt31]

funchords- my nics are hardwired to the motherboard and there are 2 of them.

[twk3]

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.

[funchords]

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.

[netdevil]

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.

[twk3]

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

[funchords]

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

[twk3]

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

[funchords]

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.