hap lite works fine but not reachable from LAN

Hi there,

I recently bought a HAP lite for using it as a swich + Access Point (to widen the coverage of my current WLAN setup)
I took out of the box, set standard config as AP+switch, given static IP as per my LAN (192.168.1.x) , and changed SSID to my current one (of course same password).
I tested it with my iMac (HAP lite with port 1 to my DSL router, iMac on port 2) and everything was OK and smooth.

So I installed the HAP lite in its final position (under TV to act as a switch for my AppleTV and a miniPC), again all OK (switch and AP functions)

The point is that, even if from the DSL router I see “something” with the IP address of the HAP lite, I cannot access the HAP lite anymore.
No web interface, no SSH. I can just ping it but no way to see the config page.

Thinking to have done something wrong, I removed the HAP lite, reset it (I couldn’t access it !) and made same config and tests.
Again all OK, but again once placed under the TV… same. HAP lite seen from the router but no config page or SSH access.

What did I wrong for not being able to access it anymore?
What can I do to access it (for example to switch AP on/off) ?

thanks since now to who will help me!

Did you configure auto-updates?
This just happened to me when I ran an update. Not sure what the solution is yet.

I would expect an IP conflict - when your router assigne the same ip to a device as you assigned to your hAP Lite.

Try to connect to it via winbox by MAC address (you can find MAC address on a sticker somewhere on you hAP Lite).

Sorry for late replies (I didn’t switch on notification for replies) and thanks for yours
Unfortunately I still have the same problem, it seems the only way (from other RouterOS forums) is to factory reset and disable the firewall, but it doesn’t look good to me !

@matuss : from the DSL router I see that all addresses assigned are via DHCP (192.168.1.10x) and the HAP lite has 192.168.1.18. DHCP starts from 192.168.1.100

@muid: I updated directly when I firstly login into the HAP lite.

Any further idea or suggestion?

When you connect a wireless device to hAP lite (e.g. a smart phone), does it get IP address from correct IP network (192.168.1.x)? Can you connect to hAP lite from wireless devices using webfig?

@mkx: Unfortunately I didn’t check this :frowning:
Yesterday few minutes before reading your reply (!) I resetted the HAP lite to the default config and now I have to decide if reconfig again as I did previously - but surely I will be in the same trouble - or completely disable the firewall (which keeps being not the best option IMHO)

I will reply with the results of this “test” (as per your post) as soon as I’ll have reconfigured the HAP lite, do you have any tip about the firewall or anything else?
From the terminal I was able to ping the HAP lite but this was the only successful way to contact it (no SSH, no weconfig, etc)

not sure if you tried using winbox which should discover the Mikrotik if your laptop is on the same network.

Also if you already have a home router, the Mikrotik does not have to be a router, it just needs to be a Layer2 switch with all it’s ports, and WLAN interface joined into one bridge.

also no firewall is needed if the Mikrotik is a switch as it will be protected by firewall on your router, unless you wish to protect it from other home users :slight_smile:

@ceroca: actually you’ve probably answered my question. As @solar77 also indicated, you were using hAP lite as if your LAN was public internet. As such it does not allow any connection coming in from “internet”, by default that’s ether1 port. You can reconfigure hAP as simple switch/AP without firewall, DHCP client and what not.

Probably the easiest way is to reset without default configuration (but you’ll have to connect to hAP lite using winbox via MAC), then create a bridge, add all ether ports to it, add wireless interface to it and run DHCP client on it (so that hAP gets IP address, default gateway and DNS server address). You could set address etc manually, but using dhcp-client is easier. You might want to set a static lease for hAP (set it on main router) so that you’ll know where to connect for management (but you can allways fall back to using winbox over MAC).

SOLVED: it was indeed the firewall blocking my access.
Reset, disabled firewall, now all OK. Thanks again for your support!

Just disable, or reconfigure: IP/Firewall/Rules: defconf: drop all not coming from LAN