Colleagues,
I've attempted to get a Ubiquti NanoStation loco M5 device working as an AREDN node and have been having some problems. The NanoStation is brand new and has a test date of 09/25/2019. The situation is:
1. I can download the AREDN firmware from the nightly build location http://downloads.arednmesh.org/snapshots/trunk/targets/ar71xx/generic/aredn-1618-5ccb4c3-ar71xx-ubnt-loco-m-xw-factory.bin using TFTP on a Win10 machine and then I can connect to the node via a WiFi connection, at this point the wired Ethernet connection doesn't work, nor can I save any changes using the AREDN setup page; I get an DTDMAC error when I attempt to save changes.
2. I then update the firmware using the contrtols on the Administration tab using the file http://downloads.arednmesh.org/snapshots/trunk/targets/ar71xx/generic/aredn-1618-5ccb4c3-ar71xx-ubnt-loco-m-xw-sysupgrade.bin from the nightly build location, not ticking the 'Keep Settings' box. The only thing this changes is the error message which is now "parameter 'MAC2' in the file '_setup.default' does not exist", I still can't save any changes or connect via the wired LAN.
3. It also appears I cannot change channel or bandwidth to suit our local arrangements.
4. I've changed the node name and that seems to stick. I've tried using the Default Values and Rebooting multiple times but nothing else seems to work.
I've tried TFTP upload and Administration upgrades multiple times, each with the same result.
I've been through the AREDN forum and have tried most of the suggestions there but still no success. Any suggestions about how I make further progress would be gratefully received!
Many thanks & 73
Dale VK1DSH
You are here
NanoStationlocoM5 issues
Mon, 06/22/2020 - 02:55
#1
NanoStationlocoM5 issues
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
Joe AE6XE
Many thanks for getting back to me and I now the unit working. I just tried all of the versions of the firmware and eventually got one that worked and didn't do the system upgrade. Also, I probably wasn't allowing enough time for the reset and DHCP processes to work properly; but after leaving things alone for a while after making changes it's come good and it appears to work correctly; changes can be saved and no error message appear. There is an amateur colleague close by and we're hoping to do an on-air test in the next day or two and that should prove everything is working.
So thanks again & 73
Dale VK1DSH