Print

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

[pblanton]

I just bought the COVR 2202 from Amazon and am waiting for it to be delivered. It should come in tomorrow.

Currently I think it will cover my house with just the two nodes, but in the future I'd like to add an extra node to cover my shop. The shop is 2000 square feet and is about 30 feet from the main house. I currently am able to receive my current wifi signal in the closest end of the shop, so I think a third node should do it, but I am unable to find add-on nodes available for purchase.

When do you expect the add-on nodes to be available? And will the COVR C1203 devices be compatible with the COVR 2202 system? Dang that'd be nice.

[FurryNutz]

I don't think add on nodes are available for both COVR models and unfortunately the COVR models are not compatible with each other.

I believe you can get another 2200 set and use BOTH units as remote points. I'll have to have someone from D-Link confirm this. I think this is possible with one of the COVR models.

[eelpout]

At the moment D-Link doesn't offer single units.

I bought two 2202 kits as well, but so far have only opened up one box for testing (the price was decent at Amazon when I got them). The amplifiers in these Covr 2200s is much stronger than some of the Linksys and TP-Link's I have already.

D-Link support said the Covr "A" unit from the 2nd kit should behave as a slave regular "point" after doing the initial setup (page 64 in the manual). I'll probably try this out sometime this week.

I'm currently running the Covr's in "bridge" access point operating mode as I like the Gargoyle routing software I'm running on a TP-Link C7 Archer unit better. I may switch over to using the Covr as a router down the road if it improves and becomes more fully featured.

[FurryNutz]

Thanks for letting us know. Please let us know how it all works out for you.

[eelpout]

FYI. I've tried multiple times to get the Covr "A" main unit from my second kit to sync up to the original "A" main, so far it's a no-go, never get the white LED that shows a successful sync. The regular point from the 2nd kit went without a hitch first try. There is something about the "A" units that's obviously different. I'm thinking there must be a way to first get these main units into a slave mode to accept the programming.

I asked D-Link support about this last week and they simply pointed me to the manual and said the standard procedure should work. I've contacted them since I've actually tried it out and failing but haven't heard back yet. (they are usually quite quick to get to me, but lagging on this)

Luckily I think I can get pretty good coverage with 3 units in our house since these large Covr's have decent amplifiers. One of the units (that currently isn't on Ethernet back-haul) sometimes starts blinking the LED white (meaning wireless back-haul signal is weak) but still has acceptable bandwidth.

[FurryNutz]

Hmmm Interesting...

Howe do you have your B Points connected, ethernet? Any of them wirelessly connected?
Are the B Points connected to a LAN switch?

Do you have DNS Relay enabled on your A Point router?

[eelpout]

Hmmm Interesting...

Howe do you have your B Points connected, ethernet? Any of them wirelessly connected?
Are the B Points connected to a LAN switch?

Do you have DNS Relay enabled on your A Point router?

The main "A" is in my home office, directly connected by Ethernet to my TP-Link router. I have one Point upstairs on Ethernet back-haul (via a couple switches in the path) and the other in the kitchen using the 5Ghz wireless back-haul. Interestingly enough on that unit, the D-Link back-haul shows up as another network name. This 2nd point will likely end up on Ethernet too, I'm just trying it out to see how well the wireless back-haul works. We're somewhat lucky in that when we bought this house years ago, we ran Ethernet to most points of the house (bundled with fiber optic too, which has been mostly useless .

I think DNS Relay is enabled, yes. I need to figure out what that really does. (Oh, OK, looked it up. I'll probably turn it off and just point to the old router)

[FurryNutz]

Ah ok So your running in AP mode. I was running in router mode last nite. For some reason disabling DNS Relay caused devices to loose internet. I need to look into this.

My B point was ethernet connected behind 5 daisy chained switches.

DNS relay just gives all connected devices a 192.168.0.1 DNS IP address and routes all traffic thru this IP address and processes out to the WAN side DNS. When DNS Relay is disable, then WAN side DNS is passed thru to all connected clients instead of 192.168.0.1. I prefer having DNS Relay disabled as this is less processing of traffic as possible. DNS relay is needed when using scheduling and access control features though.

[eelpout]

Ah ok So your running in AP mode. I was running in router mode last nite. For some reason disabling DNS Relay caused devices to loose internet. I need to look into this.
...

hmm interesting. so if you have no other router in the chain and disable DNS Relay, you're relying on the cable/DSL box to give the ISP's DNS? Hmm, not sure that'll always work. I use my TP-Link (running Gargoyle) to be the final arbiter of DNS in my chain (usually inheriting from Google, OpenDNS or Cloudflare).

[FurryNutz]

I don't have a router in front of the A point router. A point is the main host router so signal NAT here. I hadn't seen this issue with other DIR or COVR 1203/3902 systems before.

Yes, disabling DNS Relay allows the pass thru of WAN side DNS from the ISP This is normal operation seen on D-Link routers. Users can specify custom DNS as well.

[eelpout]

i heard back from D-Link and they said the main Covr “A” needs to be in “router” operational mode and the target Covr “A” from the 2nd kit needs to be in “bridge” mode for the sync to add as a node to work. Makes some sense.

hopefully i’ll get a chance to try this out this week. would have to put my main Covr unit back in router configuration and that’ll take a bit more time.

[FurryNutz]

Good to hear. Let us know how it turns out. I'll try and find some time this week to play with my 2202.

[Marwood]

i heard back from D-Link and they said the main Covr “A” needs to be in “router” operational mode and the target Covr “A” from the 2nd kit needs to be in “bridge” mode for the sync to add as a node to work. Makes some sense.

hopefully i’ll get a chance to try this out this week. would have to put my main Covr unit back in router configuration and that’ll take a bit more time.

Hi!

I know it's been a while since this was posted but hopefully someone will reply!

I'm in this exact same situation, bought a new pair of Covrs, unit B added straight away, unit A won' add.

My main unit A is in router mode, how do I go about putting or checking that my new unit A is in bridge mode when I can't get it to connect to check?

Thanks in advance!

[GreenBay42]

You will need to connect directly to it via Ethernet. It should be in router mode so your computer will get an IP. Log into it normal (192.168.0.1 or  http://dlinkrouter.local.) and configure to bridge mode. Note make sure the firmware is upgraded and the same as the other A unit so update first if needed.

Configure as a bridge. Turn the unit off. Connect it to the other A unit via Ethernet cable. Turn it on and it should auto-sync. Once booted, log in to the other A unit to see if it is there. Then unplug the ethernet cable and turn off the node. Turn it back on and make sure it connects before placing.

If you ever hard reset it, it will go back to router mode so you will have to do this process again.