Still could be some mistake by me of course. I think others are running this node hardware under AREDN so hummmm. There is a text file with a lot of device data. I downloaded the "support data" from AREDN screen the second time.
bin file and repeated the install but same result. The node rebooted when I clicked "save" into routerOS. There are some other threads of discussion related to the message on some 5 Ghz nodes. The error message was "Untested Hardware". The initial node booted up (.elf) and I was able to install the. I had to move the tftp directory to / to get it to work per the command string.įinally dnsmasq and the command string worked on the Raspberry Pi. I got that done with the help of a local networking angel (thanks Alex). Turns out I had to download and install dnsmasq. So either I am making a dnsmasq mistake or neither the Mac nor the Raspbian version of Linux support dnsmasq OR there is an error in the instruction process or the command string. FAILĪgain, similar to the Mac experience, the dnsmasq command failed with a message "BASH: dnsmasq: command not found". At this point everything is cabled up except for power to the MikroTik POE adapter.ħ I then executed the dnsmasq command as root and was prepared to power up the POE while pressing the MikroTik reset button. I then plugged the POE adapter in the Pi. I then used copy and past to put this on the command line but did not execute it.Ħ I plugged a cat 5 cable into the MikroTik dish port and into the POE adapter (no power yet). I put this on the Pi in a text file where I did the edits to change "eno1" to "eth0" and "joe" to "pi". Working directory pwd = /home/pi/tftpģ sudo ifconfig eth0 192.168.1.10 and confirm eth0 address with ifconfig commandĤ Become root via command sudo su and confirm with whoamiĥ Using copy and paste grab the dnsmasq command line from the instructions in step 5.
bin file copied to fresh tftp directory on the pi. Here is the process I followed on a Raspberry Pi 4 recently updated.ġ. This gets me to step 5 in the Linux flashing process for the Mikrotik. Update! Yes the "sudo ifconfig eth0 192.168.1.10" worked on the Raspberry Pi.
0 kommentar(er)
