Ok, so I was able to come back to the 2200 and saw v1.05 was available. I got it loaded and let the A Point update the B and itself since there isn't any actual FW files available as of yet for manual load. After loading I didn't perform a manual update.
Couple of problems: From v1.04
1. If I setup the A point router for my networking need prior to putting it on the home network with DNS Relay disabled. I don't get any internet access for some reason. I noticed that my Mac Book Pro what was wired or wireless connected, NO DNS Addresses showed up with DNS Relay disabled. This is the first for me as I normally disable DNS relay on all D-Link routers I've used before. Saw no issues with this until now with the COVR2202. Something with DNS Relay being disabled is not working right.
This issue seems fixed with V1.05 as I set up the A point behind a primary router and I disabled DNS relay and didn't set any manual DNS. Rebooted and PC that was connected to the A Point got internet services. Thank you D-Link 
2. I was able to connect the B point extender downstairs at the end of 5 switches that are daisy chained. 3 DLink DGS105/108 were replaced with HP Pro Curve 1800 series non managed switches. The front LED was solid white after getting connected.
However, speed testing with a Galaxy Tab S2, iPhone 6sP and Mac Book Pro 2018 using Ooklas's speed test app resulted in horrible speeds. Nothing over 12-15Mbps on the down. I turned off and back ON, the wifi radios on each device while near the B Point downstairs so I could ensure they were connecting to the B Point there. I have a different Non D-Link MESH system that was just tested and I see near 900Mbps while using that system.
I have since removed D-Link DGS series switches from this segment and installed HP Procure 1400/1800 series switches to the basement area. There are now only 3 switches in this daisy Chain. While at my desk testing however today with v1.05, After wirelessly connecting the B Point to the A point, I switched to AP mode, Then I connected the B Point to the A Point via Ethernet cable with a switch in between them. They seem to connect however I noticed that my switch the A and B points are connected to started blinking constantly as if there was some form of a ARP storm happening. I look at a different switch that was on a different segment of my network and it was also constantly blinking. This has 3 printers connected to this other switch is all. I rebooted the B Point to see if the constant LED activity would stop on the switch. It did however after the B point came back online, the switches LEDs started constantly blink. I let this run for over two minutes thinking the activity would settle down and stop and go back to random blinking. It didn't so I disconnected the B point from the switch and went back to wireless. I moved the A and B points to a different configuration and the constant switch LEDs keep happening. Used a DGS-1100 in between the A and B Point. I see that there was two long constant blink events on my PCs networking graph, each about 1 minute log. Now the switch seems to be back to random blinking activity. Possible it takes about 2-3 minutes for the A and B Point to settle in. Ah nope, as I was typing this, I see my network display monitor has started again and the DGS1100 is blinking constantly again. That was about 30 seconds. Now it's stopped. Letting it run for a few more minutes. Ok, seems to be stable now. The system many need 2-5 minutes to settle in, however It would bring some concern to those looking at the network activity being always constant. The connect should be good after no more than a minute. I'll power OFF the 2202 system and put it in place of my main wifi AP system and let it run for a while though Guest Network is enabled and I can't disable it. 
3. The A point router is unstable for some reason as after I rebooted the A point after DNS Relay was enabled then disabled again to see if WAN side DNS would populate devices, i was no longer able to connect to the A Point router from down stairs behind the last switch. Also noticed that my mac book pro wired or wireless would not get an IP address from the A point router. I also noticed that while I was downstairs with the B point that was wire connected, it was solid WHITE, then started blinking Amber is it seemed to loose connection with the A point router after I disabled DNS relay. I also think that maybe changing the DHCP IP address pool from .2 and .254 to .100 thru .150 and applying this change may have caused instability as well while all other wired network devices were online. I presume something that shouldn't make the router hang or cause the router to stop working correctly. I normally get this up and thought I had a day prior before going live this evening. I guess not.
I believe this maybe fixed however I haven't had a chance to confirm this as I'll need to put the A point online as main host router. Something I'll try and find time doing this week or weekend.4. Adding that when the 2202 is in Bridge (AP) mode, that guest wifi nework is enabled and being broadcast in the open. Not secure and I can not disable it.
This issue is still seen in AP Mode. There is no UI setting to enable or disable Guest Network in the A Points web page. I had to reset the A Point and configure from mobile mydlink app to get back to router mode. The guest SSID It's not seen in Router mode. I even enabled it guest network first in router mode, set a new name and set a PW. Was good here. Then disabled guest network. Then changed to AP mode and placed the A point in it's final position and powered ON the A point. The new Guest Network was seen. However after I powered ON the B Point and let it sync, I saw the default Guest Network for a few seconds then the default guest network disappeared then the Guest Network I configured appeared for a few seconds then disappeared. Seems like crazy behavior. I'll let it run for a while and see how it goes. 
So After putting the A Point in AP mode in it's position things were ok. Devices were connecting to it fine. I then connected the B point wirelessly to ensure it connected. Then connected the B point via ethernet. Saw same long constant LED activity on the switch before it finally stopped. I then moved the B point to the basement behind 3 switches and powered it ON. I went back up stairs to wait for it. I saw 1 long network activity on my PC then nothing. I attempted to log into the A point however it's web page would not pull up. I looked at my Android pads wifi analyzer and saw the SSID signal had disappeared. I went over to the A point and saw COVR led was
RED. After a few more seconds it changed back to WHITE. I went back to my desk and saw the SSID appear along with the SSID from the B point. However after a few minutes, the SSID disappeared and I could not access the A Point web page again. I looked at the A Point and the front LED was still WHITE. Also my DCS cameras started showing up as available SSID names letting me know they were no longer connected to a wifi signal. Not sure what happened here however the system seems unstable in AP mode for unknown reasons.
I had to put my prior wifi mesh system back online and take the 2202 system off line. I'll try router mode this week or weekend.
Ok, so tonite and setup the 2202 A point for router mode and connected it to the ISP modem. I left the B point off line however connected to Daisy Chained switch down to the basement where the B point is located. A Point router came to ready and seemed to be ok. However after turning on the B Point and after it came ready, the A Point routers front LED turned
RED. I was able to access the web page. The the LED turned WHITE, then shortly after that, started blinking
AMBER. I then was not able to connect to the A point routers web page. Not sure what is happening however the A point seems ok until the B Point thats ethernet connects causes the A point to stop working correctly. I've taken the 2202 system back off line and will set it up back at my desk and do some troubleshooting. I don't think it's the daisy chain switches since the other MESH system I have works in place with this configuration.
Author
Topic: COVR-2202 firmware 1.05 (Not recommended to use!) (Read 9988 times)