I have two MikroTik WLAN-Bridge SXTsq5nd Lite5.
I was able to upgrade one device with the firmware. I did the same with the second device (several times), but in the end I still can't access it with "localnode.local.mesh:8080".
Here are the steps I took:
Device: SXTsq5nd Lite5
Firmware: aredn-3.23.12.0-ath79-mikrotik-mikrotik_routerboard-sxt-5nd-initramfs-kernel.bin
Rename this to "rb.elf" and upload with "pxesrv.exe".
Then make the update with this file: aredn-3.23.12.0-ath79-mikrotik-mikrotik_routerboard-sxt-5nd-squashfs-sysupgrade.bin
I proceeded exactly according to the instructions from here: https://docs.arednmesh.org/en/latest/_downloads/45c3c92b35d89f810b754d7798a0e940/Mikrotik_First_Install_Checklist.pdf
It seems that the Lite5 did the reboot, but I can't get to it with localnode.
Does anyone have any ideas?
Any help will be greatly appreciated here.
73 de Mac, HB9EMS
Personally I NEVER use "localnode..." to get to any node. If I have not set a node name on a new flash, I will ALWAYS use the IP address to get to the node. To determine the IP address, open a command window (assuming a Windows computer here - linux has an equivalent), and type ipconfig [Return]. That will give something like this:
The Default Gateway address is the node you got an IP address from. Note that the sample above was NOT on an AREDN connected computer - hence the IP range and subnet.
While Jim's suggestion will work, it's an extra step to take. I normally use the localnode.local.mesh when setting up new nodes, or if I don't know what node I'm on (multiple nodes connected situation). I always make sure to specify it as http://localnode.local.mesh, though. The firmware should recognize port 80, which is the standard port for HTTP traffic. I've seen some act finicky on the alternative port of 8080 if it didn't redirect there itself, which, by internet standards, is a non-privledged port, meaning it's intended for user level programs.
BTW Chrissy, I normally go by Jim, not my formal name James.
The access point on the left in the picture works. The green LED next to the person symbol is lit.
What can I do?
73 de HB9EMS
+1 with Chrissy kc8ufv.
Else, if the firmware load seems to fail,
try to ping the device at 192.168.1.1 to see if the .elf (initramfs) or .bin is still loaded.
Else, try to ping the device at 192.168.88.1...the default RouterOS address.
Else, you may have faulty hardware.
73, Chuck