Hello,
I noticed that the BaseBox 2 is now listed in the supported devices. So I ordered one and flashed it. However, on bootup, on the NOCALL page with, it displays a message in red saying "!!!! UNSUPPORTED DEVICE !!!!." When I click the message it says this device has been tested as unsupported. So I am confused as to why it has been recently added to the supported device list. Is this a false positive or is this device not supported?
Thanks!
73,
Tony, W1LMS
node: NOCALL-190-248-117 model: MikroTik RouterBOARD 912UAG-2HPnD !!!! UNSUPPORTED DEVICE !!!! boardid: MikroTik RouterBOARD 912UAG-2HPnD Device HAS BEEN TESTED AS UNSUPPORTED br-dtdlink 18:FD:74:BE:F8:74 br-lan 18:FD:74:BE:F8:74 eth0 18:FD:74:BE:F8:74 eth0.1 18:FD:74:BE:F8:74 eth0.2 18:FD:74:BE:F8:74 tunl0 00-00-00-00-00-00-00-44-00-00-00-00-00-00-00-00 wlan0 18:FD:74:BE:F8:75 /proc/cpuinfo system type : Atheros AR9342 rev 3 machine : MikroTik RouterBOARD 912UAG-2HPnD processor : 0 cpu model : MIPS 74Kc V4.12 BogoMIPS : 479.23 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 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='18:fd:74:be:f8:75' hsmmmesh.settings.mac2='190.248.117' hsmmmesh.settings.node='NOCALL-190-248-117' hsmmmesh.settings.dtdmac='190.248.116'
I did the latest release (3.23.4.0 (r20028-43d71ad93e)) and the lastest nightly build (20230704-eaa5d2f (r20134-5f15225c1e)).
I am still troubleshooting, but was trying to see if anyone knew why this was happenning. I could not find anything about the RB912UAG-2HPnD in the forums. below was from the nightly build.
node: NOCALL-145-56-145 model: MikroTik RouterBOARD 912UAG-2HPnD !!!! UNSUPPORTED DEVICE !!!! boardid: MikroTik RouterBOARD 912UAG-2HPnD br-dtdlink 18:FD:74:BE:F8:74 br-lan 18:FD:74:BE:F8:74 eth0 18:FD:74:BE:F8:74 eth0.1 18:FD:74:BE:F8:74 eth0.2 18:FD:74:BE:F8:74 tunl0 00-00-00-00-00-00-00-44-00-00-00-00-00-00-00-00 /proc/cpuinfo system type : Atheros AR9342 rev 3 machine : MikroTik RouterBOARD 912UAG-2HPnD processor : 0 cpu model : MIPS 74Kc V4.12 BogoMIPS : 479.23 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 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='02:D3:25:91:38:91' hsmmmesh.settings.mac2='145.56.145' hsmmmesh.settings.node='NOCALL-145-56-145' hsmmmesh.settings.dtdmac='190.248.116'Finally tracked it down for you. The problem is that the entry in /etc/radios.json is slightly incorrect. The 't' in Mikrotik needs to be upper case. If you edit the file on your node and change the case of the character, then you should be all set.
I will try it out and report back.
Thank you very much!
Tony, W1LMS
Well, that fixed the 'unsupported device' message popping up.
However, the device still boot-loops (as before, up to 10min). Not sure what is causing it to crash during boot. I thought it was connected to the unsupported device issue, which is why I did not mention it previously, but now that part is fixed, the boot-looping still happens, about 20-30 times before it finally stops restarting.
It does adopt the new mesh address, but the wireless lights never turn on (except during POST). I initially thought the WLAN was not working, but a few minutes after it stops boot looping, it does show up on the mesh, though the WLAN lights on the device never turn on. Only the PWR and ETR lights are on.
Aside from waiting 10+ minutes for the unit to turn on and be ready, it seems to be somewhat working. If I reboot another node, once that node is up, it immediately detects all nodes around it except the BaseBox2. But after another 5-10 min, the BaseBox2 eventually shows up. So it is definitely not working the same way as the other nodes.
I also seem to be having trouble with the ETH1. Can you confirm if ETH1 behaves as WAN or LAN? I expected ETH1 to be WAN, but it is not behaving as expected. Despite receiving an address from the router, and later, the modem, the port seems to behave as if it's asleep (despite the light showing activity). After getting an address, the router shows that the BaseBox2 IP is offline. No response to PING, and does not allow SSH (I enabled SSH over WAN). It also does not show its assigned WAN IP on the Node Status page and does not indicate it has WAN, nor does it share its WAN connection (I enabled share WAN with other nodes). I did a test with another mesh node, and that one worked as expected, showing the WAN IP, sharing its WAN, and allowing SSH.
Are there some specific logs I can post here that would be helpful?
Thanks for your help!
73,
Tony, W1LMS
Just wanted to comment on new nightly build version 20230709-f4321ff (r20134-5f15225c1e). It does fix the unsupported message that was showing at the top of the page, but the other issues mentioned in my last msg are still prevalent. After PXE booting and uploading the latest firmware, it still bootloops for about 10min.
Also, One the new firmware nightly, it does not come up on 192.168.1.1. So I had to go back to the previous one. I will upload the log shortly.
Here is the log on initial boot after firmware update: https://pastebin.com/Rknrb6H7
I then corrected the lowercase 't' in /etc/radio.json, entered a node name & password and saved the configuration. After a couple of hours of boot-loops (usually its about 10min), it finally stayed on and showed up on the mesh, since I cannot access it from ETH1 once a node name is configured (even though it has an IP).
After typing the 'logread -f' command on the ssh, nothing happened. I waited several minutes and no log entries displayed. I then login to the web gui and go to setup and that action generated a log entry. But the setup page on the web gui was missing most of the settings (https://pasteboard.co/d6eUhEgldiVp.png). It only has fields for the Node Name, Node Description, Password and Verify Password. Seems this is getting worse, LOL. I have lost so much valuable time on this. It would not be so bad if it did not boot loop for so long.
I then re-ran the logread command without -f so that I could view the log prior to the current time since -f only showed from that moment and not before. Here is that log: https://pastebin.com/uMvPyhm5
Please let me know if there anything else I can upload to help resolve this.
Thanks for your help!
Tony
Installed kernel via PXE and updated firmware to 3.23.4.0 (r20028-43d71ad93e). [!!!! Unsupported Device !!!!]
After about 10min of boot-loops, the unit finally starts up and stays on. Used vi to edit the /etc/radio.json file to change the letter "t" in MikroTik to uppercase. I also access the log: https://pastebin.com/rwiGyBw2
Rebooted after making the change to the JSON file and guess what?!?!?! It booted right up. No boot-loops. I then added a node name, changed the password and saved the configuration.
The node rebooted twice and came right up. Here is the logfile for that instance: https://pastebin.com/a7PLVwC2
I then went to the advance config page and enabled 'share WAN with other mesh nodes'. It rebooted twice and received an IP address on ETH1 from the router, but is still inaccessible to connections. I was unable to bring up the webGUI via the IP address on ETH1. It also never came back up on the mesh page (mesh status). So I unplugged it and tried again. This time, it boot-looped for about 10min, but never came back up on the mesh. So the node seems to be inaccessible after turning on the share WAN with other nodes.
Also, the lights indicating wireless strength still do not work. Only the PWR and ETH lights turn on (well except during POST when all lights turn on).
While the behavior of the node seems to be very different from the nightly build, it still has some issues. Hopefully the logs are helpful.
Thanks!
Tony
Just wanted to follow up to see if the logs were helpful.
After multiple reboots, the node finally showed up on the mesh and I was able to access it to get the logs for after I enabled WAN sharing to other nodes. Still unable to access the node via ETH1, Node status page is still not showing the IP address for ETH1, not showing that it has a WAN connection, therefore, not sharing the WAN. Here are the logs: https://pastebin.com/Efr75jdF
Hope this sheds some light.
Thanks for your help.
Tony
I think at this point the best thing to do is to go create an issue in the GitHub repo so that the AREDN developers could analyze the logs and investigate the cause for what you are seeing.
73
WT0F
After the initial boot-loops after a PXE install and sysupgrade.bin upgrade,
does it do it again after a re-boot?
I had a Mikrotik hAP that, once, took about 14 minutes to settle down after a firmware upgrade,
but after following reboots, it worked as expected.
73, Chuck
The only time this node did not boot-loop is after the capitalization on the "t" in the radio.json file and after the node name change on stable firmware. All other times on stable and on beta, it boot loops for average of 10min. The boot-loops only happen on startup, does not happen after it completes startup. I have noticed that sometimes, the boot-loops last shorter than 10 min. A couple times it lasted only about 3-5min. But there has been a couple that lasted 30-60min.
After the node name configuration, ETH1 no longer works and mesh works sometimes. When mesh does not work, I reboot a few times until it comes back up. But since this node can only operate as a gateway, ETH1 not working is a big issue. WAN is just dead, despite having a IP address.
The assumption has been that the single port on this node defaults to WAN after node name configuration, though I have not received a confirmation to my earlier questions regarding that. There is both a LAN and WAN config session. Since there is only a single port, I was expecting one or the other. LAN defaulted to 5 hosts, I changed to 1 host since there are no hosts. WAN is set to DHCP, defaulted to Google DNS, also tried Cloudflare and Quad9 DNS, but I do not believe this to be a DNS issue. The router assigns the node an IP address, but despite activity lights on the node ETH, the router reports the node is idle/sleep. The node never reports it has an IP address, not from the webGUI node status page, nor from ifconfig: https://pastebin.com/FbWKkSbP
While the ETH1 does not work when connected to standard router for WAN, I did try plugging it in the hAP port 5 and turned on POE passthrough and it dtd worked, after multiple boots.
The intended use of this node was to have the BaseBox2 to be a WAN/mesh gateway for a group of hAPs at a deployment. Previously, I used a hAP for this function, but the hAP are not rated for outdoor, so I wanted to switch to something that was. Some of our deployments are in the desert and spontaneous rainstorms have formed right over us and then dissipated in a matter of minutes during deployments.
This is why I was asking earlier if ETH1 defaults to WAN. If it does not, then this won't work until I can get it in WAN mode. ETH1 works during PXEboot and initial node config, and works dtd, so very strange it does not work when connected to the router. Unless I am missing something.
Regards,
Tony
Wondering if this means I should return the device since I had not received any responses to the logs I provided. After spending many hours trying to get this work, I was not able to. I cannot use it in this state since this in an emcomm environment. So I have switched back to the hAP and boxed it up. However, if this msg is in the wrong location for support, please let me know.
Thanks!
73, Tony