try uploading the VW.v.5.5.10-us.280 it replys wrong version and won't load firm ware ?
Did i miss how to downgrade the firmware someplace?
Kevin
W1KGK
Did i miss how to downgrade the firmware someplace?
Kevin
W1KGK
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
NOCALL-116-33-158
is what is hows at the top.kevin
http://www.arednmesh.org/content/how-setup-your-aredn-node
All of the XW models, except the NanoStation M5 XW released in 3.16.1.x, have a page header something to the effect of being tested. XW devices have been up in production mode on towers for a couple years now. Let's just say that a release that includes all these XW models is long over due when we'd remove this statement.
Joe AE6XE
Any suggestions..
73's
Kevin
Joe AE6XE
its a little confusing how this work in the instructions.
73'
Kevin
Kevin,
On the box you received this device in, what is the "test date"? See this forum post related to the Nanostation Loco M5 XW:
https://www.arednmesh.org/content/second-attempt-nanostation-loco-m5-no-ethernet-problem#comment-9214
The openwrt forums have reported the same issue in the Nanostation Loco M2 XW devices too. Other devices may have the same issue. If this is the case with your device, then loading the "nano-m-xw" firmware results in a dead ethernet port. We've determined that that loading the "rocket-m-xw" image will work. Ubiquiti has new hardware revisions, but all the model numbers are still the same. I don't think this is the case however, if you have a non-loco Nanostation.
You may need to make sure your wireless adaptor is turned off, so that there is no confusion and your laptop will only receive an IP address from the mesh node. The mesh node will assign your laptop a 192.168.1.x address (and has 192.168.1.1 itself) in firstboot mode. After the node has been configured with your callsign,etc, then it will get (by default) an 8 address subnet in the 10.x.x.x space. The specific address is derived from the MAC address of the wireless card in the device.
Joe AE6XE