What's new

Beta Asuswrt-Merlin 388.2 Beta is now available for Wifi 6 models

  • 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!

Status
Not open for further replies.
RT-AX88U, dirty update from beta1 to beta2.
Running OpenVPN server and OpenVPN client to Mullvad. Using VPN Director.
Did some tests with WG server and WG client and different "routes" with VPN Director.
All gave expected results.
Thank you RMerlin.
 
Just updated to beta 2 on ax88u and I get constant ntp sync error, even after changing servers?
Copy of errors from log?
Just for information: works fine here.
 
Dirty update of RT-AX86U from 388.2 alpha1 to beta2. According to my observations, on beta2, as well as on alpha2 and beta1, static entries in ARP die 3-10 minutes after they are created. Last time I updated to beta1 with a reset and manual configuration of all parameters and this problem persisted. So this time I just did a dirty update. After this update, I attached a crutch in the form of a script that creates a static entry in ARP every 3 minutes. But I would like this problem to be fixed in the firmware. Thank you Merlin for your hard work.
P.S.: As a result, I returned to 388.2 alpha1 again, because even if the script gives a command to create a static entry every minute, sometimes there are periods of up to 1 minute when the static entry is dead.
 
Last edited:
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 🤣🤣

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.
 
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.
 
Getting random reboots on Beta 2 with AX11000 again. Below is log entries right before last reboot happened.

Code:
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.
24GHz.PNG


Explicit beamforming is not recommended but works for me.
 
I didn’t think ipv6 ip’s worked for Asus router ntp?
Happy to be proved wrong.😳
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.
[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.
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.
 
Last edited:
AX86U here. Dirty upgrade. Only issues I had were with VPN but once configuration fixed, stable.

Beta 1 after a week use was stable. The only issues I had was with this Beta initially was with open VPN where I had to remove some unsupported commands because VPN wasn’t establishing connection.

Beta 2 had VPN establishing connection but no internet. I had to reenable compression on the VPN settings. (Or use default setting from VPN provider), otherwise stable use after a day thus far. Still kicking the tires.

I saw someone mentioned issues with AX86U, but it’s it’s been solid for me so far. The only hiccup I did experience in previous firmwares is that when my family comes home, pulls up to the garage with their mobiles then I can see some lag/ slow down especially if I’m gaming, it’s quite repeatable especially since I have a routine, but figured there is some spike in processing when adding some wireless clients all at once. Not a show stopper.

My setup in a nutshell for anyone curious:
Running 40+ clients including IOTs, cameras, consoles, laptops, phones, 2.4/5.8, 1 WG vpn, 1 OVPN, YazFi segmenting network with redirect all clients to VPN on its own subnet and force DNS IP. Hosting Plex/Emby servers from a NAS behind a VPN. Cake QOS. Some iptables in scripts/nat-start that don’t run until I can first ping google, but that’s been there for some years. amtm packages always up to date, usually check/do it after every firmware update. No other entware packages other than YazFi.
 
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? I'm not sure if this is client side or server side or both and I don't think I've experienced it yet with my AC 86U connected as a client to my AX88.
 
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?
One thing at a time. My focus is currently on 388.2, 386.11 will have to wait after it's done...

The memory leak only occurs on the initial TLS connection, so it won't manifest over time.
 
Dirty upgrade to beta 2 from beta 1. 6 hours in and no errors in the log, all clients are connected as they should.

Thank you for the update.
 
Dirty from Beta_1 and no issues.
Both WG/OVPN clients connected and working well. Scripts (see sig) also working.

@shabbs
You live dangerously My Friend! I do all network upgrades, etc while The Family sleeps or out of the house.
 
Last edited:
Dirty upgrade from 388.2 Beta 1 to Beta 2 is complete. So far, no issues to report after 15+ hours of uptime using AdGuard Home, Yazi, Skynet, Scribe plugins. App plugins appear to be working as designed after some quick tests.

The only anomaly I've experienced is that my 5GHz band will not hold its manual setting of channel 116 (WIFI Radar says 116-> 130 is open). I've also tried 120 and 122 with no success as it ignores the manual setting and uses channels 38, 40, or 153 instead. The manual setting worked fine with Beta 1 and I understand WIFI code is closed source from Asus (did not change) so I suspect some sort of new local interference issue is occurring. Channel 132 seems to work despite the fact that my neighbors 5ghz is running on the same range.
 
Seeing a possible issue with DDNS page. Beta 2, RT-AX68U
It is stuck like this and clicking Apply at the bottom does not do anything.
Tried to disable and still Apply button does not work.
1680629181849.png


UPDATE:
I did a full power down and unplugged, rebooted. Now that screen is working again. Not sure what happened.
 
Last edited:
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.

You're correct, of course. But leaving the forums doesn't help. Consider continuing to participate and just ignoring the worst examples of 'members' that appear from time to time.
 
Status
Not open for further replies.

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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