RT-AC88U AiMesh with RT-AC68U problems

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

espineira

New Around Here
I have a RT-AC88U running firmware 384.17_0 and trying to add an RT-AC68U running 384.17_0 as an AiMesh node. But whenever I bring the node online the combo becomes unstable and I get constant restarts and my NAS has connectivity issues with its bonded ethernet on ports 1 & 2.

Taking the AC68U offline stops the problems. Any pointers?

Thanks!!

HERE IS THE LOG:

May 27 13:08:40 WLCEVENTD: Auth 58:6B:14:8D:C0:36
May 27 13:08:40 WLCEVENTD: Assoc 58:6B:14:8D:C0:36
May 27 13:09:03 WLCEVENTD: Disassoc 58:6B:14:8D:C0:36
May 27 13:09:03 WLCEVENTD: Disassoc 58:6B:14:8D:C0:36
May 27 13:09:36 WLCEVENTD: Auth 58:6B:14:8D:C0:36
May 27 13:09:36 WLCEVENTD: Assoc 58:6B:14:8D:C0:36
May 27 13:10:38 rc_service: cfg_server 1347:notify_rc restart_obd_monitor
May 27 13:13:45 rc_service: cfg_server 1347:notify_rc restart_wireless
May 27 13:13:46 kernel: ubi1: attaching mtd10
May 27 13:13:46 kernel: ubi1: scanning is finished
May 27 13:13:46 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
May 27 13:13:46 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 27 13:13:46 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 27 13:13:46 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 27 13:13:46 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 27 13:13:46 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 27 13:13:46 kernel: ubi1: max/mean erase counter: 40/17, WL threshold: 4096, image sequence number: 527176359
May 27 13:13:46 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 27 13:13:46 kernel: ubi1: background thread "ubi_bgt1d" started, PID 28813
May 27 13:13:47 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 28831
May 27 13:13:47 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
May 27 13:13:47 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 27 13:13:47 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
May 27 13:13:47 kernel: UBIFS (ubi1:0): reserved for root: 0 bytes (0 KiB)
May 27 13:13:47 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 2A6BEA28-491B-4503-A426-8F74D62305AF, small LPT model
May 27 13:13:47 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 27 13:13:47 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
May 27 13:13:47 kernel: ubi1: detaching mtd10
May 27 13:13:47 kernel: ubi1: mtd10 is detached
May 27 13:13:48 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 13:13:48 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 13:13:48 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link DOWN.
May 27 13:13:48 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
May 27 13:13:53 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link UP at 1000 mbps full duplex
May 27 13:13:53 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
May 27 13:13:53 kernel: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
May 27 13:13:53 kernel: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
May 27 13:13:53 acsd: eth7: Selecting 5g band ACS policy
May 27 13:13:53 : Auth 74:75:48:0D:D7:87
May 27 13:13:53 : Assoc 74:75:48:0D:D7:87
May 27 13:13:53 : Assoc 74:75:48:0D:D7:87
May 27 13:13:57 WLCEVENTD: Auth 68:FF:7B:C2:2C:FE
May 27 13:13:57 WLCEVENTD: Assoc 68:FF:7B:C2:2C:FE
May 27 13:13:58 WLCEVENTD: Auth A8:5E:45:98:64:31
May 27 13:13:58 WLCEVENTD: Assoc A8:5E:45:98:64:31
May 27 13:13:58 WLCEVENTD: Deauth_ind 68:FF:7B:C2:2C:FE
May 27 13:13:58 kernel: wfd_registerdevice Successfully registered dev wds0.0.4 ifidx 1 wfd_idx 0
May 27 13:13:58 kernel: Register interface [wds0.0.4] MAC: 04:d4:c4:50:fb:d8
May 27 13:13:59 WLCEVENTD: Auth 58:6B:14:8D:C0:36
May 27 13:13:59 WLCEVENTD: Assoc 58:6B:14:8D:C0:36
May 27 13:13:59 acsd: eth7: selected channel spec: 0xe06a (100/80)
May 27 13:13:59 acsd: eth7: Adjusted channel spec: 0xe06a (100/80)
May 27 13:13:59 acsd: eth7: selected channel spec: 0xe06a (100/80)
May 27 13:13:59 acsd: acs_set_chspec: 0xe06a (100/80) for reason APCS_INIT
May 27 13:13:59 WLCEVENTD: Auth 00:BB:3A:42:9F:77
May 27 13:13:59 WLCEVENTD: Assoc 00:BB:3A:42:9F:77
May 27 13:14:01 WLCEVENTD: Disassoc 74:75:48:0D:D7:87
May 27 13:14:01 WLCEVENTD: Disassoc 74:75:48:0D:D7:87
May 27 13:15:22 WLCEVENTD: Auth 4C:56:9D:1A:2A:5F
May 27 13:15:22 WLCEVENTD: ReAssoc 4C:56:9D:1A:2A:5F
May 27 13:15:27 rc_service: cfg_server 1347:notify_rc restart_wireless
May 27 13:15:28 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
May 27 13:15:28 kernel: ubi1: attaching mtd10
May 27 13:15:28 kernel: ubi1: scanning is finished
May 27 13:15:28 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
May 27 13:15:28 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 27 13:15:28 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 27 13:15:28 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 27 13:15:28 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 27 13:15:28 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 27 13:15:28 kernel: ubi1: max/mean erase counter: 40/17, WL threshold: 4096, image sequence number: 527176359
May 27 13:15:28 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 27 13:15:28 kernel: ubi1: background thread "ubi_bgt1d" started, PID 29281
May 27 13:15:29 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 29311
May 27 13:15:29 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
May 27 13:15:29 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 27 13:15:29 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
May 27 13:15:29 kernel: UBIFS (ubi1:0): reserved for root: 0 bytes (0 KiB)
May 27 13:15:29 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 2A6BEA28-491B-4503-A426-8F74D62305AF, small LPT model
May 27 13:15:29 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 27 13:15:29 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
May 27 13:15:29 kernel: ubi1: detaching mtd10
May 27 13:15:29 kernel: ubi1: mtd10 is detached
May 27 13:15:31 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 13:15:31 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 13:15:31 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link DOWN.
May 27 13:15:31 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
May 27 13:15:34 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
May 27 13:15:34 kernel: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
May 27 13:15:35 acsd: eth7: Selecting 5g band ACS policy
May 27 13:15:35 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link UP at 1000 mbps full duplex
May 27 13:15:41 WLCEVENTD: Auth AC:D5:64:BA:33:F9
May 27 13:15:41 WLCEVENTD: ReAssoc AC:D5:64:BA:33:F9
May 27 13:15:41 acsd: eth7: selected channel spec: 0xe06a (100/80)
May 27 13:15:41 acsd: eth7: Adjusted channel spec: 0xe06a (100/80)
May 27 13:15:41 acsd: eth7: selected channel spec: 0xe06a (100/80)
May 27 13:15:41 acsd: acs_set_chspec: 0xe06a (100/80) for reason APCS_INIT
May 27 13:15:52 WLCEVENTD: Auth 58:6B:14:8D:C0:36
May 27 13:15:53 WLCEVENTD: ReAssoc 58:6B:14:8D:C0:36
May 27 13:15:57 WLCEVENTD: Auth 4C:56:9D:1A:2A:5F
May 27 13:15:57 WLCEVENTD: ReAssoc 4C:56:9D:1A:2A:5F
 

