D-Link Forums
COVR - D-Link Whole Home Systems => COVR-2202 => Topic started by: GreenBay42 on September 02, 2020, 08:29:08 AM
-
Another new beta for the "guest network broadcast in AP mode" issue. Still not 100% but they said it is no longer open and the broadcast will stop after 3-5 minutes after a reboot.
ftp://FTP2.DLINK.COM/PRODUCTS/COVR-2202/REVA/BETA/COVR-2200_REVA_FIRMWARE_v1.06B03_HOTFIX.zip (ftp://FTP2.DLINK.COM/PRODUCTS/COVR-2202/REVA/BETA/COVR-2200_REVA_FIRMWARE_v1.06B03_HOTFIX.zip)
-
Ok, Will check this out and report my findings. ;)
-
Ok,
Router mode seems to be still working.
I do see dlink guest for a few seconds from the B point however it disappears soon after and doesn't return. Same for Bridge (AP) mode.
Unfortunately I have found a bug. ::) The A point is crashing I believe, and starts blinking AMBER after connecting the B point via Ethernet while in Bridge (AP) mode. A Gb switch is in between the A point and B Point. Doesn't do this in router mode. My 1 wired PC connected to the switch also looses internet connectivity. :-\ B Points front LED is WHITE. Wifi is still broadcasting.
Testing the B Point directly connected to the A Points #2 port directly with out a switch has same results for Bridge (AP) mode.
A factory reset and setup from scratch was performed along with two tests each for router and Bridge (AP) Mode.
I tested this new FW and COVR behind a main host router. So I'll try and find some time to put the COVR system online as main host router mode and see how it goes. ???
Update 10/6/2020:
I found that it was not the A point that was crashing or stopping. It was the upstream non D-Link gateway modem I had the 2202 system connected too. I tried a different non D-Link MESH system and it also causes problems at the gateway modem. I how have the 2202 system configured in AP Mode behind a different non D-Link router and the entire system is working fine with the B point ethernet connected behind 3 daisy chained DGS 1 series switches. I've contacted the Mfr of the non D-Link gateway modem about the problem seen on there modem. ;)
Still wish D-Link would try to implement changing from Bridge mode back to Router mode with out having to factory reset the A Point and setup from scratch. ???
-
Thanks for the update. I sent HQ your findings.
-
Thank you. ;)
-
I wanted to get a couple of pictures, one of the A Point after its crashed with the A Point Ethernet connected in AP mode.
And what I see on the network when the B point is connected to Ethernet when it first turns ON and syncs with the A Point.
(https://i.postimg.cc/1V3jsQ69/APoint-Crashed-With-BPoint-Ethernet-Connected.png) (https://postimg.cc/1V3jsQ69)
And what I see on the network when the B point is connected to Ethernet when it first turns ON and syncs with the A Point. ARP storm?
(https://i.postimg.cc/G8Q5W247/Bit-Meter-ARPStorm-When-BPoint-Ethernet-Connected.png) (https://postimg.cc/G8Q5W247)
I just put the A point online as main host router and then turned ON the B point connected Ethernet behind 4 Daisy Chained switches.
I see this ARP storm happened 3 times then has gone away:
(https://i.postimg.cc/SJFG69DW/Bit-Meter-ARPStorm-When-BPoint-Ethernet-Connected-Router-Mode.png) (https://postimg.cc/SJFG69DW)
I presume this maybe by design...
A Point>DGS-1100>DGS-108>DGS-105>DGS-105 in basement that the B point connects too.
I noticed that I could not get the iphone or pad to connect to Airport Extreme. I changed the SSID name to Airport then they connected. I changed back to Airport Extreme and they would not connect and found the A point at RED. I powered OFF the A point, Then I went down and removed the B Point from Ethernet and restarted the A point.
A point is WHITE again and devices are reconnected. Something with B point Ethernet connected maybe causing the A Point to not work right in router mode.
I had to run into town for a bit. I returned and system is still online. B Point is wireless connected though with a weak connection. Why I'm hoping to Ethernet connect the B point in the basement...I'll try again to connect the B Point via Ethernet. I'll try and capture logs if the A point remains connectable.
Update 10/6/2020:
I found that it was not the A point that was crashing or stopping. It was the upstream non D-Link gateway modem I had the 2202 system connected too. I tried a different non D-Link MESH system and it also causes problems at the gateway modem. I how have the 2202 system configured in AP Mode behind a different non D-Link router and the entire system is working fine with the B point ethernet connected behind 3 daisy chained DGS 1 series switches. I've contacted the Mfr of the non D-Link gateway modem about the problem seen on there modem. ;)
-
My config is a COVR-2203 in bridge mode (AP) mode. I want to make clear, since no one seems to be talking about it, that when in bridge mode the guest wifi configuration is missing from the menu in both the app and web client.
FW 1.03 - 1.05 - guest network could be setup prior to switching to BM but when in BM would not connect but still broadcast
FW 1.06B03 - guest mode is off no matter if it was setup prior to switching to BM
The biggest issue for me is that the 'mesh system' does not work as a mesh at all. It works as a star and I have no idea if it supposed to or if the FW is broken. Since most people only run one B unit I think this is under talked about.
-
Can you post screen captures of the Guest Network menu option seen on the A Points web page while in router and bridge mode?
What browser are you using?
My config is a COVR-2203 in bridge mode (AP) mode. I want to make clear, since no one seems to be talking about it, that when in bridge mode the guest wifi configuration is missing from the menu in both the app and web client.
FW 1.03 - 1.05 - guest network could be setup prior to switching to BM but when in BM would not connect but still broadcast
FW 1.06B03 - guest mode is off no matter if it was setup prior to switching to BM
The biggest issue for me is that the 'mesh system' does not work as a mesh at all. It works as a star and I have no idea if it supposed to or if the FW is broken. Since most people only run one B unit I think this is under talked about.
-
So after having the 2202 system on line as main host router with B point wirelessly connected, I attempted to connect the B point in the basement to the A Point via ethernet connection with a few switches in the middle. Soon as I connected the B Point in the basement to the last switch in the daisy chain the A Point seemed to stop working and all wifi and wired devices lost internet access. I checked the A Point and the front LED was still WHITE. I tried a wired PC to connect to the A Point to see if I could get to the web page and long in and could not access the web page. So capturing logs was not successful.
I presume there maybe an issue with maybe having too many switches in the mix though this works for my COVR1203 system and other non D-Link MESH systems.
I'll try and test the B Point at the first swtich (DGS-1100) thats right behind the A Point and see what happens. I may test at each switch to see what happens.
Seems that there is a problem with B Point being ethernet connected. ???
-
Ok so I took the B Point and connected it behind the DGS-1100 switch, it connected OK here and A Point remained operational and online. NO problems. I skipped the DGS-108 that was next and went to the living room DGS-105 and connected the B Point there. It connected OK here and A Point remained operational and online. NO problems. I then went back to the DGS-105 in the basement and connected the B Point there again. Powered ON the B Point and also power cycled the switch there. I did move the connected to a different port as well for the B Point. It connected OK here and A Point remained operational and online. NO problems. Possibly this one switch or the port on this switch could have been in a bad state though other devices were connected to this one switch and working, i.e. xbox.
The system is now working as expected in router mode with B Point Ethernet connected behind daisy chained switches. I'll let this run for a while and see if anything appears. Hopefully not. ::)
-
Just reporting that the 2202 system has been running very well since clearing the switch/B point issue. Let the system run over the long weekend and it has been good in router mode with the B point wired behind a few daisy chained switches. I games and streamed and have many devices connected. No complaints from other house hold members. Seems that v106B03 is pretty good.
I hope D-Link was able to review the bug found in Bridge (AP) mode. ???
-
I PM'd you more questions from the engineers. Sounds like they replicated the issue.
-
Good. I replied.
Other than the Bridge mode and B Point causing the A Point to show front AMBER led and crash. Router mode is working very well. Enjoying this system, finally. ::) This version of FW seems stable and is working well. ;)
-
Here are two screen shots:
I included links as well since embedded links aren't working.
Wireless config in bridge mode...no guest option
https://ibb.co/xH8zNqJ (https://ibb.co/xH8zNqJ)
(https://ibb.co/xH8zNqJ)
Main page showing in bridge mode
https://ibb.co/DKHNM3w (https://ibb.co/DKHNM3w)
(https://ibb.co/DKHNM3w)
Let me know if you want any more screenshots.
FW1.06B03, factory reset on pt A and both pt B's after upload.
-
I know that Guest Network was a problem that plagued the 2202 system while in bridge mode. Was being broadcast in bridge mode even when it was not enabled. So D-Link may have taken Guest Network out in this FW.
I would send this information to D-Link support to ask them about this to see if this is a permanent change or something they may bring back.
-
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.
-
is this version stable for AP mode or only router mode? also, I have a problem where I have three instances of the signal one locked signal, another guest one, and one open signal, so what's the problem this time.
my region is EMEA and the support of this region is really trash.
my latest FW is 1.05
Edit: I have three instances of each network from each point for example I'm having from point A one locked Network X, another guest one, and one open Network X with no password. same for point B, this is really frustrating.
-
When you first update FW, update the B points first, then update the A point lastly. Factory reset the ALL points and setup from scratch. I would not enabled Guest Network just yet.
After the A point is setup first and up and running, then turn on one B point at a time. Make sure the 1st B point is synced completely with the A Point and shows having the same SSID name and PW and placed it its remote location. Then turn on the other B point and do the same. Sync both B point while in same room or near the A Point. After both B points are fully synced, place in remote locations.
I would troubleshoot your odd problems with turning OFF the 2nd B point and just run the A point and 1 B point to help narrow down whats going on.
Try v1.06 FW by using the mentioned FW update process.
is this version stable for AP mode or only router mode? also, I have a problem where I have three instances of the signal one locked signal, another guest one, and one open signal, so what's the problem this time.
my region is EMEA and the support of this region is really trash.
my latest FW is 1.05
Edit: I have three instances of each network from each point for example I'm having from point A one locked Network X, another guest one, and one open Network X with no password. same for point B, this is really frustrating.
-
An yes, this FW works in AP Mode as well. I have mine set up in AP mode and B point Ethernet connected behind 3 switches. DGS series.
An earlier problem I found was resolved and not related to the COVR system.
-
Update: yesterday I took a short way and returned the cover to router mode while replacing my DHCP server on the cover system with another on my main Mikrotik, although my region is EMEA and since the support in this region is really trash (their website doesn't function correctly for crying out loud) I used the 1.06B03 FW and surprisingly it's working like charm, the Guest networks, and the open networks are now off not seen even on the wifi graph (i don't know if this is because I changed the Operation of the system or not), since yesterday it didn't crash, it didn't drop the connection, or disconnected the slave from the Masterpoint A.
so Overall I'm satisfied with this FW, till now at least.
-
Thank you for letting us know. I Think v1.06 is the best FW to date. AP mode has been stable for me.
I wish they would allow to return to router mode from bridge mode with out having to setup from scratch. :-\
-
I've asked multiple times about switching back to router mode from AP but not getting any kind of answer. ::)
-
Whom should I send an email too. LOL I'll send a hot potato over there and get some response. :o
-
Silence usually means NO.
Oh are we good on the other issue (guest network broadcasting)? I need to close it out.
-
>:( I'd like confirmation though. ;)
Yes, Guest Network is fixed now. Finally. ;)
-
Thank you for letting us know. I Think v1.06 is the best FW to date. AP mode has been stable for me.
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.
-
Really?
What are the exact steps?
I wondering if not using styles like from years ago to unhide some web page content works.
IF thats the case, should be easy for D-Link to just add this back in for normal web page selection. ::)
-
Please help. I installed version 1.06, but unfortunately after a while the speed decreases to the second point by half. I want to connect the two points with internet cable. Is my version ok for a good speed?
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=49573.0)
- What region are you located?
- Are you wired or wireless connected to the router?
- Was a Factory Reset performed before and after any firmware updates then set up from scratch?
Link> >FW Update Process (http://forums.dlink.com/index.php?topic=42457.0)
- Was the router working before any firmware updates?
What is the Mfr and model# of the ethernet switch in the configuration?
What is the distance in between the A and B points? Ft.
Please help. I installed version 1.06, but unfortunately after a while the speed decreases to the second point by half. I want to connect the two points with internet cable. Is my version ok for a good speed?
-
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
-
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
-
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 ;) )
-
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
-
COVR mesh system will not support separation of SSIDs.
-
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 ;) )
-
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.
-
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.
-
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.
-
If I live in singapore (not NA region), can i update to 1.06?
-
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?
-
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.
-
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.
-
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!
-
Be sure to do a back up config saved to file for safe keeping. Saves time if a reset is needed.
Enjoy.
-
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)
-
Yes B first the A.
Yes.