Received configuration request from 00:00:00:00:00:00

[maddoglee]

Received configuration request from 00:00:00:00:00:00

[maddoglee]

I busted it open and used the serial port to set the mac address and a bunch of parameters as suggested by this website:

https://community.netgear.com/t5/Orbi-Wi-Fi-5-AC-and-Orbi-with/ORBI-RBR50-firmware-appears-corrupted-after-circuit-breaker-was/m-p/2295279#M138276

and this one

https://community.netgear.com/t5/Orbi-Wi-Fi-5-AC-and-Orbi-with/Is-my-13-month-old-RBR50-bricked/m-p/2011067#M107505

It's all working again. It seems that fixing it using serial comms is the only way if you can't ping the device.
Thanks for spending the time giving me a hand. Hopefully, this thread will point people in the right direction if they run into the same issue.

[jclehner]

The mac address I used with the -m command was randomly generated

-m doesn't make sense with anything but the actual MAC address of the device.

Please try running the following commands, and post their output:

% arp -a
% sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -m <MAC FROM LABEL> -c 'arp -a'
% sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -c 'arp -a'
% arp -a

[maddoglee]

Hi,

Sorry for the late reply, I've been on holiday.
I tried the commands without success. I didn't realise the MAC address was on the label initially, but I had tried it before your reply.
Here is the output.

% arp -a

% sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -m 14:59:C0:4D:C3:27 -c 'arp -a'
Waiting for Ethernet connection (Ctrl-C to skip).
Adding 10.164.183.252 to interface en8.
Advertising NMRP server on en8 ... \
Received configuration request from 00:00:00:00:00:00.
Sending configuration: 10.164.183.253/24.
Received upload request: filename 'firmware'.
Executing 'arp -a' ... 
? (10.164.183.253) at 0:0:0:0:0:0 on en8 permanent [ethernet]
Using remote filename 'firmware'.
Uploading RBR50-V9.2.5.2.34SF-HW.img ... Timeout while waiting for ACK(0)/OACK.

% sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -c 'arp -a'                     
Waiting for Ethernet connection (Ctrl-C to skip).
Adding 10.164.183.252 to interface en8.
Advertising NMRP server on en8 ... -
Received configuration request from 00:00:00:00:00:00.
Sending configuration: 10.164.183.253/24.
Received upload request: filename 'firmware'.
Executing 'arp -a' ... 
? (10.164.183.253) at 0:0:0:0:0:0 on en8 permanent [ethernet]
Using remote filename 'firmware'.
Uploading RBR50-V9.2.5.2.34SF-HW.img ... Timeout while waiting for ACK(0)/OACK.

% arp -a
? (10.0.0.1) at (incomplete) on en8 ifscope [ethernet]
? (10.0.255.255) at ff:ff:ff:ff:ff:ff on en8 ifscope [ethernet]
? (239.255.255.250) at 1:0:5e:7f:ff:fa on en8 ifscope permanent [ethernet]
% 

I've also tried another old Macbook that is running High Sierra and has a built-in ethernet port. I get the same Timeout :( so it doesn't seem to be the USB-C hub or firewall. I've turned off the firewalls on both computers.

[jclehner]

Does the following command work?

% sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -c 'arp -d $IP; arp -s $IP 14:59:C0:4D:C3:27`

[maddoglee]

it didn't work....

% sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -c 'arp -d $IP; arp -s $IP 14:59:C0:4D:C3:27'
Waiting for Ethernet connection (Ctrl-C to skip).
Adding 10.164.183.252 to interface en8.
Advertising NMRP server on en8 ... |
Received configuration request from 00:00:00:00:00:00.
Sending configuration: 10.164.183.253/24.
Received upload request: filename 'firmware'.
Executing 'arp -d $IP; arp -s $IP 14:59:C0:4D:C3:27' ... 
10.164.183.253 (10.164.183.253) deleted
Using remote filename 'firmware'.
Uploading RBR50-V9.2.5.2.34SF-HW.img ... Timeout while waiting for ACK(0)/OACK.
% 

...and just in case I am going crazy with the MAC address.. here's the label.

