What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

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

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-36sf-hw.91732/
https://www.snbforums.com/threads/c...50-rbk53-rbr50-rbs50-v-9-2-5-2-37sf-hw.93104/

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

Changes (vs 9.2.5.2.37SF-HW):

1. Toolchain: binutils is upgraded 2.43.1->2.44.
2. Toolchain: Go is upgraded 1.23.3->1.23.6.
3. OpenVPN is upgraded 2.6.12->2.6.13.
4. lighttpd package is upgraded 1.4.76->1.4.77.
5. DNSCrypt Proxy v.2 is upgraded 2.1.5->2.1.7.
6. util-linux package is upgraded 2.40.2->2.40.4.
7. e2fsprogs package is upgraded 1.47.1->1.47.2.
8. curl package is upgraded 8.11.0->8.12.0.
9. bind package is upgraded 9.18.31->9.18.33.
10. proftpd package is upgraded 1.3.8b->1.3.8c.
11. ca-certificates package is upgraded 20240203->20241223.
12. sysstat package is upgraded 12.7.6->12.7.7.
13. pcre2 package is upgraded 10.44->10.45.
14. libtalloc package is upgraded 2.4.2->2.4.3.
15. gettext-full package is upgraded 0.23->0.23.1.
16. iperf3 package is upgraded 3.17.1->3.18.
17. nano package is upgraded 8.2->8.3.
18. Host tools: upgrade mkimage/u-boot to 2025.01.
19. Host tools: upgrade e2fsprogs to 1.47.2.
20. Host tools: upgrade xz to 5.6.4.
21. Host tools: upgrade quilt to 0.68.

The link is:

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

Voxel.
 
Last edited:
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-36sf-hw.91732/
https://www.snbforums.com/threads/c...50-rbk53-rbr50-rbs50-v-9-2-5-2-37sf-hw.93104/

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

Changes (vs 9.2.5.2.37SF-HW):

1. Toolchain: binutils is upgraded 2.43.1->2.44.
2. Toolchain: Go is upgraded 1.23.3->1.23.6.
3. OpenVPN is upgraded 2.6.12->2.6.13.
4. lighttpd package is upgraded 1.4.76->1.4.77.
5. DNSCrypt Proxy v.2 is upgraded 2.1.5->2.1.7.
6. util-linux package is upgraded 2.40.2->2.40.4.
7. e2fsprogs package is upgraded 1.47.1->1.47.2.
8. curl package is upgraded 8.11.0->8.12.0.
9. bind package is upgraded 9.18.31->9.18.33.
10. proftpd package is upgraded 1.3.8b->1.3.8c.
11. ca-certificates package is upgraded 20240203->20241223.
12. sysstat package is upgraded 12.7.6->12.7.7.
13. pcre2 package is upgraded 10.44->10.45.
14. libtalloc package is upgraded 2.4.2->2.4.3.
15. gettext-full package is upgraded 0.23->0.23.1.
16. iperf3 package is upgraded 3.17.1->3.18.
17. nano package is upgraded 8.2->8.3.
18. Host tools: upgrade mkimage/u-boot to 2025.01.
19. Host tools: upgrade e2fsprogs to 1.47.2.
20. Host tools: upgrade xz to 5.6.4.
21. Host tools: upgrade quilt to 0.68.

The link is:

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

Voxel.
Hi
Is anyone having issues loading the latest firmware? Am a loyal follower of this firmware for several years.
Normally, it is straightforward. This time my first satellite ended up on a default IP 192.168.1.250 and currently refuses to work. The second satellite will not upload the new firmware even though it looks to start up loading it - it resolutely stays on the .37 firmware.
Any insight appreciated.

Update - fixed
For me, I had to load the Netgear V2.5.2.4.img image before I loaded the RBR50-V9.2.5.2.38SF-HW.
I am at a loss why that worked and directly trying to update from RBR50-V9.2.5.2.37SF-HW to RBR50-V9.2.5.2.38SF-HW failed.

