Print

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

[IceMan]

First, I have to say that I've poured over the forums and have read and tried the remedies others have suggested to no avail.  I've called D-Link technical support, and on the last time, cannot get through.  The phone just stays silent for 20 minutes.

This is my second DIR-655.  The first one lasted a few months before doing this.  After a few weeks, I returned it hoping it was a hardware issue.  The second one has been an issue right out of the box.

LOGS:
I have numerous wireless link resets.  I went for a few days without turning on my laptop and the wireless log was filled with this pattern.

When the wireless is up for a usable period of time, the DWA-160 adapter has an extremely hard time making a secure connection.  The log displays Wireless Device with MAC address xx.xx.xx.xx Received Deauthentication.  The MAC associates with my wireless adapter.  And something really weird, for a while the MAC address was showing up as the MAC of the router as being Deauthinticated!!

Setup:
Cable Broadband Internet ->
Motorola Modem ->
DIR-655 (A3, ver 1.11 upgraded 1.21)
=> PC Win XP SP3 on cat5e
=> VoIP device
=> PC Win XP SP3 wireless (DWA-160 adapeter, and Intel 345ABG used independently.  Adapters are disabled when not in use, as to help avoid any conflicts)

Router is configured as (bold is current, followed by settings that have been tried in any conceivable combination):
802.11n/g, 802.11g, 802.11n/g/b
Auto Chanel Scan, 1, 6, 11 (neighbors are on 1 and 11 mostly)
Best Transmission Rate
Chanel Width 20/40Mhz, 20Mhz
Visible Network
WPA2/AES, WPA/WPA2 and TKIP and AES, None

No Port Forwarding (yet),
No MAC filtering
Enable UPnP is checked

Transmit Power is High
Beacon Period 80, 100
RTS 2100, 2346
Frag 2100, 2346

MTU 1500, 1492

Firmware versions, 1.21, 1.11, 1.20 no securespot.

The router is not in any place close to any other 2.4Ghz device.  It is on the second floor in the middle of my house.  I have a Vonage VoIP about 5 feet away (I have removed power from that to see if that helped, no change in the wireless behavior), and DECT 6.0 phones (and base) more than 25 feet away.  I've even eliminated my cell phone as any interference.

I have about 4 competing wireless devices that I can pick up with my adapter.  Channels 1 and 11 and about 20-30% signal strength.  I know the password to one of my neighbors and can connect to their internet no problem.  And I can connect to any other Public Hotspot without issue.

