Print

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

[osj]

As many others I am facing problems with wireless restarts on my DIR-825. From other threads (like http://forums.dlink.com/index.php?topic=5851.0) I have figured out that the problem is related to a certain kind of traffic coming from PCs connected by WIRE to the router. If I connect all my PCs with wireless I see no wireless restarts.

I have seen posts about that Symantec Endpoint (SEP) firewall is causing this behavior, which I also have installed on the PC that I have problems with, however I think there is also another issue. (or maybe SEP is only an indirect cause)

I have captured the packets from my PC while monitoring the wireless restarts, and I have found that packets send to UDP port 5355 to multicast address 224.0.0.252 (via wired ethernet) is causing wireless restart on DIR-825. (Hardware Version: A1 Firmware Version: 1.12NA)

From this description http://en.wikipedia.org/wiki/Link-local_Multicast_Name_Resolution it seems to be a kind of DNS packet, and in the packet I see that it contain the name of the computer where I have a shared printer.

If I delete the printer, the packets stops, and the wireless restarts stop.... and I can reproduce the wireless restarts by "replaying" the capture.

How can problems like this be reported to D-link, so there is a chance to remove at least one of the root causes to wireless restart in a future firmware?

Best regards...Ole

[osj]

I just found that mDNS packets send to multicast address 224.0.0.251 by a wired device also cause immediate wireless restart.

[ibaboun]

Same results over here.

Thanks for your findings. Could not use wifi for more that two minutes with the wired computed turn on.

Now I have been working with wifi for more than a hour, with the wired computer been off.

On the wired computer the printer is not share, but I was using Symantec Endpoint Protection.

[osj]

Actually the wired PC was not the one with the shared printer, but it was trying to connecting to a remote unavailable printer.... I guess that cause it to send the DNS lookups with a certain interval.

However, even with no remote printers installed - I still see wireless restarts, now caused by mDNS (multicast DNS) packets in my network... I am not sure which application is sending them, but these packets should definitely not cause wireless restart in the D-link router.

[ibaboun]

Turning off the network threat prevention (SEP) from the wired PC have resolve the wifi restart of the router. I do not need to turn the wired PC off any more.
By the way. I have 3 DIR 825 on my net, but only one working as router. The three 825 experienced the wifi restart. They all have different firmware version, but are the A1 hardware.

[osj]

Unfortunately I have to realize that it is impossibly to report even very reproducible problems to D-link, because their 1st line support believe that all problems can be solved by "making factory default" or "adjusting the antennas". It seems to be pure knowledge-base support, it is not possibly to reach a technical support level that even know how to open a Wireshark capture.

To bad for D-link that end-users cannot open trouble tickets, maybe they are not even aware of how bad some of their products are performing in the real world. I think there are a lot of people that could contribute as beta-testers and help getting D-links products more stable, if they would try to use the feedback and open a dialog.

The only solution at the moment seems to be applying different workarounds found on the internet, while still hoping for a new firmware release. I guess I will still wait a couple of months, before I give up on D-link and start looking for another router.

[koesterm]

I experience the same problem as well.  I have spent several hours on the line only for them to tell me its a defective router and RMA it.  I know its not the router as I've been able to replicate this on 2 different routers and didn't have the problem until firmware 1.12.

Does Dlink read these, can't they issue a fix.  This is really frustrating.