Print

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

[FurryNutz]

Distance can be a factor.

Glad you got them working better on wired connections.

Enjoy. 

I solved the problem by connecting the two points with the internet cable.  The wi-fi connection between them has a problem but I don't bother anymore

[eelpout]

I wish they would allow to return to router mode from bridge mode with out having to setup from scratch. 

use google chrome's inspect and unhide the operation page and reselect router mode I did it once and it worked LOL.

Curious as to how you did this. I can't find the operation page in the html anywhere.

( i'm still  on v1.04, afraid to take the plunge )

[hoangdinh86]

Please, adding support separate 2.4GHz and 5GHz SSIDs. Because, It transmits 2.4GHz even though it has 2 thin walls, which results in not as fast as 5GHz

[FurryNutz]

COVR mesh system will not support separation of SSIDs.

[FurryNutz]

Might have to update, though I haven't seen it either.

I wish they would allow to return to router mode from bridge mode with out having to setup from scratch. 

use google chrome's inspect and unhide the operation page and reselect router mode I did it once and it worked LOL.

Curious as to how you did this. I can't find the operation page in the html anywhere.

( i'm still  on v1.04, afraid to take the plunge )

[FurryNutz]

Any updates on this?

Another frustrating morning with COVR here. When I first got up today, I logged on with my work laptop and checked in on my phone just fine. When the kids tried to log on for school with their Chromebooks (less than 10 active devices on the network in total, all devices that had previously joined the network), the network went down. The B point seemed to crash—blinking orange. The A point couldn’t be joined by any devices, though the color was white and it was broadcasting its SSID.

I unpowered A, the Ethernet switch, and B, and then restarted the fiber modem, then A, the switch, and B. Now everything is back up and running, but it’s really frustrating to have the system keel over every other week. Sometimes it happens at the start of day. (It often takes the laptop several minutes to connect, and it’s using Ethernet connected to point B.) And sometimes it happens at the end of the workday. I don’t know if it’s the complexity of a two-point system or D-Link’s build quality or software, but the reliability of this system is really disappointing. I’m about ready to plug my old ASUS N-66U back in. It would run for months without needing a restart. I was trying to buy a router, but it seems I’ve bought a pet instead.

[heidarren]

I've found that ethernet connection will create loop, maybe due to it connect both 5G2 and LAN at the same time, then the whole network will be broken and a restart is needed, this happened in both router and AP mode. No problem if both COVRs were connected via wireless, something's wrong with the connection logic in this model.

[FurryNutz]

How do you have yours connected?
Is there a ethernet switch in between the A and B Point?
The B Point should be wirelessly connected first then ethernet connected behind the A point.

I have 4 switches Daisy Chained in between the A and B point here.

Something I haven't encountered. I've had mine in AP mode mostly and ethernet connected. Just the one B point ethernet connected. Haven't seen any loops or issues with this version of FW. Been the most stable to date.

I've found that ethernet connection will create loop, maybe due to it connect both 5G2 and LAN at the same time, then the whole network will be broken and a restart is needed, this happened in both router and AP mode. No problem if both COVRs were connected via wireless, something's wrong with the connection logic in this model.

[born996]

If I live in singapore (not NA region), can i update to 1.06?

[FurryNutz]

I haven't seen any information regarding this being a specific regional FW so I believe it's open to everyone.

You can downgrade back to what you had if it doesn't work. I would have those prior version FW file on hand just in case.

If I live in singapore (not NA region), can i update to 1.06?

[eelpout]

I know this unit is on life support but had a question. I'm running in bridge mode on v1.04, haven't upgraded since everything is stable. 3 units, using Ethernet as the backbone.

If I was to go to v1.06b3 (to get rid of the guest SSID) is it still recommended to upgrade B units first and then the main? If I don't reset all units after the upgrade, what might happen? Will the guest mode not disappear unless I reset? Thanks in advance.

[FurryNutz]

Yes update B points first. Then the A point lastly.

I recommend factory resetting ALL points and setup from scratch.
Guest Network issue was fixed on this version of FW:
http://forums.dlink.com/index.php?topic=75828.msg308265#msg308265

I know this unit is on life support but had a question. I'm running in bridge mode on v1.04, haven't upgraded since everything is stable. 3 units, using Ethernet as the backbone.

If I was to go to v1.06b3 (to get rid of the guest SSID) is it still recommended to upgrade B units first and then the main? If I don't reset all units after the upgrade, what might happen? Will the guest mode not disappear unless I reset? Thanks in advance.

[eelpout]

Yes update B points first. Then the A point lastly.

I recommend factory resetting ALL points and setup from scratch.
Guest Network issue was fixed on this version of FW:
http://forums.dlink.com/index.php?topic=75828.msg308265#msg308265

went ahead and upgraded the 3, 2202's, without doing a factory reset and things seems OK. and the guest network did disappear.

thanks!

[FurryNutz]

Be sure to do a back up config saved to file for safe keeping. Saves time if a reset is needed.

Enjoy.

[gozaine]

Yes update B points first. Then the A point lastly.

I recommend factory resetting ALL points and setup from scratch.
Guest Network issue was fixed on this version of FW:
http://forums.dlink.com/index.php?topic=75828.msg308265#msg308265

I know this unit is on life support but had a question. I'm running in bridge mode on v1.04, haven't upgraded since everything is stable. 3 units, using Ethernet as the backbone.

If I was to go to v1.06b3 (to get rid of the guest SSID) is it still recommended to upgrade B units first and then the main? If I don't reset all units after the upgrade, what might happen? Will the guest mode not disappear unless I reset? Thanks in advance.

what is the procedure to update?
first B and then A?
Is this update recommended? (1.06B03 Hotfix)