You are here

hAP ac lite .elf file load

16 posts / 0 new
Last post
KN4BAR
hAP ac lite .elf file load

Hi All:
New to AREDN. Have flashed two M2 radios OK. Trying to flash a brand new, right out of the box hAP ac lite RouterBoard with no success. Does the router need the quicksteps configuration routine first to make it useable, or should it be flashable right out of the box??? I am getting this dialog from the tiny PXE server when trying to install the .elf file:

2:30:32 PM DHCPc:discovering for another DHCPd on LAN
2:30:32 PM ROOT=d:\Downloads\pxesrv\files\
2:30:32 PM DHCPd 192.168.88.34:67 started...
2:30:32 PM TFPTd 192.168.88.34:69 started...
2:30:32 PM HTTPd:80 started...
2:30:37 PM DHCPc:no other DHCPd discovered
2:31:12 PM DHCPd:REQUEST received, MAC:48-8F-5A-E1-19-1C, XID:E4886FC5
2:31:12 PM DHCPd:BOOTP REQUEST
2:31:12 PM DHCPd:ACK sent, IP:192.168.88.120, XID:E4886FC5
2:31:22 PM DHCPd:REQUEST received, MAC:48-8F-5A-E1-19-1C, XID:FBC37F56
2:31:22 PM DHCPd:BOOTP REQUEST
2:31:22 PM DHCPd:ACK sent, IP:192.168.88.120, XID:FBC37F56
2:31:59 PM DHCPd:DISCOVER received, MAC:48-8F-5A-E1-19-1C, XID:9624AEC7
2:32:00 PM DHCPd:OFFER sent, IP:192.168.88.110, XID:9624AEC7
2:32:00 PM DHCPd:REQUEST received, MAC:48-8F-5A-E1-19-1C, XID:9624AEC7
2:32:00 PM DHCPd:ACK sent, IP:192.168.88.110, XID:9624AEC7
2:33:45 PM TFTPd stopped...
2:33:45 PM DHCPd stopped...
2:33:45 PM HTTPd stopped...
nc8q
nc8q's picture
?quicksteps configuration routine?

Does the router need the quicksteps configuration routine first to make it useable, or should it be flashable right out of the box?

The Mikrotik hAP AC lite (RB952Ui-5ac2nD) should be flashible right out of the box.
Installation instructions are here:
 https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#mikrotik-first-install-process
I use linux. I cannot assist with a windows install.
What is 'quicksteps configuration routine' ?

I hope this helps,
Chuck
 

KN4BAR
Thanks Chuck:

Thanks Chuck:
"quickstart" referred to instructions in the RouterBoard box for configuring the router as a wireless AP.
I saw another post about this same problem from earlier this year....never saw what the resolution was.
Two questions that were asked....is the PC being used the only DHCP available and was the firewall properly allowing traffic from the tiny PXE server. My answer to both questions is YES. I am following the published instructions to the letter.
 

nc8q
nc8q's picture
"quickstart" referred to

"quickstart" referred to instructions in the RouterBoard box for configuring the router as a wireless AP.

Thanks for the explanation. I have never read the instructions in the box.
The boot-loader may be the same, but the firmware and configuration is dissimilar.
Under AREDN firmware, the 2.4 GHz or 5.8 GHz radios may be configured as a AP, but not both at the same time.
or
As an AREDN node, the 2.4 GHz radio operates in Ad-Hoc mode, not AP mode.
or
With AREDN firmware, the 2.4 GHz radio can be operated as a Client and connected to a standard AP.
But we digress.

I saw another post about this same problem from earlier this year....never saw what the resolution was.
Please share the URL of this post.

So, your error is at step (4.) ?
PXE Boot: Windows Procedure

    You will need to install and configure a PXE Server on your Windows computer. The example below uses Tiny PXE which can be downloaded from erwan.labalec.fr. There may be other alternative Windows programs that accomplish the same goal, such as ERPXE or Serva.

...
     4. 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.


Chuck



 

kd4twj
Button hold time

I just loaded my first hAP AC lite last week.  It was fresh out of the box.  I followed the standard instructions that nc8q referenced.  I was using Linux (Debian). The one mistake that I was making initially is that I was releasing the reset button after I saw the communication occurring between the MikroTik and PXE in the console window. I saw the status on DHCP, etc... 
I needed to hold the button longer for the TFTP to properly initialize, roughly 20 seconds, as indicated in the instructions. 

That may not be your issue, but I figured that it was worth mentioning. 

Good Luck

Dean 
 

K6CCC
K6CCC's picture
Use these instructions

I don't know which set of instructions you are using (there are several), but this is what I have used with absolute 100% success on every Mikrotik device I have flashed.
https://www.arednmesh.org/content/installing-aredn-firmware-mikrotik-usi...
Do include the part about having a switch in between the MT device and your PC (BTW, that is for the benefit of your PC, not the MT).
 

AF4H
DHCP OK but no TFTP?

It looks to me like DHCP is issuing an IP, but the router is not pulling from TFTP. Is your assessment the same?

Just to confirm as well, your router is cabled to the PC via the WAN port, and you're holding the reset button from the time power is applied to the router through the time the TFTP completes?

I did the flash successfully on a hAP AC Lite fresh out of the box, so there is no need to do the initial configuration through RouterOS.

Like Chuck, I did my config via a Linux host... Maybe it would help to link us to the config.ini and a screenshot of the Tiny PXE setup?

KN4BAR
yes. PC to WAN port via a

yes. PC to WAN port via a dumb switch. patch cables checked and OK. I've attached a screen shot of the tiny PXE server setup and the config.ini file. I have even tried disabling Win 10 firewall to to this and just keep getting the same results.

