You are here

Perplexed - Hap AC Lite assigns IP but Camera not Pingable

7 posts / 0 new
Last post
W5SAT's picture
Perplexed - Hap AC Lite assigns IP but Camera not Pingable

I can't figure out this problem.  For a couple of weeks, I had an Amcrest IP camera on one of the LAN ports of my MikroTik hAP AC Lite working just fine.  A few days agao, I realized I couldn't access the camera.  Checked all of the usual things but couldn't access the camera even though the AC Lite was assigning a DHCP address.  I put the camera on my home router, it got a IP address and worked fine.  I factory reset the camera, tried again on the AC Lite and still can't ping or access the camera in any way and can't pull in a RTSP stream either.  Tried a differnt Amcrest IP camera and the same problem - the camera gets an IP address on the LAN port of the AC Lite but is unreachable.  Everything else on the AC lite gets an IP and works fine. 

I even SSHed into the AC lite and cannot ping the camera(s) from the command prompt.  

In short, two different cameras that used to work on the AC lite will no longer work even though they both work fine on my home network router.

I'm stumped and could really use some help on this one.  Here is a screen shot fo the Hap AC Lite DHCP section.

nc8q's picture
ping .vs. nmap
Is either camera discoverable with nmap? has Windows binaries in case you are not running Unix, Mac, Linux, BSD,...
Did the cameras respond to pings before?

W5SAT's picture
Chuck, No - Nmap is not
Chuck, No - Nmap is not showing the cameras.  Yes, the cameras responded to pings (and web GUI) before this happened...

I could just go back to "factory fresh" on the AREDN firmware and start over I suppose.  I have spent a few hours trying to sort out this mystery - I was hoping for " Oh yea, that's a known bug" solution. :)

nc8q's picture
Maybe try the failsafe 5 if/then/else 15 second reset b4 factory

Failsafe Mode

Failsafe Mode is a method of restoring a node to an operational state.

Reset Password or DHCP:

After the node fully boots press and hold the reset button for 5 seconds which will cause the unit to enable DHCP and reset the root password to 'hsmm'.

Full Failsafe:

After the node fully boots press and hold the reset button for 15 seconds which will cause the unit to behave as if it had just been flashed with the AREDN™ firmware.

You would need to go through the node settings again just as if it was the first time installing the AREDN™ firmware on the node.

w6bi's picture

Although not identical, I had my home hAP AC Lite assign an IP address near, but not IN its DHCP address pool to a Sunba 405DX ECO camera.  It didn't show up in the list of allocated IP addresses, though.  I found it with an NMAP scan.  The camera was not pingable at that address though.  Very strange...

Do you have enough direct host addresses?
The default mode for LAN is direct host 5, so perhaps you are out of addresses especially if you have several reservations. If you reset, assign 13 host direct. Reboot. Sign in again. Update OLSR. 
The first time I used the hAP in a demo, I had everyone try to sign in, and only four people could do that. It ran out of addresses. 
Brett, KG7GDB 
W5SAT's picture
Thanks everybody for the
Thanks everybody for the insight and ideas.  In the end a reset was needed back to factory fresh AREDN (holding the reset mutton as Chuck NC8Q suggested.

BTW, I was only using 3 of the DHCP addresses and I did try the OSLR restart to no avail.

It only took 10 or 15 minutes to setup the Hap AC Lite again after the reset so not a lot of effort.


Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer