CAPsMAN not adding dynamically interfaces to bridge

RouterOS Wireless Networking
1

Hi there,

Need help figuring out why CAP interfaces are not being added dynamically to the bridge as ports on the CAPsMAN, when Local Forwarding is Enabled.

[admin@CAPsMAN] > caps-man datapath print 
 0 name="private" client-to-client-forwarding=yes bridge=bridge-private local-forwarding=yes 
 1 name="public" bridge=bridge-guests local-forwarding=no

Result:

[admin@CAPsMAN] > /interface bridge port print 
Flags: X - disabled, I - inactive, D - dynamic, H - hw-offload 
 #     INTERFACE                                                         BRIDGE                                                         HW  PVID PRIORITY  PAT
 0   H ;;; defconf
       ether2                                                            bridge-private                                                 yes    1     0x80     
 1   H ;;; defconf
       ether3                                                            bridge-private                                                 yes    1     0x80     
 2   H ;;; defconf
       ether4                                                            bridge-private                                                 yes    1     0x80     
 3 I H ;;; defconf
       ether5                                                            bridge-private                                                 yes    1     0x80     
 4 ID  outside-guests                                                    bridge-guests                                                         1     0x80     
 5 ID  upstairs-guests                                                   bridge-guests                                                         1     0x80     
 6 ID  downstairs-guests                                                 bridge-guests                                                         1     0x80

As you can see, only the interfaces using the public datapath have been added as ports to bridge-guests.

Much obliged.

2

Local forwarding means the traffic is forwarded to a bridge on the cap itself, not on capsman. You can select the bridge in the cap settings on your cap.

3

local-forwarding=no => the interface is part of bridge on the CAPsMAN, the interface shows as disabled on CAP
local-forwarding=yes => the interface stays as part of bridge on the CAP

4

Thanks, that clarifies some aspects.

Still, my confusion remains about whether the cap interfaces should or should not be dynamically added to the respective bridge in capsman.

Datapath settings allow defining a bridge irrespective of Local Forwarding enabled or disabled.

Moreover, in another installation, this seems to be the case, all cap interfaces show up as bridge ports, for both local forwarding and capsman forwarding datapaths. I just can’t figure out why this installation behaves different than the others.

[admin@MAN] > /caps-man datapath print detail 
 0 name="private" client-to-client-forwarding=yes bridge=bridge-private local-forwarding=yes 
 1 name="public" bridge=bridge-guests 
[admin@MAN] > 
[admin@MAN] > /interface bridge port print    
Flags: X - disabled, I - inactive, D - dynamic, H - hw-offload 
 #     INTERFACE                                           BRIDGE                                           HW  PVID PRIORITY  PATH-COST INTERNAL-PATH-COST    HORIZON
 0   H ;;; defconf
       ether2-LAN                                          bridge-private                                   yes    1     0x80         10                 10       none
 1 I H ;;; defconf
       ether3                                              bridge-private                                   yes    1     0x80         10                 10       none
 9  D  private-5Ghz                                        bridge-private                                          1     0x80         10                 10       none
10 ID  private-24Ghz                                       bridge-private                                          1     0x80         10                 10       none
11 ID  guests-5Ghz                                         bridge-guests                                           1     0x80         10                 10       none
12 ID  guests-24Ghz                                        bridge-guests                                           1     0x80         10                 10       none

Thanks.

5

Just to clarify why I’m struggling with this choice of Local vs CapsMAN datapath…

Been using CapsMAN forwarding all the time, you get to see traffic on cap interfaces, everything works, beautiful. Until, I’ve come to realize that in CAPsMAN forwarding mode - traffic shows double in queue trees. As a result - WiFi bandwidth is throttled by Queue trees to 1/2 of what’s supposed to be, on the download (bridge-local is the queue tree download parent). With Local Forwarding - this doesn’t happen, but SOME clients wifi ‘went down’ after switching to Local forwarding.

:confused: