I'm having trouble getting AREDN on a brand new Nanostation M5 XW. I can connect to it on 192.168.1.20 and see the following:
Device Model: NanoStation M5
Version: v6.2.0 (XW)
Date: 2019-07-03 11:20:27
When I power it on while holding the reset button, I see the 1-3, 2-4 flashing pattern of the LEDs after about 30 seconds. But when I try to put the file using tftp, I get a "Transfer timed out".
tftp 192.168.1.20tftp> bintftp> trace onPacket tracing on.tftp> verboseVerbose mode on.tftp> put /Users/ck/Downloads/aredn-3.20.3.1-ath79-ubnt_nanostation-m-xw-factory.binputting aredn-3.20.3.1-ath79-ubnt_nanostation-m-xw-factory.bin to 192.168.1.20:/Users/ck/Downloads/aredn-3.20.3.1-ath79-ubnt_nanostation-m-xw-factory.bin [octet]sent WRQ <file=/Users/ck/Downloads/aredn-3.20.3.1-ath79-ubnt_nanostation-m-xw-factory.bin, mode=octet>sent WRQ <file=/Users/ck/Downloads/aredn-3.20.3.1-ath79-ubnt_nanostation-m-xw-factory.bin, mode=octet>sent WRQ <file=/Users/ck/Downloads/aredn-3.20.3.1-ath79-ubnt_nanostation-m-xw-factory.bin, mode=octet>sent WRQ <file=/Users/ck/Downloads/aredn-3.20.3.1-ath79-ubnt_nanostation-m-xw-factory.bin, mode=octet>sent WRQ <file=/Users/ck/Downloads/aredn-3.20.3.1-ath79-ubnt_nanostation-m-xw-factory.bin, mode=octet>Transfer timed out.
I don't have a fully dumb switch, but I'm using a Netgear GS108T which I assume should be fine.
I'm using a Macbook Pro with a Thunderbolt to Ethernet adapter, WiFi turned off, Firewall turned off.
I cannot ping 192.168.1.20 when it is in the 1-3,2-4 flashing pattern. I can ping it successfully when it boots up in AirOS mode.
What am I missing here?
Thanks
Christian
Is Wi-Fi disabled on your computer?
What is the IP address of your computer immediately before the
'tftp 192.168.1.20' ?
You should be able to ping the node on 192.168.1.20 while it is in 'TFTP' mode.
Maybe try this without the VLAN switch in between.
Chuck
Yes, wifi is off, the computer is set to manual IP for ehternet: 192.168.1.100, netmask 255.255.255.0, gateway 192.168.1.1
Thanks for confirming that I should be able to ping it at 192.168.1.20 while it is in TFTP mode.
I will try direct connection without the switch.
Christian
I tried a direct ethernet cable to a raspberry pi (wifi off), and direct ethernet cable to my Macbook Pro (wifi off, ethernet on 192.168.1.100).
I'm puzzled why I can TFTP flash an XM radio, but not my XW radio with exactly the same cables and configuration.
Is there any value in trying to do it through the AirOS GUI? I'm assuming I would have to downgrade to an unsigned version, and to upload that I would also need a working TFTP setup.
Is JTAG my only other option?
Thanks
Christian
There was no response from your new XW device during the TFTP upload.
I was troubled by your XW ignoring the TFTP upload.
Which is why I was trying to ensure that the IP addresses were still valid.
"What is the IP address of your computer immediately before the 'tftp 192.168.1.20' ?"
I was suggesting that you try to ping the device immediately before the TFTP
to ensure that the IP addresses were active and that a route existed.
Beyond that I am baffled.
If the XW device responds to a ping (and is in TFTP mode), then the TFTP upload should not be ignored.
The TFTP transfer may fail, but not because of a 'timeout'.
:-|
Chuck
My laptop is at 192.168.1.100, netmask 255.255.255.0, gateway 192.168.1.1 (ethernet only, no wifi). When the Nanostation boots up into AirOS mode, I can ping it at 192.168.1.20 and connect to the web interface. Then I unplug the Nanostation from the PoE injector, and hold down the reset button while plugging it in. After 25-30 seconds I get the 1-3,2-4 flashing led pattern. I then go to the laptop and cannot ping 192.168.1.20, and tftp fails.