[ 386.4 alpha Build(s) ] Testing available build(s)

[mittar]

I had to go back on 386.3.2 because periodicaly loosing Internet once per two days on RT-AX86U. There is no error in log except services like VPN cannot connect, conmon pings are not working, of course devices behind router don't see Internet. LAN or connection in the network is normal. Restart DNS/DHCP Server (dnsmasq) doesn't help, restart of Internet Connection fixed the issue (or router restart of course). Because no error and Internet state shows Connected in Network Map even in situation when Internet is not working X hours I believe that there is issue with detecting the Internet as it doesn't re-initialize the service when some issue on WAN and router believes that all is OK but it is not.

Loosing of Internet 03:26 - there's no error
Oct 3 03:25:19 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=XX SRC=XX DST=XX LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=1565 PROTO=TCP SPT=58276 DPT=8083 SEQ=4118066621 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
Oct 3 03:25:34 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=XX SRC=XX DST=XX LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=51947 PROTO=TCP SPT=56900 DPT=34972 SEQ=2969562692 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
Oct 3 03:26:51 ovpn-client2[3111]: [XX] Inactivity timeout (--ping-restart), restarting
Oct 3 03:26:51 ovpn-client2[3111]: SIGUSR1[soft,ping-restart] received, process restarting
Oct 3 03:26:51 ovpn-client2[3111]: Restart pause, 5 second(s)
Oct 3 03:26:56 ovpn-client2[3111]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Oct 3 03:26:56 ovpn-client2[3111]: TCP/UDP: Preserving recently used remote address: [AF_INET]XX:X
Oct 3 03:26:56 ovpn-client2[3111]: Socket Buffers: R=[524288->1048576] S=[524288->1048576]
Oct 3 03:26:56 ovpn-client2[3111]: NOTE: setsockopt TCP_NODELAY=1 failed
Oct 3 03:26:56 ovpn-client2[3111]: UDP link local: (not bound)
Oct 3 03:26:56 ovpn-client2[3111]: UDP link remote: [AF_INET]XX:X
Oct 3 03:27:00 ovpn-client1[3011]: [XX] Inactivity timeout (--ping-restart), restarting
Oct 3 03:27:00 ovpn-client1[3011]: SIGUSR1[soft,ping-restart] received, process restarting
Oct 3 03:27:00 ovpn-client1[3011]: Restart pause, 5 second(s)
Oct 3 03:27:05 ovpn-client1[3011]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Oct 3 03:27:05 ovpn-client1[3011]: TCP/UDP: Preserving recently used remote address: [AF_INET]XX:X
Oct 3 03:27:05 ovpn-client1[3011]: Socket Buffers: R=[524288->1048576] S=[524288->1048576]
Oct 3 03:27:05 ovpn-client1[3011]: NOTE: setsockopt TCP_NODELAY=1 failed
Oct 3 03:27:05 ovpn-client1[3011]: UDP link local: (not bound)
Oct 3 03:27:05 ovpn-client1[3011]: UDP link remote: [AF_INET]XX:X
Oct 3 03:27:56 ovpn-client2[3111]: [UNDEF] Inactivity timeout (--ping-restart), restarting
Oct 3 03:27:56 ovpn-client2[3111]: SIGUSR1[soft,ping-restart] received, process restarting
Oct 3 03:27:56 ovpn-client2[3111]: Restart pause, 5 second(s)
Oct 3 03:28:01 ovpn-client2[3111]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Oct 3 03:28:05 ovpn-client1[3011]: [UNDEF] Inactivity timeout (--ping-restart), restarting
Oct 3 03:28:05 ovpn-client1[3011]: SIGUSR1[soft,ping-restart] received, process restarting
Oct 3 03:28:05 ovpn-client1[3011]: Restart pause, 5 second(s)
Oct 3 03:28:10 ovpn-client1[3011]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Oct 3 03:28:21 ovpn-client2[3111]: RESOLVE: Cannot resolve host address: XX:X (Temporary failure in name resolution)
Oct 3 03:28:31 ovpn-client1[3011]: RESOLVE: Cannot resolve host address: XX:X (Temporary failure in name resolution)
Oct 3 03:28:42 ovpn-client2[3111]: RESOLVE: Cannot resolve host address: XX:X (Temporary failure in name resolution)
Oct 3 03:28:42 ovpn-client2[3111]: Could not determine IPv4/IPv6 protocol

 

[L&LD]

@Amiga, I would be cautious about putting an Alpha firmware on a customer's router, yes, on day one. However, I've been using this myself since August 11, 2021 (53 days) without issues. It fixes many little things under the hood and is an obvious upgrade over the 'release' of just a few days prior (August 8, 2021).

