Hi
This is my first post on the forum and I hope this has not been covered before.
I have a MikroTik RB911G-5HPnD-QRT antenna that was left attached to my home after I switched to a different ISP about 2 years ago. I had the antenna sitting in a box and thought I would try and install the AREDN firmware on it. I see the antenna is listed in the supported devices.
I have tried the procedure at https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#mikrotik-first-install-process. The only difference is the IP of the antenna is 192.168.88.1. I go through the instructions and I get to the point that the PXE server says "TFTPd: DoReadFile: rb.elf". I click the offline button but the antenna never reboots and I cannot log into it via a web browser.
I'm not sure what I am doing wrong?
Thanks
Kent
N6WT
You are here
MikroTik RB911G-5HPnD-QRT
Sat, 04/09/2022 - 20:27
#1
N6WT
MikroTik RB911G-5HPnD-QRT
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
Kent, since the rb.elf file was successfully sent the QRT should load it temporarily into RAM and come up on the address of 192.168.1.1. That's where you should look for it.
Orv W6BI
If you need more detailed instructions I hang out in CQ805 on Slack.
Use 192.168.1.10 on your computer and .100 as the pool start and turn off the firewall. If this doesn't work, there is something else being done incorrectly--make sure to hold the reset button until the rb.elf transfers. It may take longer than "20 seconds" if Windows does its lazy bring-up-the-network-nonsense. (A dumb switch in between doesn't hurt).
Key point: If you see any mention of 88 at this point, the QRT booted RouterOS and not the rb file you're trying to send it.
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#mikrotik-first-install-process
Hi, Kent:
"The only difference is the IP of the antenna is 192.168.88.1."
There should not be any difference(s) if you follow the instructions.
"192.168.88."
is not mentioned in the install instructions for the Mikrotik devices.
Please tell us the step(s) immediately before "the PXE server says "TFTPd: DoReadFile: rb.elf"
I hope this helps,
Chuck
Chuck
To log into the QRT antennas MikroTik OS I must use 192.168.88.1. So to get the antenna to read the rb.elf file from PXE is to set my computers IP to 192.168.88.XX.
Orv suggested that after the rb.elf file is read the AREDN firmware uses 192.168.1.1. I have tried both 192,168.88.1 and 192.168.1.1 now and still no joy.
One of the important functions of a PXE server is to give the node an IP address via DHCP as well as providing the firmware image via tftp. Therefore, you do not need to use the 192.168.88.x address because the device will receive an IP address on the subnet being served by your PXE server. This is described in the link from the AREDN documentation that gives additional details about PXE servers (https://en.wikipedia.org/wiki/Preboot_Execution_Environment). Look under the Details section in that link for more information about PXE.
The reason AREDN suggests using the 192.168.1.x network is to eliminate the need to change IP addresses on your computer during the install process. The AREDN firmware will use the 192.168.1.x network once it is loaded, so using it all the way through the process will simplify things for you.
I have tried 192.168.1.x. The only way I could get the "TFTPd: DoReadFile: rb.elf" was to use 192.168.88.50.
One suggestion would be to take the radio to someone local in your area who can look at the device. I've flashed a bunch of QRT5 radios and we find them to be really good AREDN nodes -- they have full one watt output with a very nice high-gain panel. I'm sure someone in your area can help with flashing it.
Hi, Kent:
'I go through the instructions and I get to the point that the PXE server says "TFTPd: DoReadFile: rb.elf". '
Good this far.
"I click the offline button but the antenna never reboots and I cannot log into it via a web browser."
How did you determine that the device(QRT) never reboots?
Omitted is the part where you put your computer's ethernet on a 192.168.1.X/24 address. Any address in the range 2 to 254 should work. Documentation suggests using 192.168.1.100.
"With the unit powered off, press and hold the reset button on the node while powering on the device.
Continue holding the reset button until you see TFTPd: DoReadFile: rb.elf in the Tiny PXE log window.
Release the node’s reset button and click the Offline button in Tiny PXE.
You are finished using Tiny PXE when the elf image has been read by the node.
The node will now automatically reboot with the temporary AREDN® Administration image.
Install the sysupgrade Firmware Image.
After booting the elf image(comma) the node will have a default IP address of 192.168.1.1.
Your computer should already have a static IP address on this subnet, but if not then give your computer an IP address on this subnet."
If "With the unit powered off, press and hold the reset button on the node while powering on the device.", then
the QRT will have no IP address until it gets one from your TFTP-server.
If you can set your TFTP-server to issue a 192.168.88.50 address, then it should be able to issue any IP address...
including 192.168.1.100.
KJ6VMH, K6ZAP, and KB6BF are nearest you and have upgraded their Mikrotik nodes this calendar year.
Perhaps you can arrange some in-person assistance.
I hope this helps,
Chuck
Greetings HB9TVP
Reference:
Critical: There must be only 1 DHCP server on the network of your workstation and AREDN device.
Suggest: Please use 192.168.1.x instead of 192.168.88.x on your workstation/PXE-server.
73, Chuck
How are you testing that the router does not start after loading the .elf file?
73, Chuck
I am not familiar with using the LEDs as a diagnostic tool.
Once "09:05:21 TFTPd:DoReadFile:rb.elf B:1452 T:0" displays, you are done with the TFTP server
and you switched PXE offline. Good.
Now, I do not understand "Communication is also blocked???".
The Mikrotik device should now be on 192.168.1.1.
Is your computer still on 192.168.1.110?
Can you PING the Mikrotik at 192.168.1.1?
If yes, using your favorite browser, can you display http://192.168.1.1 ?
73, Chuck
The Mikrotik device should now be on 192.168.1.1.
Is your computer still on 192.168.1.110?
Can you PING the Mikrotik at 192.168.1.1?
If yes, using your favorite browser, can you display http://192.168.1.1 ?
I do not understand "It doesn't seem to be blocked with any IP ????"
- After PXE reports '14:09:23 TFTPd:DoReadFile:rb.elf B:1452 T:0',
- The Mikrotik device will reboot.
- The Mikrotik device should now be on 192.168.1.1.
- Is your computer still on 192.168.1.110?
- Can you PING the Mikrotik at 192.168.1.1?
- If yes, using your favorite browser, can you display http://192.168.1.1 ?
73, ChuckI tried this with different IP addresses including 192.168.88.xxx
Gruss Urs
I think I should bow out and let a Windows guru follow up.
I do have 2 queries:
1. It seems that your workstation (+PXE server) is using 192.168.1.10.
It seems that its PXE server is offering 10 DHCP addresses: .11 through .20.
I am baffled where/why 192.168.1.21 is mentioned in your .PDF
2. Your .PDF contains 'mikrotik enshalten mit reset' :: Mikrotik shut off with reset!
The Mikrotik RB911 should reboot after the rb.elf upload, but it should not be shut off
until after the factory.bin has been loaded and configured!
The device should be powered up in TFTP mode and not be powered down until after
the new factory.bin firmware is configured.
73, Chuck