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

  • 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.

Voxel

Part of the Furniture
Continuation of

https://www.snbforums.com/threads/custom-firmware-build-for-orbi-rbk50-v-2-5-0-42sf-hw.60308/
. . .
https://www.snbforums.com/threads/c...50-rbk53-rbr50-rbs50-v-9-2-5-2-11sf-hw.71395/
https://www.snbforums.com/threads/c...50-rbk53-rbr50-rbs50-v-9-2-5-2-12sf-hw.72157/

New version of my custom firmware build: 9.2.5.2.13SF-HW.

Changes (vs 9.2.5.2.12SF-HW):

1. Toolchain: GCC is upgraded 9.3.0->9.4.0.
2. Toolchain: Go is upgraded 1.16.3->1.16.5.
3. wireguard package is upgraded 1.0.20210424->1.0.20210606.
4. curl package is upgraded 7.76.1->7.77.0 (fixing CVE-2021-22897, CVE-2021-22898, CVE-2021-22901).
5. expat package is upgraded 2.2.10->2.4.1 (fixing CVE-2013-0340).
6. ethtool package is upgraded 5.10->5.12.
7. util-linux package is upgraded 2.36.2->2.37.
8. iperf3 package is upgraded 3.9->3.10.1.
9. nano package is upgraded 5.6.1->5.8.
10. Slight optimization of some components.

The link is:

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

Voxel.
 

vansmak

New Around Here
Continuation of

https://www.snbforums.com/threads/custom-firmware-build-for-orbi-rbk50-v-2-5-0-42sf-hw.60308/
. . .
https://www.snbforums.com/threads/c...50-rbk53-rbr50-rbs50-v-9-2-5-2-11sf-hw.71395/
https://www.snbforums.com/threads/c...50-rbk53-rbr50-rbs50-v-9-2-5-2-12sf-hw.72157/

New version of my custom firmware build: 9.2.5.2.13SF-HW.

Changes (vs 9.2.5.2.12SF-HW):

1. Toolchain: GCC is upgraded 9.3.0->9.4.0.
2. Toolchain: Go is upgraded 1.16.3->1.16.5.
3. wireguard package is upgraded 1.0.20210424->1.0.20210606.
4. curl package is upgraded 7.76.1->7.77.0 (fixing CVE-2021-22897, CVE-2021-22898, CVE-2021-22901).
5. expat package is upgraded 2.2.10->2.4.1 (fixing CVE-2013-0340).
6. ethtool package is upgraded 5.10->5.12.
7. util-linux package is upgraded 2.36.2->2.37.
8. iperf3 package is upgraded 3.9->3.10.1.
9. nano package is upgraded 5.6.1->5.8.
10. Slight optimization of some components.

The link is:

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

Voxel.
I run Wireguard as a homeassistant addon on a raspberry. Is there any advantage to running it on the orbi other than one less point of fail?
 
Last edited:

Voxel

Part of the Furniture
I run Wireguard as a homeassistant addon on a raspberry. Is there any advantage to running it on the orbi other than one less point of fail?
If you wish to use VPN (WireGuard) for all your devices in your LAN then it has sense to use Orbi. I.e. single VPN config from VPN provider for all your LAN.

Voxel.
 

Skippy Bosco

Regular Contributor
A couple of suggestions to consider for enhancements to the firmware while we're waiting for the newer updates to be released by Netgear to the open source.

1) A thin version of the firmware that has any non critical resources disabled and/or removed. Essentially just the core services for common function, but all secondary resources removed.

2) A consideration of updating the update check to poll for Voxel firmware update.
 

Voxel

Part of the Furniture
1) A thin version of the firmware that has any non critical resources disabled and/or removed. Essentially just the core services for common function, but all secondary resources removed.

2) A consideration of updating the update check to poll for Voxel firmware update.
Well, let us see:

1) Thin version. Is not it enough just to disable practically all NG's 'cookies' such as Armor, Disney Circle, not workable ReadyCloud, my own SMB, etc? I have all above disabled and CPU of my ORBI is practically idle. 'How-to' is in my QuickStart.txt.

I think that there could be something e.g. like single option in NVRAM to disable all these 'cookies'. Just to understand your wishes. All of these settings are kept in your backed up config, so no any needs to repeat any manipulations after flasing the new version. And even more: if you flash the stock: it is OK also with this config.

We are doing the 'perfection' together. I read your feedback. Just to understand and clarify.

2) Problematic, sorry. Checking new fw is hardcoded in the original binary from NG firmware. They refer to NG site. Either I have to hack it (legality?) or... No source codes unfortunately.

Voxel.
 

Skippy Bosco

Regular Contributor
Well, let us see:

1) Thin version. Is not it enough just to disable practically all NG's 'cookies' such as Armor, Disney Circle, not workable ReadyCloud, my own SMB, etc? I have all above disabled and CPU of my ORBI is practically idle. 'How-to' is in my QuickStart.txt.

I think that there could be something e.g. like single option in NVRAM to disable all these 'cookies'. Just to understand your wishes. All of these settings are kept in your backed up config, so no any needs to repeat any manipulations after flasing the new version. And even more: if you flash the stock: it is OK also with this config.

We are doing the 'perfection' together. I read your feedback. Just to understand and clarify.

