I’ ve bought a Mikrotik cAP ax and connected it via ethernet cable to hAP Lite RB941-2ND. I want to use it as an access point in order to extend WiFi in my house. It emits WiFi signal however connected devices show: no internet connection. How should I configure it to gain internet access?
Right now you have a “LAN” side with ether2 and wifi1 and wifi2 in a bridge, and a “WAN” side configured as pppoe connection on ether1.
What is the configuration of the hAP Lite RB941-2ND?
Which ports are you using to connect the two devices (like ether1 on the Cap Ax and ether 3 on the hAP lite)?
What is your ISP connection? (I presume a xDSL or similar trough a ISP modem/router connected to the hap Lite, but it is not clear form the information you provided)
Well, it is a shame that Mikrotik does not have a quickset profile for this very common scenario: dumb AP. It is the most common - especially for a CAP ax.
I would reset configuration again and tick the “no default configuration” checkbox. After first boot up this device can be configured manually by using Winbox. Just needs to configure wifi1/wifi2, add a bridge, add all ports to it. connect lan cable on eth1 to your HAP and enable dhcp client on eth1 and you are done.
easy peasy…
For a one flat subnet 192.168.1.0/24 and 192.168.1.10 assigned to capax, looks like.
…
/interface bridge
add name=bridge vlan-filtering=no
/interface ethernet
set [ find default-name=ether1 ] name=eth1-router comment="connection to main router"
set [ find default-name=ether2 ] name=emergaccess comment="local access off bridge"
/interface wifi
settings as required
/interface list
add name=MANAGE
/interface bridge port
add bridge=bridge interface=eth1-router
add bridge=bridge interface=wifi1-2Ghz-name
add bridge=bridge interface=wifi2-5GHz-name
add wlans as required....
/ip neighbor discovery-settings
set discover-interface-list=MANAGE
/interface list member
add interface=bridge list=MANAGE
add interface=emergaccess list=MANAGE
/ip address
add address=192.168.1.10/24 interface=bridge network=192.168.1.0
add address=192.168.55.1/30 interface=emergaccess network=192.168.55.0
/ip dns
set servers=192.168.1.1
/ip route
add dst-address=0.0.0.0/0 gateway=192.168.1.1
/tool mac-server
set allowed-interface-list=NONE
/tool mac-server mac-winbox
set allowed-interface-list=MANAGE
If your talking with vlans, and no capsman (with capsman no clue)
Trusted vlan, where capax gets its IP address from is 192.168.10.0/24
Only trusted vlan is identified and needs bridge tagged.
…
/interface bridge
add ingress-filtering=no name=bridgegym vlan-filtering=yes
/interface ethernet
set [ find default-name=ether2 ] name=emergaccess
/interface vlan
add interface=bridgegym name=homeVlan vlan-id=12 { mandatory, management vlan must be identified in /interface vlan - do not put any other vlans here!! }
/interface list
add name=management
/interface wireless { as required }
/interface bridge port
add bridge=bridgegym ingress-filtering=yes frame-types=admit-only-vlan-tagged interface=ether1 comment="from router"
add bridge=bridgegym ingress-filtering=yes frame-types=admit-only-untagged-and-priority-tagged interface=homeWLan pvid=12
add bridge=bridgegym ingress-filtering=yes frame-types=admit-only-untagged-and-priority-tagged interface=HVAC_WLAN pvid=49
add bridge=bridgegym ingress-filtering=yes frame-types=admit-only-untagged-and-priority-tagged interface=mediaWlan pvid=40
/ip neighbor discovery-settings
set discover-interface-list=management
/interface bridge vlan
add bridge=bridgegym tagged=ether1,bridgegym untagged=homeWLan vlan-ids=12
add bridge=bridgegym tagged=ether1 untagged=mediaWlan vlan-ids=40
add bridge=bridgegym tagged=ether1 untagged=HVAC_WLAN vlan-ids=49
/interface list member
add interface=homeVlan list=management
add interface=emergaccess list=management
/ip address
add address=192.168.10.84/24 interface=homeVlan network=192.168.10.0 comment="IP of capax on trusted subnet"
add address=192.168.36.1/30 interface=emergaccess network=192.168.36.0 comment="ether2 access off bridge"
/ip dns
set allow-remote-requests=yes servers=192.168.10.1 { Note: Done so all dns requests use trusted subnet }
/ip route
add disabled=no dst-address=0.0.0.0/0 gateway=192.168.10.1 comment="ensures route avail through trusted subnet gateway"
/system ntp client
set enabled=yes
/system ntp client servers
add address=192.168.10.1
/tool mac-server
set allowed-interface-list=none
/tool mac-server mac-winbox
set allowed-interface-list=management