I’m tryed CapsMan features and got a problem with CapsMan manager forwarding mode .
Cap1 adapter apear in local bridge , i can ping Bridge assigned IP, but S-NAT does not work , i cannot ping any internet addresses.
I have some static routes to another networks , this netwoks i can ping too. It’s seems that only i something wrong with NAT.
In my local bridge configured DHCP and some ethernet ports . If i connect directly to ether by cable , all works perfectly.
With local forward mode , all is working right.
Is it manager beta problem , or i miss something ?
I’d rather think you missed something - I have a very similar setuip here (with 16 caps) and it’s working perfectly.
Did you configure the correct bridge in Datapath?
Are your caps in the same network you are distributing to the w/l clients?
It’s pretty hard to figure out your problem without seeing your actual configuration…
# jan/02/1970 00:39:22 by RouterOS 6.12
# software id = VQKC-CB3T
#
/interface wireless
# managed by CAPsMAN
# channel: 2412/20/gn, SSID: Test, CAPsMAN forwarding
set [ find default-name=wlan1 ] band=2ghz-b l2mtu=1600 rx-chains=0 tx-chains=\
0
/interface wireless cap
set caps-man-addresses=10.0.0.1 enabled=yes interfaces=wlan1
/ip address
add address=10.0.0.2/24 interface=ether1 network=10.0.0.0
/ip route
add distance=1 gateway=10.0.0.1
PC connected by wire to CapsMan ether9 (belongs to bridge1) . All is Ok - got IP by dhcp , srcnat is working , can ping 8.8.8.8.
PC connected by wireless . I got addresses from 99.0 network by DHCP . I can ping 99.1. Can ping 34.1 (added static route to internet router 34.1, and srcnat not afected to 34.1) Ping to 8.8.8.8 - NO REPLY.
What I miss ?
please contact support@mikrotik.com to get access to the test release of RouterOS v6.13rc as we have made some fixed for the CAPsMAN and CAP that would help you.