hi guys..im still exploring my new hap ac2 and got question..
I have the following setup:
Internet ---->HAP AC2 (local ip 192.168.1.1) —>Dlink dgs 1100 switch (static local IP 192.168.1.2)—> asus router as APs static local ip 192.168.1.3 & 192.168.1.4 (not Vlan aware devices)
hap ac2 trunking port 2 (vlan30,vlan40) to the switch port 1 n configured as tagged vlans
asus AP 1 connect to port 3 on switch as untagged vlan30
asue AP 2 connect to port 4 on switch as untagged vlan40
vlan30 - tagged port 1, untagged port 3
vlan40 - tagged port 1, untagged port 4
management vlan - vlan1
router hap ac2
DHCP address space : 192.168.1.0/24
gateway for DHCP network : 192.168.1.1
addresses to give out : 192.168.1.10 - 192.168.1.254
interface : vlan30
DHCP address space : 10.10.30.0/24
gateway for DHCP network : 10.10.30.1
addresses to give out : 10.10.30.2 - 10.10.30.254
interface : vlan40
DHCP address space : 10.10.40.0/24
gateway for DHCP network : 10.10.40.1
addresses to give out : 10.10.40.2 - 10.10.40.254
default config enable for hap ac2
i can access the internet wifi from asus AP 1 and got ip 10.10.30.254
i can access the internet wifi from asus AP 2 and got ip 10.10.40.254
questions..
I am able to connect to the hap ac2 local IP (192.168.1.1) via Winbox when connected to mikrotik wifi
I also want to be able to connect to the switch (192.168.1.2) & Asus APs (192.168.1.3 & 192.168.1.4) via local IP wirelessly.
Aleady tried to use mikrotik wifi to connect to those local IP but cannot sad.gif
Any solutions/suggestions will be highly appreciated..sorry if my question is bit noob
The setup you’ve got can’t work … and it’s due to routing which is broken for APs right now. Let’s consider the AP1:
it’s configured with 192.168.1.3/24
it’s connected to DGS port 3, which in turn is access (untagged) port member of vlan30
hAP ac2 has vlan30 configured and IP address associated is 10.10.30.1/24
hAP ac2, OTOH, has 192.168.1.1/24 configured on another interface (bridge I presume)
So when AP1 tries to connect to 192.168.1.1, it tries to connect directly to that IP address because according to configuration it is in the same IP subnet (subnet mask covers both own and remote IP address). However, the remote IP address is not present on the same L2 (ethernet, VLAN) network.
When hAP ac2 tries to connect to AP1, it looks for it on the vlan1 (management) network for the very same reasons (according to IP subnet mask).
Connectivity to internet and to hAP ac2 works just fine for wireless clients because they are in the correct subnet. The “management” IP address of AP1 is not.
And the same is true for AP2.
The problem with VLAN-dumb gear is that one can not separate management subnet from “user” subnet. Full stop.
You can get it working for switch because it’s VLAN aware. You just have to pass management VLAN through trunk connection between hAP ac2 and DGS.
I strongly suggest you that for management VLAN you use VLAN ID different than 1. VLAN tags with ID 1 are implicit default VLAN ID (pvid) on RouterOS and if you’re not really really careful, those might pass either tagged or untagged cross interfaces and things might not work as expected. And you can change management VLAN on DGS without much hassle. Just be careful when doing it to keep a backdoor if things go wrong (e.g. prepare two access - untagged - ports on DGS, one for each of VLANs so you can connect to one of those and re-gain management of DGS).