I let them know this is the same Alpha firmware I use on my own network hardware. They're aware that if anything comes up with the Alpha, I will downgrade them to the official release, asap, and at no charge.

The Alpha has made my 2x RT-AX86U's in wired backhaul mode much more consistent for ~8 weeks now. Just one more reason to use the Alpha than to be stuck on the inferior previous version immediately before it. And I'm not the only one that has been enjoying the benefits of the Alpha either, of course. Many others have similar experiences right here too.

Thanks for the heads up on the sales!

 

[elorimer]

Thanks for the heads up on the sales!

The AX55 for $60 certainly caught my eye for a mesh node.

 

[L&LD]

I don't buy AP's or nodes, I buy routers.

But depending on the performance, for $60,it may be tempting for some.

 

[maxbraketorque]

@L&LD, I didn't know that the same band could be used for backhaul and connections. There has to be a 2x increase in latency when using that approach, but I guess the increased speed associated with avoiding using the 2.4 GHz band is more than worth it?

 

[L&LD]

Yes, using the fastest connection (when the fastest throughput is required) is (almost) always worth it.

Keep in mind that Repeaters are just 'dumb' AiMesh nodes too. They both half the throughput and double the latency of the network.

The great CPU and 'just enough RAM' on the RT-AX68U ('great', for currently available routers), including the RF processors, are enough to mitigate those effects as much as possible for less than 1Gbps ISP speeds (as I stated above too).

Repeater mode = wireless AiMesh

 

[elorimer]

I don't buy AP's or nodes, I buy routers.

It is a router, sort of an AX56 without some of the extra bits like USB ports. Broadcom, but no Merlin support, no addons, but still cheaper than everything else, so that's why maybe a node. But a lot cheaper than Newegg without the return hassles.

 

[Centrifuge]

It is a router, sort of an AX56 without some of the extra bits like USB ports. Broadcom, but no Merlin support, no addons, but still cheaper than everything else, so that's why maybe a node. But a lot cheaper than Newegg without the return hassles.

It looks hackable. USB Female to RJ45 Ethernet Male Adapter>USB openwrt router?, and bam adguard, wireguard all of it.

 

[elorimer]

Darn. I went to buy it on a lark and it is now $100. Should have kept my mouth shut. I was going to repurpose the 68u I'm using as a node and repurpose it as a router, then use this to have ax for local in the house.

 

[L&LD]

Who knows? Maybe you dodged a bullet?

 

[Treadler]

@Amiga, I would be cautious about putting an Alpha firmware on a customer's router, yes, on day one. However, I've been using this myself since August 11, 2021 (53 days) without issues. It fixes many little things under the hood and is an obvious upgrade over the 'release' of just a few days prior (August 8, 2021).

I let them know this is the same Alpha firmware I use on my own network hardware. They're aware that if anything comes up with the Alpha, I will downgrade them to the official release, asap, and at no charge.

The Alpha has made my 2x RT-AX86U's in wired backhaul mode much more consistent for ~8 weeks now. Just one more reason to use the Alpha than to be stuck on the inferior previous version immediately before it. And I'm not the only one that has been enjoying the benefits of the Alpha either, of course. Many others have similar experiences right here too.

Thanks for the heads up on the sales!

+1
Ive been using the Alpha since release & everything ‘just works’ in my modest home network scenario.

 

[Gar]

