New cAP ac / cannot access webfig on 192.168.88.1

RouterOS Beginner Basics
1

Hello,

It is surely just something I’m missing, but I cannot connect to Webfig on a new cAP ac. I’m just trying for now to set up a separated network for wifi devices, behind my router.

As detailed in https://i.mt.lv/routerboard/files/1517384612cAP-ac-wg.pdf the AP is plugged on eth1 to my router and I can see it’s getting an address through DHCP. I then connect to the AP through Wifi, but I cannot open http://192.168.88.1 (the connection times out). What I find strange (but I’m really a beginner!) is that I get on my laptop and address within my router’s range (10.x.x.x). So I don’t know to access admin panel.

I’ve tried multiple times to reset the device (I was trying to have it in CAP mode since I’m also replacing my wired router with a Mikrotik at the same time but I was not able to set up CAPsMan, so for now I’m just back to adding a new Wifi network on my existing configuration). With the same result. I assume that the LED mentioned in the user’s manual is the first one: I plugged the power in the injector, then - during boot process - press reset button until the first LED flashes, release the button, but still the same problem (get an address on my local network, no access to webfig).

Any idea of what I’m doing wrong and what I can do to get the default behavior?

Thanks!

2

You need to wipe your cAP config and set it up to be a L2 device, a simple wired/wireless switch: See this post for details.

Don’t use webfig… use winbox neighbors tab, this way you can manage it in L2.

3

OK, thanks!

It seems it was defaulting to CPE mode. I now have my cAP behind my hEX router in CAP mode. I have problem setting up dual band, but that’s another story (and maybe another question here after having exhausted what I can think of!)

Solved! (how can I mark it as solved?) => OK, just found it!

4

Thanks for marking it SOLVED!

Re: dual band problem Looks like CAPsMAN provisioning setup issue most likely.

5

Indeed! It’s taken me a bit of time… When having (and playing with) multiple configurations results vary due to order of rules. I’ve thought that it would only apply provisioning rules that make sense (e.g. band filtering), but one has to actively restrict the rules that can apply. I’ve finally added the MAC addresses (no fleet management issue for me!)