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

[LimJK]

My Configuration:

• AiMesh Router: AX88U 386.1_alpha4-gd4b7146753 + 2 x AiMesh Nodes: AC86U 386.1_alpha4-gd4b7146753
• Backhaul (Priority:"Auto", Type:"Wired"), Cisco SG100D 8-Port Gigabit Switch from Router to Nodes, ISP: 1 Gbps Fibre

My Test Exercise with Alpha4: Full Factory Reset of AiMesh Router / Nodes, I tried to leave NVRAM using Merlin FW defaults with the following changes:

• AiProtection - ENABLE
• Wireless:
  • 2.4 GHz: Fixed Channel Bandwidth 20MHz, Fixed Control Channel: 11, Explicit / Universal Beamforming: Disable
  • 5.0 GHz: Fixed Channel Bandwidth 80MHz, Fixed Control Channel: 149
• WAN DDNS: Using Asus DDNS Service with Let’s Encrypt
• VPN Servers:
  • OpenVPN works with MacBookPro Tunnelblick 3.8.5beta01, iPhoneXsMax iOS OpenVPN Connect 3.2.2
  • IPSec works with MacBookPro & iPhoneXsMax Native Configurations
  • Instant Guard works with iPhoneXsMax iOS Instant Guard 1.0.9

I have been running smoothly for about 2 (Edit again ) 16 hours . Thank You

 

[gmt]

Hi, in my case when I tried to add the CA and the rest of the certificates in the openvpn client , they are not saved

Nov 30 08:58:20 rc_service: httpd 1307:notify_rc restart_vpnclient1
Nov 30 08:58:20 ovpn-client1[24983]: Options error: You must define CA file (--ca) or CA path (--capath)
Nov 30 08:58:20 ovpn-client1[24983]: Use --help for more information.
Nov 30 08:58:20 openvpn: Starting OpenVPN client 1 failed!

When open the "Keys & Certificates" all the previously added fields are empty. Any suggestions?

 

[Krism]

I don't know this is because of the new alpha4 version (haven't seen this in alpha3), but since upgrade seen this happen already 3 times:

Nov 30 10:12:50 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Nov 30 10:12:53 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link Up at 1000 mbps full duplex

 

[gmt]

OK solved with alpha4,

 

[Intrepid2007]

I updated from alpha 2 to alpha 4 without problems (on both my routers).

Alpha 2 was running very stable for the last weeks and I didn't need to restart my router once, I hope this will be the same for this firmware release...

I noticed that the OpenVPN remote IP issue has been fixed too in this release, nice !

 

[brianward317]

I believe I figured out the problem with RT-3100. I reset the router and manually uploaded Alpha 4 from my PC. If I go under Aimesh, there are no settings at all and it's just a blank screen. So I factory reset it and went back to the early version of Alpha 3, if I go under the aimesh in Alpha 3, you get all the aimesh settings. Thought I would mention it, it appears the aimesh might be broken on the latest version of Alpha 3 going into Alpha 4.

 

[Deleted member 22229]

Just flashed 386.1 A4 AX58U. Install went smooth and all is working as expected.

 

[GDT]

Flashed AX86U from alpha3 to alpha4 and break DHCP. I found wrong settings in first and last DHCP IP, once I manually resetted them it worked.
I have issues with my Sky Q box and topology changes, but they are not related to the alpha firmware, and I'm still investigating.

 

[Mutzli]

Dirty update from alpha_3_g2 to alpha_4. So far everything works as expected.

 

[JWoo]

same here, AX58U, need to factory reset otherwise update will not work. since Alpha 3. (AX58U added)

when i upload the firmware, without any error message it reboot the AX58U, and the same old firmware intact.

I have the RT-AX58U with Alpha 4 running. Please make sure you flashed the latest Alpha 4 stored by Merlin very early in the morning 11/30.

 

[Unisoft]

There was some earlier discussion on the MTU causing problems. You should make sure you set MTU to 1500. WAN DNS issues can cause the time not to sync. Turn off DoT if you use it. Set the WAN DNS to reliable upstream DNS servers in your area. Worse case set the time servers to an IP address in lieu of a URL. Also, this is beta firmware and the first Merlin for the AX86U. You might do well to use one of the AC86U's for a main router until the bugs have been worked out of the firmware for the AX86U.

• MTU was already 1500
• Need DNS over TLS so wouldn't be able to turn that off.
• In the end, it was "uk.pool.ntp.org" that wasn't liked (UK NTP specific and works in Windows OS) and wanted "pool.ntp.org".
• Interesting thing was, that it failed on primary NTP server address "uk.pool.ntp.org" and completely ignored time.google.com or actual IP address of the google NTP service and also tried time.windows.com which were set as the secondary server.

Same behaviour on RT-AC86U and two new RT-AX86U routers.

 

[skeal]

