How can i connect an access point CAP XL AC to a RB3011UiAS-RM to share network and internet with the AP?
just a bridged network
RB3011 (bridge - ethernet port) -----cable-----(ethernet port - bridge - WLAN interfaces) CAP XL
On CAP XL only IP address on bridge needed for management. RB3011 does everything (WAN/LAN/DHCP/DNS/Firewall …) as needed.
CAP XL does nothing of this. CAP XL is only an ethernet to wifi converter.
But in CAP XL bridge only wlan or wlan + ether1?
And wireless connections should have network ip, Router as DHCP to asign LAN ip on wireless connections. Should disable dhcp on CAP XL?
Yes disable DHCP server on CAP XL. You can use a DHCP client on the bridge to assign an IP address to the CAP XL
If in the default config the “Interface lists” LAN and WAN are still there, make sure the bridge is on the LAN interface list, or disable/remove the firewall rules.
On the bridge connect all interfaces of the CAP XL (ether1, ether2, wlan1,wlan2) and all eventual extra virtual WLAN used for extra SSID
RB3011 will assign DHCP leases (IP address, default route, DNS…) to the wireless clients through the bridged network.
Bridgde is on LAN interface and firewall rules are disabled
When i connect to my wifi says 169.254 and winbox says 0.0.0.0 on neightboards
if a put it on slave again winbox says Router ip 192.168.10.1 and AP ip is 192.168.10.200 but i cant enter to AP now.
I have internet access and LAN access on wired connections but wireless connections now cant access to internet, and doesnt assign LAN ip.
No, assign DHCP server to bridge.
(In MT slave interfaces have no functions, services, IP addresses, VLAN, or memberships for the interface. Apply them to the bridge master)
Now i have router and AP lan IP (.10.1 router and .10.200 AP) but wifi terminals have 169.254 ip
But i cant reach AP with winbox after disable DHCP on the AP.
Something wrong in your setup
RB3011
RB3011 bridge with DHCP server
RB3011 ethernet interface connected to RB3011 bridge
cable between RB3011-CAP ethernet interfaces
CAP ethernet interface connected to CAP bridge
CAP bridge with DHCP client
WLAN1 connected to CAP bridge
WLAN2 connected to CAP bridge
2nd ethernet connected to CAP bridge
I have this config
RB3011
RB3011 Ethernet 1/10 +SFP Ports inside Bridge
Wan connected to Ethernet port 1 and CAP connected to Ethernet port 10
DHCP Server on interface Bridge
DHCP Pool 192.168.10.100-192.168.10.254
DHCP Client Ether 1 and Bridge
Im user of TPlink, and other brands are a way easy than Mikrotik But i want to learn mikrotik but is hard sry if im slow and thx for the patience
Im seeing when i connect to wifi first is trying to aquire ip from my Internet Modem then gives an error and give me the ip 169.254
… check CAP … I suspect to see: DHCP client is on ether 1, and ether1 not connected to bridge, DHCP server on bridge (this is from Default setup as home AP)
Must be : DHCP server removed, DHCP client moved to bridge, ether1 connected to bridge
aquire ip from my Internet Modem
… how is the RB3011 set up? It is either the internet modem or the RB3011 that is giving IP addresses.
The problem was this you say Ether 1 was out of bridge i found the problem before reads you. thx a lot.
i solved the connection problem. now wireless and wired can connect and have internet now i have another problem connection drops randomly wired and wireless. I need to see the logs to see why drop sometimes or if is an external problem
connection drops randomly wired and wireless
For wireless there are many possible reasons, but wired is unusual as a problem.
You have “Log” in Winbox/webfig/CLI menu.
For more wireless info on the CAP add “Wireless” in “/System Logging topics=wireless”
You will get things in de Log like in this post: http://forum.mikrotik.com/t/feedback-capsman-tests-coming-from-unifi/154224/1
Wired connection is on the RB3011 only I assume.
For ethernet , never needed Log for analysing, but check error counter of the interfaces and check DHCP. If you do want logging add “topics=dhcp” and “topics=interface”, it might help (or not).
Just one possible remedy in this small setup is to modify all STP modes on all bridges from “RSTP” to “none”. RSTP will prevent network loops, but can stop all traffic for multiple seconds if a change in the network is detected.
BTW Zedonius, for future reference, please use a more useful subject line on your next request. Making a subject that actually tells what the issue is that you are asking about makes it far easier to search for, and know what the general question is about.
Think about the confusion if every request for help had a subject similar to: “Please help”
At least he recognizes that he is the issue and not the evil router or AP with a mind of its own. 
Of course i never say is an evil router im the evil noob on this plataform 
Now i have another problem i dont know why but on switch 1 (where WAN is connected) only can connect 1 LAN and the others not internet available when i plug Lan cable. But on Switch 2 all works normally.
Port 1 Wan
Port 2 PC
Port 3 PC Internet works on this port ( 
)
Port 4 PC
Port 5 PC
Port 6 DVR
Port 7 DVR
Port 8 NAS
Port 9 NAS
Port 10 Wifi internet works on this port (all notebooks connected works perfectly)
Not cable problem cable is ok.
Did you add these ports that don’t work under your bridge?
Yes obviously
Nothing is obvious in MT world and the attempt at assistance was valid.
Suggest posting your config to provide a better picture.
/export hide-sensitive file=anynameyouwish
# dec/27/2021 12:04:38 by RouterOS 6.47.10
# software id = 4MY7-M590
#
# model = RB3011UiAS
# serial number = E7E80FB1E25F
/interface bridge
add admin-mac=DC:2C:6E:19:83:B5 auto-mac=no comment=defconf name=bridge \
protocol-mode=stp
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
/ip dhcp-server
add address-pool=default-dhcp disabled=no interface=bridge name=defconf
/interface bridge port
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge comment=defconf interface=ether6
add bridge=bridge comment=defconf interface=ether7
add bridge=bridge comment=defconf interface=ether8
add bridge=bridge comment=defconf interface=ether9
add bridge=bridge comment=defconf interface=ether10
add bridge=bridge comment=defconf interface=sfp1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether1 list=WAN
/ip address
add address=192.168.88.1/24 comment=defconf interface=bridge network=\
192.168.88.0
/ip dhcp-client
add comment=defconf disabled=no interface=ether1
/ip dhcp-server lease
add address=192.168.88.254 client-id=1:bc:32:5f:e:10:5d mac-address=\
BC:32:5F:0E:10:5D server=defconf
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf dns-server=8.8.8.8,1.1.1.1 \
gateway=192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan
/ip firewall filter
add action=accept chain=input comment=\
"defconf: accept established,related,untracked" connection-state=\
established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=\
invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment=\
"defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=drop chain=input comment="defconf: drop all not coming from LAN" \
in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" \
ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" \
ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" \
connection-state=established,related
add action=accept chain=forward comment=\
"defconf: accept established,related, untracked" connection-state=\
established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" \
connection-state=invalid
add action=drop chain=forward comment=\
"defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat \
connection-state=new in-interface-list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" \
ipsec-policy=out,none out-interface-list=WAN
/system clock
set time-zone-name=America/Argentina/Buenos_Aires
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN