Forum Replies Created
-
Only issues I have seen online is where XT8 nodes had been difficult to update, after XT8 Primary node was updated, but once all where updated, stability and usability was good.
In a completely sane world, madness is the only freedom (J.G.Ballard).
I agree. I got alerted that a new update is available for the main node, but the 2nd node says it’s already got the latest even if it’s not.
Liked by:
You need to login in order to vote
Version 3.0.0.4.388_24621
V1 – 49.61 MB
V2 – 50.23 MB
2024/03/19– Fixed command injection vulnerability.
– Fixed the ARP poisoning vulnerability. Thanks to the contribution of Xin’an Zhou.
– Fixed code execution in custom OVPN. Thanks to the contrubution of Jacob Baines.
– Fixed the injection vulnerability in AiCloud.
– Fixed stack buffer overflow in lighttpd. Special thanks to Viktor Edstrom.
– Fixed CVE-2023-35720
– Fixed the code execution vulnerability in AiCloud. Thanks to the contribution of chumen77.
– Fixed the XSS and Self-reflected HTML injection vulnerability. Thanks to the contrubution of Redfox Cyber Security.*Please be advised that due to a security upgrade in AiMesh, we strongly recommend against downgrading to previous firmware versions, as this may lead to connection issues. Should you encounter any difficulties, resetting the AiMesh router to its default settings and re-establishing the mesh connection can resolve the problem.
V1 – https://dlcdnets.asus.com/pub/ASUS/…_300438824621.zip?model=ASUS ZenWiFi AX (XT8)
Please unzip the firmware file, and then verify the checksum.
SHA256: 2cd1851f75abf270c34ec4643617aa03235c3d1415696a8a9100dc1b79972378V2 – https://dlcdnets.asus.com/pub/ASUS/…_300438824621.zip?model=ASUS ZenWiFi AX (XT8)
Please unzip the firmware file, and then verify the checksum.
SHA256: 97fd1726378ce1d449f3b5e143e00c7cffb0da7b961f944f267bf7e1c13712b0Thanks for this!
For the early adopters, please give some feedback.
And also, if the added security really makes it hard to pair up with nodes after updating.
Thanks again.
Liked by:
You need to login in order to vote
Great new in that the manual selected (any channel) tip seems to help with 160MHz backhaul stability for your AiMesh system
In a completely sane world, madness is the only freedom (J.G.Ballard).
Ok, spoke too soon. Backhaul reverted to 2.4ghz (yellow light). I guess I’m not meant to be using 160ghz. Anyways, I’m fine if I’ll be stuck at 80ghz… i still get the full speed of my internet and there weren’t really problems when i was at 80ghz anyway, so why fix something that isn’t broken.
Guys, thanks anyways for the tips, help and suggestions. At least I’ve exhausted all options. Maybe it’s a radar thing here in our area that keeps on shutting down the 160ghz. At least I know now, it just doesn’t work for me.
Thanks again!
Liked by:
You need to login in order to vote
So far so good. Duplicated dodgy’s settings and tomthumb’s tips. I unticked the CONTROL CHANNEL DFS option. Now the control channel sticks and stays at 100. Backhaul is stable so far!
thanks guys!
Liked by:
You need to login in order to vote
Agreed it is worth a try, I used to also have to manually set channel bandwidth to 160MHz before. This was with previous old FW versions. Now I do not need to.
This might help too – For me, setting it to auto works fine but it does take upto 15 minutes to get to 160MHz backhaul and stabilise at that. I just leave it for 15-20 minutes as it always first shows as 2.4Ghz and then 15 minutes later 160Mhz comes up. It always first defaults the backhaul to 2.4Ghz for me for around 15 minutes. It may do the same for you even if you set it manually to 160Mhz.
Also, under ‘AiMesh’ – ‘Management’ – I manually set ‘Backhaul Connection Priority’ to ‘5GHz-2 WiFi first’. As I have 4 units, I also manually set ‘Preferred WiFi Uplink AP’ to the nearest XT8 to the node.
Hope this helps. It took me a while and a lot of patience to get to understand the quirks on my setup.
Thanks to you all for your suggestions.
Liked by:
You need to login in order to vote
FWIW I run a wired backhaul, so your results may differ Jamie,
A quirk I found with my mesh.
If I run 5GHz-2 on Control Channel > Auto = Bandwidth defaults to 80 MHz
Run 5GHz-2 Control Channel > manual selected (any channel) = Bandwidth holds 160 MHz
(auto selects channel 100 = 80MHz / manual channel 100 = 160 GHz)
5GHz-1 dose not follow the same behaviour, if favours 160 MHz regardless of settings.
Tom…
Interesting.
i might really have to tinker around some more with 5ghz 2 settings and do more comprehensive tests when my schedule permits.
thanks for sharing your info!
Liked by:
You need to login in order to vote
If you want to start a new topic, I am sure we can work through a few options to see if we can manage to get 160 MHz back haul working for your XT8
In a completely sane world, madness is the only freedom (J.G.Ballard).
Right now am pretty much satisfied with 80ghz. We only have a couple of iphones in our household that can handle 160ghz bandwidth anyway. So as for now, no need to really push/force use the 160ghz. It’s just hanging in my head why I couldn’t make it work. But Thanks again for the infos and suggestions. So appreciate them.
Liked by:
You need to login in order to vote
Hi,
I’m On 3.0.0.4.388_23285-g5068da5 which is stable without any issues, Wired backhaul all green.
I’m wondering if i should do the upgrade? i haven’t seen any feed back which support upgrade or ones voting against itWhat do you recon?
You should try updating. You can always go downgrade back to the firmware that worked best for you.
Liked by:
You need to login in order to vote
Still none here for Asian Asus site.
If nothing by tomorrow, let us know and I will speak with ASUS
In a completely sane world, madness is the only freedom (J.G.Ballard).
got my update just today. i had to upload manually after downloading from asus asian support site. i was trying to update via in-app and kept getting i was on the latest update…so did it manually.
will observe this new one now.
thanks again!
Liked by:
You need to login in order to vote
