What's new

My experience with the RT-AC86U

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Here is what I see, AC86U and AX86U compared side by side to test AC clients at the same locations - same room 3m away, behind one wall 10m away and behind 2 walls 15m away, plus some more differences:

- AX86U shows 4dBm lower signal strength from clients on all channels, perhaps less sensitive radio.
- AC86U can do >60Mbps real transfers on channels 36-48, but no more than 40Mbps on 149-161.*
- AX86U can do >60Mbps real transfers on channels 149-161, but no more than 40Mbps on 32-48.*
- 2.4GHz band is exactly the same on both, same dBm reported and same transfer speeds.
- despite the dBm differences on 5GHz band, I would say both routers have identical performance to AC clients, just need to be set differently.
- I tried to crash AX86U with my test transfer to USB attached SSD and it survived, AC86U doesn't. I've seen this on AX88U though - 1GB RAM.
- AX86U LEDs are much brighter than the LEDs on AC86U - a bit uncomfortable, if the router is used in a dark room.
- AX86U WAN LED blinks differently when WAN port is used and when 2.5GbE port is used for WAN. I like 2.5GbE port LED better.
- Asus App can't restore AX86U LEDs after turned off, no LAN LEDs coming up. Works in Asuswrt-Merlin GUI though. Minor inconvenience.

* - Wi-Fi environment specific

I have the router for few days only and had no much time to play with it. The case is a bit cheap plasticky looking, the antennas were not aligned perfectly and needed slight force adjustment. Acceptable for $250 router though with good hardware inside. I like the normal power jack and the new switch, but there is a design flaw - on/off switch is at the wrong side of the power jack and is too close to it. It's a bit hard to reach.

I had to open a new thread for this comparison information, apologies @Oracle.

Thanks for the comparison. I guess I can stop contemplating purchasing an AX86U, at least for the wifi performance. There will be an edge for router VPN performance.

The LEDs can be made dimmer by coloring over them with a black Sharpie. Still visible, but much dimmer. It works great.
 
Some more running time and some more observation: changing pid_max still doesn't appear to make a difference.
The stuck commands keep coming.

I'm now interested to simply and combine the 2 override scripts (for nvram and wl) into one, so it's easier to install, use and maintain. The overrides are the best solution we have so far.
 
Some more running time and some more observation: changing pid_max still doesn't appear to make a difference.
The stuck commands keep coming.
As I said, it wasn't intended to stop the problem just make it less frequent. But YMMV depending on what you're running on the router.
 
I'm now interested to simply and combine the 2 override scripts (for nvram and wl) into one, so it's easier to install, use and maintain. The overrides are the best solution we have so far.
Well, the timeout command is also super-duper handy... that's been my go-to fix for many, many months now -- at least, within my own scripts - not on a system-wide level. ;)
 
Some more running time and some more observation: changing pid_max still doesn't appear to make a difference.
The stuck commands keep coming.

I'm now interested to simply and combine the 2 override scripts (for nvram and wl) into one, so it's easier to install, use and maintain. The overrides are the best solution we have so far.
Initially I can run nvram test script with no issue. Until I run the script by @Martinski that reveal I do have some stuck process. Those stuck process does not affect nvram get script though. After clearing those stuck process then the nvram script get stuck. I remember the first time I change pid_max nvram script still fail. I rebooted, change pid_max and leave it.

Something I have noticed for some time is conn_diag db file. My conn_diag db file usually stuck and not updating a day or two after reboot. After change pid_max the db files keep updating every minute. I have it for about a week in 386.5_2 and now three days in 386.7. The last time Martinski’s script detect stuck process is on 19th Jun. Changing pid_max works for me.
 
Well, the pid_max change might be making a difference.
The rate of wl errors is the same but nvram errors haven't popped up yet after 3 days of uptime. I don't know what to make of these stats yet. (Not available means 0 errors.)
Usage statistics of nvram and wl overrides
Uptime: 09:02:20 up 3 days, 16:13, load average: 2.68, 2.88, 2.95
nvram use count: 11890
nvram errors count: not available
wl use count: 21098
wl errors count: 6

@chongnt, any response from Asus on your bug report? Shall I try to push from my side?

As a side note, I wish there was a build of Merlin's firmware without the bloatware (closed source features that rely on sending your traffic data to a third party to exploit it). That would give space to include more valuable stuff instead but I realize that's too much to ask for.
 
Well, the pid_max change might be making a difference.
The rate of wl errors is the same but nvram errors haven't popped up yet after 3 days of uptime. I don't know what to make of these stats yet. (Not available means 0 errors.)


@chongnt, any response from Asus on your bug report? Shall I try to push from my side?

As a side note, I wish there was a build of Merlin's firmware without the bloatware (closed source features that rely on sending your traffic data to a third party to exploit it). That would give space to include more valuable stuff instead but I realize that's too much to ask for.
Unfortunately I have not get any feedback from my local Asus support. Appreciate if you can push from your side too. Hopefully they will treat this with higher priority with more reported case.
 
After nearly 7 days of uptime, it looks like the pid_max change clearly has an impact on the nvram get stuck commands (so far 0 stuck) and not on wl (14 stuck).
I thought these 2 were manifestations of the same root cause but there's a difference now. Or maybe there is something else at play here.
Usage statistics of nvram and wl overrides
Uptime: 11:50:27 up 6 days, 19:01, load average: 3.12, 3.05, 2.97
nvram use count: 21954
nvram errors count: not available
wl use count: 39006
wl errors count: 14
 
After nearly 7 days of uptime, it looks like the pid_max change clearly has an impact on the nvram get stuck commands (so far 0 stuck) and not on wl (14 stuck).
I thought these 2 were manifestations of the same root cause but there's a difference now. Or maybe there is something else at play here.
If you run this script followed immediately by ps w and post all the results in that other thread we might be able to guess what's happening.
 
Any conditions as to when do I have to run the above? Is it ok that I have the nvram and wl command overrides active? (They kill stuck processes and retry the commands.)
 
Any conditions as to when do I have to run the above? Is it ok that I have the nvram and wl command overrides active? (They kill stuck processes and retry the commands.)
No idea. There's too many moving parts in play and I'm not intimately familiar with everything that's run/running on your router. Just dump the information as-is and we might get lucky and be able to spot something.
 
Here you are, script output:
Print netlink sockets for which there is no process with the same number

Process 1091 not found
Process 1232 not found
Process 1243 not found
Process 1247 not found
Process 2087 not found
Process 2225 not found
Process 2409 not found
Process 2752 not found
Process 32771 not found
Process 33697 not found
Process 33781 not found
Process 33845 not found
Process 33852 not found
Process 33859 not found
Process 33860 not found
Process 33861 not found
Process 34002 not found
Process 34010 not found
Process 34012 not found
Process 34013 not found
Process 34017 not found
Process 34739 not found
Process 34743 not found
Process 34744 not found
Process 34746 not found
Process 34747 not found
Process 34748 not found
Process 34751 not found
Process 34753 not found
Process 34807 not found
Process 34810 not found
Process 34811 not found
Process 34813 not found
Process 34856 not found
Process 34857 not found
Process 34858 not found
Process 34929 not found
Process 34995 not found
Process 35113 not found
Process 35179 not found
Process 35270 not found
Process 35522 not found
Process 50758 not found