espineira

New Around Here
And again...

May 27 14:05:03 WLCEVENTD: Disassoc 58:6B:14:8D:C0:36
May 27 14:05:03 WLCEVENTD: Disassoc 58:6B:14:8D:C0:36
May 27 14:05:22 WLCEVENTD: Auth 74:75:48:83:D0:82
May 27 14:05:22 WLCEVENTD: ReAssoc 74:75:48:83:D0:82
May 27 14:09:28 WLCEVENTD: Auth A4:83:E7:37:39:68
May 27 14:09:28 WLCEVENTD: Assoc A4:83:E7:37:39:68
May 27 14:10:30 rc_service: cfg_server 1347:notify_rc restart_wireless
May 27 14:10:30 kernel: ubi1: attaching mtd10
May 27 14:10:30 kernel: ubi1: scanning is finished
May 27 14:10:30 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
May 27 14:10:30 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 27 14:10:30 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 27 14:10:30 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 27 14:10:30 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 27 14:10:30 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 27 14:10:30 kernel: ubi1: max/mean erase counter: 40/17, WL threshold: 4096, image sequence number: 527176359
May 27 14:10:30 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 27 14:10:30 kernel: ubi1: background thread "ubi_bgt1d" started, PID 5034
May 27 14:10:31 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 5055
May 27 14:10:32 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
May 27 14:10:32 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 27 14:10:32 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
May 27 14:10:32 kernel: UBIFS (ubi1:0): reserved for root: 0 bytes (0 KiB)
May 27 14:10:32 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 2A6BEA28-491B-4503-A426-8F74D62305AF, small LPT model
May 27 14:10:32 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 27 14:10:32 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
May 27 14:10:32 kernel: ubi1: detaching mtd10
May 27 14:10:32 kernel: ubi1: mtd10 is detached
May 27 14:10:33 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 14:10:33 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 14:10:33 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link DOWN.
May 27 14:10:33 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
May 27 14:10:37 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link UP at 1000 mbps full duplex
May 27 14:10:37 kernel: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
May 27 14:10:37 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
May 27 14:10:37 acsd: eth7: Selecting 5g band ACS policy
May 27 14:10:37 acsd: acs_update_driver(440): acs update failed ret code: -22
May 27 14:10:37 acsd: acs_set_initial_chanspec(378): eth7: update driver failed
May 27 14:10:38 : Auth AC:D5:64:BA:33:F9
May 27 14:10:38 : ReAssoc AC:D5:64:BA:33:F9
May 27 14:10:39 acsd: eth7: selected channel spec: 0xd986 (136u)
May 27 14:10:39 acsd: eth7: Adjusted channel spec: 0xd986 (136u)
May 27 14:10:39 acsd: eth7: selected channel spec: 0xd986 (136u)
May 27 14:10:39 acsd: acs_set_chspec: 0xd986 (136u) for reason APCS_INIT
May 27 14:10:40 WLCEVENTD: Auth A4:83:E7:37:39:68
May 27 14:10:40 WLCEVENTD: Assoc A4:83:E7:37:39:68
May 27 14:11:23 rc_service: cfg_server 1347:notify_rc restart_wireless
May 27 14:11:23 kernel: ubi1: attaching mtd10
May 27 14:11:23 kernel: ubi1: scanning is finished
May 27 14:11:23 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
May 27 14:11:23 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 27 14:11:23 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 27 14:11:23 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 27 14:11:23 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 27 14:11:23 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 27 14:11:23 kernel: ubi1: max/mean erase counter: 40/17, WL threshold: 4096, image sequence number: 527176359
May 27 14:11:23 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 27 14:11:23 kernel: ubi1: background thread "ubi_bgt1d" started, PID 5364
May 27 14:11:24 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 5381
May 27 14:11:25 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
May 27 14:11:25 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 27 14:11:25 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
May 27 14:11:25 kernel: UBIFS (ubi1:0): reserved for root: 0 bytes (0 KiB)
May 27 14:11:25 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 2A6BEA28-491B-4503-A426-8F74D62305AF, small LPT model
May 27 14:11:25 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 27 14:11:25 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
May 27 14:11:25 kernel: ubi1: detaching mtd10
May 27 14:11:25 kernel: ubi1: mtd10 is detached
May 27 14:11:26 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 14:11:26 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 14:11:26 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link DOWN.
May 27 14:11:26 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
May 27 14:11:28 BONDING: not linked
May 27 14:11:30 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link UP at 1000 mbps full duplex
May 27 14:11:30 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
May 27 14:11:30 kernel: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
May 27 14:11:31 acsd: eth7: Selecting 5g band ACS policy
May 27 14:11:31 : Auth AC:D5:64:BA:33:F9
May 27 14:11:31 : ReAssoc AC:D5:64:BA:33:F9
May 27 14:11:32 acsd: eth7: selected channel spec: 0xd986 (136u)
May 27 14:11:32 acsd: eth7: Adjusted channel spec: 0xd986 (136u)
May 27 14:11:32 acsd: eth7: selected channel spec: 0xd986 (136u)
May 27 14:11:32 acsd: acs_set_chspec: 0xd986 (136u) for reason APCS_INIT
May 27 14:11:34 WLCEVENTD: Auth A4:83:E7:37:39:68
May 27 14:11:34 WLCEVENTD: Assoc A4:83:E7:37:39:68
May 27 14:11:38 BONDING: successfully
May 27 14:11:39 WLCEVENTD: Auth 54:33:CB:EA:8A:A3
May 27 14:11:39 WLCEVENTD: Assoc 54:33:CB:EA:8A:A3
May 27 14:12:36 rc_service: cfg_server 1347:notify_rc restart_wireless
May 27 14:12:37 kernel: ubi1: attaching mtd10
May 27 14:12:37 kernel: ubi1: scanning is finished
May 27 14:12:37 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
May 27 14:12:37 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 27 14:12:37 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 27 14:12:37 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 27 14:12:37 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 27 14:12:37 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 27 14:12:37 kernel: ubi1: max/mean erase counter: 40/17, WL threshold: 4096, image sequence number: 527176359
May 27 14:12:37 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 27 14:12:37 kernel: ubi1: background thread "ubi_bgt1d" started, PID 5722
May 27 14:12:38 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 5740
May 27 14:12:38 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
May 27 14:12:38 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 27 14:12:38 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
May 27 14:12:38 kernel: UBIFS (ubi1:0): reserved for root: 0 bytes (0 KiB)
May 27 14:12:38 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 2A6BEA28-491B-4503-A426-8F74D62305AF, small LPT model
May 27 14:12:38 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 27 14:12:38 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
May 27 14:12:38 kernel: ubi1: detaching mtd10
May 27 14:12:38 kernel: ubi1: mtd10 is detached
May 27 14:12:40 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 14:12:40 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 14:12:40 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link DOWN.
May 27 14:12:40 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
May 27 14:12:44 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link UP at 1000 mbps full duplex
May 27 14:12:44 kernel: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
May 27 14:12:44 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
May 27 14:12:44 acsd: eth7: Selecting 5g band ACS policy
May 27 14:12:44 : Auth AC:D5:64:BA:33:F9
May 27 14:12:44 : ReAssoc AC:D5:64:BA:33:F9
May 27 14:12:46 acsd: eth7: selected channel spec: 0xd986 (136u)
May 27 14:12:46 acsd: eth7: Adjusted channel spec: 0xd986 (136u)
May 27 14:12:46 acsd: eth7: selected channel spec: 0xd986 (136u)
May 27 14:12:46 acsd: acs_set_chspec: 0xd986 (136u) for reason APCS_INIT
 