[INFO]   Sun Dec 21 16:52:42 2008   Wireless link is up
[INFO]   Sun Dec 21 16:52:21 2008   Stored configuration to non-volatile memory
[INFO]   Sun Dec 21 16:52:20 2008   Wireless link is down
[INFO]   Sun Dec 21 16:52:20 2008   Wireless restart
[INFO]   Sun Dec 21 16:52:20 2008   Disconnect all stations
[INFO]   Sun Dec 21 16:49:18 2008   Blocked incoming UDP packet from 60.222.224.133:51983 to xxx.xxx.xxx.xxx:1027
[INFO]   Sun Dec 21 16:48:11 2008   Blocked incoming TCP connection request from 60.172.222.17:12200 to xxx.xxx.xxx.xxx:7212
[INFO]   Sun Dec 21 16:45:01 2008   Log viewed by IP address 192.xxx.xxx.xxx
[INFO]   Sun Dec 21 16:37:08 2008   Blocked incoming TCP connection request from 222.187.220.174:6000 to xxx.xxx.xxx.xxx:1433
[INFO]   Sun Dec 21 16:31:36 2008   Log viewed by IP address 192.xxx.xxx.xxx
[INFO]   Sun Dec 21 16:29:39 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 secured and linked
[INFO]   Sun Dec 21 16:29:38 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:29:38 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:29:37 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Received Deauthentication
[INFO]   Sun Dec 21 16:29:37 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:29:35 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:29:35 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:29:26 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Received Deauthentication
[INFO]   Sun Dec 21 16:29:26 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:29:26 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:29:18 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Authentication Failed
[INFO]   Sun Dec 21 16:29:18 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:29:18 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:29:14 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Authentication Failed
[INFO]   Sun Dec 21 16:29:13 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:29:13 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:29:13 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Authentication Failed
[INFO]   Sun Dec 21 16:29:01 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:28:59 2008   Above message repeated 3 times
[INFO]   Sun Dec 21 16:28:58 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Received Deauthentication
[INFO]   Sun Dec 21 16:28:52 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:28:49 2008   Above message repeated 5 times
[INFO]   Sun Dec 21 16:28:48 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Received Deauthentication
[INFO]   Sun Dec 21 16:28:46 2008   Above message repeated 3 times
[INFO]   Sun Dec 21 16:28:41 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Authentication Failed
[INFO]   Sun Dec 21 16:28:41 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:28:41 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:28:41 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Received Deauthentication
[INFO]   Sun Dec 21 16:28:40 2008   Above message repeated 2 times
[INFO]   Sun Dec 21 16:28:38 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:28:38 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:28:38 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Received Deauthentication
[INFO]   Sun Dec 21 16:28:30 2008   Above message repeated 13 times
[INFO]   Sun Dec 21 16:28:29 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:28:29 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:28:29 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Received Deauthentication
[INFO]   Sun Dec 21 16:28:28 2008   Above message repeated 2 times
[INFO]   Sun Dec 21 16:28:27 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:28:27 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:28:25 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Received Deauthentication
[INFO]   Sun Dec 21 16:28:24 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:28:23 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:28:22 2008   Above message repeated 3 times
[INFO]   Sun Dec 21 16:28:22 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Received Deauthentication
[INFO]   Sun Dec 21 16:28:15 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Authentication Failed
[INFO]   Sun Dec 21 16:28:15 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 associated
[INFO]   Sun Dec 21 16:28:15 2008   Above message repeated 1 times
[INFO]   Sun Dec 21 16:28:07 2008   IceMan: Wireless system with MAC address xxxxxxxxxxxx6 disconnected for reason: Received Deauthentication

I am extremely close to giving up on this, if anyone has any further suggestions, please let me know!!

[kegobeer]

I doubt the problem lies with the router alone.  I think it's a combination of the router and your particular wifi card in your particular computer.  I had connection issues with my Dell e1705 and the DWA-643.  Once I dumped that card and installed an Atheros chipset wifi (replaced the Intel 3945ABG) I was running without issues.  Then, when I installed Vista I had BSODs with the default driver available for my wifi card!  I ended up finding a modded inf that prevented the BSODs and improved performance.

So....is it possible to borrow another D-Link adapter (perhaps an internal card or ExpressCard if you have a laptop) and see if you can isolate the issue?

[IceMan]

kegobeer, thanks for your reply. 

I've updated both drivers (DLink DWA-160, and Intel's 3945ABG) and neither one works.  I've tried using each proprietary connection software, as well as Windows Zero Config.

I've borrowed friends laptops when they stop by.  If the router is broadcasting a wireless signal, the other computers connect at 1Mbps, even in the same room as the router.  Other times, their computer will pick up a strong signal, but never be able to connect to it.

Oh yeah, the other computers are using Broadcom 802.11 b/g drivers and card.

When my Dell 1405 using DWA-160 finally connects, it seems to work for a period of time (few minutes to a few hours).  Then the connection seems to fade to 1Mbps, which is where it'll finally be Deauthenticated.  After that it takes a lot of work to get it to connect again.  Maybe the MAC address is blacklisted in the router??  I don't know.

[funchords]

Maybe the MAC address is blacklisted in the router??  I don't know.

Certainly what I'm seeing in the logs looks like blacklisting, which is a feature of WPA/WPA2/802.1X methods. 

You have so much going on it's hard to tell what's next, but I can give you some tips (this is not a step-by-step, so read all of it before doing anything):

