[Thread-1] [ 386.1_Alpha Build(s) ] Testing available build(s)

[Delusion]

Is it possible to disable\enable AiProtection via SSH? if possible, what are the commands?

TNX

 

[Xentrk]

I flashed Alpha 4 on RT-AC88U last night. Alpha 4 fixed the issue I had with the watchdog messages being output to system log in the Alpha 1 to Alpha 3 releases every 30 seconds.

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>

Message no longer appear. Thank you @RMerlin

 

[jerry6]

alpha 4 working well on my rt5300 3 days no issues
thanks

 

[visortgw]

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

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.

 

[Svenskmat]

alpha 4 working well on my rt5300 3 days no issues
thanks

Any Airmesh nodes?

 

[LimJK]

Is it possible to disable\enable AiProtection via SSH? if possible, what are the commands?

TNX

Delusion,
Through trial and error, I found the few AiProtection NVRAM variables :

AiProtection: wrs_protect_enable

• Malicious Sites Blocking: wrs_mals_enable
• Two-Way IPS: wrs_vp_enable
• InfectedDev Prevent&Block: wrs_cc_enable

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

 

[Mr Tvardovsky]

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.

There 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).

 

[isr25]

Hi all,

Using AX86U with Alpha 4. My ISP provides an IPTV STB connected to LAN4 with VLAN tagging 600 while WAN port is tagged with VLAN 500. I just noticed that after turning on the IPTV STB, the log will be full of the below lines, and the router CPU will get hotter by the minute - usually around 77-78C, but will rise up to 96C (ambient temp around 33C). I noticed the error logs is coming from my wireless Roku - not the IPTV device through ethernet). Not sure why the wired device error will affect the Roku though. The error will continue until I turn off the IPTV STB, then the CPU temp will gradually go down to normal temps. Should I report this to the official Asus 386 beta thread as well?

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

 

[Unisoft]

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.

 

[Vexira]

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.

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.

 

[Keith Gorham]

I have been following / reading this thread since day one, and I have an question that I have not seen asked or answered.

For the RT-AC68U I have three options to get the latest firmware.

​

1) Released Asus 386 branch​

2) RC 386 main branch​

3) Alpha Merlin Code​

​

Of the main 386 code, I am guessing that the RC386 is the newest (best?) followed by the merlin release then the released branch. Is this correct?

 

[bbunge]

There 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).

1. AiMesh 2.0 allows the node LED's to be turned off
2. Recent Asus firmware does use SMB2. OK it uses both SMB1 and SMB2

 

[MoonPie2000]

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.

Thanks visortvw for the confirmation. I am excited about trying mesh setup.

 

[cmillar6]

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.

 

[Deleted member 22229]

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.

I have flashed every firmware available. AX58U. All Merlin's. RC2-8-9 Asus Beta. Asus official 384.10177. They all work good. Alpha 4 seems the best so far.
Just to add. I don't use AiMesh or any other features just a straight up router that works.

 

[crkpot]

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.

 

[RMerlin]

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.

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.

 

[JWoo]

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.

Ditto. Also can concur as I have flashed between AsusWRT RC versions, 384.17 and the @RMerlin 386 Alpha versions without problem.

 

[RichyE]

I did a clean flash from 384.19 on all my routers
I flashed Alpha 4 on RT-AC86U as main router and also on 2 RT-AC68U as node.
I looks promising but it caused allot of problems for me and because of the wife and daughter I went back to 384.18

The problems:
When IP v6 is activated wifi reboots every 30 seconds
When Guest network is activated ( also on the nodes) I can't acces any wifi any more
And I have 24 devices but only 10 can connect (phone, table, computer, etc) all the IOT (google,, Nest, Tuya, etc) can't acces the wifi

 

[L&LD]

What does a 'clean flash' mean to you?