Community discussions

MikroTik App
 
massinia
Member Candidate
Member Candidate
Topic Author
Posts: 159
Joined: Thu Jun 09, 2022 7:20 pm

CAPsMAN unstable after upgrade to 7.3

Thu Jun 09, 2022 7:51 pm

Hello everybody :)
I've been using a CAPsMAN simple setup for months with one hAP lite TC and one cAP lite (both with 6.49.4), after updating to 7.3 I can't get over the two days of uptime.

This is my config:
# jun/09/2022 18:38:40 by RouterOS 6.49.6
# software id = KB7X-3K0F
#
# model = RB941-2nD
# serial number = <CENSORED>
/interface bridge
add admin-mac=2C:C8:1B:0D:DA:D2 auto-mac=no comment=defconf name=bridge
/interface wireless
# managed by CAPsMAN
# channel: 2447/20-eC/gn(18dBm), SSID: MikroTik, local forwarding
set [ find default-name=wlan1 ] band=2ghz-g/n channel-width=20/40mhz-XX \
    disabled=no distance=indoors frequency=auto installation=indoor mode=\
    ap-bridge ssid=MikroTik wireless-protocol=802.11 wps-mode=disabled
/caps-man security
add authentication-types=wpa2-psk encryption=aes-ccm group-encryption=aes-ccm \
    name=security1
/caps-man configuration
add channel.band=2ghz-g/n country=italy datapath.local-forwarding=yes \
    distance=indoors installation=indoor mode=ap name=cfg1 security=security1 \
    ssid=MikroTik
/caps-man interface
add configuration=cfg1 disabled=no l2mtu=1600 mac-address=2C:C8:1B:0D:DA:D6 \
    master-interface=none name=cap1 radio-mac=2C:C8:1B:0D:DA:D6 radio-name=\
    2CC81B0DDAD6
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods="" mode=\
    dynamic-keys supplicant-identity=MikroTik
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
/ip dhcp-server
add address-pool=default-dhcp disabled=no interface=bridge name=defconf
/caps-man manager
set enabled=yes
/caps-man provisioning
add action=create-dynamic-enabled master-configuration=cfg1
/interface bridge port
add bridge=bridge comment=defconf ingress-filtering=yes interface=ether2
add bridge=bridge comment=defconf ingress-filtering=yes interface=ether3
add bridge=bridge comment=defconf ingress-filtering=yes interface=ether4
add bridge=bridge comment=defconf ingress-filtering=yes interface=pwr-line1
add bridge=bridge comment=defconf ingress-filtering=yes interface=wlan1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/ip settings
set max-neighbor-entries=2048
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether1 list=WAN
/interface ovpn-server server
set auth=sha1,md5
/interface wireless cap
# 
set caps-man-addresses=127.0.0.1 enabled=yes interfaces=wlan1
/ip address
add address=192.168.88.1/24 comment=defconf interface=bridge network=\
    192.168.88.0
/ip dhcp-client
add comment=defconf disabled=no interface=ether1
/ip dhcp-server lease
add address=192.168.88.20 client-id=1:b8:27:eb:68:3d:ff mac-address=\
    B8:27:EB:68:3D:FF server=defconf
add address=192.168.88.10 client-id=1:4c:20:b8:e4:e3:60 mac-address=\
    4C:20:B8:E4:E3:60 server=defconf
add address=192.168.88.2 client-id=1:dc:2c:6e:c7:ea:b mac-address=\
    DC:2C:6E:C7:EA:0B server=defconf
add address=192.168.88.5 client-id=1:f8:d0:27:a:a2:fd mac-address=\
    F8:D0:27:0A:A2:FD server=defconf
add address=192.168.88.21 client-id=1:dc:a6:32:3f:db:e0 mac-address=\
    DC:A6:32:3F:DB:E0 server=defconf
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf dns-server=192.168.88.1 gateway=\
    192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan
/ip firewall filter
add action=accept chain=input comment=\
    "defconf: accept established,related,untracked" connection-state=\
    established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=\
    invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment=\
    "defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=drop chain=input comment="defconf: drop all not coming from LAN" \
    in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" \
    ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" \
    ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" \
    connection-state=established,related
add action=accept chain=forward comment=\
    "defconf: accept established,related, untracked" connection-state=\
    established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" \
    connection-state=invalid
add action=drop chain=forward comment=\
    "defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat \
    connection-state=new in-interface-list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" \
    ipsec-policy=out,none out-interface-list=WAN
/ip service
set telnet disabled=yes
set ftp disabled=yes
set www disabled=yes
set ssh disabled=yes
set api disabled=yes
set api-ssl disabled=yes
/ip upnp
set enabled=yes
/ip upnp interfaces
add interface=ether1 type=external
add interface=bridge type=internal
/system clock
set time-zone-name=Europe/Rome
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
The connected devices are at most 10, after about 24 hours of uptime the cpu reaches 100% when I connect with winbox and it restarts itself after a minute.
On log there is:
system,error,critical kernel failure in previous boot
system,error,critical out of memory condition was detected

Is there anything I can do?
I've already tried resetting and reconfiguring from scratch with version 7.3

Thanks
 
biomesh
Long time Member
Long time Member
Posts: 561
Joined: Fri Feb 10, 2012 8:25 pm

Re: CAPsMAN unstable after upgrade to 7.3

Thu Jun 09, 2022 9:04 pm

Since it is reporting out of memory conditions on the hap lite (which has 32MB RAM) you should probably move the capsman server to the cap lite since it has 64 MB RAM and let the hap lite be a capsman client. If you only have two APs, you could also just skip capsman and configure them separately.

The smips devices with 32MB run pretty lean on 6.x so they have a higher chance of running out of RAM on 7.x
 
massinia
Member Candidate
Member Candidate
Topic Author
Posts: 159
Joined: Thu Jun 09, 2022 7:20 pm

Re: CAPsMAN unstable after upgrade to 7.3

Thu Jun 09, 2022 9:40 pm

Thanks for your help :)

I will follow your advice and let you know, I forgot to write that
system,error,critical kernel failure in previous boot
system,error,critical out of memory condition was detected
Is in the log of both devices.
 
biomesh
Long time Member
Long time Member
Posts: 561
Joined: Fri Feb 10, 2012 8:25 pm

