[CAPSMAN] Clients suddenly cannot access gateway

chasanb · Thu Sep 01, 2022 8:40 am

Hi,

I have :
1. A full working RB1100x4 (stable 6.49.6) running as CAPsMAN manager dan Internet Gateway
2. Seven RBcAPGi-5acD2nD (stable 6.49.6) running as CAP.

CAPsMAN running with no forwarding and enable client to client forwading.

The problem is clients suddenly cannot access the internet gateway. Client cannot ping the gateway but they exist at Registration Table.
I have to disconnect and connect several time so client can access the gateway again.
Some times, at DHCP lease, some client struggle with offering IP.

The problem not exist while running without CAPsMAN with SAME config (channel, tx-power, SSID).

here is my CAPsMAN config:

/caps-man channel
add band=2ghz-g/n control-channel-width=20mhz extension-channel=eC frequency=2472 name=2.4widebandch11 tx-power=16
add band=2ghz-g/n control-channel-width=20mhz extension-channel=Ce frequency=2412 name=2.4widebandch01 tx-power=16
add band=2ghz-g/n control-channel-width=20mhz extension-channel=disabled frequency=2462 name=2.4narrowband11 tx-power=16
add band=5ghz-n/ac control-channel-width=20mhz frequency=5765 name=channel5-153 tx-power=18
add band=5ghz-n/ac control-channel-width=20mhz frequency=5785 name=channel5-157 tx-power=18
add band=5ghz-n/ac control-channel-width=20mhz frequency=5825 name=channel5-165 tx-power=18
add band=5ghz-n/ac control-channel-width=20mhz frequency=5745 name=channel5-149 tx-power=18
add band=5ghz-n/ac control-channel-width=20mhz frequency=5805 name=channel5-161 tx-power=18
/caps-man datapath
add client-to-client-forwarding=yes l2mtu=1600 local-forwarding=yes name=datapath1
/caps-man configuration
add country=indonesia datapath=datapath1 installation=any mode=ap name="XXX_2.4" ssid="XXX"
add country=indonesia datapath=datapath1 name=XXX5G ssid=XXX5G
/caps-man interface
add channel=2.4widebandch01 configuration="XXX_2.4" disabled=no l2mtu=1600 mac-address=DC:2C:6E:6A:77:E2 master-interface=none name=cap_Accounting \
    radio-mac=DC:2C:6E:6A:77:E2 radio-name=DC2C6E6A77E2
add channel=channel5-149 configuration=XXX5G disabled=no l2mtu=1600 mac-address=DC:2C:6E:6A:77:E3 master-interface=none name=cap_Accounting_5G radio-mac=\
    DC:2C:6E:6A:77:E3 radio-name=DC2C6E6A77E3
add channel=2.4widebandch11 configuration="XXX_2.4" disabled=no l2mtu=1600 mac-address=DC:2C:6E:0D:EA:28 master-interface=none name=cap_Cutting \
    radio-mac=DC:2C:6E:0D:EA:28 radio-name=DC2C6E0DEA28
add channel=channel5-165 configuration=XXX5G disabled=no l2mtu=1600 mac-address=DC:2C:6E:0D:EA:29 master-interface=none name=cap_Cutting_5G radio-mac=\
    DC:2C:6E:0D:EA:29 radio-name=DC2C6E0DEA29
add channel=2.4widebandch01 configuration="XXX_2.4" disabled=no l2mtu=1600 mac-address=2C:C8:1B:C1:41:E4 master-interface=none name=cap_Gd.Roll \
    radio-mac=2C:C8:1B:C1:41:E4 radio-name=2CC81BC141E4
add channel=channel5-161 configuration=XXX5G disabled=no l2mtu=1600 mac-address=2C:C8:1B:C1:41:E5 master-interface=none name=cap_Gd.Roll_5G radio-mac=\
    2C:C8:1B:C1:41:E5 radio-name=2CC81BC141E5
add channel=2.4narrowband11 configuration="XXX_2.4" disabled=no l2mtu=1600 mac-address=48:8F:5A:17:56:BA master-interface=none name=cap_Marketing \
    radio-mac=48:8F:5A:17:56:BA radio-name=488F5A1756BA
