I've scoured the AREDN forum, read all docs I can find here related to loading a MikroTik hAP ac Lite with the current AREDN firmware and am having no luck getting the initial load of AREDN to take. The process goes just as documented in the AREDN docs for this device, the Tiny PXE shows the rb.elf file was seen and loaded, but after several minutes and what seems several auto-reboots of the hAP ac lite, it reverts to the default network of 192.168.88.X and MikroTik OS 6.48.6 that the unit came with. It's a brand new device from Amazon 2 days ago. I set the boot device to "try-ethernet-once-then-nand", made sure "protected routerboot" is off. Ethernet cables are in the appropriate locations during the process, just nothing I do seems to make this unit take the latest base file. I turned off my computer's firewall and disabled virus software. So, looking for ideas, suggestions or a direction to go. While complicated, the process to do this seems pretty straightforward, but just doesn't seem to be working for me. It is an RB952U1-5ac2nD-US, which I believe is the correct model number. Any help or ideas appreciated.
73, Bill, N4SV
Yes, the dumb switch was in place...and the dumb operator too...me. I discovered I downloaded the wrong firmware file and after getting the correct one for the hAP ac lite it worked fine. However, my new 3.24 version of AREDN on the hAPac lite, on the same channel (-2) and same bandwidth (10 MHz) as my existing nodes and the new node doesn't see my existing nodes? Are there incompatibilty issues between 3.24 and older ones like 3.16 and 3.19? I'd like to load 3.24 on my older Ubiquiti nodes but they are all Sunset and likely don't have enough memory. Suggestions?
73, Bill, N4SV
Hi Bill. It's been a long time. I hope all is well.
Are you by chance a Linux guy also? For the Mikrotik devices, I started using Linux quite some time ago and find it much easier.
My laptop, even with a dumb switch in-line does not want to keep the IP if I don't have something like an operational node on the end. I don't fight it any more and don't even bother with the dumb switch. I have network profiles I can pull-down to go between the Mikrotik IP and DHCP. And I keep two terminal windows open, one for doing "ifconfig" (and ping) and the other for sending the command to program the device. I've had good success doing things this way for the last several devices.
I also made a helper script that makes getting the command string correct real easy. I can email to you if interested. But if you don't do any Linux, I probably cannot help.
73 - Mike
Thought I recognized that call Mike, how's things with you...still in Virginia? I am really red faced on this one as the break/fix was my own doing. When downloading the latest AREDN files I grabbed the wrong files, not the ones for the hAp ac lite. Went back to the download section of the AREDN site and got the right files and the load went off as expected...but...now the new MikroTik node isn't seeing my legacy Ubiquiti nodes, and I am on the same channel (-2) and bandwidth (10 MHz). My old nodes are on 3.16 or 3.19 versions, is there some compatibility issues between them and the new 3.24? I've been away from AREDN so long all my old Ubiquiti gear has become Sunset, so had to get some new stuff. I'd love to try a 3.24 load on one of the old Ubiquiti devices but I am afraid they don't have enough memory. Any thoughts?
73, Bill, N4SV
Well I guess I have spent way too much time hammering on this thing as I discovered I had another brain burp...I had the wrong channel set on the new node. All my nodes are on channel -1, not -2...set the right channel and all is well. Links to my "remote" nodes (on the far end of my property) are a bit slower to respond when my computer is connected to the hAP ac lite than when on one of my old stand-by Ubiquiti devices, but that is likely due to more gain/power/antenna on the Ubiquiti than on the MikroTik. And the hAP ac lite is on the included 24 volt power supply, so should be good there. Thanks for reading my post and providing feedback.