The ARDEN procedure to new install on a Mikrotik LHG5AC XL with v6.48.6 firmware requires downgrading to v4.45.8. The linked OpenWRT downgrade procedure states that OpenWRT newer than v6.46 must be downgraded to v4.45.8. The procedure provided does not work because on reboot the log file states that v6.45.8 cannot be installed because it is newer than the "factory version of v6.48.6". I upgraded to v6.48.7 to verify the procedure works when newer than v6.48.6. Mikrotik states that downgrading below the factory version is blocked because the hardware doesn't support it. All attempts to install ARDEN result in a hang requiring a power cycle and the unit returns to the undamaged v6.48.6 (now 6.48.7). Does anyone have a suggestion on how to install ARDEN on this unit?
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
BTW, I deal with RouterOS daily.
Ironic that this requires a level of understanding of SSH? or other direct access to the code inside the antennas, and one of my long term tasks is to "go elsewhere" to learn this stuff.
The procedure to flash AREDN firmware onto new devices is already challenging to teach, but this takes it to another level. Is there a more elegant solution on the way to us folks who just want to buy equipment and get it running?
If this issue about needing to downgrade the manufacturer software or not being able to do so isn't solvable ... then I'm going to have to avoid all the new ac Mikrotik equipment. That makes things AREDN a lot harder to implement.
Any clarity available today? Thanks ... Ed
Dave was doing the same procedure using the same OS (Linux) but for some reason wasn't successful. I think we're good.
Orv W6BI
To be clear ... when Dave did this using a Linux OS it did not work, but when you did this using a Linux OS it did? I assume your machine also was a different machine. How well are Windows machines running SSH doing with this firmware rollback procedure?
I've had one Windows machine fail to do firmware installs, but another work fine. Go figure.
Ed
I try to avoid using Windows as much as possible. While I do mildly dislike it, it's just that I'm much more comfortable with Linux.
To be clear - for this particular exercise we did NOT roll back the version of RouterOS; we just put it into tftp and had the LHG suck the image off the Linux box (as outlined using a PXE server when using Windows).
Hope that's clear.
Orv W6BI
This was a new AC type device with firmware that was newer than the OpenWRT can work with, but instead of rolling back the firmware which is what is suggested in the orange color box talking about bootloop issues ... you used this procedure with the factory firmware left alone
PXE Boot: Linux Procedure
1,2,3
...... 4. Open a terminal window to execute the following dnsmasq command with escalated privileges:
and ... on one Linux machine it would not work but on another Linux machine it took fine and you then were at the NOCALL and could proceed further from there?
If yes ... that's really good news. Re Windows ... I don't like it either but I have to exist with one foot in both worlds.
Ed