Recent content by Tonot1

Perhaps a small summary for those who aren't yet upo to speed about the details for converting RBR50's to RBS50's. Netgear started out with the RBR50 a long while ago, then came with the RB50V2..... Why? The original RBR50 (also called the RBR50V1) was quite easily converted to an RBS50...

I've done some more testing.... Updates via GUI will ONLY be accepted when the firmware is actually for an RBS50... Hacked RBS50 firmware is always identified as an RBR50 (done deliberately), so ti will NOT pass the firmware check. This applies to both Netgear as Voxel firmware..... Sorry, once...

When doing my initial "testing and delivery of the hackedf firmware", I just used the new firmware-versions and updated them by GUI, BUT the device was still a ROUTER (not hacked)... Okay, did some limited checking... The impression I'm getting from these limited tests is that the "hacked...

No problem,I renamed the file to *.img; it's on github .Note that this is the same file, just with another name (you can rename it yourself, or download the renamed one). Sorry, I've been doing the updates most of the time with tftp, not through the GUI; otherwise I would have noticed this myself.

No, you're not stupid... Unless the GUI checks the extension, it should work.

You're welcome! Please report the result when done, so that others are informed.

Latest firmware can be found on Github: https://github.com/Ton-O/RBR50V2_TO_RBS50/releases Just click on the version you need below: - V2.7.5.6 for Netgear's firmware - V9.2.5.2.39SF-HW for Voxel's firmware. Then download the associated asset (IMG-file) that shows up. As mentioned many times in...

Nope! I'm still interested in running RBR50V2's as satellites and noticed latest versions haven't been provided, so I started to redo the previous workflow. Since I ran into some issues, I contacted schmellic who rapidly responded with tips. He went on to a different mesh-system, so he's not...