Nov 16 11:42:55 RT-AC88U-8248 rc_service: watchdog 439:notify_rc start_cfgsync
Nov 16 11:42:55 RT-AC88U-8248 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Nov 16 11:43:25 RT-AC88U-8248 rc_service: watchdog 439:notify_rc start_cfgsync
Nov 16 11:43:25 RT-AC88U-8248 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Nov 16 11:43:55 RT-AC88U-8248 rc_service: watchdog 439:notify_rc start_cfgsync
<snip>
Merlin includes AiMesh code exactly as provided by Asus -- there are none of the value added enhancements that we are so used to enjoying in our primary routers.I currently have a x88u and am getting ready to setup AiMesh with a x86u.have Why do you think it is better to run ASUS stock on AiMesh nodes instead of Merlin? Also I have both a VPN server and client w/routing running. Do you know of any issues with this when using AiMesh? Thanks
Any Airmesh nodes?alpha 4 working well on my rt5300 3 days no issues
thanks
Delusion,Is it possible to disable\enable AiProtection via SSH? if possible, what are the commands?
TNX
To Enable:
nvram set wrs_protect_enable=1
nvram set wrs_mals_enable=1
nvram set wrs_vp_enable=1
nvram set wrs_cc_enable=1
nvram commit && reboot
To Disable:
nvram set wrs_protect_enable=0
nvram set wrs_mals_enable=0
nvram set wrs_vp_enable=0
nvram set wrs_cc_enable=0
nvram commit && reboot
Merlin includes AiMesh code exactly as provided by Asus -- there are none of the value added enhancements that we are so used to enjoying in our primary routers.
Dec 4 16:10:20 kernel: wl0: random key value: 5BBF3F1EDE7F2E06772202486405A4216ED8D4B3C2F50C360A2FCB38592D30DD
Dec 4 16:10:20 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind B8:B7:F1:XX:XX:XX, status: 0, reason: Unspecified reason (1)
Dec 4 16:10:20 wlceventd: wlceventd_proc_event(505): eth6: Auth B8:B7:F1:XX:XX:XX, status: Successful (0)
Dec 4 16:10:20 wlceventd: wlceventd_proc_event(534): eth6: Assoc B8:B7:F1:XX:XX:XX, status: Successful (0)
Dec 4 16:10:24 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) (phyId: 8) Link Up at 100 mbps full duplex
Dec 4 16:13:34 kernel: wl0: random key value: 040859FC1D3386B6155A0053C1444E0CF5F5480D00B209E706545CBB873BA6B7
Dec 4 16:13:34 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind C8:3A:6B:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 4 16:13:41 wlceventd: wlceventd_proc_event(505): eth6: Auth C8:3A:6B:XX:XX:XX, status: Successful (0)
Dec 4 16:13:41 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind C8:3A:6B:XX:XX:XX, status: 0, reason: Unspecified reason (1)
Dec 4 16:13:41 wlceventd: wlceventd_proc_event(505): eth6: Auth C8:3A:6B:XX:XX:XX, status: Successful (0)
Dec 4 16:13:41 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind C8:3A:6B:XX:XX:XX, status: 0, reason: Unspecified reason (1)
Dec 4 16:13:41 wlceventd: wlceventd_proc_event(505): eth6: Auth C8:3A:6B:XX:XX:XX, status: Successful (0)
Dec 4 16:13:41 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind C8:3A:6B:XX:XX:XX, status: 0, reason: Unspecified reason (1)
Dec 4 16:13:41 wlceventd: wlceventd_proc_event(505): eth6: Auth C8:3A:6B:XX:XX:XX, status: Successful (0)
Dec 4 16:13:41 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind C8:3A:6B:XX:XX:XX, status: 0, reason: Unspecified reason (1)
Dec 4 16:13:41 wlceventd: wlceventd_proc_event(505): eth6: Auth C8:3A:6B:XX:XX:XX, status: Successful (0)
Dec 4 16:13:53 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind C8:3A:6B:XX:XX:XX, status: 0, reason: Unspecified reason (1)
Dec 4 16:13:53 wlceventd: wlceventd_proc_event(505): eth6: Auth C8:3A:6B:XX:XX:XX, status: Successful (0)
Dec 4 16:13:53 wlceventd: wlceventd_proc_event(534): eth6: Assoc C8:3A:6B:XX:XX:XX, status: Successful (0)
Dec 4 16:13:57 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind C8:3A:6B:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
...
...
...
...
Dec 4 16:16:06 kernel: CONSOLE: : wlc_apps_ps_enq_resp txq full, frame discarded
Dec 4 16:16:06 kernel: CONSOLE: 186754.905 wl1.0: wlc_apps_ps_enq_resp txq full, frame discarded
Dec 4 16:16:06 kernel: CONSOLE: 186754.905 wl1.0: wlc_apps_ps_enq_resp txq full, frame discarded
Dec 4 16:16:06 kernel: CONSOLE: 186754.905 wl1.0: wlc_apps_ps_enq_resp txq full, frame discarded
Dec 4 16:16:06 kernel: CONSOLE: 186754.905 wl1.0: wlc_apps_ps_enq_resp txq full, frame discarded
Dec 4 16:16:06 kernel: CONSOLE: 186754.905 wl1.0: wlc_apps_ps_enq_resp txq full, frame discarded
Dec 4 16:16:06 kernel: CONSOLE: 186754.905 wl1.0: wlc_apps_ps_enq_resp txq full, frame discarded
Dec 4 16:16:06 kernel: CONSOLE: 186754.905 wl1.0: wlc_apps_ps_enq_resp txq full, frame discarded
Dec 4 16:16:06 kernel: CONSOLE: 186754.905 wl1.0: wlc_apps_ps_enq_resp txq full, frame discarded
with adaptive qos don't use automatic bandwidth, you need to use manual, also try using the flex qos script with adaptive qos see if that helps.So, despite TWO brand new AX-86U AND factory reset and entering config by hand not backup file, the following bugs are evident to me in alpha4 (and could be Asus ones):
1. Secondary NTP server never used if primary is unreachable (pool.ntp.org and time.google.com or IP address of time.google.com)
2. Adaptive QOS and "automatic" does not seem to monitor bandwidth correctly. Previously, streaming video upstream from NAS would immediately show in a QOS category under UPLOAD. Now its not even showing, yet some types are working.
1. AiMesh 2.0 allows the node LED's to be turned offThere are actually 2 little reasons why I personally prefer to run Merlin on the nodes, too:
1) You can access their AMTMs and e.g. define led control schedule;
2) I have a shared drive attached via USB to one of the nodes. On my home network it runs reliably only with Samba v2 enabled, which is another Merlin enhancement (stock Asus includes v1 only).
Thanks visortvw for the confirmation. I am excited about trying mesh setup.Merlin includes AiMesh code exactly as provided by Asus -- there are none of the value added enhancements that we are so used to enjoying in our primary routers.
I currently have OpenVPN servers/clients active on my RT-AX88U router with no issues -- AiMesh nodes should have no bearing on VPN functionality as it all runs on primary router.
AX58u users, is anybody having trouble flashing between Alpha 2,3,4 ?? My AX58u just reboots when I try to flash and I have to reset the router to make it take the next Alpha. I've gone back and experimented going between 384.17,384.18,384.19 and it flashes just fine so I don't think its hardware related.
AX58u users, is anybody having trouble flashing between Alpha 2,3,4 ?? My AX58u just reboots when I try to flash and I have to reset the router to make it take the next Alpha. I've gone back and experimented going between 384.17,384.18,384.19 and it flashes just fine so I don't think its hardware related.
Apparently you can't do dirty upgrades on this router with the alpha builds so far, you have to factory reset first then upgrade firmware.
Ditto. Also can concur as I have flashed between AsusWRT RC versions, 384.17 and the @RMerlin 386 Alpha versions without problem.Just boot without any USB stick plugged as recommended in the documentation.
I've done plenty of RT-AX58U firmware flashes on my development unit without ever having to do a factory default reset.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!