May be that will help someone else. @Voxel, I would be interested in any insight you may have.
Thanks @Voxel for your continued support.
 
Last edited:
Hey Voxel, first of all thank you for keeping the RBK50s alive, it's great you're doing a much better job than Netgear ever did…

SITUATION:
I am about to switch to a fiber optics connection here in Austria. There is no modem installed and I am inclined to keep it like that and connect the RBR50 directly to the OTP (I see no point in buying a router - an AVN FritzBox! or something similar - because… the RBR50 is a router, isn't it!

The ISP I am inclined to select (there are 22 of them to chose from) is saying that connecting the RBK50 to their OTP should work. They haven't provided detailed instructions yet because I have not yet activated the contract.

QUESTION:
Are there any special hints / instructions to connect the RBR50 with the Voxel firmare (latest issue) to the OTP? On several forums I read from people with the stock firmware who are saying "this was plug&play and super easy" to others who have multiple issues (some did not manage to set this up at all).

Would very much appreciate your take on this and maybe some info about how-to do this.
 
@Voxel - question what is the RBR50 Router trying to access to determine if it is connected to the internet?
I have my RBR50 in AP mode behind the main router. The RBR50 has a purple light on it, but I DO have internet access. The RBR50 status page suggests I don't:
Not-connected.png


I have turned off (filtered) all access to the usual Netgear websites to prevent inadvertent issues with firmware upgrading. Maybe that is the issue? Perhaps the RBR50 is trying to "call home" to Netgear to check the internet? If this is the case, perhaps the firmware could point to some other web url instead of a Netgear one?

Netgear webistes.png


Thanks.
 
I have turned off (filtered) all access to the usual Netgear websites to prevent inadvertent issues with firmware upgrading.

You may have overcomplicated your situation a bit. You don't have to block Netgerar sites. If you are upgrading your RBR/RBS from my firmware to my firmware, there should be no such problems at all. If you had the stock firmware, you should first install the stock firmware V2.5.2.4, then to simplify the procedure disconnect the internet (disconnect the WAN cable from your RBR), and then upgrade to my firmware.

In case of problems with any your RBS, you should use TFTP method:


Here above is a description of how to do it.

It is better to use this method in two steps with your problematic RBS:

(1) First install the stock V2.5.2.4 via TFTP.
(2) Install my version via TFTP immediately afterwards.

Your RBS will be connected at this time only to your computer via ethernet, without Internet access.

Voxel.
 
You may have overcomplicated your situation a bit. You don't have to block Netgerar sites. If you are upgrading your RBR/RBS from my firmware to my firmware, there should be no such problems at all. If you had the stock firmware, you should first install the stock firmware V2.5.2.4, then to simplify the procedure disconnect the internet (disconnect the WAN cable from your RBR), and then upgrade to my firmware.

In case of problems with any your RBS, you should use TFTP method:


Here above is a description of how to do it.

It is better to use this method in two steps with your problematic RBS:

(1) First install the stock V2.5.2.4 via TFTP.
(2) Install my version via TFTP immediately afterwards.

Your RBS will be connected at this time only to your computer via ethernet, without Internet access.

Voxel.
Thanks @Voxel
I understand your points.
Notwithstanding what you say regarding upgrading your firmware to your later firmware, on both my RBS50 satellites, they would not upgrade from .37 to .38 with first going to the Netgear V2.5.2.4. On other releases I have not had such an issue.
 
Thanks @Voxel
I understand your points.
Notwithstanding what you say regarding upgrading your firmware to your later firmware, on both my RBS50 satellites, they would not upgrade from .37 to .38 with first going to the Netgear V2.5.2.4. On other releases I have not had such an issue.
I'm sorry, I can't tell you what happened in your particular case. Nothing special about the .38 version.

I update firmware very often, more often than other users since I use intermediate betas, and I haven't encountered this.

Try the TFTP method though. Sometimes inexplicable things happen.

Voxel.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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