I’m new in mikrotik world, and I’m configuring my firts routers/APs. Currently I’m testing some scenarios and some devices/configurations.
I have a long/strange network between two house (I share network with my parents), more o lest is like (router from ISP connected by long cable to AP, this AP connected by wifi 5Gh to another AP in mode station, this AP connected by long cable to another AP, and at this last AP is where I connect my Mikrotik Hardware):
Router (ISP)------AP:Tp-Link AP300–)))) ((((–AP station: TP Link AP300-------------AP: TP Link WA901ND —))))) (((((–Mikrotik or other PCs/devices
DHCP server is at fisrt TP Link AP300 because is bettter than DHCP from the ISP Router
Well, first of all I buy a hAP ax³, and configure de wifi 2G as station of the last AP. All correct, it takes de Address, and masquerade the output,.
For other reasons I recently buy a hAP ax Lite, and I want to configure like other, but there are stranges things:
It connects well to last AP (authorized connection) but it doesn’t take IP by DHCP.
If I put static IP on mikrotik I can ping to the last AP (192.168.1.3) and to the second (192.168.1.2) but it can’t ping to the other part of lan (don’t cross de wifi connection). But at the same time de ax³ it’s working correct, and other devices connected directly to the last AP can’t go to internet too.
If I disable de DHCP server at first AP and I enable on the last one, mikrotik takes IP, but can’t acces de main router and internet
The interface “wifi-WAN” have identical configuration on ax³ and on Lite (very basic, mode station, in any bridge, DHCP Client…)
And what versions are AX3 and AX Lite ?
Bridge station mode had some fixes in recent versions.
You can already try after upgrading to latest stable version and see if it works then.
this is more or lest a topology schema
DHCP pool is between 192.168.1.200 and 192.168.1.240 and is “empty”. The Ac^3 is taken 192.168.1.201.
Here are the export of ax³ (that works fine): config_hap_ax3.rsc (6.98 KB)
Here are the export of lite (doesn’t work): lite_config.rsc (6.09 KB)
All devices are upgraded to 7.15
They connect to TP_LINK_A39C_2 that have MAC Filtering enabled and properly configured.
I also try to configure de Lite connecting directly to the first AP (who have de DHCP server) and here it takes IP and have connection to internet.
I think that the problem is on wifi link between the to TP LINK 300, but I don’t understand why Lite is the only device who have problems, and why this problem…
More info!
I installed a new wAP AC (upgraded to 7.15 and with wireless package) and it do like Lite (no DHCP Client, and with static IP it can’t ping 192.168.1.2)
Here the export: wap-config.rsc (4.43 KB)
If you want your wAP ac to route between its clients (192.168.88.0/24) and upstream network (192.168.1.0/24), then you have to remove wlan1 interface from bridge. Also add wlan1 interface to WAN interface list (otherwise NAT doesn’t work) … LAN and WAN interface lists are no magic and membership has to be maintained manually. Unless detect-internet function does its job but it sometimes fails miserably leading to random misbehaviour, so it’s generally advised to turn it off (set detect-interface-list=none).
You also have to set default route on your wAP ac in order to reach the internet (since you’re setting WAN IP manually):
/ip route
add gateway=192.168.1.1
but looking at your topology it does seem that it’s something in your TPlink network preventing your RBs to reach default gateway … 192.168.1.x are supposed to be in same L2 network, so ping should “just work”. Since you can reach .4 (the AP which wAP ac is connecting to) and .3 (the AP beyond .4), it doesn’t seem to be the issue in ROS config … to this point. The route snippet above only comes into play after you’re able to reach 192.168.1.1.
I already removed wlan1 from bridge (without I can not set DHCP client on wlan1), but is true that wlan1 wasn’t on WAN Interface List. Despite I can not go to internet, and NAT does’nt couldn’t do his job properly, I supose that from mikrotik terminal I should ping to all 192.168.1.x network. I think similar, It’s strange, but it seams a L2 problem between TP Link AP300, not ROS problem.
