Voxel Custom firmware build for Orbi RBK50/RBK53 (RBR50, RBS50) v.

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.


Part of the Furniture
Continuation of

. . .

New version of my custom firmware build:

Changes (vs

1. Toolchain: Go is upgraded 1.16.6->1.17.
2. OpenSSL v. 1.1.1 package is upgraded 1.1.1k->1.1.1l (fixing CVE-2021-3711, CVE-2021-3712).
Base Scores (SUSE): 9.8 and 5.3.​
3. DNSCrypt Proxy v.2 is upgraded 2.0.45->2.1.0.
re: what to change in your config​
4. ipset package is upgraded 7.14->7.15.
5. procps-ng package is upgraded 3.3.16->3.3.17.
6. elfutils package is upgraded 0.180->0.182.
7. pcre package is upgraded 8.44->8.45.
8. libpcap package is upgraded 1.10.0->1.10.1.
9. util-linux package is upgraded 2.37.1->2.37.2.
10. unbound package (used in stubby) is upgraded 1.13.1->1.13.2.
11. e2fsprogs package is upgraded 1.46.3->1.46.4.
12. OpenVPN client init script: fix bash style comparison '==' -> '='.
13. Fix ez-ipupdate compilation (synchronize with LBR20).
14. Syncronize dropbear init script with LBR20 (net-wall call).
15. Change 'net-util' to avoid TrendMicro cron update schedule (R8900/R9000 specific).
16. Host tools (e2fsprogs): is upgraded to 1.46.4.

The link is:

https://www.voxel-firmware.com (thanks to vladlenas for his help with hosting).


Skippy Bosco

Regular Contributor
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?


New Around Here
Hi @Voxel, I followed your downgrade instructions to flash your FW into RBK50 but the stock 2.7 FW is auto-updating it (for satellites and the router) after the downgrade to 2.5. The solution for me was very simple: Just disconnect the RBK50 router from the internet (from the ISP modem), that way the auto-update won't manage to contact netgear's servers and will keep the downgraded 2.5. I then flashed voxel FW and reconnected the internet.
My suggestion is to put this info in the quickstart guide, because I've seen someone that tried to flash Voxel after the RB50 auto-updated and it obviously soft-bricked the satellites.


New Around Here
Thanks for all of your work on this. I'd like to try downgrading to the previous Voxel version on my router – is there anything special I need to do, or can I just install via the web UI as normal?

context: I've used this firmware for quite some time on my RBK50 which has two RBS40 satellites (that were converted from RBK40). Everything has been working great for months until I upgraded to this new version. Now both of my satellites shows as "Config sync" and no amount of resetting and fiddling has fixed it.

Oddly, even with the Config Sync status wireless clients connected to the satellite and network successfully, so I'm not quite clear on what exactly is happening with the status vs. actual connectivity.


New Around Here
I acquired a pair of RBS40's with two cans of beer and I'm planning to extend the current RBK50 set of 4 at summer cottage with those.

As the environment consist of multiple buildings with some distance in between and rf blocking elements the placement of devices is important for optimal coverage.

There will likely be couple of daisy chained access points. Should I use 50's for those or will it make a difference?

And is my understanding correct that there is no Voxel image for RBS40 but they should function fine as satellites. What fw version should be used with those?

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!