Hi forum,
I come here after debricking a Meraki MR12 and getting OpenWRT installed back on to it. Was feeling pretty good about myself too having managed that. I can just about remember installing it many moons ago, then bricked it trying to get to the latest version. Bad idea, but working again but still on old(er) version.
I had a spare Aruba AP11 with better specs than the MR12, so thought I would have a go at that too.
I've followed [OpenWrt Wiki] Aruba AP-303 and can get as far as successfully completing step 4. I say successful as although the instructions say not to bother too much about the wrong image error, I also get an ipq error
Invalid image format version: 0x675148
Uncompressing Kernel Image ... OK
ipq: fdt fixup unable to find compatible node
So up comes BusyBox with a shell prompt. So far so good.
BusyBox v1.35.0 (2022-09-03 02:55:34 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 22.03.0, r19685-512e76967f
-----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@(none):/#
(note: I've had a few stabs a this now, hence the 22.03.0 version)
I can ping myself (192.168.1.1) but nothing else as root. And from my tftp server I can't ping 192.168.1.1. And after maybe 30secs to a minute, the AP will reboot itself. I have no time to troubleshoot the lack of connectivity as the AP is back to booting up again and I'm back at an apboot again with no image found to boot.
I can see in /etc/config/network that the IP is set at 192.168.1.1 in the brief time i have console access
While sat at the apboot prompt, if I do nothing, type nothing, then the AP also resets itself after exactly 2 mins, but has the courtesy to tell me it's doing a reset.
Timeout waiting for command
resetting ...
APBoot 2.5.0.2 (build 70487)
Built: 2019-05-14 at 12:29:35
Model: AP12
DRAM: 512 MiB
Flash: Detected MX25R3235F: total 4 MiB
In Busybox, it just starts booting the AP again with no warning or indication that it's doing a reset.
So I'm kind of stuck and out of ideas. Is the idq error significant? Can see a few posts where that same idq error is mentioned but those are in log files and no one is talking specifically about that.
Any and all help gratefully accepted.
Thanks
Mike
