I saw that new Voxel firmware was posted today so started to upgrade my RBR50 and 2x RBS50s. I have made a mistake though through trying to load the RBR firmware to a satellite. The satellite did reject the wrong firmware bu then allowed me to select the correct one, however it has come back online with the wrong IP address. It is now set to 198.168.1.250 and this shows on the RBR50 summary page as connected with a good connection. The Router and Satelites were however all set on fixed IP addresses of 192.168.178.201-203.
So what to do. I have the factory Netgear firmware V2.5.2.4 as I thought I could load this and recover the situation. However, I think I read I can't just do a reset of the satellite as it will brick it if on Voxel firmware. Even though the RBR is telling me the IP of the faulty satellite, I can just seem to connect to it by choosing a manual IP address in the same range on my pc.
Can anyone offer some guidance on how to recover this situation please?
Solved:
What I did:
TFTP into the RBS50 using the instructions
here and loaded Netgear V2.5.2.4 firmware. Note I found I needed to do this by enabling the TFTP client on Windows. In order to be able to load the firmware you need to do this:
My RBS50 kept updating to V2.7.3.22 Netgear firmware once I plugged it in to my network. I tried to update from V2.7.3.22 to Voxel firmware but it wouldn't work for me - which is also what Voxel says in his readme. I blocked access to the following update related sites using the firewall on my router which then stopped the auto update happening. In between I had to
Refer to this for further information:
Disable auto update
Once the RBS50 was back on my network I then updated the firmware again from V2.5.2.4 to the new Voxel firmware from the Orbi WebGui as usual.
All-in-all a very long-winded exercise.