You are here


7 posts / 0 new
Last post
KE0NA's picture

A friend and I recently purchased two new RBLHG-2nD's from Amazon and we had a really tough time loading the bin file using the Daily Builds but finally got it to load. But there are no channels below Channel 1 and there is a header showing "!!!UNTESTED HARDWARE!!!.

I have attached the Support Data file (.tgz) and here is the Sysinfo:

 node: KE0NA-MSP-LHG
model: MikroTik RouterBOARD RBLHG-2nD
boardid: MikroTik RouterBOARD RBLHG-2nD
Device has not been tested. Please file a ticket with your experiences.
br-lan 48:8F:5A:7B:73:D4
eth0   48:8F:5A:7B:73:D4
eth0.1 48:8F:5A:7B:73:D4
eth0.2 48:8F:5A:7B:73:D4
tunl0  00-00-00-00-00-00-00-44-00-00-00-00-00-00-00-00
wlan0  48:8F:5A:7A:73:D4
wlan0-1 4A-8F-5A-7A-73-D4-00-44-00-00-00-00-00-00-00-00
system type : Qualcomm Atheros QCA9533 ver 2 rev 0
machine : MikroTik RouterBOARD RBLHG-2nD
processor : 0
cpu model : MIPS 24Kc V7.4
BogoMIPS : 432.53
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa : mips1 mips2 mips32r1 mips32r2
ASEs implemented : mips16
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

Thank you for your help,

Dave - KE0NA
Support File Attachment: 
nc8q's picture
Please file a ticket with your experiences.

Hi, Dave:

 Short answer: (*)Please file a ticket with your experiences.

Medium answer: I find it very obtuse to understand what that(*) means.
The developers use '' for collaboration.
Someone should 'file a ticket' on about this issue.

Long answer:
I think:
- Mikrotik has changed the 'boardid' or 'board_name' on a functionally identical product.
- When the aredn*.elf file loads, it discovers the current 'boardid'.
- if the .elf file finds a match in a lookup table, it sets 'sysinfo/board_name' to a valid value, else sets to 'unknown'.
- When the aredn*.bin file loads, it obtains the 'board_name' and sets appropriate configurations.
- In your case: the aredn*.bin file is finding: board_name='unknown'.
- If your board
MikroTik RouterBOARD RBLHG-2nD is identical to a former
MikroTik RouterBOARD LHG-2nD board
then you may be able to fool the aredn*.bin file into setting configurations appropriate for your device.
I do not know what the value is for 2.4 GHz Mikrotik LHG devices.
I have done this with new 'RBLHG-5HPnD-XL-INTL' devices.
I hope this helps.



KE0NA's picture
Thank you Chuck, my apologies

Thank you Chuck, my apologies for submitting my "ticket" in the wrong place. I did not want to go into too much detail with the difficulty we had gettting the .bin file loaded, but we ended up overwriting "unknown" in the "sysinfo/board_name" file with the value of a board in the list of supported devices to do so. 
I would like to try the method you suggested, where would I enter the value "MikroTik RouterBOARD LHG-2nD board" and at what point in the load process?


nc8q's picture
where would I enter the value

Hi, Dave:

 No apology anticipated, warranted, or expected.

 You did not submit a 'ticket' in the wrong place, because you did not submit a 'ticket'.
You placed a 'post' in a 'forum'.
'Tickets' about an AREDN issue would be placed on ''.
I think.

 I was intentionally vague about what to enter and not so vague about where.
My ticket (aredn_ar71xx/issues/572) was about a new Mikrotik LHG HP5nD-XL-INTL.

 Until the developers correct your (yet to be ticketed. (Hint.)) issue and release a Nightly Build,
you may be able to set an appropriate value into sysinfo/board_name.
"at what point in the load process?"
Before my issue was fixed in a Nightly Build, I set the value to
before TFTP'ing the .bin file.

I hope this helps,

KE0NA's picture
RE: submitting an AREDN GitHub ticket

Hello Chuck,

I had to remember my GitHub password, it has been a few years since I logged in (retired 3 years ago) :-) - thanks for the hint... GitHub ticket #582 sumitted.
So in the meantime, I should try putting (in my case) the string "rb-lhg-2hpnd" into the "board_name" file after loading the .elf file, then perform the sysupgrade on the aredn*.bin (daily build)?


nc8q's picture
I should try putting...

I would, but I am fearless.

KE0NA's picture
Updated aredn*.bin will be in next Daily Build

Joe, AE6XE has inform me that the fix will be available in the next Daily Build.

Thank you Joe!

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer