ubiquiti-tftp is making me crazy ...
I loaded Linux on a Chromebook, downloaded the AREDN firmware for a ubiquiti Rocket M5 and followed the instructions.
The first step was to "Set Static IP Address" by editing /etc/network/interfaces.
That file didn't exist so I let nano create it.
I then populated it as instructed auto eth0 iface eth0 inet static address 192.168.0.100 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 4.4.4.4 dns-nameservers 8.8.8.8
The next step was to edit /etc/resolv.conf as follows nameserver 8.8.8.8 # Replace with your nameserver ip nameserver 4.4.4.4 # Replace with your nameserver ip
I didn't know what to use as a "nameserver ip" so I just used 127.0.0.1
It required "sudo /etc/init.d/network-manager restart" to play network restart nicely.
The problem is when I run "tftp 192.168.1.20" then "bin" then "trace on" then put /home/kd4e/aredn3.22.8.bin
NOTE: I shortened the downloaded file name as recommended in a Forum thread back in April.
it returns an error that it can't find the bin file (while I'm looking at that bin file in file manager).
What did I do wrong, please?
Thanks
I loaded Linux on a Chromebook, downloaded the AREDN firmware for a ubiquiti Rocket M5 and followed the instructions.
The first step was to "Set Static IP Address" by editing /etc/network/interfaces.
That file didn't exist so I let nano create it.
I then populated it as instructed auto eth0 iface eth0 inet static address 192.168.0.100 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 4.4.4.4 dns-nameservers 8.8.8.8
The next step was to edit /etc/resolv.conf as follows nameserver 8.8.8.8 # Replace with your nameserver ip nameserver 4.4.4.4 # Replace with your nameserver ip
I didn't know what to use as a "nameserver ip" so I just used 127.0.0.1
It required "sudo /etc/init.d/network-manager restart" to play network restart nicely.
The problem is when I run "tftp 192.168.1.20" then "bin" then "trace on" then put /home/kd4e/aredn3.22.8.bin
NOTE: I shortened the downloaded file name as recommended in a Forum thread back in April.
it returns an error that it can't find the bin file (while I'm looking at that bin file in file manager).
What did I do wrong, please?
Thanks
Did you follow the latest directions for installs in the online documentation?
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#ubiquiti-first-install-process
There is also a handy one-page checklist here:
https://arednmesh.readthedocs.io/en/latest/_downloads/a4033d28abe53a0876592c128e7ad747/Ubiquiti_First_Install_Checklist.pdf
NOTE: When I edit and save /etc/resolv.conf then run a network restart - it reverts to the pre-edit setting 192.168.50.1.
TFTP is failing to see the .bin file on the Chromebook (I tried changing file permissions to Read-Write in Group, no joy.)
Do you mean 'Step 4' here:
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installin...
To whit:
"Open a command window on your computer and execute a file transfer command to send the AREDN firmware to your device. Target the default IP address of your Ubiquiti node, such as 192.168.1.20 (or 192.168.1.1 for AirRouters). The following is one example of TFTP commands that transfer the firmware image to a node:"
?
I used Linux to TFTP AREDN's Ubiquiti-factory.bin to my nodes and never touched '/erc/resolv.conf'.
I have no clue why your Mac/Linux box is getting a 'pre-edit setting'.
"TFTP is failing to see the "
There may be an error in your path or you are not in the directory that contains the factory.bin file.
73, Chuck
That said, all I need is a hint about the reason TFTP would fail to see the bin file, and why resolv.conf is being reset (despite no mention of that in the instructions at techmint.com)
"I need is a hint about the reason TFTP would fail to see the bin file,"
There is a typo in the path or you are not in the same directory as the factory.bin file.
(despite no mention of that in the instructions at techmint.com)
Excuse me, but why are you following instructions at techmint.com and then asking for help at arednmesh.org's forum?
Please, let us use the same page in the same hymnal.
;-)
73, Chuck
Since I'm on a Chromebook running a minimalist version of Linux that I've not used before, and there's apparently no user-friendly app in it to adjust the "Ethernet network adapter" settings - before I bothered anyone here I tried to find an answer, elsewhere, online.
There's no typo in the path.
The instructions only say to provide the full path - not to be in that directory prior to opening TFTP.
I'm providing the path "/home/kd4e/aredn3.bin".
I just changed directories to /home/kd4e and ran TFTP - it now works (it may be good to add that to the instructions).
However, the "put" times out after 5 attempts.
The lights are flashing as per the instructions.
Per the April thread suggestions I changed two of the cables and powered-off and repowered the ubiquiti device.
Tried TFTP again - same thing - it times out after 5 attempts. (I ran it a second time, same result).
What's the most-probable failure-point when TFTP times-out, in this use case, please?
I only speak enough linux to be dangerous, so I'll shut up now and leave the answers to experts...
Dear, Thanks
I think Mac OS is sufficient and almost identical to Linux.
I have no clue as to what installation instructions your spoke of in your post.
Please follow the instructions on this web site:
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#ubiquiti-first-install-process
73, Chuck
I printed those and have followed them to the letter - as described in a prior post.
I am using a USB to RJ-45 adapter as the Chromebook lacks a standard LAN port.
Is there any reason to believe that the adapter might cause the TFTP failure to connect?
Given that as a possibility - I dug out an ancient MS laptop (used to program Moto mobiles and a GE repeater) - will try that, shortly, and report back.
have you tried to just use a relative path instead of an absolute path?
ie.
cd /directory/where/bin/file/exists
tftp 192.168.1.20
bin
trace
put aredn-file-factory.bin
Question: Should I be able to Ping the ubiquiti from the Chromebook (when the lights are flashing 1-3/2-4)? If I can, does that mean I don't need to look for the solution in the physical connection? (If not while the lights are flashing, is there another way I can test the connection-only?
yes. you should ping 192.168.1.20 before attempting the tftp (when the lights are alternating 1-3/2-4)
also, your local IP should be like: 192.168.1.2/255.255.255.0 (NOT 192.168.0.x)
I can Ping 192.168.50.1 (the default value in /etc/resolv.conf)
I checked the cable and USB-RJ45 adapter on a Lenovo - it works fine pinging an old router.
I'm unclear on setup ... per the AREDN one-page checklist (and the longer version as well) ...
4th step is to "Set Static IP Address"
NOTE: I'm using the terminal emulator in Debian Linux on a HP Chromebook 11 - so I edited /etc/network/interfaces
That file didn't exist so I let nano create it.
I then populated it as instructed auto eth0 iface eth0 inet static address 192.168.1.2 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 4.4.4.4 dns-nameservers 8.8.8.8
The instructions I followed (to Set Static IP in Debian) said to also edit /etc/inet.d/resolv.conf (the default nameserver there was 192.168.50.1 and no matter what I change it to - restarting the network results in it being restored to that value).
I restarted the network using sudo /etc/init.d/network-manager restart
No Ping of 192.168.1.20
WDYT, please?
What is the IP address (and NETMASK) of your Chromebook immediately before attempting the TFTP command?
If using Linux, 'ifconfig' will display.
If using Windows, 'ipconfig' will display.
I do not use '/etc/resolv.conf' nor *netmanager*.
I use Linux and I enter a command like this immediately before the TFTP command:
sudo ifconfig eth0 192.168.1.9
('.9 ' or any number among '.2 ' to '.9 ' or '.21 ' to .254 ' would likely be safe.)
('eth0' should be replaced with your ethernet device's actual name.)
Since you mentioned being able to ping 192.168.50.1 (home router?)
I assume that your Chromebook has an IP address between 192.168.50.2 through 192.168.50.254.
Typically an IP address in the 192.168.x.x range has a NETMASK of 255.255.255.0.
If your Chromebook has an ethernet port with an IP address of 192.168.50.x (and a NETMASK of 255.255.255.0),
it is not permitted to send a ping to 192.168.1.x out of that ethernet port.
73, Chuck
Also, please see the error message from tftp.
Thanks
Removed and retried - same time-out error.
This indicates a loss of data in the transmission.
Could be a broken;
port on the computer or port on the AREDN device or
a bad cable.
If using Windows, I would like to see the display from this command:
IPCONFIG
(https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/ipconfig)
I see a cursor in your attached image.
Can you 'cut-n-paste' the text from your display then into a post here, in lieu of attaching an image?
73, Chuck
I'll see if I can get a cut & paste on a USB stick and bring it over to this laptop.
The LAN port on the old Dell laptop has been used to program old Motorola and GE gear - so it's tested-good.
I've swapped the cables to known good ones.
I'll try a different ubiquiti device - in case this one is just being obstinate ... lol
UPDATE: It was the device! Just swapped in a different one and it accepted the bin put just fine. Cool!
UPDATE2: Saved and changed to DHCP (less than intuitive in Win7) and http://localnode opened the very nice device display. I'll see how many other of the devices will play nicely. After that I'll need to sort a camera and a mini weather station. Good fun!
UPDATE3: Well, hit a new-old wall. Back to the failure message for 3 different devices. I tried reversing the change to DHCP - and even rebooted the laptop - but it still fails "Error on server: Firmware check failed" (I also made a fresh download and checked the md5sum.)
Note that your Wi-Fi has an address and netmask and gateway.
When TFTP'ing, if your computer doesn't know where to send the 192.168.1.x packets,
it will send them out the Wi-Fi port, 192.168.50.x.
It is recommended, when attempting to TFTP on the ethernet port,
to disable the Wi-Fi port.
73, Chuck
I don't have the time to fuss with them ...
Is this is the same as the "LiteBeam M5" on the supported hardware list?
"Ubiquiti LBE-M5-23-US 5GHz LiteBeam M5 23dBi airMAX"
Thanks