Print

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

[imrambi]

I've been running a 2590 for roughly 1 year. I started off with firmware 1.20 and learned soon after implementation that the wireless would drop. After looking into this, I found that it was OS independent and it seemed that it could be a stuck beacon and a reboot of the access point. I tried updating the firmware to see if that would help, now I am running:

Model Name      DAP-2590   
Firmware Version      1.25   15:41:33 08/31/2012   
System Name      D-Link DAP-2590


Once I've updated to 1.25, I have noticed more problems.

1. The access point seems to go down (possible due again to stuck beacon), and not come back up. The access point is running via POE and when the wireless is unavailable, neither is the web interface. When this happens the only way is to fix the issue is a hard reboot of the access point. Once rebooted, the access point seems functional in all respects.

2. Today I noticed second problem that required a hard reboot.

I have the access point setup running two wireless networks with VLANS.

Private network lets call the SSID Business-Staff. This is password protected via WPA2.
Public network with SSID Business. This is open with no password.

Today I was notified that wireless was not correct, and with two devices I saw the following:

Businecs-Staff (Open)
Busineks-Staff (Open)
Business (Protected)

Note the misspellings and the wrong configuration. I was able to get to the web interface, but when telling the access point to reboot, it seemed to hang, and then required a hard reboot. Upon looking at the logs, I see normal traffic of association and disassociation and then silence from the access point until I started looking into the issue.

Is there a way to prevent the hangs and and the reboots?

[FurryNutz]

Link>Welcome!

• What region are you located?

Wireless Configurations
Links>Wireless Installation Considerations and Managing Signal Congestion and Good Neighbour Policy

• What wireless modes are you using?
• 2.4Ghz Routers only: Try single mode G or N or mixed G and N?
• Channel Width set for Auto 20/40Mhz or try 20Mhz only.
• Try setting a manual Channel to a open or unused channel. 1, 6 or 11. 11 for single mode N if the channel is clear.
• What security mode are you using? Preferred security is WPA-Personal. WPA2/AES Only. Some WiFi adapters don't support AES, so you might want to try TPIK only or Auto TPIK and AES.
• What wireless devices do you have connected?
• Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by?
• Any other WiFi routers in the area? Link> Use InSSIDer to find out. How many?[/b]

[imrambi]

I am located in NA.

Currently running mixed modes, bgn.
I have attempted changing width. There was no change in behavior.
Running on channel 11. This is the freest channel in the area.
The secured network is WPA personal. Other is wide open.
The behavior of a reset can happen with devices from a 1-2 to potentially 15+.
No cordless phones that I am aware of.
Yes, there are 3-4 other access points, all with low signals.

[FurryNutz]

Does this AP have any power settings? Try lowering from High to Medium...

Can you change from Mixed mode to single mode or dual mode and test?

[imrambi]

I will have to check the transmit power change when I am there to make sure it has no effect on coverage. I can change it from 100% to 50%.

I have flipped it to dual mode as I see no issue with that. The problem is that issues like this seem to come up every couple of weeks, so I will have to monitor it.

If neither one of these test work around the issue, what would be another step?

[FurryNutz]

Can you post a picture of this incorrect SSID names that are incorrect?
Adding Screenshots In A Post

[imrambi]

Once I can see the misspellings I will get a screenshot. The access point again had to be manually rebooted. This is from the log:

Mar  8 01:52:44 DAP2590 kernel: [Wireless]Deauth:STA MACADDR2 (reason 6)
Mar  8 01:52:45 DAP2590 kernel: [Wireless]Association Success:STA MACADDR1
Mar  8 01:55:48 DAP2590 kernel: [SYSACT] Too many BC/MC packets
Mar  8 01:55:48 logserver dnsmasq[58589]: /etc/hosts x.x.x.254 is DAP2590.myhost.com
Mar  8 02:00:05 DAP2590 kernel: [Wireless]Deauth:Aging STA MACADDR1
Mar  8 02:00:05 logserver dnsmasq[58589]: /etc/hosts x.x.x.254 is DAP2590.myhost.com
Mar  8 09:49:58 DAP2590 kernel: [SYSACT]Web login success from x.x.x.15
Mar  8 09:49:58 logserver dnsmasq[58589]: /etc/hosts x.x.x.254 is DAP2590.myhost.com
Mar  8 09:58:06 DAP2590 kernel: [Wireless]Initiate Wireless success
Mar  8 09:58:06 logserver dnsmasq[58589]: /etc/hosts x.x.x.254 is DAP2590.myhost.com
Mar  8 09:58:07 DAP2590 kernel: [Wireless]Association Success:STA MACADDR1

There was no wireless signal until a manual reboot. The web login @ 9:49:58 is when I tried to reboot the access point through the web interface. Upon telling it to reboot, there was no sign of rebooting. After a couple of minutes of waiting, I manually rebooted it at 9:58:06.

This is with dual mode, not tri-mode. Will be changing the transmit power. Also changed the channel to what seemed to be more a a free channel.

[FurryNutz]

I would recommend that you phone contact your regional D-Link support office and get help on this.
I'd ask them about this: [SYSACT] Too many BC/MC packets