Re: CAPsMAN unstable after upgrade to 7.3

Thu Jun 09, 2022 11:36 pm

If you see it on both, I would just skip capsman on 7.x for now.
 
erlinden
Forum Guru
Forum Guru
Posts: 1920
Joined: Wed Jun 12, 2013 1:59 pm
Location: Netherlands

Re: CAPsMAN unstable after upgrade to 7.3

Fri Jun 10, 2022 8:37 am

You might want to consider:
  • not using auto for frequency
  • not using 40MHz bandwidth on the 2,4GHz radio
This configuration is spot on for causing interference, both on your network and on the wireless networks in the neighborhood.

Why use CAPsMAN in the first place?
 
massinia
Member Candidate
Member Candidate
Topic Author
Posts: 159
Joined: Thu Jun 09, 2022 7:20 pm

Re: CAPsMAN unstable after upgrade to 7.3

Fri Jun 10, 2022 9:09 am

Hi, I left everything by default and configured capsman following this video:
https://youtu.be/taQ70m0DVYA

Why use CAPsMAN in the first place?

I would like to add another cAP lite and we have noticed that with capsman, devices switch between access points much faster.

With RouterOS 6.49.4 it worked for months ... now with 7.3 after 24 hours I can't connect with Winbox because the cpu goes to 100% and they restart by themselves, if I don't connect with winbox they keep working,

Is there any way to figure out what causes this problem? Any way to store the log before reboot?

Thanks

PS. in the network there is a raspberry with zerotier and the upnp is active.
 
massinia
Member Candidate
Member Candidate
Topic Author
Posts: 159
Joined: Thu Jun 09, 2022 7:20 pm

Re: CAPsMAN unstable after upgrade to 7.3

Fri Jun 10, 2022 3:44 pm

I am starting to think that the problem is not capsman, this is the boot log after updating to 7.3.1

Image

Device just updated and reset, only capsman mode activated with reset button, no other changes.
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: CAPsMAN unstable after upgrade to 7.3  [SOLVED]

Fri Jun 10, 2022 5:12 pm

Do you have the same issue on 7.4beta2?
 
massinia
Member Candidate
Member Candidate
Topic Author
Posts: 159
Joined: Thu Jun 09, 2022 7:20 pm

Re: CAPsMAN unstable after upgrade to 7.3

Fri Jun 10, 2022 5:48 pm

Do you have the same issue on 7.4beta2?
I'll try it soon, now I'm trying to log the problem :)
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: CAPsMAN unstable after upgrade to 7.3

Sat Jun 11, 2022 6:24 pm

I'll try it soon, now I'm trying to log the problem :)
Okay, keep us updated
 
massinia
Member Candidate
Member Candidate
Topic Author
Posts: 159
Joined: Thu Jun 09, 2022 7:20 pm

Re: CAPsMAN unstable after upgrade to 7.3

Sun Jun 12, 2022 10:23 am

Here is the log after 24 hours of uptime, it restarted after I connected with winbox (100% CPU)

