I have a Nanobridge M5 XM hardware. This is a used unit from eBay. It was running airOS 5.6.1beta2. I ran the AREDN test utility and it came back GOOD. I loaded AREDN 3.15.1.0 on it through the airOS gui. When it boots the first time, it comes up showing there is 0K of flash available. Where it normally shows NOCALL there is nothing there. After trying to go through the first setup, I'm unable to save any configuration.
I tried a tftp of AREDN but get a "error on server: ???????????d" error. The same thing happens if I try to tftp airOS 5.5.11.
I was able to install AREDN on a "sister" nanobridge by taking it down to airOS 5.5.11 first via the gui and then taking it to AREDN via tftp. It configured fine and meshed right up.
I've got the support dump and the zip from the test utility. I can't seem to get an ssh session to work. What's scary is that the test utility came back GOOD but something clearly wasn't good. I'd appreciate any ideas on next steps, and I'd suggest changing the warning on the install web page to say even if it comes back GOOD, if you're running 5.6+, take it back to 5.5 first.
Mike
You are here
Nanobridge M5 unable to save config
Mon, 01/04/2016 - 17:44
#1
kg9dw
Nanobridge M5 unable to save config
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
support file
utility backup file...changed from .zip to tgz so it would upload.
I'll see if I can get some better wording to downloads page and see if we can check the test utility. My guess is that the fact its a beta threw off the test tool as those builds are not seen reguraly if you got a GOOD/GOOD (it should be two goods not one you may be running an old version of the test utility if its only one)
Basically you can not install AREDN on a 5.6 AirOS device. This includes Beta's as well.
The flash layout may be 'good', but the version of uboot in flash is not agreeable. Did you receive a good/bad (or bad/good)? Is there another uboot version to check for?
Joe
This didn't get caught because I was using one of Daryl's early builds (1.1.3) of the test utility that just checked the map (just got a GOOD). I just downloaded the latest utility, ran it against one of the other three nanobridges and got a BAD/GOOD response.
Sorry for the run-around on this. Good news is I've confirmed that taking it down to 5.5.11 and then to AREDN works, and if you get it stuck in the state I did (boots but can't save config) that you can take it UP to 5.6.3 and then back DOWN to 5.5.11, and then OVER to AREDN. This might be something to try for the guys that can't seem to get a tftp to work but a ping will work.
Mike
Hey guys, I hit this scenario again. This time I was using the latest build of Daryl's utility. The node had 5.6.1beta4. I ran the utility and got back GOOD/GOOD. I loaded AREDN 3.16.1B1 and was unable to save any config. I captured the support file, then upgraded it to 5.6.3, downgraded to 5.5.11, then loaded AREDN. There's definitely something not getting caught in the uboot check utility for nodes running beta code.
Are you buying these new and getting beta firmware from Ubiquiti ?