add channel=channel5-153 configuration=XXX5G disabled=no l2mtu=1600 mac-address=48:8F:5A:17:56:BB master-interface=none name=cap_Marketing_5G radio-mac=\
    48:8F:5A:17:56:BB radio-name=488F5A1756BB
add channel=2.4widebandch11 configuration="XXX_2.4" disabled=no l2mtu=1600 mac-address=2C:C8:1B:C8:31:2A master-interface=none name=cap_PPIC radio-mac=\
    2C:C8:1B:C8:31:2A radio-name=2CC81BC8312A
add channel=channel5-157 configuration=XXX5G disabled=no l2mtu=1600 mac-address=2C:C8:1B:C8:31:2B master-interface=none name=cap_PPIC_5G radio-mac=2C:C8:1B:C8:31:2B \
    radio-name=2CC81BC8312B
/caps-man rates
add basic=9Mbps ht-basic-mcs=mcs-3,mcs-4,mcs-5,mcs-6,mcs-7 ht-supported-mcs=mcs-3,mcs-4,mcs-5,mcs-6,mcs-7,mcs-8,mcs-9,mcs-10,mcs-11,mcs-12,mcs-13,mcs-14,mcs-15 name=\
    rate2.4 supported=9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps vht-supported-mcs=""
/caps-man security
add authentication-types=wpa2-psk encryption=aes-ccm,tkip name=security1 passphrase=xxxxx!
/caps-man manager
set enabled=yes

here is config without CAPsMAN at CAP


/interface wireless
set [ find default-name=wlan1 ] band=2ghz-g/n channel-width=20/40mhz-eC country=indonesia disabled=no frequency=2472 mode=ap-bridge ssid="XXX" tx-power=\
    16 tx-power-mode=all-rates-fixed wps-mode=disabled
# managed by CAPsMAN
# channel: 5785/20-eCee/ac(15dBm), SSID: Sekawan5G, local forwarding
set [ find default-name=wlan2 ] band=5ghz-n/ac channel-width=20/40/80mhz-Ceee disabled=no frequency=5580 mode=ap-bridge ssid=Sekawan5G wps-mode=disabled
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/interface wireless cap
# 
set bridge=bridgeLocal caps-man-addresses=192.168.23.1 discovery-interfaces=bridgeLocal enabled=yes interfaces=wlan2

Please help. Thank You

erlinden · Thu Sep 01, 2022 10:38 am

Do the accesspoints have internet access in this case?
Can the client ping the gateway and/or the accesspoint?
Do the client have a correct IP configuration?
What does the logging say?
How many clients are connected per radio?
Are you aware that the config is not the same (as for instance the bandwidth of de CAPsMAN on the 5G radio is 20MHz)?
Are you sure that you can run 40MHz width on the 2.4G radio (as that is consuming the entire band: bottom up and top down)?

ivicask · Thu Sep 01, 2022 1:35 pm

viewtopic.php?t=156124

This is old issue, as matter of fact it just happend to me while moving between 2 caps, samsung s21 ultra phone, shows connected full signal, can't acces network, can't connect to router, wifi off/on, all works fine..

Only solution I know it works is switching to capsman forwarding.

chasanb · Thu Sep 01, 2022 4:27 pm

Do the accesspoints have internet access in this case?
Can the client ping the gateway and/or the accesspoint?
Do the client have a correct IP configuration?
What does the logging say?
How many clients are connected per radio?
Are you aware that the config is not the same (as for instance the bandwidth of de CAPsMAN on the 5G radio is 20MHz)?
Are you sure that you can run 40MHz width on the 2.4G radio (as that is consuming the entire band: bottom up and top down)?

CAP have internet access configured via static IP.
Client cannot ping the gateway but I not sure ping CAP, I will check it later.
Client get IP from DHCP from RB1100x4 as Internet gateway also as a DHCP server. At this point, some times client struggle with DHCP Lease (keep offering IP).

I confuse about logging, because I cannot find related mac address for "diconnected" client. Otherwise, the "normal" client showed in the log as normal.

 
 20:13:35 caps,info 18:02:AE:7D:E7:95@cap_Cutting connected, signal strength -58 
20:13:35 caps,info 18:02:AE:7D:E7:95@cap_Gd.Roll disconnected, registered to other interface, signal strength -73 
20:21:21 caps,info E0:1F:88:63:7A:0E@cap_Cutting_5G connected, signal strength -87

Per radio handle about 10 - 20 client. Is it normal?
Only few users connect to 5G radio. So I not get this particular problem.
Yes, I sure run 40MHz on 2.5G radio, I need more throughput. But, I have radio with 20MHz config also get this problem.

Thankyou

chasanb · Fri Sep 02, 2022 11:46 am

this is logging while error happen. Client cannot ping to anywhere.

15:37:22 caps,info 14:CC:20:B0:45:EB@cap_Accounting disconnected, received disassoc: sending station leaving (8), signal strength -46 
15:37:25 caps,info 14:CC:20:B0:45:EB@cap_Accounting connected, signal strength -41 
15:37:25 caps,info 14:CC:20:B0:45:EB@cap_Accounting disconnected, received disassoc: sending station leaving (8), signal strength -41 
15:37:26 caps,info 14:CC:20:B0:45:EB@cap_Accounting connected, signal strength -40 
15:37:26 caps,info 34:0A:33:B9:DE:83@cap_Accounting disconnected, received disassoc: sending station leaving (8), signal strength -36 
15:37:55 caps,info 34:0A:33:B9:DE:83@cap_Accounting connected, signal strength -34 
15:37:55 caps,info 14:CC:20:5A:24:47@cap_Accounting disconnected, received disassoc: sending station leaving (8), signal strength -55 
15:37:58 caps,info 14:CC:20:5A:24:47@cap_Accounting connected, signal strength -54 
15:38:14 caps,info 8C:BE:BE:18:61:69@cap_Gd.Roll disconnected, received disassoc: unspecified (1), signal strength -66 
15:38:15 caps,info 8C:BE:BE:18:61:69@cap_Cutting connected, signal strength -54 
15:38:16 caps,info D0:9C:7A:11:A4:EE@cap_Gd.Roll connected, signal strength -70 
15:38:26 caps,info 14:CC:20:5A:24:47@cap_Accounting disconnected, received disassoc: sending station leaving (8), signal strength -54 
15:38:27 caps,info 14:CC:20:5A:24:47@cap_Accounting connected, signal strength -53 
15:39:25 caps,info 14:CC:20:5A:24:47@cap_Accounting disconnected, received disassoc: sending station leaving (8), signal strength -48 
15:39:28 caps,info 14:CC:20:5A:24:47@cap_Accounting connected, signal strength -51 
15:39:36 caps,info 14:CC:20:B0:45:EB@cap_Accounting disconnected, received disassoc: sending station leaving (8), signal strength -37 
15:39:36 caps,info B4:31:61:14:ED:B3@cap_Cutting connected, signal strength -64 
15:39:38 caps,info 14:CC:20:B0:45:EB@cap_Accounting connected, signal strength -42 
15:39:38 caps,info 14:CC:20:B0:45:EB@cap_Accounting disconnected, received disassoc: sending station leaving (8), signal strength -42 
15:39:39 caps,info 14:CC:20:B0:45:EB@cap_Accounting connected, signal strength -42 
15:40:57 caps,info 0C:A8:A7:1C:74:4A@cap_Gd.Roll reassociating 
15:40:57 caps,info 0C:A8:A7:1C:74:4A@cap_Gd.Roll connected, signal strength -56 
15:41:24 caps,info 2C:D0:66:1B:6D:64@cap_Cutting disconnected, received deauth: sending station leaving (3), signal strength -64 
15:41:34 caps,info 68:BF:C4:66:F2:DE@cap_Accounting disconnected, extensive data loss, signal strength -70 
15:41:36 caps,info 0C:98:38:DF:7B:2D@cap_Cutting disconnected, extensive data loss, signal strength -86 
15:41:36 caps,info 0C:90:43:01:B8:91@cap_Accounting reassociating 
15:41:36 caps,info 0C:90:43:01:B8:91@cap_Accounting connected, signal strength -77 
15:41:39 caps,info 1C:77:F6:40:BE:99@cap_Gd.Roll disconnected, extensive data loss, signal strength -65 
15:41:53 caps,info E4:B5:03:3E:28:89@cap_Cutting disconnected, received deauth: sending station leaving (3), signal strength -80 
15:42:04 caps,info 0C:90:43:01:B8:91@cap_Gd.Roll connected, signal strength -78 
15:42:04 caps,info 0C:90:43:01:B8:91@cap_Accounting disconnected, registered to other interface, signal strength -84 
15:42:14 caps,info 00:EC:0A:7D:86:28@cap_Cutting disconnected, received disassoc: unspecified (1), signal strength -62 
15:42:14 caps,info 00:EC:0A:7D:86:28@cap_Gd.Roll connected, signal strength -54 
15:42:39 caps,info B4:31:61:14:ED:B3@cap_Cutting disconnected, received deauth: sending station leaving (3), signal strength -73

anuser · Sat Sep 03, 2022 10:23 pm

Have you tried disabling STP on the bridge of your CAPs?

/interface bridge
set [ find name=bridge1 ] protocol-mode=none

gotsprings · Tue Sep 06, 2022 2:15 am

This used to happen to me all the time. I found I could disable the interface of the radio that was doing this. Then reenable it. This would allow traffic to move again.

I wasted months on this and finally just gave up and switched vendors.

I lost some really cool stuff I wrote in caps-man and that slick quick interface... But I don't have hundreds of complaint tickets anymore.

chasanb · Tue Sep 06, 2022 11:30 am

Hi,

I just found the solution. I try to decrease the tx-power.

In the datasheet, this cAP support up to 22dbm, but in fact (some of my cAP) if I set to 20dbm the hardware can be unstable.
So I decrease the tx-power at 18dbm and the problem is gone.
I dont know why this is happen. May be hardware issue.

Feel free to correct me.

Thanks

chasanb · Tue Sep 06, 2022 11:31 am

Have you tried disabling STP on the bridge of your CAPs?

/interface bridge
set [ find name=bridge1 ] protocol-mode=none

HI anuser, I am not using bridge.
I try to decrease the tx-power and the problem is gone.

erlinden · Tue Sep 06, 2022 11:49 am

How are the CAPs powered?

chasanb · Wed Sep 07, 2022 5:09 am

How are the CAPs powered?

Via PoE Switch HP 1420-24g-poe+ (124w) switch (jh019a).
Deliver power for six mikrotik cAPs and one Engenius EAP300

gotsprings · Wed Sep 07, 2022 2:49 pm

How are the CAPs powered?
Via PoE Switch HP 1420-24g-poe+ (124w) switch (jh019a).
Deliver power for six mikrotik cAPs and one Engenius EAP300

When you see it next... select the radio in caps-man that shows the connected clients. Disable it (red X in Winbox or use terminal). Then reenable it. If traffic starts passing again... you are seeing exactly what I had happening.

UpRunTech · Thu Sep 08, 2022 5:45 am

I have to disconnect and connect several time so client can access the gateway again.

I had these sorts of dramas begin when I updated some systems to stable 6.49.6 from a long term. Try and downgrade to the long-term version on the controller and cAPs.

My next step is to try v7 and if it persists go back to v6 long term.

It's infuriating when 5 new Macbooks connect to the AP and traffic passes for a little bit then stops completely even though CAPSMAN shows they are registered. I can walk them to another AP and traffic will flow again. I have to make the problem AP to reconnect to CAPSMAN to get things going again (power cycle, re-provision, dis/enable CAPSMAN)

Mikrotik really need to get their top programmer onto it to sort it out because it's pointless to use Mikrotik if you can't use CAPSMAN reliably in 2022. It's a state machine problem, some kind of FIFO problem or there are tables and structs not being updated properly (neglected updates or bad pointers) but whatever it is it's a silent fail and a user has no recourse to fix it except complain.

CAPSMAN is great in theory but it's not robust and I have been dealing with these sorts of issues on and off for years. If v7 doesn't improve things I'll just have to stop using Mikrotik for larger wireless systems which would be a shame.

[CAPSMAN] Clients suddenly cannot access gateway

[CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Re: [CAPSMAN] Clients suddenly cannot access gateway

Who is online