hAP lite TC RouterOS 7.3.1
Jun/12/2022 08:42:04 system,info,account user admin logged in from 192.168.88.20 via winbox
Jun/12/2022 08:42:21 route,debug,calc 3 Main publish
Jun/12/2022 08:42:29 dhcp,debug defconf received request id 1515289530 from 192.168.88.2 '1:dc:2c:6e:c7:ea:b'
Jun/12/2022 08:42:29 dhcp,debug,packet     ciaddr = 192.168.88.2
Jun/12/2022 08:42:29 dhcp,debug,packet     chaddr = DC:2C:6E:C7:EA:0B
Jun/12/2022 08:42:29 dhcp,debug,packet     Host-Name = "MikroTik"
Jun/12/2022 08:42:29 dhcp,debug,packet     Msg-Type = request
Jun/12/2022 08:42:29 dhcp,debug,packet     Parameter-List = Subnet-Mask,Classless-Route,Router,Static-Route,Domain-Server,NTP-Server,CAPWAP-Server,Vendor-Specific
Jun/12/2022 08:42:29 dhcp,debug,packet     Client-Id = 01-DC-2C-6E-C7-EA-0B
Jun/12/2022 08:42:29 dhcp,debug lease bound, extending
Jun/12/2022 08:42:29 dhcp,debug defconf sending ack with id 1515289530 to 192.168.88.2
Jun/12/2022 08:42:29 dhcp,debug,packet     ciaddr = 192.168.88.2
Jun/12/2022 08:42:29 dhcp,debug,packet     yiaddr = 192.168.88.2
Jun/12/2022 08:42:29 dhcp,debug,packet     siaddr = 192.168.88.1
Jun/12/2022 08:42:29 dhcp,debug,packet     chaddr = DC:2C:6E:C7:EA:0B
Jun/12/2022 08:42:29 dhcp,debug,packet     Subnet-Mask = 255.255.255.0
Jun/12/2022 08:42:29 dhcp,debug,packet     Router = 192.168.88.1
Jun/12/2022 08:42:29 dhcp,debug,packet     Domain-Server = 192.168.88.1
Jun/12/2022 08:42:29 dhcp,debug,packet     Address-Time = 600
Jun/12/2022 08:42:29 dhcp,debug,packet     Msg-Type = ack
Jun/12/2022 08:42:29 dhcp,debug,packet     Server-Id = 192.168.88.1
Jun/12/2022 08:42:36 route,debug,calc 3 Main publish
Jun/12/2022 08:42:57 certificate,debug start CRL update
Jun/12/2022 08:43:12 route,debug,calc 3 Main publish
Jun/12/2022 08:43:30 route,debug,calc 3 Main publish
Jun/12/2022 08:43:39 caps,debug [::ffff:127.0.0.1:51933,Run,[2C:C8:1B:0D:DA:D1]] lost connection, echo timeout
Jun/12/2022 08:43:40 caps,debug 9C:76:13:9F:B8:2B@cap1 disconnected, interface disabled, signal strength -66
Jun/12/2022 08:43:40 caps,debug [DC:2C:6E:C7:EA:0B/13/a38a,Run,[DC:2C:6E:C7:EA:0B]] lost connection, echo timeout
Jun/12/2022 08:44:01 route,debug,calc 1.3.1 Tag updated routes for merging
Jun/12/2022 08:44:03 route,debug,calc 1.3.4 Merge route updates
Jun/12/2022 08:44:04 route,debug,calc 2.2 Merge forwarding path updates
Jun/12/2022 08:44:04 route,debug,calc 3 Main publish
Jun/12/2022 08:44:06 route,debug,calc 6.1 Cleanup merge
Jun/12/2022 08:44:06 route,debug,calc 1.3.1 Tag updated routes for merging
Jun/12/2022 08:44:06 route,debug,calc 1.3.4 Merge route updates
Jun/12/2022 08:44:06 route,debug,calc 2.2 Merge forwarding path updates
Jun/12/2022 08:44:06 route,debug,calc 3 Main publish
Jun/12/2022 08:44:06 route,debug,calc 6.1 Cleanup merge
Jun/12/2022 08:44:06 route,debug,calc 3 Main publish
Jun/12/2022 08:44:13 route,debug,calc 1.3.1 Tag updated routes for merging
Jun/12/2022 08:44:13 route,debug,calc 1.3.4 Merge route updates
Jun/12/2022 08:44:13 route,debug,calc 2.2 Merge forwarding path updates
Jun/12/2022 08:44:13 route,debug,calc 3 Main publish
Jun/12/2022 08:44:22 route,debug,calc 6.1 Cleanup merge
Jun/12/2022 08:44:22 route,debug,calc 3 Main publish
Jun/12/2022 08:44:32 route,debug,calc 1.3.1 Tag updated routes for merging
Jun/12/2022 08:44:32 route,debug,calc 1.3.4 Merge route updates
Jun/12/2022 08:44:33 caps,debug DC:2C:6E:C7:EA:0B/13/a38a failed to connect, timeout
Jun/12/2022 08:44:33 route,debug,calc 2.2 Merge forwarding path updates
Jun/12/2022 08:44:33 route,debug,calc 3 Main publish
Jun/12/2022 08:44:43 route,debug,calc 6.1 Cleanup merge
Jun/12/2022 08:44:44 route,debug,calc 1.3.1 Tag updated routes for merging
Jun/12/2022 08:44:44 route,debug,calc 1.3.4 Merge route updates
Jun/12/2022 08:44:45 route,debug,calc 2.2 Merge forwarding path updates
Jun/12/2022 08:44:45 route,debug,calc 3 Main publish
Jun/12/2022 08:44:49 route,debug,calc 6.1 Cleanup merge
Jun/12/2022 08:44:49 route,debug,calc 3 Main publish
Jun/12/2022 08:44:52 caps,debug ::ffff:127.0.0.1:51933 failed to connect, timeout
Jun/12/2022 08:44:53 caps,debug DC:2C:6E:C7:EA:0B/13/a38a failed to connect, ssl: unexpected message (6)
Jun/12/2022 08:44:54 certificate,debug start CRL update
Jun/12/2022 08:44:54 caps,debug ::ffff:127.0.0.1:51933 failed to connect, ssl: unexpected message (6)
Jun/12/2022 08:44:56 caps,debug CAP lost connection, send timeout
Jun/12/2022 08:44:56 caps,info CAP disconnected from MikroTik (::ffff:127.0.0.1:5246)
Jun/12/2022 08:44:56 caps,debug CAP Joined->Discover
Jun/12/2022 08:45:02 caps,debug CAP discovery target list:
Jun/12/2022 08:45:02 caps,debug   ::ffff:127.0.0.1:5246
Jun/12/2022 08:45:04 route,debug,calc 1.3.1 Tag updated routes for merging
Jun/12/2022 08:45:04 route,debug,calc 1.3.4 Merge route updates
Jun/12/2022 08:45:04 route,debug,calc 2.2 Merge forwarding path updates
Jun/12/2022 08:45:12 dhcp,debug defconf received request id 671939283 from 192.168.88.21 '1:dc:a6:32:3f:db:e0'
Jun/12/2022 08:45:12 dhcp,debug,packet     secs = 65535
Jun/12/2022 08:45:12 dhcp,debug,packet     ciaddr = 192.168.88.21
Jun/12/2022 08:45:12 dhcp,debug,packet     chaddr = DC:A6:32:3F:DB:E0
Jun/12/2022 08:45:12 dhcp,debug,packet     Host-Name = "raspberrypi"
Jun/12/2022 08:45:12 dhcp,debug,packet     Msg-Type = request
Jun/12/2022 08:45:12 dhcp,debug,packet     Parameter-List = Subnet-Mask,Classless-Route,Static-Route,Router,Domain-Server,Host-Name,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Server-Id,Renewal-Time,Rebinding-Time,Domain-Search
Jun/12/2022 08:45:12 dhcp,debug,packet     Max-DHCP-Message-Size = 1472
Jun/12/2022 08:45:12 dhcp,debug,packet     Client-Id = 01-DC-A6-32-3F-DB-E0
Jun/12/2022 08:45:12 dhcp,debug,packet     Unknown(145) = 01
Jun/12/2022 08:45:12 dhcp,debug lease bound, extending
Jun/12/2022 08:45:12 route,debug,calc 3 Main publish
Jun/12/2022 08:45:12 system,info,account user admin logged out from 192.168.88.20 via web
Jun/12/2022 08:45:12 dhcp,debug defconf sending ack with id 671939283 to 192.168.88.21
Jun/12/2022 08:45:12 dhcp,debug,packet     ciaddr = 192.168.88.21
Jun/12/2022 08:45:12 dhcp,debug,packet     yiaddr = 192.168.88.21
Jun/12/2022 08:45:12 dhcp,debug,packet     siaddr = 192.168.88.1
Jun/12/2022 08:45:12 dhcp,debug,packet     chaddr = DC:A6:32:3F:DB:E0
Jun/12/2022 08:45:12 dhcp,debug,packet     Subnet-Mask = 255.255.255.0
Jun/12/2022 08:45:12 dhcp,debug,packet     Router = 192.168.88.1
Jun/12/2022 08:45:12 dhcp,debug,packet     Domain-Server = 192.168.88.1
Jun/12/2022 08:45:12 dhcp,debug,packet     Address-Time = 600
Jun/12/2022 08:45:12 dhcp,debug,packet     Msg-Type = ack
Jun/12/2022 08:45:12 dhcp,debug,packet     Server-Id = 192.168.88.1
Jun/12/2022 08:45:12 dhcp,debug defconf received request id 671939283 from 192.168.88.21 '1:dc:a6:32:3f:db:e0'
Jun/12/2022 08:45:12 dhcp,debug,packet     secs = 65535
Jun/12/2022 08:45:12 dhcp,debug,packet     ciaddr = 192.168.88.21
Jun/12/2022 08:45:12 dhcp,debug,packet     chaddr = DC:A6:32:3F:DB:E0
Jun/12/2022 08:45:12 dhcp,debug,packet     Host-Name = "raspberrypi"
Jun/12/2022 08:45:12 dhcp,debug,packet     Msg-Type = request
Jun/12/2022 08:45:12 dhcp,debug,packet     Parameter-List = Subnet-Mask,Classless-Route,Static-Route,Router,Domain-Server,Host-Name,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Server-Id,Renewal-Time,Rebinding-Time,Domain-Search
Jun/12/2022 08:45:12 dhcp,debug,packet     Max-DHCP-Message-Size = 1472
Jun/12/2022 08:45:12 dhcp,debug,packet     Client-Id = 01-DC-A6-32-3F-DB-E0
Jun/12/2022 08:45:12 dhcp,debug,packet     Unknown(145) = 01
Jun/12/2022 08:45:12 dhcp,debug lease bound, extending
Jun/12/2022 08:45:12 dhcp,debug defconf sending ack with id 671939283 to 192.168.88.21
Jun/12/2022 08:45:12 dhcp,debug,packet     ciaddr = 192.168.88.21
Jun/12/2022 08:45:12 dhcp,debug,packet     yiaddr = 192.168.88.21
Jun/12/2022 08:45:12 dhcp,debug,packet     siaddr = 192.168.88.1
Jun/12/2022 08:45:12 dhcp,debug,packet     chaddr = DC:A6:32:3F:DB:E0
Jun/12/2022 08:45:12 dhcp,debug,packet     Subnet-Mask = 255.255.255.0
Jun/12/2022 08:45:12 dhcp,debug,packet     Router = 192.168.88.1
Jun/12/2022 08:45:12 dhcp,debug,packet     Domain-Server = 192.168.88.1
Jun/12/2022 08:45:12 dhcp,debug,packet     Address-Time = 600
Jun/12/2022 08:45:12 dhcp,debug,packet     Msg-Type = ack
Jun/12/2022 08:45:12 dhcp,debug,packet     Server-Id = 192.168.88.1
Jun/12/2022 08:45:17 route,debug,calc 6.1 Cleanup merge
Jun/12/2022 08:45:18 route,debug,calc 3 Main publish
Jun/12/2022 08:45:22 caps,debug CAP discovery over, results:
Jun/12/2022 08:45:23 caps,debug   MikroTik (::ffff:127.0.0.1:5246)
Jun/12/2022 08:45:23 caps,debug CAP Discover->Select
Jun/12/2022 08:45:23 caps,info CAP selected CAPsMAN MikroTik (::ffff:127.0.0.1:5246)
Jun/12/2022 08:45:23 caps,debug CAP Select->Connect
Jun/12/2022 08:45:50 route,debug,calc 3 Main publish
Jun/12/2022 08:46:06 system,info,account user admin logged out from 192.168.88.20 via winbox
Jun/12/2022 08:46:07 caps,debug DC:2C:6E:C7:EA:0B/13/31bc failed to connect, timeout
Jun/12/2022 08:46:14 caps,info CAP connect to MikroTik (::ffff:127.0.0.1:5246) failed: timeout
Jun/12/2022 08:46:14 caps,info CAP failed to join MikroTik (::ffff:127.0.0.1:5246)
Jun/12/2022 08:46:14 caps,debug CAP Connect->Select
Jun/12/2022 08:46:14 caps,debug CAP did not find suitable CAPsMAN
Jun/12/2022 08:46:14 caps,debug CAP Select->Sulking
Jun/12/2022 08:46:14 caps,debug ::ffff:127.0.0.1:34650 failed to connect, timeout
Jun/12/2022 08:46:14 caps,debug ::ffff:192.168.88.2:49229 failed to connect, timeout
Jun/12/2022 08:46:22 dhcp,debug defconf received request id 3168231040 from 192.168.88.20 '1:b8:27:eb:68:3d:ff'
Jun/12/2022 08:46:23 dhcp,debug,packet     secs = 65535
Jun/12/2022 08:46:23 dhcp,debug,packet     ciaddr = 192.168.88.20
Jun/12/2022 08:46:23 dhcp,debug,packet     chaddr = B8:27:EB:68:3D:FF
Jun/12/2022 08:46:23 dhcp,debug,packet     Host-Name = "raspberrypi"
Jun/12/2022 08:46:23 dhcp,debug,packet     Msg-Type = request
Jun/12/2022 08:46:23 dhcp,debug,packet     Parameter-List = Subnet-Mask,Classless-Route,Static-Route,Router,Domain-Server,Host-Name,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Server-Id,Renewal-Time,Rebinding-Time,Domain-Search
Jun/12/2022 08:46:23 dhcp,debug,packet     Max-DHCP-Message-Size = 1472
Jun/12/2022 08:46:23 dhcp,debug,packet     Class-Id = "dhcpcd-8.1.2:Linux-5.15.32+:armv6l:BCM2835"
Jun/12/2022 08:46:23 dhcp,debug,packet     Client-Id = 01-B8-27-EB-68-3D-FF
Jun/12/2022 08:46:23 dhcp,debug,packet     Unknown(145) = 01
Jun/12/2022 08:46:23 dhcp,debug lease bound, extending
Jun/12/2022 08:46:23 dhcp,debug defconf sending ack with id 3168231040 to 192.168.88.20
Jun/12/2022 08:46:23 dhcp,debug,packet     ciaddr = 192.168.88.20
Jun/12/2022 08:46:23 dhcp,debug,packet     yiaddr = 192.168.88.20
Jun/12/2022 08:46:23 dhcp,debug,packet     siaddr = 192.168.88.1
Jun/12/2022 08:46:23 dhcp,debug,packet     chaddr = B8:27:EB:68:3D:FF
Jun/12/2022 08:46:23 dhcp,debug,packet     Subnet-Mask = 255.255.255.0
Jun/12/2022 08:46:23 dhcp,debug,packet     Router = 192.168.88.1
Jun/12/2022 08:46:23 dhcp,debug,packet     Domain-Server = 192.168.88.1
Jun/12/2022 08:46:23 dhcp,debug,packet     Address-Time = 600
Jun/12/2022 08:46:23 dhcp,debug,packet     Msg-Type = ack
Jun/12/2022 08:46:23 dhcp,debug,packet     Server-Id = 192.168.88.1
Jun/12/2022 08:46:34 caps,debug CAP Sulking->Discover
Jun/12/2022 08:46:49 caps,debug CAP discovery target list:
Jun/12/2022 08:46:52 caps,debug   ::ffff:127.0.0.1:5246
Jun/12/2022 08:47:16 route,debug,calc 1.3.1 Tag updated routes for merging
Jun/12/2022 08:47:17 route,debug,calc 2.2 Merge forwarding path updates
Jun/12/2022 08:47:17 route,debug,calc 3 Main publish
Jun/12/2022 08:47:20 route,debug,calc 6.1 Cleanup merge
Jun/12/2022 08:47:20 certificate,debug start CRL update
Jun/12/2022 08:47:21 route,debug,calc 1.3.1 Tag updated routes for merging
Jun/12/2022 08:47:21 route,debug,calc 1.3.4 Merge route updates
Jun/12/2022 08:47:23 route,debug,calc 2.2 Merge forwarding path updates
Jun/12/2022 08:47:23 route,debug,calc 3 Main publish
Jun/12/2022 08:47:24 route,debug,calc 6.1 Cleanup merge
Jun/12/2022 08:47:31 dhcp,debug defconf received request id 1515289530 from 192.168.88.2 '1:dc:2c:6e:c7:ea:b'
Jun/12/2022 08:47:32 dhcp,debug,packet     ciaddr = 192.168.88.2
Jun/12/2022 08:47:32 dhcp,debug,packet     chaddr = DC:2C:6E:C7:EA:0B
Jun/12/2022 08:47:32 dhcp,debug,packet     Host-Name = "MikroTik"
Jun/12/2022 08:47:32 dhcp,debug,packet     Msg-Type = request
Jun/12/2022 08:47:32 dhcp,debug,packet     Parameter-List = Subnet-Mask,Classless-Route,Router,Static-Route,Domain-Server,NTP-Server,CAPWAP-Server,Vendor-Specific
Jun/12/2022 08:47:32 dhcp,debug,packet     Client-Id = 01-DC-2C-6E-C7-EA-0B
Jun/12/2022 08:47:32 dhcp,debug lease bound, extending
Jun/12/2022 08:47:33 caps,debug CAP discovery over, results:
Jun/12/2022 08:47:35 caps,debug   MikroTik (::ffff:127.0.0.1:5246)
Jun/12/2022 08:47:36 caps,debug CAP Discover->Select
Jun/12/2022 08:47:36 caps,info CAP selected CAPsMAN MikroTik (::ffff:127.0.0.1:5246)
Jun/12/2022 08:47:37 caps,debug CAP Select->Connect
Jun/12/2022 08:47:37 dhcp,debug defconf sending ack with id 1515289530 to 192.168.88.2
Jun/12/2022 08:47:37 dhcp,debug,packet     ciaddr = 192.168.88.2
Jun/12/2022 08:47:37 dhcp,debug,packet     yiaddr = 192.168.88.2
Jun/12/2022 08:47:37 dhcp,debug,packet     siaddr = 192.168.88.1
Jun/12/2022 08:47:37 dhcp,debug,packet     chaddr = DC:2C:6E:C7:EA:0B
Jun/12/2022 08:47:37 dhcp,debug,packet     Subnet-Mask = 255.255.255.0
Jun/12/2022 08:47:37 dhcp,debug,packet     Router = 192.168.88.1
Jun/12/2022 08:47:37 dhcp,debug,packet     Domain-Server = 192.168.88.1
Jun/12/2022 08:47:37 dhcp,debug,packet     Address-Time = 600
Jun/12/2022 08:47:37 dhcp,debug,packet     Msg-Type = ack
Jun/12/2022 08:47:37 dhcp,debug,packet     Server-Id = 192.168.88.1
Jun/12/2022 08:47:59 route,debug,calc 1.3.1 Tag updated routes for merging
Jun/12/2022 08:48:00 route,debug,calc 2.2 Merge forwarding path updates
Jun/12/2022 08:48:00 route,debug,calc 3 Main publish
Jun/12/2022 08:48:02 route,debug,calc 6.1 Cleanup merge
Jun/12/2022 08:48:02 route,debug,calc 1.3.1 Tag updated routes for merging
Jun/12/2022 08:48:02 route,debug,calc 1.3.4 Merge route updates
Jun/12/2022 08:48:02 route,debug,calc 2.2 Merge forwarding path updates
Jun/12/2022 08:48:02 route,debug,calc 3 Main publish
Jun/12/2022 08:48:02 route,debug,calc 6.1 Cleanup merge
Jun/12/2022 08:48:02 caps,info CAP connect to MikroTik (::ffff:127.0.0.1:5246) failed: timeout
Jun/12/2022 08:48:03 caps,info CAP failed to join MikroTik (::ffff:127.0.0.1:5246)
Jun/12/2022 08:48:03 caps,debug CAP Connect->Select
Jun/12/2022 08:48:03 caps,debug CAP did not find suitable CAPsMAN
Jun/12/2022 08:48:03 caps,debug CAP Select->Sulking
Jun/12/2022 08:48:22 caps,debug CAP Sulking->Discover
Jun/12/2022 08:48:24 caps,debug CAP discovery target list:
Jun/12/2022 08:48:24 caps,debug   ::ffff:127.0.0.1:5246
Jun/12/2022 08:48:28 certificate,debug start CRL update
Jun/12/2022 08:48:35 caps,debug ::ffff:192.168.88.2:59553 failed to connect, timeout
Jun/12/2022 08:48:41 caps,debug CAP discovery over, results:
Jun/12/2022 08:48:41 caps,debug   MikroTik (::ffff:127.0.0.1:5246)
Jun/12/2022 08:48:41 caps,debug CAP Discover->Select
Jun/12/2022 08:48:41 caps,info CAP selected CAPsMAN MikroTik (::ffff:127.0.0.1:5246)
Jun/12/2022 08:48:41 caps,debug CAP Select->Connect
Jun/12/2022 08:48:50 route,debug,calc 3 Main publish
Jun/12/2022 08:48:57 caps,debug DC:2C:6E:C7:EA:0B/13/6583 failed to connect, timeout
Jun/12/2022 08:48:59 caps,info CAP connected to MikroTik (::ffff:127.0.0.1:5246)
Jun/12/2022 08:48:59 caps,debug CAP Connect->Join
Jun/12/2022 08:49:01 caps,info [::ffff:127.0.0.1:41810,Join,[2C:C8:1B:0D:DA:D1]] joined, provides radio(s): 2C:C8:1B:0D:DA:D6
Jun/12/2022 08:49:01 caps,info CAP joined MikroTik (::ffff:127.0.0.1:5246)
Jun/12/2022 08:49:01 caps,debug CAP Join->Joined
Jun/12/2022 08:49:08 caps,info cap1: selected channel 2452/20-Ce/gn(20dBm)
Jun/12/2022 08:49:18 route,debug,calc 3 Main publish
Jun/12/2022 08:49:33 route,debug,calc 1.3.1 Tag updated routes for merging
Jun/12/2022 08:49:33 route,debug,calc 1.3.4 Merge route updates
Jun/12/2022 08:49:39 route,debug,calc 2.2 Merge forwarding path updates
Jun/12/2022 08:49:39 caps,debug [::ffff:127.0.0.1:41810,Run,[2C:C8:1B:0D:DA:D1]] lost connection, keepalive timeout
Jun/12/2022 08:49:39 system,info,account user admin logged in from 192.168.88.20 via winbox
Jun/12/2022 08:49:41 dhcp,debug defconf received discover id 898288576 from 0.0.0.0 '1:dc:2c:6e:c7:ea:b'
Jun/12/2022 08:49:41 dhcp,debug,packet     secs = 15
Jun/12/2022 08:49:41 dhcp,debug,packet     flags = broadcast
Jun/12/2022 08:49:41 dhcp,debug,packet     ciaddr = 0.0.0.0
Jun/12/2022 08:49:41 dhcp,debug,packet     chaddr = DC:2C:6E:C7:EA:0B
Jun/12/2022 08:49:41 dhcp,debug,packet     Host-Name = "MikroTik"
Jun/12/2022 08:49:41 dhcp,debug,packet     Msg-Type = discover
Jun/12/2022 08:49:41 dhcp,debug,packet     Parameter-List = Subnet-Mask,Classless-Route,Router,Static-Route,Domain-Server,NTP-Server,CAPWAP-Server,Vendor-Specific
Jun/12/2022 08:49:41 dhcp,debug,packet     Client-Id = 01-DC-2C-6E-C7-EA-0B
Jun/12/2022 08:49:41 dhcp,debug lease found, bound, offer
Jun/12/2022 08:49:41 dhcp,info defconf deassigned 192.168.88.2 for DC:2C:6E:C7:EA:0B MikroTik
Jun/12/2022 08:49:43 dhcp,debug defconf sending offer with id 898288576 to 255.255.255.255
Jun/12/2022 08:49:43 dhcp,debug,packet     flags = broadcast
Jun/12/2022 08:49:43 dhcp,debug,packet     ciaddr = 0.0.0.0
Jun/12/2022 08:49:43 dhcp,debug,packet     yiaddr = 192.168.88.2
Jun/12/2022 08:49:43 dhcp,debug,packet     siaddr = 192.168.88.1
Jun/12/2022 08:49:43 dhcp,debug,packet     chaddr = DC:2C:6E:C7:EA:0B
Jun/12/2022 08:49:43 dhcp,debug,packet     Subnet-Mask = 255.255.255.0
Jun/12/2022 08:49:43 dhcp,debug,packet     Router = 192.168.88.1
Jun/12/2022 08:49:43 dhcp,debug,packet     Domain-Server = 192.168.88.1
Jun/12/2022 08:49:43 dhcp,debug,packet     Address-Time = 600
Jun/12/2022 08:49:43 dhcp,debug,packet     Msg-Type = offer
Jun/12/2022 08:49:43 dhcp,debug,packet     Server-Id = 192.168.88.1
Jun/12/2022 08:49:43 dhcp,debug defconf received request id 898288576 from 0.0.0.0 '1:dc:2c:6e:c7:ea:b'
Jun/12/2022 08:49:43 dhcp,debug,packet     secs = 15
Jun/12/2022 08:49:43 dhcp,debug,packet     flags = broadcast
Jun/12/2022 08:49:43 dhcp,debug,packet     ciaddr = 0.0.0.0
Jun/12/2022 08:49:43 dhcp,debug,packet     chaddr = DC:2C:6E:C7:EA:0B
Jun/12/2022 08:49:43 dhcp,debug,packet     Host-Name = "MikroTik"
Jun/12/2022 08:49:43 dhcp,debug,packet     Address-Request = 192.168.88.2
Jun/12/2022 08:49:43 dhcp,debug,packet     Msg-Type = request
Jun/12/2022 08:49:43 dhcp,debug,packet     Server-Id = 192.168.88.1
Jun/12/2022 08:49:43 dhcp,debug,packet     Parameter-List = Subnet-Mask,Classless-Route,Router,Static-Route,Domain-Server,NTP-Server,CAPWAP-Server,Vendor-Specific
Jun/12/2022 08:49:43 dhcp,debug,packet     Client-Id = 01-DC-2C-6E-C7-EA-0B
Jun/12/2022 08:49:43 dhcp,debug lease offered, addressed to me
Jun/12/2022 08:49:44 dhcp,info defconf assigned 192.168.88.2 for DC:2C:6E:C7:EA:0B MikroTik
Jun/12/2022 08:49:44 dhcp,debug defconf sending ack with id 898288576 to 255.255.255.255
Jun/12/2022 08:49:44 dhcp,debug,packet     flags = broadcast
Jun/12/2022 08:49:44 dhcp,debug,packet     ciaddr = 0.0.0.0
Jun/12/2022 08:49:44 dhcp,debug,packet     yiaddr = 192.168.88.2
Jun/12/2022 08:49:44 dhcp,debug,packet     siaddr = 192.168.88.1
Jun/12/2022 08:49:44 dhcp,debug,packet     chaddr = DC:2C:6E:C7:EA:0B
Jun/12/2022 08:49:44 dhcp,debug,packet     Subnet-Mask = 255.255.255.0
Jun/12/2022 08:49:44 dhcp,debug,packet     Router = 192.168.88.1
Jun/12/2022 08:49:44 dhcp,debug,packet     Domain-Server = 192.168.88.1
Jun/12/2022 08:49:44 dhcp,debug,packet     Address-Time = 600
Jun/12/2022 08:49:44 dhcp,debug,packet     Msg-Type = ack
Jun/12/2022 08:49:44 dhcp,debug,packet     Server-Id = 192.168.88.1
Jun/12/2022 08:49:45 route,debug,calc 3 Main publish
Jun/12/2022 08:50:02 dhcp,debug lease 192.168.88.12 expired
Jun/12/2022 08:50:06 system,info,account user admin logged out from 192.168.88.20 via winbox
Jun/12/2022 08:50:06 dhcp,info defconf deassigned 192.168.88.12 for 9C:76:13:9F:B8:2B RingStickUpCam-2b
Jun/12/2022 08:50:19 dhcp,debug defconf received request id 2876827417 from 192.168.88.21 '1:dc:a6:32:3f:db:e0'
Jun/12/2022 08:50:19 dhcp,debug,packet     secs = 65535
Jun/12/2022 08:50:19 dhcp,debug,packet     ciaddr = 192.168.88.21
Jun/12/2022 08:50:19 dhcp,debug,packet     chaddr = DC:A6:32:3F:DB:E0
Jun/12/2022 08:50:19 dhcp,debug,packet     Host-Name = "raspberrypi"
Jun/12/2022 08:50:19 dhcp,debug,packet     Msg-Type = request
Jun/12/2022 08:50:19 dhcp,debug,packet     Parameter-List = Subnet-Mask,Classless-Route,Static-Route,Router,Domain-Server,Host-Name,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Server-Id,Renewal-Time,Rebinding-Time,Domain-Search
Jun/12/2022 08:50:19 dhcp,debug,packet     Max-DHCP-Message-Size = 1472
Jun/12/2022 08:50:19 dhcp,debug,packet     Client-Id = 01-DC-A6-32-3F-DB-E0
Jun/12/2022 08:50:19 dhcp,debug,packet     Unknown(145) = 01
Jun/12/2022 08:50:19 dhcp,debug lease bound, extending
Jun/12/2022 08:50:23 dhcp,debug defconf sending ack with id 2876827417 to 192.168.88.21
Jun/12/2022 08:50:24 dhcp,debug,packet     ciaddr = 192.168.88.21
Jun/12/2022 08:50:24 dhcp,debug,packet     yiaddr = 192.168.88.21
Jun/12/2022 08:50:24 dhcp,debug,packet     siaddr = 192.168.88.1
Jun/12/2022 08:50:24 dhcp,debug,packet     chaddr = DC:A6:32:3F:DB:E0
Jun/12/2022 08:50:24 dhcp,debug,packet     Subnet-Mask = 255.255.255.0
Jun/12/2022 08:50:24 dhcp,debug,packet     Router = 192.168.88.1
Jun/12/2022 08:50:24 dhcp,debug,packet     Domain-Server = 192.168.88.1
Jun/12/2022 08:50:24 dhcp,debug,packet     Address-Time = 600
Jun/12/2022 08:50:24 dhcp,debug,packet     Msg-Type = ack
Jun/12/2022 08:50:24 dhcp,debug,packet     Server-Id = 192.168.88.1
Jun/12/2022 08:50:25 dhcp,debug defconf received request id 2876827417 from 192.168.88.21 '1:dc:a6:32:3f:db:e0'
Jun/12/2022 08:50:25 dhcp,debug,packet     secs = 65535
Jun/12/2022 08:50:25 dhcp,debug,packet     ciaddr = 192.168.88.21
Jun/12/2022 08:50:25 dhcp,debug,packet     chaddr = DC:A6:32:3F:DB:E0
Jun/12/2022 08:50:25 dhcp,debug,packet     Host-Name = "raspberrypi"
Jun/12/2022 08:50:25 dhcp,debug,packet     Msg-Type = request
Jun/12/2022 08:50:25 dhcp,debug,packet     Parameter-List = Subnet-Mask,Classless-Route,Static-Route,Router,Domain-Server,Host-Name,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Server-Id,Renewal-Time,Rebinding-Time,Domain-Search
Jun/12/2022 08:50:25 dhcp,debug,packet     Max-DHCP-Message-Size = 1472
Jun/12/2022 08:50:25 dhcp,debug,packet     Client-Id = 01-DC-A6-32-3F-DB-E0
Jun/12/2022 08:50:25 dhcp,debug,packet     Unknown(145) = 01
Jun/12/2022 08:50:25 dhcp,debug lease bound, extending
Jun/12/2022 08:50:26 dhcp,debug defconf sending ack with id 2876827417 to 192.168.88.21
Jun/12/2022 08:50:26 dhcp,debug,packet     ciaddr = 192.168.88.21
Jun/12/2022 08:50:26 dhcp,debug,packet     yiaddr = 192.168.88.21
Jun/12/2022 08:50:26 dhcp,debug,packet     siaddr = 192.168.88.1
Jun/12/2022 08:50:26 dhcp,debug,packet     chaddr = DC:A6:32:3F:DB:E0
Jun/12/2022 08:50:26 dhcp,debug,packet     Subnet-Mask = 255.255.255.0
Jun/12/2022 08:50:26 dhcp,debug,packet     Router = 192.168.88.1
Jun/12/2022 08:50:26 dhcp,debug,packet     Domain-Server = 192.168.88.1
Jun/12/2022 08:50:26 dhcp,debug,packet     Address-Time = 600
Jun/12/2022 08:50:26 dhcp,debug,packet     Msg-Type = ack
Jun/12/2022 08:50:26 dhcp,debug,packet     Server-Id = 192.168.88.1
Jun/11/2022 11:51:51 system,error,critical router was rebooted without proper shutdown
Jun/11/2022 11:51:51 route,rpki,debug stats roas 0 roa 0 nodes4 0 nodes6 0
Jun/11/2022 11:51:52 system,error,critical kernel failure in previous boot
Jun/11/2022 11:51:52 system,error,critical out of memory condition was detected
cAP lite RouterOS 7.3.1
Jun/12/2022 08:47:54 caps,info CAP connect to MikroTik (2C:C8:1B:0D:DA:D2/6/0) failed: timeout
Jun/12/2022 08:47:54 caps,info CAP failed to join MikroTik (2C:C8:1B:0D:DA:D2/6/0)
Jun/12/2022 08:47:54 caps,debug CAP Connect->Select
Jun/12/2022 08:47:54 caps,info CAP selected CAPsMAN MikroTik (::ffff:192.168.88.1:5246)
Jun/12/2022 08:47:54 caps,debug CAP Select->Connect
Jun/12/2022 08:47:54 certificate,debug start CRL update
Jun/12/2022 08:48:05 certificate,debug start CRL update
Jun/12/2022 08:48:14 caps,info CAP connect to MikroTik (::ffff:192.168.88.1:5246) failed: timeout
Jun/12/2022 08:48:14 caps,info CAP failed to join MikroTik (::ffff:192.168.88.1:5246)
Jun/12/2022 08:48:14 caps,debug CAP Connect->Select
Jun/12/2022 08:48:14 caps,debug CAP did not find suitable CAPsMAN
Jun/12/2022 08:48:14 caps,debug CAP Select->Sulking
Jun/12/2022 08:48:19 caps,debug CAP Sulking->Discover
Jun/12/2022 08:48:19 caps,debug CAP discovery target list:
Jun/12/2022 08:48:22 caps,debug CAP discovery over, no results
Jun/12/2022 08:48:22 caps,debug CAP Discover->Select
Jun/12/2022 08:48:22 caps,debug CAP did not find suitable CAPsMAN
Jun/12/2022 08:48:22 caps,debug CAP Select->Sulking
Jun/12/2022 08:48:25 certificate,debug start CRL update
Jun/12/2022 08:48:27 caps,debug CAP Sulking->Discover
Jun/12/2022 08:48:27 caps,debug CAP discovery target list:
Jun/12/2022 08:48:29 caps,debug CAP discovery over, no results
Jun/12/2022 08:48:29 caps,debug CAP Discover->Select
Jun/12/2022 08:48:29 caps,debug CAP did not find suitable CAPsMAN
Jun/12/2022 08:48:29 caps,debug CAP Select->Sulking
Jun/12/2022 08:48:34 caps,debug CAP Sulking->Discover
Jun/12/2022 08:48:34 caps,debug CAP discovery target list:
Jun/12/2022 08:48:37 caps,debug CAP discovery over, results:
Jun/12/2022 08:48:37 caps,debug   MikroTik (::ffff:192.168.88.1:5246)
Jun/12/2022 08:48:37 caps,debug   MikroTik (2C:C8:1B:0D:DA:D2/6/0)
Jun/12/2022 08:48:37 caps,debug CAP Discover->Select
Jun/12/2022 08:48:37 caps,info CAP selected CAPsMAN MikroTik (2C:C8:1B:0D:DA:D2/6/0)
Jun/12/2022 08:48:37 caps,debug CAP Select->Connect
Jun/11/2022 11:47:18 system,error,critical router was rebooted without proper shutdown by watchdog timer
Now I try 7.4beta2 and then I'll go back to 6.49.6
 