A number in brackets is a *guess* at an associated process
And from ps w:
PID USER VSZ STAT COMMAND
1 admin 13440 S /sbin/init
2 admin 0 SW [kthreadd]
3 admin 0 SW [ksoftirqd/0]
4 admin 0 SW [kworker/0:0]
5 admin 0 SW< [kworker/0:0H]
6 admin 0 SW [kworker/u4:0]
7 admin 0 SW [rcu_preempt]
8 admin 0 SW [rcu_sched]
9 admin 0 SW [rcu_bh]
10 admin 0 SW [migration/0]
11 admin 0 SW [watchdog/0]
12 admin 0 SW [watchdog/1]
13 admin 0 SW [migration/1]
14 admin 0 SW [ksoftirqd/1]
16 admin 0 SW< [kworker/1:0H]
17 admin 0 SW< [khelper]
18 admin 0 SW [kdevtmpfs]
19 admin 0 SW< [writeback]
21 admin 0 SWN [ksmd]
22 admin 0 SW< [crypto]
23 admin 0 SW< [bioset]
24 admin 0 SW< [kblockd]
25 admin 0 DW [skbFreeTask]
26 admin 0 SW [bcmFapDrv]
27 admin 0 SWN [kswapd0]
28 admin 0 SW [fsnotify_mark]
53 admin 0 SW [btnhandler0]
54 admin 0 SW [btnhandler1]
55 admin 0 SW [btnhandler2]
56 admin 0 SW [kworker/1:1]
57 admin 0 SW< [linkwatch]
58 admin 0 SW< [ipv6_addrconf]
59 admin 0 SW< [deferwq]
60 admin 0 SW [ubi_bgt0d]
170 admin 0 SWN [jffs2_gcd_mtd2]
204 admin 0 SW [bcmFlwStatsTask]
208 admin 0 SW [bcmsw_rx]
209 admin 0 SW [bcmsw]
217 admin 0 SW [pdc_rx]
285 admin 18508 S /bin/swmdk
292 admin 1568 S {wdtctl} wdtd
296 admin 1712 S hotplug2 --persistent --no-coldplug
299 admin 1752 S /usr/sbin/envrams
362 admin 0 SWN [jffs2_gcd_mtd9]
540 admin 0 SW [dhd_watchdog_th]
541 admin 0 SW [wfd0-thrd]
546 admin 0 SW [dhd_watchdog_th]
547 admin 0 SW [wfd1-thrd]
927 admin 11756 S console
981 admin 0 SW [kworker/1:2]
1011 admin 11752 S /sbin/PS_pod
1015 admin 3324 S /sbin/syslogd -m 0 -S -O /tmp/syslog.log -s 256 -l 7
1017 admin 3324 S /sbin/klogd -c 5
1068 admin 0 SW [kworker/0:2]
1075 admin 11752 S /sbin/wanduck
1082 admin 8312 S asd
1087 admin 2376 S /usr/sbin/haveged -r 0 -w 1024 -d 32 -i 32
1088 admin 13540 S nt_monitor
1089 admin 6824 S protect_srv
1090 admin 13800 S /sbin/netool
1100 admin 11460 S nt_center
1230 admin 2924 S /bin/eapd
1240 admin 11752 S wpsaide
1242 admin 4648 S /usr/sbin/wlc_nt
1246 admin 3744 S nas
1278 admin 5032 S /usr/sbin/wlceventd
1741 admin 5012 S nt_actMail
1952 admin 3120 S /usr/sbin/acsd
1954 admin 2856 S /usr/sbin/dhd_monitor
1966 admin 3324 S crond -l 9
1969 admin 5412 S vis-dcon
1973 admin 4804 S vis-datacollector
1974 admin 6956 S /usr/sbin/infosvr br0
1976 admin 3384 S sysstate
1977 admin 11752 S watchdog
1978 admin 11752 S check_watchdog
1981 admin 4272 S rstats
1983 admin 11752 S amas_lanctrl
2026 admin 3208 S lld2d br0
2033 admin 10532 S vis-dcon
2037 admin 12484 S networkmap --bootwait
2040 admin 10680 S mastiff
2041 admin 11752 S bwdpi_check
2043 admin 11756 S pctime
2086 admin 19964 S roamast
2088 admin 13808 S conn_diag
2091 admin 1704 S /usr/sbin/sd-idle-2.6 -i 1800
2101 admin 3316 S lldpd -L /usr/sbin/lldpcli -I eth1,eth2,eth3,eth4,eth5,eth6,wds0.*.*,wds1.*.* -s RT-AC86U
2105 nobody 3316 S lldpd -L /usr/sbin/lldpcli -I eth1,eth2,eth3,eth4,eth5,eth6,wds0.*.*,wds1.*.* -s RT-AC86U
2107 admin 12760 S cfg_server
2159 admin 14920 S amas_lib
2167 admin 2356 S dropbear -p 192.168.20.1:22 -j -k
2217 admin 0 SW [kworker/u4:2]
2324 admin 0 SW [scsi_eh_0]
2325 admin 0 SW< [scsi_tmf_0]
2326 admin 0 SW [usb-storage]
2343 admin 11752 S usbled
2379 admin 3680 S /usr/sbin/ntp -t -S /sbin/ntpd_synced -p pool.ntp.org
2410 admin 0 SW< [kworker/0:1H]
2417 admin 1916 S /bin/mcpd
2500 admin 11752 S disk_monitor
2548 admin 6448 S /etc/openvpn/vpnserver1 --cd /etc/openvpn/server1 --config config.ovpn
2550 admin 6448 S /etc/openvpn/vpnserver1 --cd /etc/openvpn/server1 --config config.ovpn
2696 admin 3324 S /sbin/udhcpc -i eth0 -p /var/run/udhcpc0.pid -s /tmp/udhcpc_wan -t2 -T5 -A160 -H ****-AP -O33 -O249
2766 admin 0 SW [jbd2/sda1-8]
2767 admin 0 SW< [ext4-rsv-conver]
2829 admin 0 SW< [kworker/1:1H]
2844 admin 5200 S vnstatd -d --noadd --config /opt/share/dn-vnstat.d/vnstat.conf
2872 nobody 28624 S pixelserv-tls 192.168.20.2
3608 nobody 80904 S dnsmasq --log-async
3609 admin 2596 S dnsmasq --log-async
3832 nobody 3096 S avahi-daemon: running [RT-AC86U.local]
3861 admin 11392 S /usr/sbin/nmbd -D -s /etc/smb.conf
3864 admin 1856 S /usr/sbin/wsdd2 -d -w -i br0 -b sku:RT-AC86U,serial:************
3866 admin 11560 S /usr/sbin/smbd -D -s /etc/smb.conf
3867 admin 6940 S vsftpd /etc/vsftpd.conf
3870 admin 2408 S miniupnpd -f /etc/upnp/config
3874 admin 12880 S minidlna -f /etc/minidlna.conf -R -W
3913 admin 3324 S {tailtopd} /bin/sh /jffs/addons/scmerlin.d/tailtopd
3915 admin 3324 S N {tailtop} /bin/sh /jffs/addons/scmerlin.d/tailtop
4284 admin 2484 S dropbear -p 192.168.20.1:22 -j -k
4309 admin 3328 S -sh
6354 admin 12132 S /usr/sbin/smbd -D -s /etc/smb.conf
17988 admin 11108 S httpd -i br0
67358 admin 3192 S sleep 5
67372 admin 3192 S N sleep 4
67376 admin 3328 R ps w
 
