Where is the TFTP method for Ubiquity Nano M2 nodes documented?
There are references to what looks like it, that point to the old aredn web site, but the link is no longer valid.
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
it already is.
Well, that makes me feel pretty stupid as no matter how hard I looked at it a couple days ago, I didn't see it. I even remembered and then tried to search for your post here in the forums which had the steps in it, and couldn't find that either. Luckily I had cut-and-pasted a copy of your post on my home computer and was able to get at it that way.
I spent my career from 1969-until-recently working in the computer systems industry (analyst, designer,.independent consultant, etc/starting in unit-record, time-sharing and then interactive/on-line), so I feel I have a basis to say this: Documentation and directions always seem very easy to find and understand by the people who put it there, but not always so much by the folks who are just feeling their way into brand new territory. New users should be coddled whenever possible. YMMV.
- Don - AA7AU
Just loaded the AREDN firmware into a newly-acquired Nanostation M3.
Tip: you may have to disable your firewall like I did, or the tftp command will not work. I was getting a host connection error message when I ran the tftp command until I disabled the firewall.
I used the tftp command which was a feature in my install of Windows 10. This version seems to work a bit differently than as described under the TFTP instructions, "Issue the commands on your computer to send the AREDN firmware to your device". When I run ftp from the command line, "ftp <IP address>" usually brings me to an ftp command prompt, where I can do the described "bin", "put", etc commands.
But the tftp version that Windows 10 includes didn't do that when I entered "tftp 192.168.1.20". It responded with the tftp help information instead and returned me to the command shell prompt.
So I performed the firmware update by folding all of the parameters into the tftp command line, namely,
tftp -i 192.168.1.20 put <full path and.bin file location>
There is no trace option, but the upload completed in about a minute and I was returned to the command prompt.
Otherwise, thank you for the tftp instructions!
Our group in Southern Yavapai County, AZ has been using tftp -i 192.168.1.20 put <full path and.bin file location>, but have had numerous problems.
Quite often we get "connection failed" messages, then sometimes it works just great.
Sometimes we do not get the transfer complete message, but the software has been transferred and works.
Yesterday we we successfully did the tftp and then decided to do it again. It appeared to be transferring and the command prompt came back. On reboot, it came up as the previous callsign id and the "NO-CALL" did not come up.
I mention these only in case someone else has had these experiences and can fix errors between the keyboard and chair. :)
Vance - KC8RGO