User avatar
Ca6ko
Member
Member
Posts: 499
Joined: Wed May 04, 2022 10:59 pm
Location: Kharkiv, Ukraine

Re: CAPsMAN unstable after upgrade to 7.3

Sun Jun 12, 2022 10:41 am

It's better to go straight back to 6.48.6 Long-term
 
massinia
Member Candidate
Member Candidate
Topic Author
Posts: 159
Joined: Thu Jun 09, 2022 7:20 pm

Re: CAPsMAN unstable after upgrade to 7.3

Sun Jun 12, 2022 10:56 am

Yes, probably 32 MB of RAM is not enough for the 7.3.x and CAPsMAN.
 
massinia
Member Candidate
Member Candidate
Topic Author
Posts: 159
Joined: Thu Jun 09, 2022 7:20 pm

Re: CAPsMAN unstable after upgrade to 7.3

Tue Jun 14, 2022 11:48 am

Apparently the problem is not CAPsMAN, hAP lite reboots itself with out of memory error also when used as a simple router.

1. Reset and set "Home AP" with Quick Set
2. Connect Internet and 10 devices, wait approximately 24 hours
3. Login with WinBox and router reboot itself.

It is incredible that only I have reported the problem...
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11433
Joined: Thu Mar 03, 2016 10:23 pm

Re: CAPsMAN unstable after upgrade to 7.3

Tue Jun 14, 2022 12:11 pm

It is incredible that only I have reported the problem...

Could it be that nobody else manages to reach the step #2 from your list? :wink:
 
massinia
Member Candidate
Member Candidate
Topic Author
Posts: 159
Joined: Thu Jun 09, 2022 7:20 pm

Re: CAPsMAN unstable after upgrade to 7.3

Sun Jun 19, 2022 12:23 am

Do you have the same issue on 7.4beta2?
No and I don't know why but you were right, 7.4beta2 and beta4 handle RAM much better, when you only have 32MB it's essential.
I had never see 5 days of uptime with 7.3 and 7.3.1

Thanks
 
massinia
Member Candidate
Member Candidate
Topic Author
Posts: 159
Joined: Thu Jun 09, 2022 7:20 pm

Re: CAPsMAN unstable after upgrade to 7.3

Sat Sep 10, 2022 12:46 pm

I had never see 5 days of uptime with 7.3 and 7.3.1
Just to say that from RouterOS 7.4 I have no more problems.

Thank you all

Who is online

Users browsing this forum: PBondurant and 42 guests