AREDN Experts,
I'm getting errors when trying to flash 3.22.1.0 onto a Ubiquity Rocket M5 and Ubiquity NanoStation M5:
- On both of my Windows 10 computers: “Connect Request Failed”
- On my old Windows XP computer: “Firmware check failed” or it just sits forever
Things I’ve tried so far to fix this:
- Used a cable tester on all my cables, found 1 cable with a bad connection on pin 8, stopped using that cable
- Got a 10/100 switch
- Got a PoE injector from Amazon (non-Ubiquity brand, this is last in line after the 10/100 switch, before the radio)
- Tried loading all available firmware files (-m, -xw, etc., unplugging everything in between each attempt, re-doing the radio reset sequence)
- Pings now report fine: 4/4, 0% loss, 0ms
- The radios have an old Ubiquity AirOS loaded on them (v6.3.6 XW). See existing firmware settings, attached, for the Rocket.
Any help is appreciated.
On Windows, you need to use the tftp method as referred to above to transfer the Rocket XW factory firmware directly from a PC.
Follow the directions carefully and it will work.
Good Luck.
-Brett, KG7GDB
Argh.
Microsoft Windows [Version 10.0.19043.1645]
(c) Microsoft Corporation. All rights reserved.
C:\Users\glenn>cd documents
C:\Users\glenn\Documents>cd ham and radio
C:\Users\glenn\Documents\HAM and Radio>cd aredn
C:\Users\glenn\Documents\HAM and Radio\AREDN>cd rocket m5
C:\Users\glenn\Documents\HAM and Radio\AREDN\Rocket M5>cd factory
C:\Users\glenn\Documents\HAM and Radio\AREDN\Rocket M5\factory>dir
Volume in drive C is OS
Volume Serial Number is 2E03-5FBD
Directory of C:\Users\glenn\Documents\HAM and Radio\AREDN\Rocket M5\factory
04/17/2022 06:36 PM <DIR> .
04/17/2022 06:36 PM <DIR> ..
04/17/2022 06:35 PM 6,685,084 aredn-3.22.1.0-ar71xx-generic-ubnt-rocket-m-squashfs-factory.bin
04/17/2022 06:35 PM 6,685,084 aredn-3.22.1.0-ar71xx-generic-ubnt-rocket-m-ti-squashfs-factory.bin
04/17/2022 06:35 PM 6,685,084 aredn-3.22.1.0-ar71xx-generic-ubnt-rocket-m-xw-squashfs-factory.bin
04/17/2022 06:36 PM 6,488,476 aredn-3.22.1.0-ath79-generic-ubnt_rocket-m-squashfs-factory.bin
04/11/2022 04:32 PM 6,488,476 rocket-factory-m.bin
04/11/2022 04:31 PM 6,685,084 rocket-factory-xw.bin
6 File(s) 39,717,288 bytes
2 Dir(s) 684,447,780,864 bytes free
C:\Users\glenn\Documents\HAM and Radio\AREDN\Rocket M5\factory>ping 192.168.1.20
Pinging 192.168.1.20 with 32 bytes of data:
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\glenn\Documents\HAM and Radio\AREDN\Rocket M5\factory>tftp -i 192.168.1.20 put aredn-3.22.1.0-ar71xx-generic-ubnt-rocket-m-xw-squashfs-factory.bin
Connect request failed
C:\Users\glenn\Documents\HAM and Radio\AREDN\Rocket M5\factory>ping 192.168.1.20
Pinging 192.168.1.20 with 32 bytes of data:
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Reply from 192.168.1.20: bytes=32 time=1ms TTL=128
Reply from 192.168.1.20: bytes=32 time=3ms TTL=128
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3ms, Average = 1ms
C:\Users\glenn\Documents\HAM and Radio\AREDN\Rocket M5\factory>tftp -i 192.168.1.20 put aredn-3.22.1.0-ar71xx-generic-ubnt-rocket-m-xw-squashfs-factory.bin
Connect request failed
C:\Users\glenn\Documents\HAM and Radio\AREDN\Rocket M5\factory>ping 192.168.1.20
Pinging 192.168.1.20 with 32 bytes of data:
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Reply from 192.168.1.20: bytes=32 time=1ms TTL=128
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\Users\glenn\Documents\HAM and Radio\AREDN\Rocket M5\factory>
You can use a 'live install' CD/USB media to boot and try out linux without writing anything to a HD/SSD.
I hope this helps,
Chuck
K6CCC and NC8Q,
Please see atatched for actions taken imemdiately before the TFTP error message and TFTP command.
Thank you
Could I be misinterpreting the expected double reboot after issuing the TFTP command? I take a "reboot" to mean that all 4 signal LED's flash in unison. The LED indication that I see is as follows:
1) before TFTP command, 1/3 & 2/4 cycling as described
2) after issuing TFTP command, 1/3 or 2/4 stay solid (frozen) for about 35 seconds
3) all 1/3,2/4 LED's go out for 1-2 seconds
4) 1/3 & 2/4 cycling again
5) every so often, the cycling 1/3,2/4 stops and the 1/3,2/4 freeze (with no TFTP commands being issued). Seems to be a cycle.
here's the commands & results from some of my trials just now:
C:\Users\glenn>cd\
C:\>dir
Volume in drive C is OS
Volume Serial Number is 2E03-5FBD
Directory of C:\
11/18/2015 12:00 PM <DIR> Apps
04/17/2022 06:35 PM 6,685,084 ar71xx-rocket-m.bin
04/17/2022 06:35 PM 6,685,084 aredn-3.22.1.0-ar71xx-generic-ubnt-rocket-m-ti-squashfs-factory.bin
04/17/2022 06:36 PM 6,488,476 ath79-rocket-m.bin
01/11/2017 11:29 PM <DIR> delete me
11/18/2015 01:44 PM <DIR> DELL
05/09/2020 05:10 AM <DIR> Downloads
11/18/2015 11:02 AM <DIR> Drivers
09/14/2020 09:36 PM <DIR> Intel
01/15/2017 06:18 PM <DIR> My Music
03/18/2022 07:56 PM <DIR> My-Installs
12/07/2019 02:14 AM <DIR> PerfLogs
04/21/2022 08:19 PM <DIR> Program Files
04/11/2022 07:30 PM <DIR> Program Files (x86)
06/12/2021 06:02 PM <DIR> Python27
11/21/2021 01:25 AM <DIR> RMS Express
04/17/2022 06:35 PM 6,685,084 rocket-m-xw.bin
09/14/2020 09:16 PM <DIR> Users
04/17/2022 07:16 AM <DIR> Windows
11/21/2021 02:26 AM <DIR> WSJT
4 File(s) 26,543,728 bytes
16 Dir(s) 683,426,467,840 bytes free
C:\>ping 192.168.1.20
Pinging 192.168.1.20 with 32 bytes of data:
Reply from 192.168.1.20: bytes=32 time=1ms TTL=128
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Reply from 192.168.1.20: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\>tftp -i 192.168.1.20 put rocket-m-xw.bin
Connect request failed
C:\>tftp -i 192.168.1.20 put c:\rocket-m-xw.bin
Connect request failed
C:\>tftp -i 192.168.1.20 put ath79-rocket-m.bin
Connect request failed
C:\>tftp -i 192.168.1.20 put ar71xx-rocket-m.bin
Connect request failed
C:\>tftp -i 192.168.1.20 put c:\ar71xx-rocket-m.bin
Connect request failed
C:\>tftp -i 192.168.1.20 put rocket-m-xw.bin
Connect request failed
C:\>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.102: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
C:\>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>tftp -i 192.168.1.20 put rocket-m-xw.bin
Connect request failed
C:\>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>tftp -i 192.168.1.20 put rocket-m-xw.bin
Connect request failed
1) before TFTP command, 1/3 & 2/4 cycling as described
2) after issuing TFTP command, 1/3 or 2/4 stay solid (frozen) for about 35 seconds
3) all 1/3,2/4 LED's go out for 1-2 seconds
4) 1/3 & 2/4 cycling again
5) every so often, the cycling 1/3,2/4 stops and the 1/3,2/4 freeze (with no TFTP commands being issued).
Seems to be a cycle.
a) C:\>tftp -i 192.168.1.20 put rocket-m-xw.bin
Connect request failed
-----
Hi, Glenn:
All seems as expected until 2).
-----
a) Indicates an aberration in the install response.
Maybe try a different computer?
-----
I am not a Windows user and cannot assist further.
73, Chuck
This was the nanoStation. I'll try the Rocket next.
Thanks for helping
I run into the same issue with a Rocket M5. Now I tried the same way as you: turning off the antivirus and the Win10 firewall, and - voilà - it worked the first time. Great!
Funny thing is that I've already flashed several Rockets, same model, same age - and they all worked without this. Just this one refused to be flashed. Strange.
Many thanks for the help!