I was thinking more along the lines of the active processes that are not needed as part of core function but still run today.

For example: button detect, circled, upagent, bonjour, print, etc.

Even with Circle disabled, the process is active and killing it spawns a new pid.

as well as disabling debugging & logging parameters from the running processes.

I can use this to disable some, but others like button detect and disabling debugging and logging are not as evident.

Code:
nvram set noarmor=1
nvram set nocircle=1
nvram set nocloud=1
nvram set samba_disable=1
nvram commmit
reboot


2) Problematic, sorry. Checking new fw is hardcoded in the original binary from NG firmware. They refer to NG site. Either I have to hack it (legality?) or... No source codes unfortunately.

If not checking against Voxel (by adjusting the IP via a local host to change the destination it pings, perhaps just black holing the various call backs to Netgear as that is often a complaint from users wishing to disable calling home pings that they view in their network monitoring.
 

theoak

Regular Contributor
One person's "thin" is another "Why in the **ll did you remove that!!!"

It is a bit of a slippery slope.

I think Voxel has the right approach essentially just updating the binaries as new versions are released. If folks want to hack, slice and dice, they can do the same as he does.
 

Skippy Bosco

Regular Contributor
One person's "thin" is another "Why in the **ll did you remove that!!!"

It is a bit of a slippery slope.

I think Voxel has the right approach essentially just updating the binaries as new versions are released. If folks want to hack, slice and dice, they can do the same as he does.

The intent would be either an addition to the quickstart or a delta that allows for both. The standard that exists today, and an offering for those that have simple needs and want to maximize performance and stability over functionality. The recent issues with Traffic Meter is a great example where additional functionality that many don't even think about can cause significant instability.
 
Last edited:

mmacgilli1

New Around Here
Continuation of

https://www.snbforums.com/threads/custom-firmware-build-for-orbi-rbk50-v-2-5-0-42sf-hw.60308/
. . .
https://www.snbforums.com/threads/c...50-rbk53-rbr50-rbs50-v-9-2-5-2-11sf-hw.71395/
https://www.snbforums.com/threads/c...50-rbk53-rbr50-rbs50-v-9-2-5-2-12sf-hw.72157/

New version of my custom firmware build: 9.2.5.2.13SF-HW.

Changes (vs 9.2.5.2.12SF-HW):

1. Toolchain: GCC is upgraded 9.3.0->9.4.0.
2. Toolchain: Go is upgraded 1.16.3->1.16.5.
3. wireguard package is upgraded 1.0.20210424->1.0.20210606.
4. curl package is upgraded 7.76.1->7.77.0 (fixing CVE-2021-22897, CVE-2021-22898, CVE-2021-22901).
5. expat package is upgraded 2.2.10->2.4.1 (fixing CVE-2013-0340).
6. ethtool package is upgraded 5.10->5.12.
7. util-linux package is upgraded 2.36.2->2.37.
8. iperf3 package is upgraded 3.9->3.10.1.
9. nano package is upgraded 5.6.1->5.8.
10. Slight optimization of some components.

The link is:

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

Voxel.

Thanks @Voxel for your work. All smooth 1 day in. Been benefiting from your work for over a year and always a reliable, smooth experience. (Have even bought you a few beers over the past year via paypal! Keep it going.)
 

mith_y2k

Regular Contributor
I recently noticed this issue. It first appeared on an older version of Voxel, so when this version came out I upgraded and restarted thinking that it would solve the issue. Any idea?

Code:
[email protected]:/tmp/mnt/sda1# which grep
/opt/bin/grep
[email protected]:/tmp/mnt/sda1# grep
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
 

Voxel

Part of the Furniture
I recently noticed this issue. It first appeared on an older version of Voxel, so when this version came out I upgraded and restarted thinking that it would solve the issue. Any idea?

Code:
[email protected]:/tmp/mnt/sda1# which grep
/opt/bin/grep
[email protected]:/tmp/mnt/sda1# grep
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
It is not related to firmware, but to your Entware installation. Because of '/opt/bin/grep'.

Check that '/opt/lib/libc.so.6' exists on your USB drive. Maybe you should re-install Entware (e.g. something wrong with USB partition).

1624688199697.png

Voxel.
 

markyrules

New Around Here
Hi I've really been struggling with my orbi rbr50 and am not familiar with Linux either, however I've invested in a rbk50 set last year and cant afford a new system. I'm using a set of rbk50 v2 and i'm having some issues with my devices, the router is about 12 feet away behind a door, however i am losing connection on any device i have, phone or laptop. The wifi signal remains connected however pages are not loading.

Here is my network structure: Modem -> R8000 as dhcp + main router -> rbr50 on 2nd Floor -> wired to rbs50 on 3rd floor and mesh to rbs50 on 1st floor, main router is in the basement. I am getting very low signals from the 5ghz band on my router, which is 12 feet away from my room, however this is a new set which i RMAed a couple of weeks back.

Here are some settings i've set on the orbi web gui
disabled 20/40 MHz Coexistence
2.4ghz 50% txpower
enabled beamforming
enabled mu-mimo

R8000 is the main dhcp distributor, orbi is set in AP mode.

I am at a lost and would definitely be interested to debug this with some of you here on this forum
 
Last edited:

Sign Up For SNBForums Daily Digest

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