@JWoo, 62C at zero/low load (before I shared the new SSID passwords with the household). Before I left, it was still less than 74C at 42% CPU load with 18 active devices (mostly streaming, speed tests, and gaming) and the units 'on' for over 60 minutes. The RT-AC86U was at 82C when I arrived at the home (don't remember the CPU load).

@maxbraketorque, the RT-AX68U is also a dual-band router (as are the RT-AX88U and the RT-AX86U too). I was expecting higher throughput because of my experience with the RT-AX88U and the RT-AX86U, but having such an increase in throughput, through such obstacles and, at a distance is always refreshingly surprising. To reach the speeds I was seeing, the 5GHz band was being used as both backhaul and for client devices. Very impressive speed boosts (for the distances/obstacles within that environment).

Yes, the 2x RT-AX68U's were a direct replacement for the previous RT-AC86U's, set up in wireless backhaul AiMesh mode. And, in AiMesh mode, the performance was (on average) the same for the farthest computer in the lowest level of the home (connected to the node) as when the node was powered down and the connection was to the main router.

The 'beefy gaming desktop' was the only device in the home with an Intel AX200 adaptor card (besides my work computer with an Intel AX210 adaptor). This computer could max out the ISP speeds at will (as could my work computer too, of course).

The main improvements that the customer received with this router upgrade:

• Faster connection speeds to their networks for all devices. This was evidenced by the fact that when I was rebooting the routers, the users were sometimes not even aware that I had rebooted the network.
• Lower latency for all clients. Younger (the 'gamer' in the household), older, and non-techy users all commented on how much faster their devices felt on the 'net. Yes, it was that noticeable.
• Higher throughput, throughout the home, regardless of the device used. The AiMesh node was 'required', not for enhancing the internal Wi-Fi coverage, but for extending the Wi-Fi to the end of the lawn/garden too (about another 70' from the house, and around 110' from the main router).

I followed up again today with the customer, and the status of the network was still 'great'.

Also, I want to note that none of the defaults (after flashing RMerlin firmware and doing a full reset on both routers) were changed with regards to the AX capabilities. All of their clients connected instantly to the new SSIDs and all have stayed connected. A mix of iPhones, Androids, Surface, laptops, desktops, TVs, etc.

While the performance, latency, and throughput improvements are unquestionable from the old RT-AC86U, the RT-AX68U looks and feels cheaper than the older model. They both use the same power adaptor (and identical 19V, 1.75A, and 33W specs), and power plugs. (Yes, I tested the new power plug with the old router and the old power plug with the new router too).

If the WPS Button reset method gets fixed with RMerlin firmware (anyone with updated Asus stock firmware can confirm that it works correctly for them?), then the recommended routers today would be:

RT-AX68U (entry-level). RT-AX88U (AX class and greatest 2.5GHz range). RT-AX86U (best overall router).

The RT-AC86U was a good router for many years. But, it has been surpassed (particularly when it is only $20 less at regular prices, (and $50 more expensive when the RT-AX68U is on sale).

And for the record, I was wrong about the RT-AX68U. So far, it has exceeded my expectations (contrary to what I expected after I had seen the specifications page on it, not so long ago).

I hope I didn't miss any questions?

I agree with your findings. I bought an AX88 recently when the price was low and the AX86 was out-of-stock everywhere, and find it more responsive than my "old" GT2900. It also has a stronger signal at greater range. Nice, didn't expect it, especially since the AX88 isn't that much newer than AC86/GT2900.

 

[Tex Texan]

Excuse the ignorance, but no new Merlin builds, beta or alpha, since early August and we're now into October, which seems unusual (although there was an official release for my AX88U at the end of August)

Is it simply a case of nothing new to add?

 

[John Fitzgerald]

Excuse the ignorance, but no new Merlin builds, beta or alpha, since early August and we're now into October, which seems unusual (although there was an official release for my AX88U at the end of August)

Is it simply a case of nothing new to add?

SEE POST #21 page 2.

 

[unsynaps]

Excuse the ignorance, but no new Merlin builds, beta or alpha, since early August and we're now into October, which seems unusual (although there was an official release for my AX88U at the end of August)

Is it simply a case of nothing new to add?

[ 386.4 alpha Build(s) ] Testing available build(s)

Hmm... I am surprised that we are seeing yet another round of development without a new GPL drop from Asus being built-in. I am aware that there have been problems with those GPL builds, but still??? It has been a while now... It's currently mostly component updates, which were already in the...

www.snbforums.com

 

[dsring]

For those running this alpha on RT-AX86U, is it stable? Worth the update over 386.3.2?

 

[mittar]

For those running this alpha on RT-AX86U, is it stable? Worth the update over 386.3.2?

I had to go back 386.3.2 on RT-AX86U .. after some time always stopped to work WAN Internet, LAN was OK, but wake up morning to restart WAN that Internet is not working was not feasible for me. Hoping it will be Alpha 2 without this Internet issue.

 

[Treadler]

For those running this alpha on RT-AX86U, is it stable? Worth the update over 386.3.2?

Post in thread '[ 386.4 alpha Build(s) ] Testing available build(s)'
http://www.snbforums.com/threads/386-4-alpha-build-s-testing-available-build-s.74186/post-716668

 

[princi]

Seems like the Merlin story is coming to an end - just like OpenWRT.

I’m now in Australia and forced to go with the nascent 5G rollout here - because anything associated with the NBN is outdated and way over-priced.

No Asus 5G routers. Wouldn’t be supported by Merlin anyway.

 

[Treadler]

Seems like the Merlin story is coming to an end - just like OpenWRT.

I’m now in Australia and forced to go with the nascent 5G rollout here - because anything associated with the NBN is outdated and way over-priced.

No Asus 5G routers. Wouldn’t be supported by Merlin anyway.

Re NBN, I feel your pain.
I’m on FTTP, so I guess I’m better off than some…….but as you say, the price!