hAP ac2 has 3 more ethernet ports, so more buffer on switch chip is in use … perhaps that’s a life saver? LOL
cAP ac and hAP ac are using exactly the same SOC IPQ-4018 with same integrated switch chip 8327 inside, the only difference being that on cAP only two ethernet lines are in use… I have the same OOM issues and I presume that the reason is number of wifi connections over time and wifi-qcom-ac driver not releasing memory on disconnects…
Is it possible to use SWAP file in ROS? E.g. on a USB disk
Hi,
In order to try and resolve what I think to be an ARP issue (that’s driving me nuts) I decided to try the beta, namely 7.16rs4 as that mentions fixes for arp and bridging related issues.
However, immediately after the update, the wireless was non-functional, so a breaking update. Not sure if that is intentional but now needs post update reconfig/reboot to bring it back.
It seems it’s reverted to the old ‘wireless’ package instead of the newer ‘wifi-qcom’, which I can see is present but deactivated.
The logs from first boot in case that helps look into this, but I can’t see anything that would be useful myself…
Note there were three lines that appeared on the console but not in the downloaded log file using
/log/print detail without-paging
They had no prefix on the console, but are in the in-memory log, so I added that here by hand
They seem out of place as this is not a new install so no defaults need apply, why was it trying to run a script?
After this (apart from the missing wireless) nothing out of the ordinary.
1.time=“Sep/04/2024 19:08:46” topics=“script,warning” message=“DefConf gen: Unable to find wireless interface(s)”
2.time=“Sep/04/2024 19:08:46” topics=“system,error,critical” message=“error while running customized default configuration script: interrupted”
3.time=“Sep/04/2024 19:08:46” topics=“system,error,critical” message=“” <i.e. an empty log message>
time=19:08:04 topics=system,info message="installed system-7.16rc4"
time=19:08:04 topics=system,info message="installed rose-storage-7.16rc4"
time=19:08:04 topics=system,info message="installed container-7.16rc4"
time=19:08:04 topics=system,info message="installed wireless-7.16rc4"
time=19:08:04 topics=system,info message="installed wifi-qcom-7.16rc4"
time=19:08:04 topics=system,info message="router rebooted"
time=19:08:05 topics=interface,info message="lo link up"
time=19:08:05 topics=interface,info message="VLAN100<->F/W link up"
time=19:08:05 topics=interface,info message="isp<->VLAN666<->f/w link up"
time=19:08:05 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <selecting...> state"
time=19:08:06 topics=bridge,info message=""BR100-dmz" mac address changed to 3A:96:B4:xx:xx:xx"
time=19:08:06 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <stopped> state"
time=19:08:06 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <selecting...> state"
time=19:08:06 topics=interface,info message="VLAN99 link up"
time=19:08:06 topics=bridge,info message=""BR11-lan" mac address changed to 8E:DD:3A:yy:yy:yy"
time=19:08:06 topics=interface,info message="VLAN11 link up"
time=19:08:06 topics=interface,info message="VLAN22 link up"
time=19:08:06 topics=interface,info message="VLAN24 link up"
time=19:08:06 topics=bridge,info message=""BR99-work" mac address changed to 8E:DD:3A:yy:yy:yy"
time=19:08:07 topics=bridge,info message=""BR100-dmz" mac address changed to 8E:DD:3A:yy:yy:yy"
time=19:08:07 topics=bridge,info message=""BR22-wifi-p" mac address changed to 8E:DD:3A:yy:yy:yy"
time=19:08:07 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <stopped> state"
time=19:08:07 topics=bridge,info message=""BR24-wifi-d" mac address changed to 8E:DD:3A:yy:yy:yy"
time=19:08:07 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <selecting...> state"
time=19:08:07 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <stopped> state"
time=19:08:07 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <selecting...> state"
time=19:08:10 topics=interface,info message="1:ISP-Virgin link down"
time=19:08:10 topics=interface,info message="2:LAG3 link down"
time=19:08:10 topics=interface,info message="3:LAG3 link down"
time=19:08:10 topics=interface,info message="4:eth2-vlan11 link down"
time=19:08:10 topics=interface,info message="5:eth1-vlan55 link down"
time=19:08:12 topics=interface,info message="3:LAG3 link up (speed 1G, full duplex)"
time=19:08:12 topics=interface,info message="18:LAG3(P2+P3) link up"
time=19:08:12 topics=bridge,info message=""BR11-lan" mac address changed to 78:9A:18:zz:zz:zz"
time=19:08:12 topics=bridge,info message=""BR99-work" mac address changed to 78:9A:18:zz:zz:zz"
time=19:08:12 topics=bridge,info message=""BR22-wifi-p" mac address changed to 78:9A:18:zz:zz:zz"
time=19:08:12 topics=bridge,info message=""BR24-wifi-d" mac address changed to 78:9A:18:zz:zz:zz"
time=19:08:12 topics=bridge,info message=""BR100-dmz" mac address changed to 78:9A:18:zz:zz:zz"
time=19:08:13 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <stopped> state"
time=19:08:13 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <selecting...> state"
time=19:08:13 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <stopped> state"
time=19:08:13 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <selecting...> state"
time=19:08:13 topics=interface,info message="1:ISP-Virgin link up (speed 1G, full duplex)"
time=19:08:13 topics=interface,info message="2:LAG3 link up (speed 1G, full duplex)"
time=19:08:16 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <requesting...> state"
time=19:08:16 topics=dhcp,info message="dhcp-client on isp<->VLAN666<->f/w got IP address 82.1.1.1"
time=19:08:16 topics=dhcp,debug,state message="dhcp-client on isp<->VLAN666<->f/w entering <bound> state"
time=19:08:20 topics=system,info,account message="user admin logged in from 192.168.31.69 via winbox"
It seems that the traceroute command no longer shows the return packet size? It was present in the 7.11.3 version, but no longer. In both cli and winbox
installation check fails on any of my arm chr instances, even if i change to stable channel. i dont know if that happened during testing upgrades, thus i post it here. offline fsck of both partitions are fine.
[admin@xxx] /system> reso pr
uptime: 1m6s
version: 7.16rc4 (testing)
build-time: 2024-08-30 06:24:51
free-memory: 274.4MiB
total-memory: 576.0MiB
cpu: ARM64
cpu-count: 2
cpu-load: 1%
free-hdd-space: 67.4MiB
total-hdd-space: 80.7MiB
write-sect-since-reboot: 235
write-sect-total: 235
architecture-name: arm64
board-name: CHR QEMU KVM Virtual Machine
platform: MikroTik
[admin@xxx] /system> check-installation
damaged system package: bad image
If anyone is interested in how reselect.interval is affecting wireless connection, this is what I found in my log connecting two Wi-FI ac AP using v7.16rc4:
MAC.ADD@Bridge-WLAN: AP changed channel to 5660/ac/Ceee
MAC.ADD@Bridge-WLAN: disconnected, reason code 8, signal -84
- 2/4min later -
MAC.ADD@Bridge-WLAN: connected on 5660/ac/Ceee, signal -74
MAC.ADD@Bridge-WLAN: authorized, signal -74
What exactly does this do? I’m aware it’s possible to send and receive SMS either via AT commands over a (virtual) serial port or via MBIM commands. But isn’t that already determined by setting the port in “/tool sms” accordingly (usbX for AT or lteX for MBIM)? In which use cases would you need to use this new setting?
Probably not new to this release, but at least it is still there. User Manager things.
- Terminating EAP wifi sessions by User manager doesn’t work (NAK received from NAS , error cause in the packet = 605 = not implemented)
- Many “UM NAS rebooted” messages (with but sometimes also without any reboot of the AP (=NAS), what triggers even much more disconnect attemps by UM with NAK responses
- Trying to limit wifi EAP session time, to stop the NAK loop, …
— with UM Attribute "Session Timeout " fails to be triggered (Attribute is set in User Group)
— Idem for the “Session Limit” parameter in the limitation. Assigned to user via User → User Profiles → Profile → Profile Limitations → Limitations
Only thing that is triggered and works is the validity set in Profiles.
While testing the failover to the next “User Profile” , the information to the user is missing the GMT Offset correction. (GMT time shown?)
.
.
Sent by email a few minutes ago, thus no ticket number…
I am facing Wi-Fi connection issues with my hAP ax3, causing the laptop to disconnect during Zoom meetings. As you can see in the logs the laptop gets disconnected from AP despite having the strong signal. This happened in the recent stable version (7.15.3) and still happens in the latest rc version.
The laptop has an Intel(R) Wi-Fi 6 AX203 adapter, and the version of the driver is 23.60.1.2. Anything I can do to fix it myself?
So far the only solution for me was temporarily replacing hAP ax3 with my old hAP ac2 running wifi-qcom-ac drivers, which works pretty well.
18:05:54 wireless,info 90:09:DF:**:**:E9@wifi1 disconnected, SA Query timeout, signal strength -51
18:05:55 wireless,info 90:09:DF:**:**:E9@wifi2 connected, signal strength -44
18:06:59 wireless,info 90:09:DF:**:**:E9@wifi2 disconnected, SA Query timeout, signal strength -46
18:07:00 wireless,info 90:09:DF:**:**:E9@wifi2 connected, signal strength -50
18:12:06 wireless,info 90:09:DF:**:**:E9@wifi2 disconnected, SA Query timeout, signal strength -47
18:12:20 wireless,info 90:09:DF:**:**:E9@wifi1 connected, signal strength -51
18:14:12 wireless,info 90:09:DF:**:**:E9@wifi1 disconnected, SA Query timeout, signal strength -58
18:14:12 wireless,info 90:09:DF:**:**:E9@wifi2 connected, signal strength -50
18:14:22 wireless,info 90:09:DF:**:**:E9@wifi2 disconnected, SA Query timeout, signal strength -46
18:14:22 wireless,info 90:09:DF:**:**:E9@wifi1 connected, signal strength -50
18:14:36 system,info,account user ***** logged in from 192.168.11.233 via winbox
18:14:36 system,info,account user ***** logged in from 192.168.11.233 via winbox
18:18:28 wireless,info 90:09:DF:**:**:E9@wifi1 disconnected, SA Query timeout, signal strength -56
18:18:34 wireless,info 90:09:DF:**:**:E9@wifi1 connected, signal strength -51
18:28:42 wireless,info 90:09:DF:**:**:E9@wifi1 disconnected, SA Query timeout, signal strength -56
18:28:42 wireless,info 90:09:DF:**:**:E9@wifi2 connected, signal strength -48
18:28:57 wireless,info 90:09:DF:**:**:E9@wifi2 disconnected, SA Query timeout, signal strength -48
18:29:12 wireless,info 90:09:DF:**:**:E9@wifi1 connected, signal strength -52
Another observation is the network adapter does not always select the latest and greatest AX standard with the WPA3 security type. It often favors the AC standard over AX.
Current solution is rollback to 7.14.3
Disable WPA3…
I’m using the latest driver as of posting and here’s my uptime for my ax210 WPA2 only.
netsh wlan show drivers
Interface name: WiFi
Driver : Intel(R) Wi-Fi 6E AX210 160MHz
Vendor : Intel Corporation
Provider : Intel
Date : 24/07/2024
Version : 23.70.2.3
INF file : oem27.inf
Type : Native Wi-Fi Driver
I’m using same version 23.70.2.3 adapter is AX201
Thanks everyone! I’ve disabled WPA3 for now.
Will there be a mDNS announce for the MT devices?
Right now to use a pretty name you need to set up a static record which can’t be in .local AND you need to change its address manually (or write weird scripts to update address automatically).
+1
Could you please insert the used WPA version inside the capsman registration table?
So that we could see which version of WPA is used by a client?
I think that this would be a valuable enhancement.
I already requested that feature via SUP-158802.
Details11/Jul/24 11:09 AM
Description
Hello,
I have a feature request:
It would be nice to have a column in wifi/registration-table which shows the active security-type of the registered client. e.g. wpa2-psk,wpa3-psk,etc. Maybe even more “granular” as there are many subtypes for WPA and EAP as well. WPA2-PSK+FT, WPA3+FT to just name these two.
Such a column would really help people to troubleshoot “problematic” clients. As the used authentication types if quite often the source of issues at some clients.
Thank you!