Having trouble installing AREDN on a MikroTik RouterBOARD RBLHG-5nD running RouterOS v6.44.6.
Tried with both current and nightly builds. On Windows, using PXE Server, carefully following Ray KK6RAY's YouTube video. Have previously done two HAP 5s and hoped this process would be about the same. It's a little different, and maybe that's where I've gone wrong, or perhaps the hardware isn't supported?
See below and any suggestions or info would be appreciated.
Thank you, Chris KM6KDZ
The progress goes:
- PXE server reports apparent success:
2:13:42 PM DHCPc:discovering for another DHCPd on LAN 2:13:42 PM ROOT=C:\Users\Chris\Dropbox\ham_radio\AREDN Mesh\TinyPXEServer\pxesrv\files\ 2:13:42 PM DHCPd 192.168.1.10:67 started... 2:13:42 PM TFPTd 192.168.1.10:69 started... 2:13:42 PM HTTPd:80 started... 2:13:47 PM DHCPc:no other DHCPd discovered 2:14:12 PM DHCPd:REQUEST received, MAC:C4-AD-34-E1-35-77, XID:9AF427F4 2:14:12 PM DHCPd:BOOTP REQUEST 2:14:12 PM DHCPd:ACK sent, IP:192.168.1.21, XID:9AF427F4 2:14:12 PM TFTPd:DoReadFile:aredn-1546-a2f7da4-ar71xx-mikrotik-vmlinux-initramfs.elf B:1452 T:0 2:14:43 PM TFTPd stopped... 2:14:43 PM DHCPd stopped... 2:14:43 PM HTTPd stopped...
- When I visit 192.168.1.1 the header shows !!!! UNTESTED HARDWARE !!!!
I've inserted sysinfo below, and supportdata-NOCALL-202005110954.tgz . - Go to Administration and upload the bin file. It thinks for a moment and switches to an error page:
Bad Gateway The process did not produce any response
- The device is not bricked. It lets me give it an elf file and then a bin, and, I can get back to RouterOS
Sysinfo follows (and I've attached supportdata-NOCALL-202005110954.tgz).
node: NOCALL-225-53-120 model: MikroTik RouterBOARD RBLHG-5nD !!!! UNSUPPORTED DEVICE !!!! boardid: MikroTik RouterBOARD RBLHG-5nD Device has not been tested. Please file a ticket with your experiences. br-lan C4:AD:34:E2:35:78 eth0 C4:AD:34:E2:35:78 eth0.1 C4:AD:34:E2:35:78 eth0.2 C4:AD:34:E2:35:78 tunl0 00-00-00-00-00-00-00-44-00-00-00-00-00-00-00-00 wlan0 C4:AD:34:E1:35:78 /proc/cpuinfo system type : Atheros AR9344 rev 3 machine : MikroTik RouterBOARD RBLHG-5nD processor : 0 cpu model : MIPS 74Kc V4.12 BogoMIPS : 299.82 wait instruction : yes microsecond timers : yes tlb_entries : 32 extra interrupt vector : yes hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb] isa : mips1 mips2 mips32r1 mips32r2 ASEs implemented : mips16 dsp dsp2 Options implemented : tlb 4kex 4k_cache prefetch mcheck ejtag llsc dc_aliases perf_cntr_intr_bit nan_legacy nan_2008 perf shadow register sets : 1 kscratch registers : 0 package : 0 core : 0 VCED exceptions : not available VCEI exceptions : not available nvram hsmmmesh.settings=settings hsmmmesh.settings.wifimac='c4:ad:34:e1:35:78' hsmmmesh.settings.mac2='225.53.120' hsmmmesh.settings.node='NOCALL-225-53-120' hsmmmesh.settings.dtdmac='225.53.119'
Support File Attachment:
Looks like Mikrotik changed the model string to identify the device.
from: "MikroTik RouterBOARD RBLHG 5nD"
to: "MikroTik RouterBOARD RBLHG-5nD"
Thus the device isn't recognized. For the moment if you telnet into the node and edit with 'vi' the file "/www/cgi-bin/perfunc.pm" and find, then change
from:
To:
It will probably work until an update goes into the nightly build.
Joe AE6XE
Chris KM6KDZ
Using the string 'MikroTik RouterBOARD RBLHG-5nD' removed the banner warning UNTESTED HARDWARE.
But on Admin, Firmware Update the device seemed to still be unknown:
(I'm using the nightly build.)
And doing an Upload still resulted in
Is there something else I can try, or do we need to just hang tight until the nightly catches this?
Thanks, Chris KM6KDZ
Joe AE6XE
As before, I edited perlfunc.pm replacing 'MikroTik RouterBOARD LHG 5nD' with 'MikroTik RouterBOARD RBLHG-5nD'.
So far so good, as before this removed the banner "UNTESTED HARDWARE"
Next I edited board.json replacing "unknown" with "rb-lhg-5hpnd".
The next step after editing board.json was to reboot. Tried rebooting using the UI, or reboot from the command line, either resulted in the device hung and unresponsive. Permissions on the json file looked OK... maybe I don't know how to reboot the node while it's in the middle of the install process.
I tried to continue without the reboot and got the same "unknown" display as I'd reported previously, tried the upload, and still Bad Gateway.
It's been fun going a little into the AREDN filesystem with telnet, putty and winscp. Hadn't done that before, though I use those tools regularly. I'll bet that your time troubleshooting this would be better spent on the build at this point, which I'll be more than happy to test for you.
Thanks, Chris KM6KDZ
https://drive.google.com/drive/folders/1M_edtdOHYcXy1CRFMPiNr65VBPxtg0e7...
Joe AE6XE
The yellow Untested Hardware header is still there but all else seems to be alright. All the setup worked OK. I attached the Sysinfo and Support archives. I won't be able to RF test until I do our other LHG5 (we bought 2). Do that Monday.
Chris KM6KDZ
D'oh, need to make the change in perfunc.pm too. You can edit manually one time for now to make the yelllow banner go away. I'll update images Monday.
Joe AE6XE
Joe AE6XE
Looking in perlfunc.pm it looks the new block of code is there but the condition wasn't completely changed. I think it should be 'MikroTik RouterBOARD RBLHG-5nD'.
Chris KM6KDZ
+ 'MikroTik RouterBOARD LHG-5nD' => {
Should be
+ 'MikroTik RouterBOARD RBLHG-5nD' => {
Here's the working file from my node.
Joe
Chris KM6KDZ