Print

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

[joejoeinc]

My friend who bought this mesh network system has had nothing but problems with this DLINK product.

The issues:
- Random disconnections
- Pages fail to load
- Nothing to configure in the UI (can't disable MIMO anymore since firmware update)
- Google nest randomly drops off the network
- iPhones randomly drop off the network frequently

I headed over to take a look at this system to see if I could help resolve the above issues. I found the following issues typical of most DLINK products.

- Phone app locked up or timed out
- Updating firmware failed to find an update that should be available.
- Number of devices connected never really reflects the number of devices actually connected.
- everything is super slow in the UI and phone App.
- can't disable MIMO even though the manual shows you that you can.

honestly, it's been about 12 years since I touched a dlink product and this has just reinforced the why I don't use Dlink products anymore. 

am I missing something in this product? is there a hidden config page I'm missing?

[FurryNutz]

Link>Welcome!

• What Hardware version is your router? Look at sticker under the router case.
• Link>What Firmware version is currently loaded? Found on the routers web page under status.
• What region are you located?

Internet Service Provider and Modem Configurations

• What ISP Service do you have? Cable or DSL?
• What ISP Modem Mfr. and model # do you have?

What is the distance between A and B points? 30 feet in between is recommended to start...

I recommend manually updating the COVR system by downloading the FW file and using a wired PC and web browser, send the FW file to the B points first then A point lastly...
http://forums.dlink.com/index.php?topic=75212.msg304647#msg304647

Factory reset the B points and A point and setup from scratch...

[aalllop]

My friend who bought this mesh network system has had nothing but problems with this DLINK product.

The issues:
- Random disconnections
- Pages fail to load
- Nothing to configure in the UI (can't disable MIMO anymore since firmware update)
- Google nest randomly drops off the network
- iPhones randomly drop off the network frequently

I headed over to take a look at this system to see if I could help resolve the above issues. I found the following issues typical of most DLINK products.

- Phone app locked up or timed out
- Updating firmware failed to find an update that should be available.
- Number of devices connected never really reflects the number of devices actually connected.
- everything is super slow in the UI and phone App.
- can't disable MIMO even though the manual shows you that you can.

honestly, it's been about 12 years since I touched a dlink product and this has just reinforced the why I don't use Dlink products anymore. 

am I missing something in this product? is there a hidden config page I'm missing?

Hello, I have a case opened with dlink with the same problems. I have tested all type of things. The problem happens when your device is connected to router on the 2,4 Ghz network. If you stay connected to 5 Ghz all comunications works well. You can test it on a computer with wifi analyzer app and the speed test of google. Go far away of one router to force the connection to 2,4 Ghz and yuy will se that top speed of the network is 1 mbps aprox. If you see you are connected to 5 Ghz you will have all speed of your ISP.

[FurryNutz]

Any updates on this?

My friend who bought this mesh network system has had nothing but problems with this DLINK product.

The issues:
- Random disconnections
- Pages fail to load
- Nothing to configure in the UI (can't disable MIMO anymore since firmware update)
- Google nest randomly drops off the network
- iPhones randomly drop off the network frequently

I headed over to take a look at this system to see if I could help resolve the above issues. I found the following issues typical of most DLINK products.

- Phone app locked up or timed out
- Updating firmware failed to find an update that should be available.
- Number of devices connected never really reflects the number of devices actually connected.
- everything is super slow in the UI and phone App.
- can't disable MIMO even though the manual shows you that you can.

honestly, it's been about 12 years since I touched a dlink product and this has just reinforced the why I don't use Dlink products anymore. 

am I missing something in this product? is there a hidden config page I'm missing?

[fermulator]

can confirm PRECISELY this behaviour (and more) -- there are major issues with this product's WiFi stability and performance at the moment

1. sometimes wired backhaul creation fails to form mesh properly (startup race condition? islanded mesh connections?) <-- especially bad if you get a power blip/outage ... you have to retry powercycle sequence a few times until the network actually comes online properly
2. clients can get "stuck" into 2.4GHz band (steering stops working) -- even when next to secondary node, refuses to flip to 5GHz
3. when on 2.4GHz speeds are horrendous (~1-20 Mbps)
4. when on 5.0GHz speeds are fantastic (~200-500 Mbps)

TIPS:

I used `iperf` tool locally to eliminate ISP/Internet variability which was drastically helpful, as well as took packet captures of the D-Link topology traffic in hopes that support/R&D can isolate the problem.

I used `wavemon` and `linSSID` on a Linux notebook that supported by 2.4 and 5.0 GHz bands to analyze -- confirmed wifi signals/channels are clean and this is not relevant to the problem.

Confirmed with D-Link support that when the COVR points are in bridged mode w/ wired backhaul, the placement really shouldn't matter or affect performance. (I saw several points about "at least 30' apart" ... but not too far apart, etc -- this is not relevant when using wired backhaul and placement should be flexible since WiFi mesh nodes will auto-select their channels to avoid conflicting with one another)

I contacted D-Link support and was confirmed that the case is escalated and under lab testing.

Case ID: `C6984446`

[FurryNutz]

YOu have the 1210 series COVR, I presume there maybe some differences between the 1203 and the 1210 COVR series systems so FW version will differ and maybe different. The 1210 series isn't available to the USA region.

Good Luck.

can confirm PRECISELY this behaviour (and more) -- there are major issues with this product's WiFi stability and performance at the moment

1. sometimes wired backhaul creation fails to form mesh properly (startup race condition? islanded mesh connections?) <-- especially bad if you get a power blip/outage ... you have to retry powercycle sequence a few times until the network actually comes online properly
2. clients can get "stuck" into 2.4GHz band (steering stops working) -- even when next to secondary node, refuses to flip to 5GHz
3. when on 2.4GHz speeds are horrendous (~1-20 Mbps)
4. when on 5.0GHz speeds are fantastic (~200-500 Mbps)

TIPS:

I used `iperf` tool locally to eliminate ISP/Internet variability which was drastically helpful, as well as took packet captures of the D-Link topology traffic in hopes that support/R&D can isolate the problem.

I used `wavemon` and `linSSID` on a Linux notebook that supported by 2.4 and 5.0 GHz bands to analyze -- confirmed wifi signals/channels are clean and this is not relevant to the problem.

Confirmed with D-Link support that when the COVR points are in bridged mode w/ wired backhaul, the placement really shouldn't matter or affect performance. (I saw several points about "at least 30' apart" ... but not too far apart, etc -- this is not relevant when using wired backhaul and placement should be flexible since WiFi mesh nodes will auto-select their channels to avoid conflicting with one another)

I contacted D-Link support and was confirmed that the case is escalated and under lab testing.

Case ID: `C6984446`

[fermulator]

@FurryNutz : there's no technical difference between the US and Canadian versions here other than radio frequency band requirements between the two countries.  We should have every reason to infer that the SAME problems exist between these models -- as I have confirmed the same problem as OP.

[FurryNutz]

Yet there maybe though. However let us know what you find out from D-Link support though.

Good Luck.