Keep in mind that Voxel is built mainly against the 2.5 code base as a result of 2.7 not being made available in a timely manner.
Because Voxel includes updated libraries, often more recent than what Netgear ships, the "security vulnerabilities" are address in this custom firmware months ahead...
That is strange, that is inconsistent with the official documentation.
https://kb.netgear.com/000061277/Which-features-are-disabled-on-my-Orbi-router-when-it-is-set-to-AP-Mode
If your Orbi router is in AP mode I'm not sure how you would have the access to enable access control in stock as that is a routing feature. Is it possible that you didn't have it AP mode in stock?
1) From a computer connected to your Orbi network, browse to http://orbilogin.net and log in using your orbi admin id and password.
2) Browse to the Advanced tab then Administration -> Firmware Update
3) Click Manual Update on the right side
4) Update your satellites 1 at a time using the...
Anything is possible, but currently the developer (Voxel) only owns the RBR50/RBS50. The firmware are different for each model so he has no means to test that it actually works.
Installed without issue. Fast as always. Thank You for your continued support.
The last release included QCA drivers/firmware from V2.7.3.22 stock. Should we expect to see any additional integration from that GPL release or is it not worth the effort?
1) When you moved to Voxel did you start fresh or did you import your prior config backup?
2) Can you describe your network configuration? How are your satellites attached to the Orbi router. Are they wired directly to the Lan port? (ie. Orbi Router -> Lan Port -> Orbi Sattelite) or how exactly...
1. No. If you are already running stock 2.7+, you need to revert to stock 2.5 before flashing Voxel or you will soft brick your router and satellite which will need to be TFTP to recover.
You can download 2.5 here:
Router: https://www.downloads.netgear.com/files/GDC/RBK50/RBR50-V2.5.2.4.zip...
That's because you went from the snapshot to the release. From .13 I didn't receive that message. The version check in Netgear's binaries doesn't handle that last decimal point very well in terms of comparison.