Polara

New Around Here
Don't put Merlin on the mesh router. Put it back on the latest stock Asus firmware. I have 3 RT-AC68U routers, Merlin is on the main unit only, and stock Asus FW on the mesh units and it works perfectly. Once you flash the mesh unit with stock FW, don't do anything else to it. Just plug it in and put it as close as possible to the main router. Then go on the main router in merlin and search for available routers in the mesh setup. Once it's setup for mesh, you can move it further away. It's really important to have it near the main router for initial setup.

I also have a NAS plugged into my main router, but it's only a single ethernet connection.
 
Last edited:

espineira

New Around Here
I started with stock Asus firmware on the RT-AC68U and was having issues thus why I changed to Merlin firmware and went the issues continued decided to post here. I've flashed stock firmware 3.0.0.4.385_20490-g57b06ea on the RT-AC68U and the RT-AX88U continues with Merlin 384.17_0 and is now showing issues thus far. I'll keep an eye on the logs and my NAS and report back if it starts misbehaving again. Very odd.
 

CaptnDanLKW

Regular Contributor
A few housekeeping items first, probably not related to the NAS issue.

1) The latest stock firmware for the 68U is much newer than the 86U 384.17 is based on. If you want to go stock, put the stock on the 68U that 384.17 is based off of. It's for this reason I use Merlin on all my nodes. Its just easier and there no downside. There are differing opinions but AI Mesh Stability is best when all nodes run the same code.

2) ACSD log entries tell a few things.
a) You have channel set to Auto. Change this to fixed channel for all radios
b) I see it selected Channel 100 at some point. This is a DFS channel. Avoid picking a DFS channel when selecting a fixed one.
c) for 2.4 Select 20MHz.

Since you are talking about Bonding, make sure you dont have a bridge loop. I dont have an AC88U but I suspect in the Advanced - Lan - Switch Control screen you will see an option to enable spanning tree. Keep that enabled.

I could see an issue with Jumbo Frames being enabled in AI Mesh BUT I have no data to back that up either way. If you have it enabled, disable it and test.

There are multiple Bonding protocols but LACP is what's used.

May 27 13:15:31 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 13:15:31 kernel: bond0: option slaves: unable to set because the bond device is up
May 27 13:15:34 kernel: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond

Is your NAS configured properly as well? LACP is negotiated and your logs tell me something is not correct on your NAS.

That's about the extent of my ideas. Do some forum searching. Also, specify your NAS make/model so other may be able to help.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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