What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

RT-AX86U PRO - CSIMON: M2M usr already registered

dineshgyl

Occasional Visitor
Since yesterday I am having issues with 2.4GHz network. All Wifi clients dropping.

I can see my log is flodded with following.

Code:
Mar 23 12:14:19 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:14:19 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:14:37 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:14:37 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:14:38 hostapd: eth6: STA cc:8c:bf:76:c9:97 IEEE 802.11: disassociated
Mar 23 12:14:38 wlceventd: wlceventd_proc_event(662): eth6: Disassoc CC:8C:BF:76:C9:97, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 23 12:14:55 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:14:55 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:15:10 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:15:10 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:15:15 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:15:15 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:15:21 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:15:21 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:15:32 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:15:32 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:16:00 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:16:00 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:16:12 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:16:12 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:16:24 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:16:24 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:16:38 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:16:38 kernel: CSIMON: M2M usr already registered ...

I did not make any changes. Router was running fine no reboots since Feb 17.

However yesterday suddenly all of this started coming and I did factory reset and reconfigured everything from scratch.

I am not using anything special. Just normal settings.

Operation Mode:Wireless router Firmware:3004.388.8_4

1742746798160.png


1742746829510.png


Please help. Router is new, bought it in Nov 2024.
 
Searching these forums for 'CSIMON' there are posts that suggest that USB3 use can impact 2.4Ghz Wireless.
Have you changed something related to USB3 ?

I suggest you search the forums for other hints !!!
[Top righthand search box]

Sorry I cannot offer any more useful advice.
 
The other suggestion was to change the 'AUTO' setting on Control Channel to a specific Channel.

Try running the Site Survey ... at http://<Router IP Address>/Advanced_Wireless_Survey.asp
[Set <Router IP Address> as necessary.]

Pick a Channel that is not in major use on the 2.4 GHz band.
 
Last edited:
Since yesterday I am having issues with 2.4GHz network. All Wifi clients dropping.

I can see my log is flodded with following.

Code:
Mar 23 12:14:19 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:14:19 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:14:37 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:14:37 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:14:38 hostapd: eth6: STA cc:8c:bf:76:c9:97 IEEE 802.11: disassociated
Mar 23 12:14:38 wlceventd: wlceventd_proc_event(662): eth6: Disassoc CC:8C:BF:76:C9:97, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 23 12:14:55 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:14:55 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:15:10 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:15:10 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:15:15 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:15:15 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:15:21 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:15:21 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:15:32 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:15:32 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:16:00 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:16:00 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:16:12 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:16:12 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:16:24 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:16:24 kernel: CSIMON: M2M usr already registered ...
Mar 23 12:16:38 kernel: CSIMON:  CSIMON[1.1.0] Initialization
Mar 23 12:16:38 kernel: CSIMON: M2M usr already registered ...

I did not make any changes. Router was running fine no reboots since Feb 17.

However yesterday suddenly all of this started coming and I did factory reset and reconfigured everything from scratch.

I am not using anything special. Just normal settings.

Operation Mode:Wireless router Firmware:3004.388.8_4

View attachment 64525

View attachment 64526

Please help. Router is new, bought it in Nov 2024.
Try downgrading the modulation scheme one step at a time to see if that helps. IoT devices in particular seem to have the most problems connecting and staying connected to 2.4 Ghz radios with all the bells and whistles enbled. I am getting to the point where for certain IoT devices I have them connecting to an old travel router of mine that has a single N radio running and run it as AP off a LAN port from my AX88 Pro that is on its own VLAN/subnet. Once Merlin has a stable release version of the firmware for the AX88 Pro I may try downgrading it to the lowest modulation scheme (N) on the 2.4 Ghz radio as all the devices that need greater bandwidth either already connect to the 5 Ghz radio or Ethernet.
 
Thanks will take a look. As of now, it started working fine after reboot of router but not sure how long it will work for.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top