Forum Replies Created
-
AuthorPosts
-
I’ve been trying the beta 21493. My XT8 is now telling me to upgrade to 388_21617
Seems this version of firmware is only applicable to ZenWIFI XT8 of V1 version hardware ? News to myself thou ?
Depending on how long the dev’s take to run the correct routine, I would expect 21617 to go live on the web shortly :) Tom…
Dev’s must have had a coffee break…😁
21617 is for XT8 V1 & is now live & I’m also taking it for a test drive 🤭🙈
Version 3.0.0.4.388.21617
2022/11/21 48.29 MBytes
ASUS ZenWiFi AX (XT8) Firmware version 3.0.0.4.388.21617
This version of firmware is only applicable to ZenWIFI XT8 of V1 version hardware, please check the product label before utilizing. You can check the hardware version from the product SN label or box label.1. Optimized memory usage and improved system stability.
2. Fixed 2.5G port compatibility issues.
3. Fixed USB HDD compatibility issue with the Time machine.
4. Added a new web GUI login URL http://www.asusrouter.com
5. Fixed IPTV compatibility issue with Movistar.
6. Fixed VPN fusion, AiMesh, and Network map GUI bugs.
7. Fixed WAN compatibility issue with Starlink router.
8. Fixed miniupnpc vulnerabilities, CVE-2015-603, CVE-2017-1000494
9. Fixed IPSec server vulnerability, CVE-2022-40617Please unzip the firmware file first then check the MD5 code.
MD5: 82fb58213e09f954ce01cc0dc3ca4186
DOWNLOADYou need to login in order to vote
I’ve been trying the beta 21493. My XT8 is now telling me to upgrade to 388_21617
Seems this version of firmware is only applicable to ZenWIFI XT8 of V1 version hardware ? News to myself thou ?
Depending on how long the dev’s take to run the correct routine, I would expect 21617 to go live on the web shortly :)
Tom…
You need to login in order to vote
I would not worry about the 21099 offline beta, will cause more confusion
No worries & feedback sent,
altho with my typing skills being slower than slow, the 30 min auto logout did cause me to start afresh after it kicked me out,
While working twice as hard negates the real reason of having to provide feedback twice🙈
the former always sounds better 🤭
Tom…
You need to login in order to vote
Understood, before you roll back, can you send a feedback and mention in comments box ‘UK Sentinel’ and describe issue, at least they will have a point of reference .
<noscript>
</noscript>
Will do, I did fire the same few lines of the log back to Asus support against my open ticket, marked up for info only & outlined the issue along with the beta version.
Then I would open full communication once back on the general stable release 21099.
Tom…
Interesting regarding ‘HTTPD: waiting ‘ are any USB drives in use ?
No usb connected, never had the need, With the general release fw, web history seems populate correctly, then no new data entries after 1 or 2 day’s of uptime, but trying to access web history on the beta’s lock the gui up inside a similar timeframe. TM systems don’t seem to be 100% in the recent beta’s for me, but don’t know if that’s by design or omission. Tom…
Might be worth testing the offline 21099 beta that UK Sentinel shared with me?
Can you confirm the fw dodgy, as 3.0.0.4.388.21099 is the last stable general release!
Tom…
You need to login in order to vote
Interesting regarding ‘HTTPD: waiting ‘ are any USB drives in use ?
No usb connected, never had the need,
With the general release fw, web history seems populate correctly, then no new data entries after 1 or 2 day’s of uptime, but trying to access web history on the beta’s lock the gui up inside a similar timeframe.
TM systems don’t seem to be 100% in the recent beta’s for me, but don’t know if that’s by design or omission.
Tom…
You need to login in order to vote
On beta fw 9.0.0.4.388_21493
I’m still having the same issue with the router gui locking up after trying to access it’s web history,
with an uptime of circa 36Hrs (1 to 2 days I normally see errors) but this time free ram is just over 100MB, definitely an improvement in ‘reported’ memory with 21493 fw
still seems to be a max data entry limit causing errors for me.
I had recently opened a ticket with Asus Re: my web history, but put that on hold while I took the recent beta’s for a test drive,
so for me, I’m gonna rollback to a clean install of the general release 3.0.0.4.388.21099 fw, before I continue with my open ticket with Asus.
Tom…
Router gui logs from lockup, HTTPD again!
Nov 8 12:46:21 wlceventd: wlceventd_proc_event(511): wl2.4: Disassoc 92:00:22:4E:04:B4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 8 12:49:13 HTTPD: waitting 10 minitues and restart
Nov 8 12:49:13 rc_service: httpd 1585:notify_rc restart_httpd
Nov 8 12:49:13 ZenWiFi_XT8: start httpd:80
Nov 8 12:49:13 httpd: Save SSL certificate…80
Nov 8 12:49:13 httpd: mssl_cert_key_match : PASS
Nov 8 12:49:13 httpd: Succeed to init SSL certificate…80
Nov 8 12:49:34 acsd: eth4: selected_chspec is 1008 (8)
Nov 8 12:49:34 acsd: eth4: Adjusted channel spec: 0x1008 (8)You need to login in order to vote
Running 9.0.0.4.388.21493 beta
Had some free time time this morning, so did a factory reset (gui followed by a hard rest) & then manually re-applied any custom configuration settings, followed by a system reboot.
System up with 110 free ram, web history is now available & working, but the AI protection / malicious site blocking is not.
The jffs files repopulated the web history from yesterday’s usage & show web history failed just short of 4pm, roughly about 6Hrs up time, I didn’t save the log files from yesterday, but with a quick glance I didn’t notice anything obvious, but I didn’t have a narrow enough timeline to check in depth.
Currently free ram sitting at 104 MB with an uptime of 1Hr20,
Normally I would expect the free ram to fall over the next few day’s & my web history to fail in some sort of way before I reach 72Hrs of uptime.
However as not all of the the TM systems appear to be enabled, I’m not expecting the free ram to drop to low, but will see how that affects overall stability of the system & it’s sub systems over the next few day’s.
Tom…
You need to login in order to vote
Beta 9.0.0.4_388_21493 not improved things with me,
Since installing the 21493 beta this morning, most of us have been out, so should have been ticking over on a greatly reduced workload,
Not had time to put the TrendMicro services to the test, but I can confirm just clicking the web history tab locks the router gui up for me, httpd errors in the log.
———————-
(Nov 5 21:11:54 HTTPD: waitting 10 minitues and restart
Nov 5 21:11:54 rc_service: httpd 7550:notify_rc restart_httpd
Nov 5 21:11:54 ZenWiFi_XT8: start https:57020
Nov 5 21:11:54 ZenWiFi_XT8: start httpd:80
Nov 5 21:11:54 httpd: Save SSL certificate…57020
Nov 5 21:11:54 httpd: mssl_cert_key_match : PASS
Nov 5 21:11:54 httpd: Succeed to init SSL certificate…57020)——————
internet access for all connected clients is A ok,
force closing the chrome tab & waiting 10 mins I regain router access again,
I’m able to navigate the router gui without problem on all but the web history tab,
( web history has always been hit or miss for me, but normally I see errors after 1 or 2 days, when free ram drops below 80%)
Router has uptime of 10 Hrs & free ram down to 90%
With no full fat fibre here & a 70/20 line sync, I do rely on qos to keep everyone (swmbo) happy & web history to keep an eye on the kids now & then, so everything under the Trend umbrella.
I’ll get to actually testing this beta fw out over the next few days, but not looking good so far.
Tom…
You need to login in order to vote
Cheers UK Sentinel.
Just installed the .21493 beta,
need a couple of days uptime to see how the TrendMicro performs,
but at least it’s working in this release, so defo a step up from the 21101 beta👍
free ram gained, up from 81 > 100, so not a big a jump as dodgydrains,
anything lower than 80% & router did seem to behave like a moody teenager😃
so fingers crossed there.
Tom…
You need to login in order to vote
Well I test drove the beta 21101 fw for a few days, but it has it’s problems.
I use the TrendMicro systems, but as this didn’t function correctly with the 21101 beta fw, I rolled back to the 21099 fw.
Initially TrendMicro systems were still off-line on the 21099 fw,
but a factory reset brought all TrendMicro services back on-line, so at least I have web history back again, free ram is down to 94% already, but the 21099 fw is the lesser of 2 evils.
I had been undecided if to roll back away from this beta, or to see how the free ram plays out a little bit longer, but as some web pages were slow to load & a bit erratic this morning, a rollback it was.
my initial thought had been that the router had bombed-out on the beta fw,
I managed a whopping 2.3Mbs download out of my 80/20 line.
As the TrendMicro systems came back online the cause of my poor download speed appeared,
1 of my kids on her desktop was maxing out the bandwidth with a large download,
between a flaky beta causing issues & kids being awake enough to function at 8.30am on a Saturday morning I’d point the finger at the beta fw every time👍
Until now that is 👍
Tom…
You need to login in order to vote
I also updated to the newly released beta 21101 fw,
Looks like the most of the TrendMicro isn’t fully functional, so that might also account for my huge jump in free ram 80ish free > up-to 191% free.
The gui is definitely seems more responsive now👍
but as my node is connected via ethernet, the 5GHz backhaul tweaks are wasted on me.
No improvements on my underlying web history bug tho 🙈 no web history whatsoever 🤭
Tom…
You need to login in order to vote
After a positive start running 21268,
I’m back to the general release fw 21099 on both my router & node.
Trying to access web history is still crashing the router after a a couple of days, so being no better off I’ve rolled the fw back.
Tom…
You need to login in order to vote
I’ve been following this thread ever since purchasing a pair of XT8’s the beginning of the year,
but thought it was about time to join the party so to speak, especially as 21268 has seen a noticeable improvement over 21099 & so to share my findings.
My router & node both running 21268 without issue, but that might be due to a cat6 ethernet connection between them, (but not running in dedicated ethernet backhaul mode)
A bit of background, my web history has never worked as intended, compiling data entry’s for a couple of days👍 then it abruptly stops dead with no new data being populated.
Just clicking the web history tab had crashed the router on more than 1 occasion while running 21099,
also running a manual firmware update check crashed it once, coincidentally both issues occurred when ram usage had been sitting over 80% (normally sits 77-82) & only a power off / restart, restored internet & router access.
Early days yet, but ram sitting at 82% usage, router & node seem stable & 2.5 days of continuous web history compiled 👍.
So far, so good on 21268
(21268 waz a dirty update over the top of 21099)
Tom…
You need to login in order to vote
-
AuthorPosts
