I've got 2 x RT-AC68U, one as router, and the other one as an AiMesh node, with wireless/5Ghz backbone. ~8m , clear sight, between the two units. RSSI usually hoovers around -53 dBm between them. The two other units that hass been used when I'm getting my issue is a phone and a chromecast, both should be fairly close with very good connection to the AiMesh node, however I'm not sure which router they where connected to when the issue appeared (they should be able to reach both). Apart from these units there is probably around 10 other units on the Wifi (various phones, TV:s, computer e.t.c.)
My issue is, that sometimes when I watch something on the Chromecast, it suddenly stoppes. I then check my phone and see that I'm connected to Wifi, but I do not have any internet connection. After ~10 seconds the wifi drops completely and I cant find the SSID when I rescan. After another ~30sec I can find the SSID again, and after an additional ~30sec I can get internet access on the wifi. To me it feels like something is rebooting on either the main router, or the mesh node. I am not sure if the units where connected to the router or the mesh node, but eitherway I should reach both units when scanning SSID, so feels like both are down.
Romaing assist is turned on with a threshold at -63 (I had the same issue at -70). Airtime fairness and Beamforming is enabled. I've reseted both routers more than once and set up everything from scratch. Both running latest firmware.
Below is an extract from the syslog, which i guess is from the main router. The issue appeared around 21:07 (+- 1min).
Oct 10 20:07:06 roamast: eth1: remove client [Another, not mine, Phone MAC] from monitor list
Oct 10 20:07:08 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind [Another, not mine, Phone MAC], status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Oct 10 21:06:32 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth [Chromecast MAC], status: Successful (0)
Oct 10 21:06:32 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc[ Chromecast MAC], status: Successful (0)
Oct 10 21:06:49 roamast: determine candidate node [AiMesh node MAC](rssi: -39dbm) for client [Chromecast MAC](rssi: -68dbm) to roam
Oct 10 21:06:49 roamast: Roam a client [Chromecast MAC], status [0]
Oct 10 21:07:09 roamast: determine candidate node [AiMesh node MAC](rssi: -39dbm) for client [Chromecast MAC](rssi: -68dbm) to roam
Oct 10 21:07:09 roamast: Roam a client [Chromecast MAC], status [0]
Oct 10 21:07:30 kernel: SHN Release Version: 2.0.1 890c91d
Oct 10 21:07:30 kernel: UDB Core Version: 0.2.18
Oct 10 21:07:31 kernel: sizeof forward pkt param = 192
Oct 10 21:07:31 BWDPI: fun bitmap = 3
Oct 10 21:07:45 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Oct 10 21:17:49 roamast: determine candidate node [AiMesh node MAC](rssi: -40dbm) for client [Chromecast MAC](rssi: -70dbm) to roam
Oct 10 21:17:49 roamast: Roam a client [Chromecast MAC], status [0]
Oct 10 21:33:04 roamast: determine candidate node [AiMesh node MAC](rssi: -40dbm) for client [Chromecast MAC](rssi: -69dbm) to roam
Oct 10 21:33:04 roamast: Roam a client [Chromecast MAC], status [0]
Oct 10 21:49:59 roamast: determine candidate node [AiMesh node MAC](rssi: -40dbm) for client [Chromecast MAC](rssi: -70dbm) to roam
Oct 10 21:49:59 roamast: Roam a client [Chromecast MAC], status [0]
Oct 10 21:51:04 roamast: determine candidate node [AiMesh node MAC](rssi: -40dbm) for client [Chromecast MAC](rssi: -67dbm) to roam
So, a couple of questions:
My issue is, that sometimes when I watch something on the Chromecast, it suddenly stoppes. I then check my phone and see that I'm connected to Wifi, but I do not have any internet connection. After ~10 seconds the wifi drops completely and I cant find the SSID when I rescan. After another ~30sec I can find the SSID again, and after an additional ~30sec I can get internet access on the wifi. To me it feels like something is rebooting on either the main router, or the mesh node. I am not sure if the units where connected to the router or the mesh node, but eitherway I should reach both units when scanning SSID, so feels like both are down.
Romaing assist is turned on with a threshold at -63 (I had the same issue at -70). Airtime fairness and Beamforming is enabled. I've reseted both routers more than once and set up everything from scratch. Both running latest firmware.
Below is an extract from the syslog, which i guess is from the main router. The issue appeared around 21:07 (+- 1min).
Oct 10 20:07:06 roamast: eth1: remove client [Another, not mine, Phone MAC] from monitor list
Oct 10 20:07:08 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind [Another, not mine, Phone MAC], status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Oct 10 21:06:32 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth [Chromecast MAC], status: Successful (0)
Oct 10 21:06:32 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc[ Chromecast MAC], status: Successful (0)
Oct 10 21:06:49 roamast: determine candidate node [AiMesh node MAC](rssi: -39dbm) for client [Chromecast MAC](rssi: -68dbm) to roam
Oct 10 21:06:49 roamast: Roam a client [Chromecast MAC], status [0]
Oct 10 21:07:09 roamast: determine candidate node [AiMesh node MAC](rssi: -39dbm) for client [Chromecast MAC](rssi: -68dbm) to roam
Oct 10 21:07:09 roamast: Roam a client [Chromecast MAC], status [0]
Oct 10 21:07:30 kernel: SHN Release Version: 2.0.1 890c91d
Oct 10 21:07:30 kernel: UDB Core Version: 0.2.18
Oct 10 21:07:31 kernel: sizeof forward pkt param = 192
Oct 10 21:07:31 BWDPI: fun bitmap = 3
Oct 10 21:07:45 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Oct 10 21:17:49 roamast: determine candidate node [AiMesh node MAC](rssi: -40dbm) for client [Chromecast MAC](rssi: -70dbm) to roam
Oct 10 21:17:49 roamast: Roam a client [Chromecast MAC], status [0]
Oct 10 21:33:04 roamast: determine candidate node [AiMesh node MAC](rssi: -40dbm) for client [Chromecast MAC](rssi: -69dbm) to roam
Oct 10 21:33:04 roamast: Roam a client [Chromecast MAC], status [0]
Oct 10 21:49:59 roamast: determine candidate node [AiMesh node MAC](rssi: -40dbm) for client [Chromecast MAC](rssi: -70dbm) to roam
Oct 10 21:49:59 roamast: Roam a client [Chromecast MAC], status [0]
Oct 10 21:51:04 roamast: determine candidate node [AiMesh node MAC](rssi: -40dbm) for client [Chromecast MAC](rssi: -67dbm) to roam
So, a couple of questions:
- If I understand the log correct, the Chromecast has rssi of -39 to the Mesh Node, but current RSSI is -68, shouldn't this roam to the mesh node? Does not seem like it does...
- Why does the Kernel print the SHN and UDB version, is this an indication of that something rebooted?
- Can anbody spot something in the log that might help me troubleshoot the downtime I am experiensing (happens a couple of times each week).
- Can I get the syslog from the Mesh node as well?
Last edited: