Print

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

[rcschaff]

I have my DHCP enabled but chose to make my wireless laptop static IP thru the software on the router.  This seems to have helped from dropping the wireless signal. 

My wireless problem that I have noticed is when I am trying to connect and stay connected remotely to my wireless notebook thru my desktop.  Maybe tech support needs to fix the DHCP issue, I never had problems with my linksys router.  I had bought a dir-615 router for another location and it disconnected really bad to the point that I could not rely on it and tech support could not help, so I ended up taking it back and purchasing another brand.  I don't want to do this with my dir-655.

[boldt]

rcschaff, thanks for the input.

While I am tempted to try your suggestion i would like to know why on earth would the WAP care what IP a client was using, let alone needing it to be assigned an IP by the WAP. The DHCP scope I am using has a 8 day lease which means that clients are not going to perform DHCP requests for 4 days. so there should be no broadcasts most of the time (if the DHCP broadcast traffic is the culprit)

However, in the interest of trying everything I will assign a static IP via the WAP and see if it corrects the issue.

It is extremely disappointing that there seem to be a decent number of owners with this problem, and there does not seem to be a fix or even a log entry describing what the issue might be.

I have to admit that I would like to know if there IS a solution to the problem? will tweaking these settings ever result in a stable wireless environment, or is this a lost cause? and if so is this a result of some interference that is difficult to detect, or is this due to a hardware bug that is just not widespread?

I have a few days left on my 30 day return policy and would really like to be of the majority that loves this device.
If anyone else has any thoughts or suggestions, of even had this issue with a previous unit, please let me know! At this point I am grasping at straws to see if I should cut my loses and pick a different unit.

[rcschaff]

I am having the same issue with my dir-655, although with the beta firmware installed it seems to be dropping the wireless less than before.  My linksys router never had that issue.  I use remote desktop a lot for my systems and it is very time consuming when I have to re-connect my desktop sessions.

[rcschaff]

INFO]   Mon Mar 16 10:00:27 2009   xxxx-router: Wireless system with MAC address 002191FB9490 disconnected for reason: Received Deauthentication
[INFO]   Mon Mar 16 10:00:24 2009   xxxx-router: Wireless system with MAC address 002191FB9490 secured and linked
[INFO]   Mon Mar 16 10:00:24 2009   xxxx-router: Wireless system with MAC address 002191FB9490 associated

[Lycan]

Are you running 802.11N?

[boldt]

I am running mixed (B, G & N)

[boldt]

i think that it is interesting that you are showing a de-authentication issue on one of your clients.

In my case I am not showing anything other than this repeated OVER AND OVER again in my logs:

[INFO] Mon Mar 16 12:00:56 2009 Above message repeated 1 times
[INFO] Mon Mar 16 12:00:53 2009 Wireless link is up
[INFO] Mon Mar 16 12:00:42 2009 Wireless link is down
[INFO] Mon Mar 16 12:00:42 2009 Wireless restart
[INFO] Mon Mar 16 12:00:42 2009 Disconnect all stations
[INFO] Mon Mar 16 12:00:42 2009 All Wireless shut down
[INFO] Mon Mar 16 12:00:40 2009 Wireless restart
[INFO] Mon Mar 16 12:00:35 2009 Above message repeated 2 times
[INFO] Mon Mar 16 11:53:27 2009 XXXXX: Wireless system with MAC address 001D0FB22CFC secured and linked
[INFO] Mon Mar 16 11:53:27 2009 XXXXX: Wireless system with MAC address 001D0FB22CFC associated
[INFO] Mon Mar 16 11:53:27 2009 Above message repeated 1 times
[INFO] Mon Mar 16 11:53:24 2009 Wireless link is up
[INFO] Mon Mar 16 11:53:13 2009 Wireless link is down
[INFO] Mon Mar 16 11:53:13 2009 Wireless restart
[INFO] Mon Mar 16 11:53:13 2009 Disconnect all stations
[INFO] Mon Mar 16 11:53:13 2009 All Wireless shut down
[INFO] Mon Mar 16 11:53:11 2009 Wireless restart
[INFO] Mon Mar 16 11:46:14 2009 XXXXX: Wireless system with MAC address 001D0FB22CFC secured and linked
[INFO] Mon Mar 16 11:46:14 2009 XXXXX: Wireless system with MAC address 001D0FB22CFC associated

[Lycan]

If you disable N support, does this behavior continue?

[boldt]

I just changed to mixed G & B. I'll report back in a few.

[boldt]

I regret to inform that within minutes of adjusting the wireless to mixed B/G only my resets returned:

[INFO] Mon Mar 16 12:52:43 2009 XXXXXXXX: Wireless system with MAC address 001D0FB22CFC secured and linked
[INFO] Mon Mar 16 12:52:43 2009 XXXXXXXX: Wireless system with MAC address 001D0FB22CFC associated
[INFO] Mon Mar 16 12:52:43 2009 Above message repeated 1 times
[INFO] Mon Mar 16 12:52:36 2009 Wireless link is up
[INFO] Mon Mar 16 12:52:26 2009 Wireless link is down
[INFO] Mon Mar 16 12:52:25 2009 Wireless restart
[INFO] Mon Mar 16 12:52:25 2009 Disconnect all stations
[INFO] Mon Mar 16 12:52:25 2009 All Wireless shut down
[INFO] Mon Mar 16 12:52:23 2009 Wireless restart
[INFO] Mon Mar 16 12:46:03 2009 Log viewed by IP address 192.168.1.3

[Lycan]

Are there many other wireless networks in the area? How about cordless phones?

[boldt]

I do show 3-4 other wireless networks in the area (I live in a close nit neighborhood).
I also have a 5.8 digital cordless phone. I can only imagine that the neighbors also have cordless phones utilizing varying frequencies.

How would one determine if there was interference from one of these other wireless sources is causing these wireless restarts? and if so isolating the one that is causing the issue?

This is not the first Wireless AP that has been in this same spot in my house, just the first one that keeps having a wireless restart issue.

[EddieZ]

Tried different channels (manually)?

[Lycan]

use netstumbler and see what channels are currently being used.

[lotacus]

I wishes nestumber worked with the dwa-160.