NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

screwgauge's avatar
screwgauge
Aspirant
Dec 01, 2022

Reliable way to put an Orbi Satellite (RBS50) in TFTP Server mode where I can push firmware

Hello,

Can someone please describe reliable and repeatable steps to put an Orbi Satellite (RBS50) into a mode where I can tftp put the firmware image to it.

I can get it to a state where it has IP address of 192.168.1.250, but tcpdump at that point shows port 69 is not reachable so a TFTP to it from my Mac fails.

From threads on the internet it seems the power LED should be blinking green when the Satellite is ready to receive firmware, but not amount of pressing, holding the reset button and powering off/on can put my satellite into that state.

When I can ping it at 192.168.1.250, a http access to it always shows 500, internal server error.

Would appreciate any help.

Thanks!

9 Replies

Sort By
    • screwgauge's avatar
      screwgauge
      Aspirant
      Dec 01, 2022

      No luck. nmrpflash also relies on TFTP but its unable to send the firmware to the device. I see this in tcpdump

      00:13:07.177431 IP 192.168.2.2.62444 > 192.168.2.1.tftp: 30 WRQ "firmwareoctetblksize1456" [|tftp]
      00:13:09.178786 IP 192.168.2.2.62444 > 192.168.2.1.tftp: 30 WRQ "firmwareoctetblksize1456" [|tftp]
      00:13:11.180535 IP 192.168.2.2.62444 > 192.168.2.1.tftp: 30 WRQ "firmwareoctetblksize1456" [|tftp]
      00:13:13.185118 IP 192.168.2.2.62444 > 192.168.2.1.tftp: 30 WRQ "firmwareoctetblksize1456" [|tftp]
      00:13:15.187482 IP 192.168.2.2.62444 > 192.168.2.1.tftp: 30 WRQ "firmwareoctetblksize1456" [|tftp]
      00:13:17.189839 IP 192.168.2.2.62444 > 192.168.2.1.tftp: 30 WRQ "firmwareoctetblksize1456" [|tftp]

      I need a brute force way to get the Orbi Satellite to get into TFTP server mode. Or is there an alternate way where it can act as a TFTP client and download firmware?

      • CrimpOn's avatar
        CrimpOn
        Guru
        Dec 01, 2022

        My limited experience with TFTP was frustrating because "timing is everything".  I once attempted to load firmware on an Orbi (I believe a router) with TFTP and failed five times in a row*.  Was taking aim at the trash can and thought, "what do I have to lose by  trying a few more times?"  Attempt six worked!

         

        My conclusion is that every time an Orbi powers up, there is a brief window of time when it looks for a TFTP connection.  Too soon and the Orbi isn't ready yet.  Too late, and it has already moved on to loading the previous firmware image.

         

        So, I do not believe there is anything that needs to be done.  I think Orbi's go through this process every time they power on.

         

        *part of this was me being spastic.  The TFTP software I was using seemed to forget which file was to be transferred so when I went to click on Send, there was no file and by the time I browsed to the file, the window had closed.

         

        p.s. Thanks for the hint to capture the network traffic (I use Wireshark) during a TFTP session to watch what happens.