[jclehner]

Try running the following command, using the nmrpflash version supplied below:

sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -m 14:59:C0:4D:C3:27 -c 'arp -a'

nmrpflash-0.9.22-17-g346ada7-macos.zip

[maddoglee]

Here is the output: The first part is just to show I was running the correct version... The MAC with the arp command looks correct now, but I'm still getting the time out. (The time out happens much quicker)

nmrpflash 0.9.22-17-g346ada7, Copyright (C) 2016-2024 Joseph C. Lehner
nmrpflash is free software, licensed under the GNU GPLv3.
Source code at https://github.com/jclehner/nmrpflash

libpcap version 1.10.1


% sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -m 14:59:C0:4D:C3:27 -c 'arp -a'
Waiting for Ethernet connection (Ctrl-C to skip).
Adding 10.164.183.252 to interface en8.
Advertising NMRP server on en8 ... \
Received configuration request from 00:00:00:00:00:00.
Sending configuration: 10.164.183.253/24.
Received upload request: filename 'firmware'.
Executing 'arp -a' ... 
? (10.164.183.253) at 14:59:c0:4d:c3:27 on en8 permanent [ethernet]
Using remote filename 'firmware'.
Uploading RBR50-V9.2.5.2.34SF-HW.img ... Timeout while waiting for ACK(0)/OACK.

I've also tried the follow commands with the new version without success:

sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -B -m 14:59:C0:4D:C3:27
sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -m 14:59:C0:4D:C3:27 
sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -c 'arp -d $IP; arp -s $IP 14:59:C0:4D:C3:27' 
sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -c 'sudo arp -d $IP; sudo arp -s $IP 14:59:C0:4D:C3:27'
sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -m 14:59:C0:4D:C3:27 -c 'sudo arp -a'
sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img -m 14:59:C0:4D:C3:27 -c 'arp -a'
sudo nmrpflash -i en8 -vv -f RBR50-V9.2.5.2.34SF-HW.img 

I am starting to think that opening the router and trying serial programming is the only option I have left. Let me know if you run out of ideas or don't have time for more help... but I'm happy to keep trying if you want to solve this issue. :)

[jclehner]

You could try using macOS' tftp command for uploading. Note the lack of -f.

sudo nmrpflash -m 14:59:C0:4D:C3:27 -i en8 -vv -c 'echo -e "verbose\nput RBR50-V9.2.5.2.34SF-HW.img" | tftp -e $IP $PORT'

[maddoglee]

Still doesn't work...
here's the output:

Waiting for Ethernet connection (Ctrl-C to skip).
Adding 10.164.183.252 to interface en8.
Advertising NMRP server on en8 ... /
Received configuration request from 00:00:00:00:00:00.
Sending configuration: 10.164.183.253/24.
Received upload request: filename 'firmware'.
Executing 'echo -e "verbose\nput RBR50-V9.2.5.2.34SF-HW.img" | tftp -e $IP $PORT' ... 
?Invalid command
receive_packet: timeout
Try 1, didn't receive answer from remote.
receive_packet: timeout
Try 2, didn't receive answer from remote.
receive_packet: timeout
Try 3, didn't receive answer from remote.

I found that I can't even ping the device:

 % sudo nmrpflash -m 14:59:C0:4D:C3:27 -i en8 -vv -c 'ping $IP'         
Waiting for Ethernet connection (Ctrl-C to skip).
Adding 10.164.183.252 to interface en8.
Advertising NMRP server on en8 ... -
Received configuration request from 00:00:00:00:00:00.
Sending configuration: 10.164.183.253/24.
Received upload request: filename 'firmware'.
Executing 'ping $IP' ... 
PING 10.164.183.253 (10.164.183.253): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6

I think it's bricked.... Thanks for all your help though.

[jclehner]

Thank you for your followup! Since you've got access to the router console, I too have a favor to ask: could you send me a dump of this device's bootloader?

There may be a way to fix this with nmrpflash only, but I'll have to reverse engineer the bootloader for that, and I can't seem to find it anywhere.

[jclehner]

Scratch that, these sources also contain the bootloader's source code.