I wonder why it is that when with Capsman using datapath.local-forwarding=yes (ie local forwarding mode, also known as wireless default-forwarding) then datapath.client-to-client-forwarding is ignored / not supported, resulting in that you can basically only enable client-to-client-forwarding with "manager forwarding mode" (ie datapath.local-forwarding=no). Should you need client-to-client-forwarding in local forwarding mode then you would need to remove Capsman and configure all AP's fully manually. (note client-to-client-forwarding aka default-forwarding is a wireless setting)

And since there is always that one person chiming in "why don't you just use manager forwarding mode then?", because of bandwidth, not having to run data back and forth inside the network for it to only exit the Capsman and return to same switch / router where the access point resides, essentially making a 1.000Mb/s network a 500Mb/s network, or even less.

https://wiki.mikrotik.com/wiki/Manual:C ... figuration
https://wiki.mikrotik.com/wiki/Manual:I ... e/Wireless

Er... the client-to-client-forwarding setting works fine in local forwarding mode.
Why do you think it doesn't?

There is no (inside AP) client-to-client communication happening, neither on same SSID or other, what so ever (any device, os, etc), unless AP configured manually (Cap disabled) with default-forward and everything works. Client-to-client communication only works between different APs clients if port/vlan isolation is disabled on the switch hosting the APs, but that is only due to the switch and not APs.

I use Radius VLAN tagging with Capsman, might affect it somehow.
Mikrotik-Wireless-VLANID 333
Mikrotik-Wireless-VLANID-type 0

https://wiki.mikrotik.com/wiki/Manual:RADIUS_Client

Everything else works without a hitch.

Mikrotik-Wireless-Forward either 1 or 0 doesn't affect result (and documentation only refers to 0)

I use Radius VLAN tagging with Capsman, might affect it somehow.
Mikrotik-Wireless-VLANID 333
Mikrotik-Wireless-VLANID-type 0

It's *really* unclear in the manual but set Multicast Helper to Full when using multiple VLANs or VLAN override from one SSID.

https://wiki.mikrotik.com/wiki/Manual:I ... g_override

When I have used the access list to force VLANs off one SSID things only worked properly once I turned multicast helper to full.

It's *really* unclear in the manual but set Multicast Helper to Full when using multiple VLANs or VLAN override from one SSID.

https://wiki.mikrotik.com/wiki/Manual:I ... g_override

Thank you, works <3

It's *really* unclear in the manual but set Multicast Helper to Full when using multiple VLANs or VLAN override from one SSID.

https://wiki.mikrotik.com/wiki/Manual:I ... g_override

When I have used the access list to force VLANs off one SSID things only worked properly once I turned multicast helper to full.

This worked exactly for me as well!

I have a router, switch, and two APs using CAPsMAN. I'm using the same SSIDs across both APs, with local forwarding, client-to-client enabled in datapath, and VLAN tagging done via Access List entries. Before enabling multicast helper, several devices (notably Google Homes) connected fine, got an IP, and saw the outside world, etc., but couldn't communicate with other devices on the wifi network. For clarity, the primary offenders were Google home devices which rely on multicast, but I believe I was also unable to ping them directly from other wifi hosts.

This solution worked great. I've been suffering with this problem for some time. Thank you!

+1 This did the trick for me too! I already had client-to-client forwarding enabled on my 2 APs managed by Capsman, but still the Chromecast and Google home couldn't be found on the local network.

Setting the Multicast helper to 'full' did the trick, great stuff. Spent quite a bit of time getting this working, so thanks for sharing the solution.

What doesn't work is the Client-to-Client setting in Capsman>Datapath.

If you select this in a datapath configuration, then select that configuration in Capsman>Configuration, then set that Configuration in Capsman>Provisioning...the setting doesn't carry all the way up.

It only gets picked up if you set the flag in Conguration.