Image Attachments: 
File Attachment: 
nc8q
nc8q's picture
select your Ethernet interface IP from the dropdown list called

Earlier in 'Preparation', instructions are to set your PC's ethernet device to a static address. e.g. 192.168.1.100
You need to put this address in the 'Step (3.)' (PXE setup)
select your Ethernet interface IP from the dropdown list called Option 54 [DHCP Server]
You have 192.168.88.54 instead.

I think,
Chuck


 

KG7GDB
Newer Mikrotik hAP ac have a 192.168.88.1 factory address

The hAP ac lite flash procedure is somewhat tricky, and the install directions are incorrect about the latest Mikrotik factory addresses. The newer ones use 192.168.88.1, not 192.168.1.1
I wrote a very detailed step-by-step procedure for our Willamette Valley Mesh Network users. I think you will have success if you follow my lead and use the static address of 192.168.88.100 for your PC.
Here is the link to my instructions (it is a long post, but I tried to put in all the steps):
https://groups.io/g/WVMN/message/285
My instructions were written for the AREDN v 3.20.3.1 firmware. Make sure to use the new 3.21.4.0 files:
aredn-3.21.4.0-ar71xx-mikrotik-vmlinux-initramfs.elf and aredn-3.21.4.0-ar71xx-mikrotik-rb-nor-flash-16M-ac-sysupgrade.bin
73,
Brett, KG7GDB

AB7PA
Reason for 192.168.1.x range

The nice thing about using dnsmasq (Linux) and Tiny PXE (Windows) is that you set the IP address range to anything you desire.  The node will automatically receive an IP address in the desired range, no matter what the default IP address is on the manufacturer's equipment.  We suggest using 192.168.1.x because that will be the default IP address range you'll eventually need in order to complete the AREDN configuration.  Using 192.168.1.x simply saves a step later -- and it may eliminate confusion for some people.

KN4BAR
GOOD NEWS. Success at loading

GOOD NEWS. Success at loading the AREDN firmware into my HAp ac lite routerboard. The ONLY thing I change from what I had been doing was to use the ....88.100 IP for the DHCP server address. I thought any .xxx adress was allowed and was using 54. When I changed that to 88.100 the .elf firware loaded just as it should.

Thanks to everyone who gave me their thoughts on solving my issue.

73, Paul KN4BAR

w8erw
w8erw's picture
192.168.1.100

The newer hAP AC Lite devices appear to use 192.168.88.100.  I just flashed three. 

nc8q
nc8q's picture
Online docs: installing on Mikrotik devices: Suggestion

https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#mikrotik-first-install-process
...
PXE Boot: Windows Procedure
...
Suggestion
Change:
3. Start the Tiny PXE server exe and select your Ethernet interface IP from the dropdown list called Option 54 [DHCP Server], making sure to check the Bind IP checkbox. Under the “Boot File” section, enter rb.elf into the the Filename field, and uncheck the checkbox for “Filename if user-class = gPXE or iPXE”. Click the Online button at the top of the Tiny PXE window.

To:
3. Start the Tiny PXE server exe
  a. select your Ethernet interface IP address from the dropdown list called Option 54 [DHCP Server]
  b. check the Bind IP checkbox
  c. Under the “Boot File” section, enter rb.elf into the the Filename field
  d. uncheck the checkbox for “Filename if user-class = gPXE or iPXE”
  e. Click the Online button at the top of the Tiny PXE window.

-----
Added 'address' in 3.a.

Chuck

K6CCC
K6CCC's picture
First of all, I'm glad you

First of all, I'm glad you got it.
With that said, I am a fairly extensive Mikrotik router user for non-AREDN use, and I think there is some confusion and it maybe at least partially causing part of the issue.  Except for some of the very high end devices, every Mikrotik RouterOS device from the factory comes with port 1 configured as the WAN port and is a DHCP client, and the remaining ports are bridged together and have a DHCP server in the 192.168.88.x subnet.
When you do the initial flash of a hAP, you are connecting your PC to port 1 and the PC is operating as a DHCP server.  The screen captures posted earlier show that you have the PC set for a 192.168.88.x address and therefore PXE server is assigning a 192.168.88.x address to port 1 of the hAP.  That means that both the WAN port (port 1) and the bridged LAN ports (the remaining ports) are both operating with addresses in the 192.168.88.x subnet.  This WILL causing routing problems in the hAP because it now does not know where to send packets destined for 192.168.88.x addresses.  The instructions I posted on 17 July specifically state to set your PC to a 192.168.1.10 address.  That specific address is not the important part, but some subnet OTHER THAN 192.168.88.x is important.  Note that AFTER the initial flash, your PC will need an address in the 192.168.1.x subnet, however if you followed instructions,your PC will be set as a DHCP client at that time...
As I said on the 17th, the instructions I posted have worked absolutely 100% of the time as long as you follow the directions.
BTW, all of this assumes a Mikrotik with FACTORY configuration.  RouterOS is very powerful and if someone changed the configuration in RouterOS, lots of things could be different.  RouterOS allows you to change almost any port configuration.  Port 1 on a hAP being a"WAN" port with that port having a DHCP client is the facoty config, but CAN be changed in RouterOS.
 

w8erw
w8erw's picture
192.168.1.10 vs 192.168.88.100

Indeed this is some clarification.  I did attempt your recommended settings without initial success.  Remembering earlier comments in the documentation section, I went ahead and used 192.168.88.100 which eventually did work.  My guess is that my first attempt failed because of something left over from the earlier units in the PC memory etc.  The next time, I shall insure everything is purged to a clean environment first before proceeding with 192.168.1.10.  Than you for your response and clarity.  Jim W8ERW

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer