• February 22, 2025, 03:14:22 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: DGL-4500 Wireless disconnected, INFO Client recieved Deauthentication  (Read 8335 times)

soulesschild

  • Guest

My father and my brother are currently on my DGL-4500 network, and they keep getting random disconnects from the router DGL-4500 when it used to be fine on the DGL-4300. The error I get is they recieved deauthentication in the logs. I heard mac address filtering could have caused it so I disabled it for now, but was wondering if this was a known issue and if there's anyway to fix it?

Two laptops: Macbook, and Macbook Pro, both running N
Router firmware: 1.02
Wireless info: SSID Invisible, 20/40 channel width, 2.4ghz, broadcasting N and G mixed, Channel 11, WPA2 AES cipher, 360 key interval, 64 length key.

It used to be on channel 6, so I'm hoping a changed channel will help and I'll be able to reenable mac filtering, but was just hoping for some pointers and tips from other users who have probably used this longer then I have (I just bought it yesterday)
« Last Edit: January 01, 2008, 07:25:41 PM by soulesschild »
Logged

Lycan

  • Administrator
  • Level 15 Member
  • *
  • Posts: 5335
Re: DGL-4500 Wireless disconnected, INFO Client recieved Deauthentication
« Reply #1 on: January 02, 2008, 12:22:38 PM »

Since you disabled the MAC filtering, has the issue stopped?
Logged

soulesschild

  • Guest
Re: DGL-4500 Wireless disconnected, INFO Client recieved Deauthentication
« Reply #2 on: January 03, 2008, 04:11:21 AM »

Haven't had a chance to ask, but apparently it seems good so far.
Logged

Jeff20112

  • Level 1 Member
  • *
  • Posts: 4
Re: DGL-4500 Wireless disconnected, INFO Client recieved Deauthentication
« Reply #3 on: January 03, 2008, 09:10:42 PM »

I have a similar problem - with my Wii console.  Same problem with/without MAC filtering enabled.  Log shows MAC address is associated, then about 10 seconds later it's disconnected due to deauthentication.  Looks like it's happening about every 10 minutes.  Note that Wii console is in stand-by mode (amber light).  Additionally, it has a reserved DHCP/IP address.  Router is currently configured Mixed 802.11 mode (n/g/b), 2.462 GHz - CH 11 (not auto because of Wii), Auto (WPA or WPA2), TKIP & AES.  Was using WPA2 with AES only until I tried to connect the Wii.  Apparently Wii's don't work with D-Link's WPA2 implementation (per Nintendo).  Really hated to step down security, but needed Wii to connect to Internet.

Any ideas?
Logged

whsftbldad

  • Level 1 Member
  • *
  • Posts: 5
Re: DGL-4500 Wireless disconnected, INFO Client recieved Deauthentication
« Reply #4 on: March 12, 2008, 07:30:55 PM »

Hi.  Running DGL-4500 with other items on router but not turned on.  Using Dell Latitude D610 laptop with built-in wireless (I believe it is an Intel device), running work aplications using Cisco VPN.  Used to drop the VPN connection on old DIR-624, but seems to be more often using this.  Is there a setting in the router or laptop to keep the VPN from droping it's connection.  My uptime on the internet hasn't gone down and the uptime on my DGL-4500 is at 24 days, 17 hours.  It has not gone down once since original install.  Any help would be appreciated.  I also have the issue of the deauthentication, but as stated the connection to the broadband stays up.  It just seems to be affecting the VPN.
Logged

bokeron

  • Guest
Re: DGL-4500 Wireless disconnected, INFO Client recieved Deauthentication
« Reply #5 on: March 17, 2008, 07:07:41 AM »

Just as I posted on DIR-655 forum ... are you sure this isn't a deauthentication attack ?
Logged

Lycan

  • Administrator
  • Level 15 Member
  • *
  • Posts: 5335
Re: DGL-4500 Wireless disconnected, INFO Client recieved Deauthentication
« Reply #6 on: March 17, 2008, 04:57:24 PM »

No, it's not a deauth attack. If we assume that, the attack would have to come from a WiFi user in your area, it's the handshake/ACK issue. We are looking for a way to isolate the issue now.
Logged