Even though I have no elevation and there's no one in my NW Harris Co TX area close enough to play with, I've been operating a NanoStation M2 with all the Nightly Builds with great success. I had communicated with a Rocket M2, both on the same property, until my HF station seems to have caused it to not work, reason unknown. Could be close proximity to the 80/40m inverted-V at 1500 watts even though the Rocket has a proper shield to ground. But I digress...
I recently bought and received a NanoStation M5 to play with the M2's DtD feature using the secondary port I've been reading about. The PROBLEM: I can't even log-in to the M5 with my browser (Firefox on a Windows-8 box) using the "normal" 192.168.1.20 to what I assume would be airOS. Same problem with the Raspberry Pi 2B which runs perfectly on the M2 and is used on the updates. I can't determine whether it's an XM or XW.
What might I be doing wrong? I've tried to read everything I could get my hands on about the initial Ubiquity log-in procedure. I ran the AREDN U-Boot Test and it reported BAD/GOOD so I assumed it might be a version 5.6 or later but subsequent tries failed. I can't ping it with 192.168.1.20, or 192.168.1.1. or anything. Obviously, I cannot determine the firmware version or whether it's an XM or XW. While holding the rest button for 15-20 seconds, it will go into TFTP mode but I can't load any version of the airOS using TFTP2.exe. All firewalls and VIPRE are disabled, but I have the same results and, again, with the Raspberry Pi 2B.
Suggestions?
Thanks...
Boyd Prestwood, K5YKG
near Houston, TX
I recently bought and received a NanoStation M5 to play with the M2's DtD feature using the secondary port I've been reading about. The PROBLEM: I can't even log-in to the M5 with my browser (Firefox on a Windows-8 box) using the "normal" 192.168.1.20 to what I assume would be airOS. Same problem with the Raspberry Pi 2B which runs perfectly on the M2 and is used on the updates. I can't determine whether it's an XM or XW.
What might I be doing wrong? I've tried to read everything I could get my hands on about the initial Ubiquity log-in procedure. I ran the AREDN U-Boot Test and it reported BAD/GOOD so I assumed it might be a version 5.6 or later but subsequent tries failed. I can't ping it with 192.168.1.20, or 192.168.1.1. or anything. Obviously, I cannot determine the firmware version or whether it's an XM or XW. While holding the rest button for 15-20 seconds, it will go into TFTP mode but I can't load any version of the airOS using TFTP2.exe. All firewalls and VIPRE are disabled, but I have the same results and, again, with the Raspberry Pi 2B.
Suggestions?
Thanks...
Boyd Prestwood, K5YKG
near Houston, TX
You didn't menton but is your computer set to static IP address of 192.168.1.5 with a netmask of 255.255.255.0? Then try a connection to 192.168.1.20 Follow this link. It's easy to forget to do that.
https://www.arednmesh.org/content/tftp-firmware-installation
Denis
A new purchased NSM5 is highly likely to be the XW models. This was one of the first XW models ubiquiti came out several years ago, and unlikely anyone has XM inventory anymore to buy (would have to be used on ebay).
However, there is no penalty to try and load XW or XM firmware on the wrong one. It will not accept the wrong one and give back a tftp error. But if the matching firmware, will load. But don't try to load the 3.16.x.x old firmware, it is not directly compatible and would software-brick the device. Only try to load the 3.18.9.0 or better the nightly build so that both ports are fully functional.
Joe AE6XE
Now, Joe, AE6XE... now that I knew the version and that it was an XW, I tried download to 5.5.11 via TFTP and it didn't take but at least as you said, it wouldn't be detrimental! I shall now load the factory upgrade of AREDN 3.18.9.0 for the nano M xw and then upgrade that with the latest Nightly Build.
Thanks guys... Update to follow!
73 de Boyd K5YKG
You don't need the U-Boot test utility either. Just do a TFTP install of the AREDN "factory" bin file for your device.
Your welcome glad to help as we all are. That's why this forum exists!
Denis
No peripherals connected yet so no traffic across the connection but I can click on each back & forth in the Mesh Status page successfully.
My intention is to have a MidMile(5Ghz)-to-LastMile(2GHz) "repeater" type path. Thanks to all who helped me. Also recognition to Daryl, K5DLQ, for the suggestion that will greatly simplify the future! Now, how to we start on that Conroe-to-Cypress backbone??!! All I need is elevation. Where are all the mountains in Southeast Texas!?
73 de Boyd Prestwood, K5YKG