Got shiny new hap-ac today. Tried the windows trick to load aredn, it failed. switched to RPI and dnsmasq method .
Multiply attempts fail to load the current nightly build elf file.
Cold stated hap-ac load most current firmware (6.43.3 (2018-Oct-05 13:12).
attached file has dhcp log from fail elf load and latest info on stock firmware.
any ideas??
regards
mike
Multiply attempts fail to load the current nightly build elf file.
Cold stated hap-ac load most current firmware (6.43.3 (2018-Oct-05 13:12).
attached file has dhcp log from fail elf load and latest info on stock firmware.
any ideas??
regards
mike
File Attachment:
RB952Ui-5ac2nD-US is the supported model. Not RB592....
Being a very senior citizen, I do not see so good and type even worse
MODEL NUMBER = RB952Ui-5ac2nD-US
regards
mike, this looks more like there is a cable connector problem or something -- getting errors trying to transfer the file. It looks like the device isn't getting the image to then say it's compatible or not. Try different switch or cable, make sure nothing is damaged on the pins in the RJ45 connectors both male/female.
Does it boot with RouteOS and can be accessed with a browser, to confirm the hardware is working out-of-box?
Joe AE6XE
Tried the RPI things more times than I count and the windows as well.
Additional info, the windows attempt reports:
10:22:26 PM ROOT=C:\Users\Mike\Downloads\mikrotik\
10:22:26 PM DHCPd 192.168.1.10:67 started...
10:22:26 PM TFPTd 192.168.1.10:69 started...
10:22:27 PM HTTPd:80 started...
10:22:42 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:42 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:42 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:43 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:43 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:43 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:43 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:43 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:44 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:44 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:44 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:44 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:44 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:45 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:45 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:45 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:45 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:45 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:46 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:46 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:46 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:46 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:46 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:47 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:47 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:47 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:47 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:47 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:48 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
10:22:48 PM DHCPd:unrecognised bootp packet, MAC:CC-2D-E0-FC-16-51, 0
while the RPI still says failed sending the elf file.
this post done with windows laptop (that failed upload) connected to internet port via netgear AP to my comcast, laptop to port 2 of hap
no clue as to what I manage to get wrong over and over...
I really appreciated you support, I know I must be a PIA
Best Regards
Mike
RPI never worked
Ray's pserver method never worked
I switched to:
TFTPD32 and TFTPD64 are copyrighted 1998-2018 by Philippe Jounin (philippe@jounin.net) and released under the European Union Public License 1.1 (see either the help file or the file EUPL-EN.pdf for the full text of the license)
Official site: http://tftpd32.jounin.net
after I figured out the setup and about 20 retries, the elf file loaded and everything else went as defined in loading mikrotik. It acted like the new hap didn't like the dhcp conversation on the boot sequence. I have no idea why it decided to play nice, but sure am glad it did.
The system is doing usb power pass through. To tired to mess with other things tonight.
Thanks for your support
Best Regards
mike
For or some reason this unit simply would not take the elf file.
regards
mike
I loaded my Mikrotik hap ac lite and was successful on my first attempt using the Windows method. I ran the Youtube video done by Ray KK6RAY on my tablet and just followed along step by step. I did have to pause an replay a few segments but overall it was fairly easy. Thanks, Ray. Now looking forward to what I can do with this new little node.
David - N5MXI
Doug