New Basebox5 showing !!!! UNTESTED HARDWARE !!!!

Mikrotik has added "RB" as a prefix to the boardid, according to your supportdata dump. Jim, if you're feeling adventurous you could boot the elf file and then telnet or ssh to the new BaseBox5. Once you have a command line you could navigate to /www/cgi-bin/ and edit the perlfunc.pm file using the vi editor. Almost 1200 lines into this file you will see the entry for the BaseBox5, which looks something like this: 'Mikrotik RouterBOARD 912UAG-5HPnD' => { 'name' => 'Mikrotik RouterBOARD 912UAG-5HPnD', 'comment' => '', 'supported' => '1', 'maxpower' => '30', 'pwroffset' => '0', 'usechains' => 1, 'rfband' => '5800ubntus', }, If you copy all of those lines (including the closing }, at the end), and paste them above or below the original, then you could add the "RB" prefix wherever you see the RouterBoard information. It would look like this after you edit the file: Mikrotik RouterBOARD RB912UAG-5HPnD Then you would save the file with your edits included, and refresh the web page to see if the Untested Hardware message disappears. If that seems to fix things, then you could proceed with installing the full firmware sysupgrade.bin file. Once the full firmware file is installed and the node reboots, you may see the Untested Hardware message again. If so, then repeat the above steps to edit the perlfunc.pm file on the node. If the Untested Hardware message disappears then the node should be fine -- until you decide to upgrade the firmware again. Once the development team gets the new boardId added to the firmware files then this issue will go away for good. The same issue is happening on the Mikrotik mAntBox2-12s model.