• MTU was already 1500
• Need DNS over TLS so wouldn't be able to turn that off.
• In the end, it was "uk.pool.ntp.org" that wasn't liked (UK NTP specific and works in Windows OS) and wanted "pool.ntp.org".
• Interesting thing was, that it failed on primary NTP server address "uk.pool.ntp.org" and completely ignored time.google.com or actual IP address of the google NTP service and also tried time.windows.com which were set as the secondary server.

Same behaviour on RT-AC86U and two new RT-AX86U routers.

On the Administration>System page make sure you have nothing set here:

I Played with this for days and it did the same thing to me as you. It was finally recommended to not use these settings.

 

[GaselK]

AX56U with latest Alpha4 386.1_alpha4-gd4b7146753
"QoS - WAN/LAN Bandwidth Monitor" still not working.
"Traffic Analyzer - Statistic" does not register traffic also.
Noted on traffic from PSN (PlayStation Network).

 

[Unisoft]

On the Administration>System page make sure you have nothing set here:View attachment 28091 I Played with this for days and it did the same thing to me as you. It was finally recommended to not use these settings.

Initially early on, they were on. I then turned them off as read only needed if you basically have a USB 4G stick for failover purposes. I had turned it off though before the last change of uk.pool.ntp.org to pool.ntp.org. For me, it seems like a bug where it doesn;t use the secondary NTP server even if its set.

 

[JoJoDaClown]

Alpha 4 AC5300:

1. CPU is pegged out, related to connected USB 3.0 Hard Drive since if I unmount, processor goes down to under 10%. Fixed on Alpha 4
2. Can't detect AC88U as AiMesh Node - Mesh Node was updated to Alpha 4 then WPS reset method
   1. No Change on Alpha 4
3. AiMesh Node Search appears to have an issue as the wheel keeps spinning but nothing happens, no notification of found or unfound nodes. Nothing reported in Logs related to search.
   1. No Change on Alpha 4
4. Every 30 seconds I get "rc_service: watchdog 468:notify_rc start_cfgsync" in the log (Router settings are default, no scripts or anything)
   1. Still Seeing this on Alpha 4

 

[criszz]

ax86u , wifi 2,4 led not working in alfa4 )

and this error (jffs not enabled) :
ov 30 20:02:10 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:11 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:11 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:11 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:11 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:12 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:12 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:12 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:12 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:13 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:13 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:13 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:13 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:14 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:14 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:14 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:15 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:15 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:15 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:15 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:16 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:16 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:16 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:02:18 kernel: jffs2: Error garbage collecting node at 016a78dc!
Nov 30 20:03:01 kernel: jffs2: Error garbage collecting node at 016a78dc!

 

[L&LD]

This is the end of the line for my 'dirty upgrades' it seems for my RT-AX88U (main) and an RT-AX58U in AiMesh (node).

The main router (RT-AX88U) still works great when AiMesh is not used.

I was expecting this, eventually, it has been a good run.

Details:

Updating from Alpha 3 to Alpha 4 on both routers (very latest for the 'AX58U, of course) has broken AiMesh. The 'AX58U can't connect now no matter what I'm able to try so far.

Steps that were taken.

• Flash A4 to 'AX58U.
• Remove from AiMesh.
• Reset to factory defaults (WPS method).
• Turn off the router.
• Safely remove USB drive to free up RAM from 'AX88U.
• (Did not physically remove USB drive).
• Flash A4 to 'AX88U.
• Wait 15 minutes after it booted above and then rebooted again.
• Turn on 'AX58U and wait 2 minutes for LED's to settle.
• Add 'AX58U in AiMesh via 'AX88U's GUI.
• GUI shows percentage up to around 68% and then very quickly goes to 100% and says can't add AiMesh node.
• Reset 'AX58U once more.
• Reboot 'AX88U, same issue.

At this point, I disabled Diversion, Skynet, Unbound, rebooted, and made sure they were still disabled, but the same issue, even after once again resetting the 'AX58U. Couldn't connect to 'AX58U to AiMesh.

Now, I Safely remove the USB drive, reboot the main router, and reset the 'AX58U once more. Same issue.

At this point, I'm late leaving the house, have missed my breakfast, and am running like a chicken with my head cut off, but this has been quite the ride since Dec 7, 2019, with 384.14 Beta 3!

I'll return tonight and complete a full reset and redo the network from scratch, if necessary.

Edit: I have picked up an RT-AX86U to test later with too!

 

[Deleted member 22229]

@
L&LD

Hope all turns out well and good luck !!!! Running good so far on my AX58U but i am not using Aimesh.

 

[AntonK]

Dirty upgrade from Alpha3 to Alpha4. Running smooth as silk in every respect.

 

[skeal]

Initially early on, they were on. I then turned them off as read only needed if you basically have a USB 4G stick for failover purposes. I had turned it off though before the last change of uk.pool.ntp.org to pool.ntp.org. For me, it seems like a bug where it doesn;t use the secondary NTP server even if its set.

Try using time.nrc.ca in the first server spot and nothing in the second and test.