# Start from the beginning.  Do a factory restore to defaults and test for a while there.  If you can't make that simple configuration work, then adding complexity to it won't make it work better.  Reset to defaults. Then for good measure, manually power off and power back on.  Restart your wireless client and associate to the "dlink" access point.  (run a software firewall just in case someone joins you in your open AP).   If that works non-stop, then add the next layer of complexity -- WPA2, for example. 

# If you change something (or several somethings) in the DIR-655, power it down, wait 15 seconds or so, then power it back up again.  In some of these firmwares, the entire unit is clearly not resetting -- just certain processes are.  This leaves the router in a questionable state.  Power off/on reset provides for much more assurance and reproducibility when troubleshooting.

# If you change a DIR-655 wireless parameter, change your SSID too.  This keeps your wireless clients from remembering an old setting in a saved profile.   Just add a version number to your SSID, like MyWiFiNet v21 or something...

# If you change a parameter or driver or something on only the client, restart the client computer and also power off/power on the router as before.  WPA/WPA2 does have a blacklist and both sides of a connection keep it.  In Windows, this duty is shared by multiple services and rebooting is the sure way to get back to "square 1" as far as who is locked out, for how long, and how.

# Don't use funny characters in your SSID or WPA Passphrase.  Not all devices store non-alphanumeric characters correctly, and D-Link tends to screw these up when scrambling to save and restore gateway_settings.gws (this is likely a primary reason that saved settings don't work).  Stick with letters and numbers.

[kegobeer]

Something else - try not hiding the SSID.

[DumbLink]

I am having the following msgs logged continuously...

(1) Tue Dec 23 21:28:50 2008 Blocked incoming UDP packet from 24.138.50.220:60696 to 69.183.5x.yyy:54773


INFO] Tue Dec 23 18:40:23 2008 Blocked incoming ICMP error message (ICMP type 3) from 64.53.144.160 to 69.183.5x.yyy as there is no UDP session active between 69.183.5x.yyy:27890 and 192.168.1.109:55301

Above repeats with hundreds of times with different IP address in  the log

(2) Access denied to wireless system with MAC address 0017FA000664
Above repeats with several times per minute

I would like to know how to prevent these so log can retain meaningful entries and Hope this does not negatively impact the performance of the router or wireless network...

[funchords]

I am having the following msgs logged continuously...

(1) Tue Dec 23 21:28:50 2008 Blocked incoming UDP packet from 24.138.50.220:60696 to 69.183.5x.yyy:54773


INFO] Tue Dec 23 18:40:23 2008 Blocked incoming ICMP error message (ICMP type 3) from 64.53.144.160 to 69.183.5x.yyy as there is no UDP session active between 69.183.5x.yyy:27890 and 192.168.1.109:55301

Above repeats with hundreds of times with different IP address in  the log

(2) Access denied to wireless system with MAC address 0017FA000664
Above repeats with several times per minute

I would like to know how to prevent these so log can retain meaningful entries and Hope this does not negatively impact the performance of the router or wireless network...

Your questions actually have nothing to do with the O.P.'s issue and should be in a new Topic, but quick answers are 1) is harmless and is caused by whatever you're running on port ?  on that machine has closed while peers are still trying to reach it (e.g. IM, Skype, Games, or P2P) and 2) Avoid MAC filtering for wireless access or grant 00:17:FA:00:06:64 access. If you need any more help on this, please start a new topic so we don't confuse people. Thanks.

[IceMan]

Well, I reset to factory defaults.  De-powered and re-powered the router.  Made sure no computers were trying to make wireless connections.

The wireless now continuously resets, with no wireless devices trying to connect to it.

I reverted back to ver 1.11.  Same results.

I don't have the log anymore since the reset, but I stated something like listing the MAC of the wireless router being deauthenticated... AP maybe crash...

D-LINK gets a D- for this router.  I give up.  The router is going to be replaced with something other than a D-LINK.

[EddieZ]

Defective devices do happen once in while. Try RMA it. I bought a brand new 'monday-morning' BMW a few years ago, but that does not make the brand worse than LADA...

[war59312]

I take it you have tried driver 1.2.3.0 from http://www.station-drivers.com/page/ralink.htm under RT2870/2770 USB ?