Just noticed a new issue with chronyc. Not sure if this is a sign of degraded crystal oscillator or something else.

Code:
Jul  5 02:08:08 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 03:08:20 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 03:08:20 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:02:35 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:02:51 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:07:42 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:07:43 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:08:47 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:12:50 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:12:50 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:13:55 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:16:05 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:17:57 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:17:58 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:18:46 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:20:07 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:22:50 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:23:05 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:24:42 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:27:57 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:27:58 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:33:05 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:33:06 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:33:54 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:38:12 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:38:13 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:43:04 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:43:05 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:48:28 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:48:29 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:49:01 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:53:20 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:53:21 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:53:53 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:55:30 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 09:08:44 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 09:08:44 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)

1656995990689.png
 
Just noticed a new issue with chronyc. Not sure if this is a sign of degraded crystal oscillator or something else.

Code:
Jul  5 02:08:08 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 03:08:20 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 03:08:20 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:02:35 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:02:51 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:07:42 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:07:43 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:08:47 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:12:50 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:12:50 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:13:55 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:16:05 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:17:57 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:17:58 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:18:46 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:20:07 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:22:50 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:23:05 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:24:42 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:27:57 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:27:58 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:33:05 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:33:06 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:33:54 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:38:12 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:38:13 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:43:04 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:43:05 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:48:28 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:48:29 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:49:01 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:53:20 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 08:53:21 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 08:53:53 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.253 (sgsin3-ntp-002.aaplimg.com)
Jul  5 08:55:30 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)
Jul  5 09:08:44 RT-AC86U-DBA8 chronyd[2069365]: Can't synchronise: no majority
Jul  5 09:08:44 RT-AC86U-DBA8 chronyd[2069365]: Selected source 17.253.82.125 (sgsin3-ntp-001.aaplimg.com)

View attachment 42483
I have this too.

chronyd[4658]: Can't synchronise: no majority

I am on RT-AX86U though with 386.7 firmware
 
Last edited:
I use an AX86U as my main router, but couldn't resist snapping up one of these at a relatively good price (under £100)
It's been running like a champ as an AImesh node, and even though I could just get a new router tomorrow if I needed to, it's nice to know that I've got a capable one already in the house that I can just factory reset and have up and running again in no time.

If I was in the market for a new router tomorrow for whatever reason, yeah I'd probably be looking at the AX86U (or the pro now I guess), but early failure rates aside this is still a solid bit of kit.
 

Sign Up For SNBForums Daily Digest

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