NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
I've had better luck using nmrpflash when flashing satellites. I'd give that a shot
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?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.
I wanna say that someone post that nmrpflash helps with the timing or help the user in getting to the point in where the user doesn't have to figure that out...I haven't used it yet. Might be something to check out though.
https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP
Need to press the reset button for 30 seconds then release, then it send to PUT the command and upload the FW.
Make sure you enable tftp: https://www.thewindowsclub.com/enable-tftp-windows-10Video walk through using a tftp client. Use the built in one for windows 10 though. the video is more of an example of how its done:
https://www.youtube.com/watch?v=R9DLrLQrpaw
I had a problem on a Windows 10 PC where this didn't work to use TFTP, so I switched to a Windows 7 PC and the TFTP worked.
Mac TFTP: https://www.petenetlive.com/KB/Article/0001247
screwgauge wrote:
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]Maybe I'm reading this incorrectly. Flashing firmware is sort of a chore because the device and TFTP machine have to be disconnected from everything else, the computer has to be changed to a static IP, etc. Afterwards, it all has to be put back the way it was before.
If the satellite is at 192.168.1.250 (this is before it loads the firmware image and changes to the IP address that it has been assigned, usually using DHCP to learn what that IP address is), what is the point of sending packets from 192.168.2.2 to 192.168.2.1 ?
was wondering about the 2.1 address as well. Doesn't really follow the guide
