Nodes

Hi,
I am trying to install on a device that already has Open-wrt 19.07.7 running fine on it.

Initially I tried a sysupdate via the gui as I thought it worth a try as its the same base program. This seemed to work fine but crashed whenever I reset the password as requested, it doesn't re-boot and doesn't ping although the lights look like its working.

If I press the reboot button on the GUI without changing the password it re-boots OK.

I had AREDN installed on a Motorola WR850G in late 2018. It sat on the shelf for a while until I recently found a use for it but forgot the password so I could not change the settings in the config screen. I did a pen-tip reset with the button on the back and now I cannot get into the mesh status page at all (host would not resolve). It seems to be acting as a pass-through to the WAN.

I'm looking around for AREDN compatible gear and the TP-Link CPE units look interesting for an entry-level tactical deployment. Everyone has the CPE510 in stock, but TP-Link's website and the AREDN compatibility guide show a CPE520 which doesn't seem to be for sale anywhere. Is it available in the US? It's a higher power device than the CPE510 and has an extra LAN port.

I'm checking out a new TP-Link CPE-510 with the factory firmware and noticing that it only covers channels 36 to 48 and 149-165 (5180-5240 and 5745-5825 MHz)

The docs don't say anything about this gap. There is a "*" in all the docs that basically says "your mileage may vary by region".

Did I get a device coded for the wrong region? (I am in the continental US). Or maybe this is a side effect of DFS, which is locking out the whole UNC-2 band? Should AREDN unlock all the missing frequency channels as well as opening up the ham band?

I recently purchased a new TPlink CPE210 and can not successfully install the AREDN software.  I have done numerous Ubiquiti devices without issue.  I first tried the preferred method, and it seemed to program, but it finally got into a loop where the ethernet port would enable and disable and I was unable to acquire an IP address.  So I tried the alternate method which uses the Tiny PXE Sever, which seemed to work but ended with same result.   I thought I had bricked the device, so I downloaded the TPLink factory image from TPLink, and used the Tiny PXE server to program it.  Now I can log

MAHALO to KC0EUW firmware install steps:  ​https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installin