I am about to setup my first AREDN Mikrotik node. I have watched several videos on the install. I downloaded the factory and sysupgrade files. The videos shows the initramfs-kernel file to have an .ELF extension but the newest (3.23.4.0) download has a .BIN extension.
The videos say to rename the file to RB.ELF should I change the .BIN extension to .ELF or should I rename the file to RB.BIN?
TIA
The videos say to rename the file to RB.ELF should I change the .BIN extension to .ELF or should I rename the file to RB.BIN?
TIA
"The videos shows"
What videos? Please post URL to videos.
Or follow:
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#mikrotik-first-install-process
73, Chuck
https://youtu.be/loCU6AkGDMg
I have looked at the document you gave me the link for. And the document says the same thing that the video does.
To rename the initramfs-kernel.ELF file to rb.Elf
The file that is available for download is initramfs-kernel.BIN not .ELF.
My question is how do I rename that file?
Change the extension to .ELF or leave as a .BIN?
Thank you
https://docs.arednmesh.org/en/latest/arednGettingStarted/installing_firmware.html#mikrotik-first-install-process
Aside: That video is 3 years old.
3 years ago the .elf files did not contain 'kernel' in the filename.
The current 'factory' files contain 'initramfs-kernel' in the filename.
The filename and extension need to match the configuration of TinyPXE.
Not exactly the same.
The AREDN DOCS say:
"Rename the initramfs-kernel file to rb.elf".
Note that the current DOCs do not specify the extension.
The filename and extension need to match the configuration of TinyPXE.
I hope this helps,
Chuck
Ed
Jerry
I appreciate any suggestions or advice regarding this. I'm actually trying to get a hAP that was configured for AREDN back into service. I attempted upgrading it to current AREDN firmware and failed somewhere, seemingly bricking it. I was able to recover it to RouterOS using netinstall, but have been totally unable to get it back to AREDN functionality.
I have also tried copying the bin file into the files folder on the hAP, then doing a restore, which also did not work. Just a wild chance try.
Thanks,
Carl, N7KUW
I did change my laptop back to DHCP after uploading the SYSUPGRADE, as the unit should come up with it's own AREDN Mesh IP and dhcp server. Nada.
I would greatly appreciate any suggestions - what am I missing?
Thanks,
Carl, N7KUW
But Success! I finally got the hAP back to life, with the latest AREDN firmware running on it. What an ordeal. The sad part is, I don't really know what I did to make this happen. I tried to again restore it to Mikrotik OS using Netinstall, but it would never connect. After several attempts, I hooked it back up to the 2nd ethernet port and dhcp, and saw that I again had a 192.168.1.x IP address on my laptop. So I opened the address for AREDN and was at the factory level software. Went through the process to upgrade with sysupgrade, and bingo, it worked this time.
So, scratching my head, but happy to finally get here.