Copy of errors from log?Just updated to beta 2 on ax88u and I get constant ntp sync error, even after changing servers?
Are you using IPv6 dual with IPv4? If so, try to use NTP servers that are IPV6 enabled also.Just updated to beta 2 on ax88u and I get constant ntp sync error, even after changing servers?
This is hilarious! Some relative newbie reports enthusiastically on his (I know, I'm assuming gender here) successful upgrade, and gets his butt kicked straight out of the gate
I didn’t think ipv6 ip’s worked for Asus router ntp?Are you using IPv6 dual with IPv4? If so, try to use NTP servers that are IPV6 enabled also.
Apr 4 07:17:28 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<8> stats, rc -5^[[0m
Apr 4 07:17:28 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<8> stats, rc -5^[[0m
Apr 4 07:17:28 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<9> stats, rc -5^[[0m
Apr 4 07:17:28 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<9> stats, rc -5^[[0m
Apr 4 07:17:28 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<5> stats, rc -5^[[0m
Apr 4 07:17:28 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<5> stats, rc -5^[[0m
Apr 4 07:17:29 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=1
Apr 4 07:17:29 kernel: FPM Pool 0: invalid token 0x0a900000 freed
Apr 4 07:17:29 kernel: FPM Pool 0: ISR timer is enabled. There could be multiple occurrences of the reported issue
Apr 4 07:17:29 wlceventd: wlceventd_proc_event(530): eth7: Auth 16:9A:C0:89:70:57, status: Successful (0), rssi:0
Apr 4 07:17:29 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Apr 4 07:17:29 hostapd: eth7: STA 16:9a:c0:89:70:57 IEEE 802.11: associated (aid 1)
Apr 4 07:17:29 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc 16:9A:C0:89:70:57, status: Successful (0), rssi:-84
Apr 4 07:17:29 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Apr 4 07:17:29 hostapd: eth7: STA 16:9a:c0:89:70:57 IEEE 802.11: associated
Apr 4 07:17:29 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<7> stats, rc -5^[[0m
Apr 4 07:17:29 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<7> stats, rc -5^[[0m
Apr 4 07:17:29 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<4> stats, rc -5^[[0m
Apr 4 07:17:29 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<4> stats, rc -5^[[0m
Apr 4 07:17:29 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<1> stats, rc -5^[[0m
Apr 4 07:17:29 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<1> stats, rc -5^[[0m
Apr 4 07:17:29 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<3> stats, rc -5^[[0m
Apr 4 07:17:29 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<3> stats, rc -5^[[0m
Apr 4 07:17:29 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<6> stats, rc -5^[[0m
Apr 4 07:17:29 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<6> stats, rc -5^[[0m
I am on beta 2 now from beta 1.
Would someone please post a screen shot of the 2.4 pro page you have success with? I have mine as default but have around 20-25 stubborn clients that don’t like to connect or just drop off. I am on a ax6000 with 3 mesh nodes.
When I was using IPv4 NTP servers only I noticed too many udp ntp request unreplied in the connection status but after I changed it to a dual stack server I have not seen it anymore.I didn’t think ipv6 ip’s worked for Asus router ntp?
Happy to be proved wrong.
I guess I'm just complying to what I see and use. All services that I use( ntp,streaming, email, downloads, etc.) uses IPV6 so why not. Using windows and I think it's the standard it uses IPv6 first then fallback to IPv4 if needed.[C:\~]$ tracert time.nist.gov
Tracing route to ntp1.glb.nist.gov [2610:20:6f15:15::26]
over a maximum of 30 hops:
1 2 ms 5 ms 3 ms GT-AX6000-[2600:40xxxx:xxxx::1]
2 5 ms 2 ms 3 ms 2600:40xxxx:xxxx::1
3 10 ms 5 ms 5 ms 2600:40xxxxxxxx::406
4 13 ms 12 ms 11 ms 2600:803::9a
5 15 ms 14 ms 13 ms 2600:803:b6f::5e
6 17 ms 14 ms 14 ms time-e-g.nist.gov [2610:20:6f15:15::26]
Trace complete.
[C:\~]$ tracert time.apple.com
Tracing route to time.g.aaplimg.com [2620:149:a33:3000::1e2] so why not
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms GT-AX6000 [2600:40xxxxxxxx::1]
2 6 ms 4 ms 3 ms 2600:40xxxxxxxx::1
3 10 ms 8 ms 8 ms 2600:40xxxxxxxx::406
4 9 ms 5 ms 5 ms 2600:802::71
5 4 ms 5 ms 5 ms 2600:802:f2f::32
6 6 ms 8 ms 7 ms 2620:149:bb:1242::82
7 8 ms 6 ms 4 ms 2620:149:a33:3000::1
8 8 ms 6 ms 6 ms usnyc3-ntp-003.aaplimg.com [2620:149:a33:3000::1e2]
Trace complete.
One thing at a time. My focus is currently on 388.2, 386.11 will have to wait after it's done...If B2 is incorporating OpenVPN 2.6.2 to fix a memory leak, is a similar change warranted in 386.10 for the AC routers?
Thats because Tech9 needs a internet forum to run off at the mouth, he knows in real life face to face that would not go well for him. Anyway i have had enough of this forum the mods must like this kind of verbal abuse as they do nothing to stop it. I don't need it and see zero reason to remain here. Im out.
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!