NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
OrbiOS 2.1.4 + Homekit
We’ve been monitoring issues that some users have experienced on OrbiOS 2.1.4 with Apple Homekit. In response, to those customers, we’re releasing firmware that provides a temporary work around to customers while we work towards a more permanent fix. Please use the manual firmware upgrade process to apply to your Orbi
RBR50: http://files.netgear-support.com/go/?a=d&i=RfJ5eMJWFW
RBS50: http://files.netgear-support.com/go/?a=d&i=Jg9xfs2kri
RBS50Y: http://files.netgear-support.com/go/?a=d&i=JxhCEo1rKs
RBR40: http://files.netgear-support.com/go/?a=d&i=1GqEhkEeaF
RBS40: http://files.netgear-support.com/go/?a=d&i=AyNEy82lhr
RBW30: http://files.netgear-support.com/go/?a=d&i=M0EJpwSELc
RBR20: http://files.netgear-support.com/go/?a=d&i=M6y5Hy6Pr4
RBS20: http://files.netgear-support.com/go/?a=d&i=yd3T26C5Bd
Use this work-around release only if you are having issues with Apple HomeKit connectivity.
Procedure: https://kb.netgear.com/31573/How-do-I-manually-upgrade-firmware-on-my-Orbi-Satellite
Update 5/9/18: Updated with other Orbi Models
Update 2 on 5/9/18: updated the links for RBR40, RBS40 & RBS50Y
Orbi Product Management
113 Replies
Replies have been turned off for this discussion
I have been having this SERIOUS problem with many of my homekit products displaying "no response". I updated to the newest version 2.1.4.14 which was suppose to fix this. It DID NOT fix it for me. Still...most of my homekit devices are still showing "no response". Why is this still happening? Is there some special thing I need to do...to get this new version to work with homekit? The devices work fine in their respective apps but in homekit, they show "no response". PLEASE HELP!
My previous post stated that the upgrade to 2.1.4.14 did not work for me(I was still having "no response" in my homekit app to many of my items after this update). I had to delete all accessories in the homekit app and have re-added them back into homekit. (A REAL pain because I have 30+ accessories). But now, it does appear that homekit is working correctly and connects to all accessories as it is suppose to with this new 2.1.4.14 update. At least it is working OK for the last hour. Lets hope this lasts.
Ken
Using my Mac osx 10.13.4 downloaded the link for the RBR50 which is a dmg file. The downloaded file says 31.MB and your server says 29 MB. After download, my Mac can't open it, it says invalid image. Did it like 10 times and same result.
Delete the old downloads and try again. I have same OS as you and no issue. File is .img when I just checked. Yes, Finder will say 31.1MB, difference in disk access standards.
Sorry, just realized what you're doing. You shouldn't opening the file in your Mac, you should usually Manual Update option in Orbi itself. I posted the steps earlier in this thread.
Just download the img file(s) to your Mac, login to your Orbi, Advanced, Administration, Firmware Update, Manual. Do the sat first, when it’s rebooting do the router.
I've brought this up in previous threads but my only issue I am having is that my rainmachine (and maybe other devices?) seem to lose connection randomly and then don't pick the connection back up from the orbi when this happens. I never had this issue with my Asus N66U router so I'm pretty sure this is an Orbi specific bug much like this Homekit issue. Who knows maybe the homekit fix would fix this issue? When this issue happens my log is full of DHCP requests from my RainMachine MAC address. The other device that was doing this in this log was a Roomba which is also 2.4GHz only. So that's why I say maybe this issue affects more than one device. I would appreciate if someone from Netgear would reach out to help make sure this issue gets fixed in a future firmware release.
I have tried manually assigning a 2.4GHz channel, tried a clean factory restart, etc. I have ethernet backhaul and its worked fine for me without issue.
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 02:07:08
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:59:02
[DHCP IP: 192.168.1.10] to MAC address e0:b9:4d:40:97:04, Friday, May 11, 2018 00:59:02
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:32:51
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:32:47
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:27:18
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:27:14
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:24:54
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:24:49
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:24:45
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:21:36
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:18:24
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:18:20
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:41
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:28
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:24
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:21
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:17
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:13
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:08
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:06
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:03:46
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:01:33
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:01:29
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:52:18
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:50:35
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:46:46
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:30:13
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:27:57
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:27:53
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:00:01
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 22:59:59
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 22:55:15
[DHCP IP: 192.168.1.21] to MAC address 78:24:af:45:30:da, Thursday, May 10, 2018 22:55:12
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 22:46:37
[DoS Attack: TCP/UDP Chargen] from source: 184.105.139.93, port 29977, Thursday, May 10, 2018 22:46:34
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:33:01
[DoS Attack: RST Scan] from source: 66.85.80.245, port 1414, Thursday, May 10, 2018 21:32:58
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:26:33
[DHCP IP: 192.168.1.22] to MAC address 00:05:cd:28:48:4e, Thursday, May 10, 2018 21:26:31
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:21:47
[DoS Attack: RST Scan] from source: 74.91.117.227, port 443, Thursday, May 10, 2018 21:21:46
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:01:17
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:01:14
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:01:12
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:43:03
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:43:01
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:42:42
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:42:41
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:42:24
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:42:21
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:42:02
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:42:01
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:41:43
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:41:41
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:41:24
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:41:21
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:41:03
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:41:01
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:40:42
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:40:41
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:40:23
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:40:21
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:40:02
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:40:01
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:39:44
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:39:41
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:39:22
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:39:21
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:39:04
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:39:01
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:38:42
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:38:41
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:38:24
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:38:21
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:38:02
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:38:01
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:37:44
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:37:41
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:37:22
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:37:21
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:37:04
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:37:01
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:36:42
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:36:41
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:36:24
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:36:21
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:36:02
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:36:01
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:35:44
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:35:41
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:35:23
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:35:21
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:35:04
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:35:01
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:34:42
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:34:41
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:34:24
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:34:21
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:34:03
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:34:01
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:33:44
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:33:41
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:33:22
[DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:33:21
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:33:03
My upgrade finaly worked after deleting the download files and trying again. So far it shows to be more stable in Homekit.
I have only had an ORBI for a month now, I have to say overall I am very happy with it. I am dismayed at the level of negativity here, first of all the verison of firmware is obviously not a full release so those complainng about auto update your device will not auto update to this verison. I understand people want the option to disable auto update, and I am quite sure Netgear has heard you on that. I am not trying to be a troller or personally attack anyone but the level of whinning and complaing does no one any good for many reasons.
With that said I came over from a LINKSYS device their top end model to be exact (EA9500), and it has many bugs and we get about one Firmware update a year on it and it was terrible. I for one am thankful Netgear updates so awesome because that means they are fixing problems and making the product better in a reasonable time frame. Yes there are problems and isuses, and this is the place to post them allowing Netgear to know about them makes sure they can get addressed quickly which it seems they are doing.
I Also think it is great they are giving people here and oppurtunity do download the beta builds, if you don't want to, don't downlaod it as simple as that, they place them here in the forum because you will NOT GET AN AUTO UPDATE to these builds until they are in full release.
So again all these updates and beta firmwares are a good thing making this product better, so please try to give constructive feedback, and stop the non-constructive whinning.
Also I FOUND A FIX for some of my devices geting stuck on 2.4 GHZ wireless I had 2 devices doing this a new iPad Pro and soemtimes my Samsung phone. I only have one legacy 2.4 GHZ device a nest thermostat, so I realized that these devices that were switching to the 2.4 GHZ band were doing so becuase they were seeing a higher recieved signal level, all I did is change the power level on the 2.4 GHZ band down to 50% the thermostat still connects fine and all the other devices stopped getting stuck there and are now switching to the 5 GHZ band with no issues, I left the 5 GHZ at 100% power.
This actually makes sense becuas the 2.4 GHZ band will normally travel further than the 5 GHZ, so by cutting the power level down to 50% it makes it just a little bit weaker so devices see it but stil connect to the stronger 5 GHZ band now.
I don't even think it is a Netgear issue as I have 2 iPad Pros, a 2017 model and a 2016 model the 2016 model had not had this issue at all the 2017 did have it all the time until I turned the power down to 50%, this tells me it is something specfic to some Apple models or other wireless devices but not all.
Anyway I hope you find my comments helpful, and I hope to see more bug fixes and more firmware updates being posted in this forum by Netgear, as this means more bug fixes faster, not like Linksys realising one update a year. : )
Everyone thinks the grass is greener on the other hill but when they get over there they realize how good they had it, waiting a year for bug fixes or any word from Linksys was horrible, thank you Netgear!
I basically agree with your comment. When things go wrong it can be horribly frustrating and that has a tendency to manifest itself in some pretty pointed and nasty posts. I’ve been lucky that other than some HomeKit problems i’ve had a very good experience with Orbi. And HomeKit now seems absolutely fine. My good experience certainly doesn’t negate the fact that many people have had problems, but I too would urge some balance in tone and a recognition that the fixes are coming relatively quickly in consumer electronics terms.
I was one of the beta testers for RBR50-V2.1.4.10-0430-dbg and things appeared to stabilize HomeKit.
However, now I'm having new issues with devices appearing to be connected to WiFi, but losing their internet connections. iPhones, iPads, AppleTV, PC laptops - all are intermittently losing their internet connections. DirecTV Now streaming keeps dropping out with 'lost internet connection' then resuming after 30-40 seconds.
I had hoped that applying the new hotfix firmware V2.1.4.14 would help - it did not.
This is absolute nonsense. I want to downgrade to RBR50-V2.0.1.4, the last version that didn't have any of these issues for me and I can't even do that because of autoupdates.I'm close to tossing this system out the window and going with a different OEM.
Update: I think I was finally able to disable autoupdates.
I followed these instructions: https://community.netgear.com/t5/Orbi/Firmware-V1-12-0-18-Discussion/m-p/1323973/highlight/true#M10304
But with one additional setting:
orbi_auto_upgrade=0
auto_check_for_upgrade=0
auto_update=0orbi_auto_upg=0
Setting all 4 of those to 0, I was able to downgrade to 2.0.1.4. And while the latest publicly available FW 2.1.4.10 shows as *available*, it is NOT autoupdating this time.
With that successful downgrade, I'm now 100% stable again. No HomeKit issues, no dropped Wifi internet connections.
Get your sh*t together, Netgear.
I’m still using the beta V2.1.4.10-0430-dbg which seems perfect. I seem to have a stable HomeKit Lifx environment, with no issues I can see. I was a beta tester so I have had this dbg version in place for around two weeks now. I am happy with it, so I won’t be upgrading from it any time soon.
By the way I have had my Orbi RBK50 system for about two months now, and it has never auto updated. There was some scuttlebut I read early in my time with Orbi that said if you do a manual FW upgrade the auto feature is disabled. I can’t prove that, so I don’t want to create false news if it’s not true, but it works for me. I also carried out the Telnet fix so I seem to be quarantined from auto updates for now
I keep reading that people have FW V2.1.4.14. Where did that come from? I can’t find where it can be downloaded.
This beta release firmware has fixed all my HomeKit issues
I have had no disconnect issues...however I did have my internet drop out from Comcast twice (Comcast's fault) but what I have noticed is that the Orbi doesn't recover well from this with this firmware. The internet seems to still work...but it is very slow (20mbps) or so. I have to disconnect the router and satellite and reconnect the router. Then I have to resync the satellite or it will still be a slow connection. This is using ethernet backhaul.
My only other issue is I am still having the wake on lan occurring with my Denon receiver. I installed wireshark but I really don't know how to filter down to what I want to see. I saw a number of broadcast "who is" type messages but am not sure if this is causing my issues.
Excellent job Netgear, HomeKit devices are fully responsive again!
All links in the first thread are dead.
Could be that the bug affects something else protocols? Do we have more details about it? I've a SIP network and the client is not able to prefetch the video or send special commands, if it's connected though Orbi. If I use another Wi-Fi AP everything works great.
At first, the updated firmware's had fixed my issue. Now I am running into another issue that I feel may be related. My HomeKit set up works fine for me, but my shared access to my significant other cannot keep a connection. We are using a HomePod as the hub and it disconnects for her after a few minutes. We are on the same wifi network, strong connection, tried resetting homepod, tried removing and readding her again, no luck. Any suggestions?
I am also having major Homekit connection issues. I tried to download this firmware but the link is not working. Can someone please help? I get the error message "Requested File does not exist" and asking for a File code. I am looking for RBR50 and RBS50. Thanks in advance!
I would return it while you can. I have had nothing but problems. Eero is supposed to work great with HomeKit and other Apple gear. I'd suggest that.
The links to the firmware that are down!!
Where else can I download V2.1.4.14 for RBS50?
Thanks
DoubleYouEh wrote:
The links to the firmware that are down!!
Where else can I download V2.1.4.14 for RBS50?
Thanks
Post 89 in this thread.
Post 89 of the current thread, by AC641 who publishes links to his Dropbox account as follows
https://community.netgear.com/t5/Orbi/OrbiOS-2-1-4-Homekit/m-p/1577668#M32227
Try this
I'm not sure what happened to the files on Netgear's servers, but Netgear needs to get their act together soon.
No insult, but I will not be installing router firmware downloaded from a dropbox account. That's how you end up on a bot-net.
