I'm trying to install the AREDN software on a MikroTik LHG XL 5 ac (P/N RBLHGG-5acD-XL). I can load the rb.elf file using the Tiny PXE server and the file appears to install properly. When I connect using a browser I see the initial AREDN screen. However, the NOCALL header on the screen has no suffix. It just says “NOCALL” and nothing else. At this stage of the procedure, after installing the rb.elf file, I'm used to seeing a header that says "NOCALL-XXX-XXX-XXX". If I then install the SysUpgrade software, the node accepts the SysUpgrade file and I am able to connect to it with a browser using the 192.168.1.1 IP address. When I try save the configuration with a Node Name and Password, I get an error message saying that I have an "invalid Mesh IP address". Looking at the Mesh IP address, it shows up as 10.0.0.0.
My understanding is that the Mesh IP address is derived from the MAC address of the hardware, so is there some reason that AREDN software is not able to read the MAC address of my MikroTik LHG unit?
I've tried installing the AREDN software on the MikroTik LHG multiple times using the 2368, 2378, 2390, and just today the new 2397 nightly build. All four show the same behavior.
Maybe I'm doing something wrong. I've installed the software successfully multiple times on the MikroTik hAP ac Lite units but this is my first time installing on the MikroTik LHG.
.
Thanks for any help.
73,
John, KM6ZJT
The Support Data file for the node is attached.
You are here
“Invalid Mesh IP Address” error when installing on MikroTik LHG 5 ac
Mon, 03/06/2023 - 15:14
#1
“Invalid Mesh IP Address” error when installing on MikroTik LHG 5 ac
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
After the SYSupgrade did you switch back to DHCP and reboot for a new IP address?
I switch the computer from a fixed IP address to obtaining the IP address automatically right after the rb.elf file is loaded onto the node using the Tiny PXE server and before uploading the Sysupgrade file. The computer then reconnects to the node without any problem. I'm able to then upload the Sysupgrade file but when I attempt to save the initial configuration (after adding the Node Name and Password) it gives me the Invalid Mesh Address error.
As i noted above, the initial screen displayed after the rb.elf file is loaded onto the node is just "NOCALL" without the IP address extensions that I'm used to seeing and the Mesh IP Address shows up as 10.0.0.0. It seems to me that after loading the rb.elf file I should be seeing a header with the format NOCALL-XXX-XXX-XXX. I could be wrong about that. I recognize that the actual IP address of the node will remain 192.168.1.1 until the final configuration is saved.
Thanks very much for responding. I've tried loading the AREDN software on this node many times now.
I'm getting a lot of practice with the MikroTik NetInstall utility.
One other note, I'm using the procedure for the MikroTik hAP ac Lite as a guide for this installation. That device has five ports and there is a point in the procedure where you move the ethernet cable from Port 1 to Port 2 after loading the rb.elf file. The MikroTik LHG has only one port so I just leave the cable connected to that one port as I progress from loading the rb.elf file to uploading the Sysupgrade file. Since I can't move the cable to another ethernet port, I'm wondering if I'm missing some other step at that point.
73,
John, KM6ZJT
Denis KD1HA
As suggested, I tried redoing the installation. I used the new 2405 build. I switched from the fixed IP address to DHCP after uploading the Sysupgrade file but before saving the configuration. It made no difference. The procedure went exactly the same. The AREDN screen still shows a Mesh IP address of 10.0.0.0 and because of that it gives me the "invalid Mesh IP address" error when I try to save the configuration.
At this point, I tried entering a valid subnet 10 address into the AREDN Setup screen. When I did that, I got a new error:
nv parameter 'MAC2' in file '/etc/config.mesh/_setup.default' does not exist
That was interesting because it gave me a path to where that value is stored. Taking it one step further, I ssh'd into the node and navigated to the file referenced in the error message. That file has a line that says:
wifi_ip=10.<MAC>
As a test, I replaced <MAC> with an valid IP address. Going back to the Setup screen the new Mesh IP was visible. When I tried to save that configuration, I got a new error message:
nv parameter 'DTDMAC' in file '/etc/config.mesh/_setup.default' does not exist
There is also a line in the _setup.default file that says:
dtdlink_ip=10.<DTDMAC>
I don’t know what the DTDMAC address is supposed to be so I stopped there. And I’m not knowledgeable enough to figure out where the MAC and DTDMAC, which seem to be variables, are getting their values.
I know that the inability of the AREDN software to read the MAC address is not a hardware problem because when I use the MikroTik WinBox utility it reads the MAC address fine.
I’m stumped. I guess I’ll just wait for the next nightly build.
73,
John, KM6ZJT
Unfortunately, my understanding is that the software for the RBLHGG-5acD-XL part number is only available in the Nightly Builds. I could be wrong about that. If you could point me to a stable build for the RBLHGG-5acD-XL, that would be great. The information on the nightly build web page says it's stable but I'm not so sure.
Thanks for responding.
I've also reposted this issue as a possible bug here: https://www.arednmesh.org/content/problem-initial-install-mikrotik-lhg-nightly-build-2405
73,
John, KM6ZJT
I can load the 'initramfs-kernel.bin' then load the 'sysupgrade.bin', but
after that the device goes brain dead.
73, Chuck
Hi, Chuck.
I have not used the SXTsqG-5ac. I have two hAP AC Lite devices and now the LHG device. When I did the hAP for the first time, it took me a number of attempts to get the software to load properly. All three of my devices have come from the factory with an initial IP address of 192.168.88.1. If I leave that IP address as is at the start when doing the installation process, with the plan of changing the computer over to 192.168.1.10 after the rb.elf file is loaded to re-establish communication with the MikroTik device (which then has an IP address of 192.168.1.1), it seems I always lose the connection and I can't get it back. Because of that problem I always change the IP address on the MikroTik device to 192.168.1.1 before starting the AREDN installation procedure. If I do that, the procedure works fine (at least on the hAP). Did your SXTsqG-5ac come from the factory with an initial IP address of 192.168.88.1? If so, did you change it to 192.168.1.1 before trying to load the AREDN software?
John, KM6ZJT
https://www.arednmesh.org/content/installing-aredn-firmware-mikrotik-usi...
Thanks, K6CCC.
I do have a dumb switch between the node and my computer throughout the installation process.
I reviewed the presentation. Could you clarify in what way you believe I'm not following the procedure in the presentation? The only thing I may have done differently is that I've changed the computer to acquire its IP address automatically at a different point. The presentation says to do it after loading the rb.elf file. Interestingly, both the instructions on the AREDN web site and the MikroTik First Install Checklist both say to do it at the very end, after uploading the sysupgrade file, configuring the node, and saving the changes. That's the point where the node's LAN address changes from the 192.168.1.1 to 10.XXX.XXX.XXX. Actually, I've tried the procedure multiple times and tried changing to DHCP both after loading the rb.elf file and after loading the sysupgrade file. Neither of those have worked. And since I can't save the configuration after loading the sysupgrade file, I can't get to that last step.
I can load the AREDN software onto the MikroTik hAP ac Lite very reliably but I just can't seem to get this LHG node done.
I do appreciate you reviewing my lengthy problem description and for providing the presentation.
73,
John, KM6ZJT
You said you are trying to use the 192.168.88.x address range.
I think what you are referring to is that I said, "All three of my devices have come from the factory with an initial IP address of 192.168.88.1". What I was saying was that, as received from the factory, all three of my devices have had that default IP address. In my early attempts at installing the AREDN software on the MikroTik hAP a couple of years ago, I attempted to do the installation starting with that IP address. It wouldn't work. I learned that the first thing I need to do, before starting the AREDN installation, is to change the IP address of the node to 192.168.1.1 using MikroTik's RouterOS. That's the only way I can get the installation process to work on the MikroTik hAP. And that's what I've been doing with the MikroTik LHG. I don't see that recommendation to start with an IP address of 192.168.1.1 in the AREDN procedure so I was just asking Chuck if he makes that change before starting the installation process on his SXTsqG-5ac. I probably could have worded my comment to Chuck a little more clearly.
73,
John, KM6ZJT
Nope. Don't need to do that. When you put the node into NetInstall mode (RouterOS term), it becomes a DHCP client of the PXE server.
The approach of leaving the hMikroTik hAP ac Lite IP address as 192.168.88.1 (as it comes from the factory) and then using the AREDN installation procedure as it is written hasn't worked for me. It's great if you are able to get that to work. Do you think that when I change the IP address of the MikroTik LHG to 192.168.1.1 using RouterOS before I begin the AREDN installation process it is causing my problem in getting the "invalid Mesh IP Address" error message?
Do you think that when I change the IP address of the MikroTik LHG to 192.168.1.1 using RouterOS before I begin the AREDN installation process it is causing my problem in getting the "invalid Mesh IP Address" error message?
Reference: https://docs.arednmesh.org/en/latest/arednGettingStarted/installing_firmware.html#mikrotik-first-install-process
This thread is about difficulty loading Nightly Build firmware on the new 802.11ac devices.
Hi, John:
When using the TFTP method of loading firmware on Mikrotik devices, the devices start with no IP address then receive one from the TFTP server. I feel it is best to use the 192.168.1.0/24 network throughout the initramfs-kernel.bin and the sysupgrade.bin loads. After the sysupgrade.bin first install finishes, the device is now a (DHCP) server and then the workstation needs to switch to an IP client mode.
73, Chuck
If so, did you change it to 192.168.1.1 before trying to load the AREDN software?
Hi, John:
No, I used 192.168.1.1 from beginning through loading the 'initramfs-kernel.bin' file.
Here is my procedure:
My computer does not lose its 192.168.1.9 address until I change it to DHCP client afterwards.
I have tried this procedure with a simple ethernet switch with the same results...failure.
73, Chuck
I'm continuing to investigate my problem. Not sure I'll ever get it to work.
73,
John, KM6ZJT
Many thanks to the AREDN development team for their quick response.
73,
John, KM6ZJT