Community discussions

MikroTik App
just joined
Topic Author
Posts: 1
Joined: Sat Aug 22, 2020 4:07 pm

CAPsMAN broken (no TX) with 7.1b1+2 on CCR2004

Sat Aug 22, 2020 4:46 pm

I use v7 on CCR2004 and it mostly works with 7.0b8.
However when I upgraded to 7.1b1, and tried again today with 7.1b2, all my active WLAN clients in CAPsMAN will stay at Tx 0 (bytes/packets) and therefore never even get an IP etc.. Downgrading to 7.0b8 immediately solves this.

My CAPsMAN APs are 2xRB4011 and SXT-ac-SA at 6.47.2 (too many problems with v7), but also an LTE12 running 7.1b2, which also doesn't work (the first client in the screenshot is registered to LTE12 and there is 0 TX).

Can you please help/fix this?
You do not have the required permissions to view the files attached to this post.
just joined
Posts: 1
Joined: Fri May 24, 2019 12:34 pm

Re: CAPsMAN broken (no TX) with 7.1b1+2 on CCR2004

Thu Aug 27, 2020 11:24 am

I see exactly the same behaviour with my setup.
Tunnels between cap and accesspoint and seem to be up and working, but no traffic is flowing.

All systems upgraded to 7.1beta2

caps: 2011UiAS
ap: (multiple)RBwAPG-5HacT2HnD


@devs: if needed please PM me for a support.rif or other tests. I will downgrade to working version, but it is a home setup who i can easily change.

More info:
I downgrade caps gw to testing (6.48beta27) and still had the issue. Next downgraded the gw to stable (6.47.2) and the gw started working again.
When I upgraded to testing it stopped working again. So it seems to be something what has been changed between stable and testing.
access points are still on 7.1beta2, so the problem seems to be in the central caps gateway.
just joined
Posts: 1
Joined: Mon Feb 08, 2021 1:14 pm

Re: CAPsMAN broken (no TX) with 7.1b1+2 on CCR2004

Mon Feb 08, 2021 1:20 pm

Same problem here.

Mikrotik CCR1016-12G
Working version: 6.47.8
Broken version: 6.48

After upgrading to 6.48 capsman partialy stopped working. Traffic is not reaching main Mikrotik. Bridge->Ports contains lot less entries than before upgrade. I guess it have something to do with this change (not 100% sure):
*) bridge - correctly remove dynamic VLAN assignment for bridge ports;

Who is online

Users browsing this forum: No registered users and 14 guests