Hi
I’ve received today two units of RBLDF-5nD EU version.
I’ve verified that they work with the original Mikrotik firmware and then I went about upgrading them to AREDN 3.19.3
Using the Tiny PXE tool I was able to load the elf file and got to the point where AREDN image was running from RAM.
The issues started when I’ve tried to permanently install the firmware.
After uploading the bin file, I’ve got the infamous Bad Gateway error.
Reading through the forum, I’ve tried to use the sysupgrade command line, however I got an error saying that the model isn’t supported.
I’ve also tried to force the sysupgrade with the -F switch but this resulted in a “bricked” router.
It appears that the model isn’t known to the firmware - on the web interface it showed as Mikrotik(Unknown).
Please advise
73 de Yoram 4Z5YR
I’ve received today two units of RBLDF-5nD EU version.
I’ve verified that they work with the original Mikrotik firmware and then I went about upgrading them to AREDN 3.19.3
Using the Tiny PXE tool I was able to load the elf file and got to the point where AREDN image was running from RAM.
The issues started when I’ve tried to permanently install the firmware.
After uploading the bin file, I’ve got the infamous Bad Gateway error.
Reading through the forum, I’ve tried to use the sysupgrade command line, however I got an error saying that the model isn’t supported.
I’ve also tried to force the sysupgrade with the -F switch but this resulted in a “bricked” router.
It appears that the model isn’t known to the firmware - on the web interface it showed as Mikrotik(Unknown).
Please advise
73 de Yoram 4Z5YR
When the device has been booted in RAM with the .elf file. Go to the Administration page and click on the "download support data" link at the bottom, then attach back here. This would give the data to see what is going on. Potentially a new board revision?
You can still boot with the .elf? It's only bricked in the sense that it is not booting to a usable device right now?
Joe AE6XE
I've restored the device to its original state using Mikrotik tools.
Yoram 4Z5YR
Yoram, Try these images. There is a new and different model string in this device. Need to use both the .elf and .bin.
https://drive.google.com/drive/folders/1qrR8Muj9Gor5gDEY9_R6kAWptKZq968q?usp=sharing
Assuming the firmware is flashed, send a support data download so I can confirm if any other issue. You may have to use the command line to do the sysupgrade and not the UI. We are pushing the limits of RAM usage to load the Nightly build on Mikrotik devices. It's possible, a special 3.19.3.0+ .elf image needs to be created to add this new device definition and get the nightly build loaded. There may not be enough RAM to get these test images loaded...
Joe AE6XE
It is working perfectly!
Bad Gateway error went away and firmware installation went smoothly.
I didn't have to resort to command line sysupgrade method.
I'll upgrade the second node and will attempt to establish node to node link.
Attached is the support data file
All the best and 73
Yoram 4Z5YR
Joe AE6XE