Forum Replies Created
-
My USB flash drive (a small 32GB stick to share some media with TVs etc. also stopped working)
Does sound like you had a few issues after the factory reset, let us know if the stability improves as after all your hard work, it better had
<noscript></noscript>I expect some of the issues were down to not just doing a reset but rolling back the firmware. As the issue with Teams seemed to occur around 1610-1613 every day this week (if not at other times also), it should be easy to see if it works today! Unless she doesn’t have a call, because they’re having a Christmas party tonight and perhaps they’ll all finish early!
You need to login in order to vote
Okay, so I’ve rolled back to 42095 (found the firmware on the Asus site) and we’ll see how this fares today.
I also did a full reset*, which caused no end of problems trying to find the mesh node and reconnecting again (eventually it just connected by itself, which begs the question – did the WPS reset method actually work?)Â I am now connected with a new SSID and passcode I had to create upon reset, so it seems it already recognised the node and downloaded the settings by itself.
The Asus setup wizard, and even the app, seems to give little to no information on how to do things – and manual searching for a new node always failed. You just have to wait it out. Pretty poor, and surely a nightmare for people less experienced/patient.
My USB flash drive (a small 32GB stick to share some media with TVs etc) also stopped working and I had to format it and set up again. Even toggling the settings off/on didn’t make it show up anywhere. Minor issue for a flash drive, but would be annoying if you had a huge hard drive with media. Sure, it may have been possible to get it working without a format, but I couldn’t find a way.
One thing of note is that when I look at the node via AIMesh and click on Network to get uplink/backhaul information, I now see the PHY rate properly again. Previously this was 0 transmit and 0 receive (can’t remember what firmware did this). It’s currently showing 2882.3 and 3062.5 (the latter the highest I’ve ever had from when it did show properly).
I pray that it doesn’t drop to 2.4GHz or anything silly! The 5GHz-2 channel has returned to WPA2-Personal from what I’d set it to before (WPA3). Not sure about the security issues, but right now I don’t want to alter anything for obvious reasons! It doesn’t seem clear if changing anything for the backhaul is causing the problems.
(Also, I do think the radar issue I mentioned was a red herring as it failed around 1610-1612 every day this week with an error relating to the node – and no mention of radar issues for any day other than the one I posted above)
* I didn’t reset the logs so some information was retained, but all the key settings were reset. Shame there’s no ‘reset to default’ for each individual Wi-Fi channel, as it’s quite hard to remember what was default after you change certain settings.
Liked by:
You need to login in order to vote
My view is that Like most industries in that region, Testing vs Getting the product out takes a lesser priority. ‘Waterfall vs Agile’ (sort-off)
<noscript></noscript>The product has been out quite a while now, and with the 6E version now on sale in selected regions, I must begin to wonder if that would do the exact same thing (drop to 2.4GHz randomly).
I’d have thought it a relatively simple fix; just don’t allow it to drop to 2.4GHz OR at the very least make it attempt a renegotiation with the 5GHz-2 backhaul at very regular intervals. Maybe it is doing that and the renegotiation process is failing, which could explain the issue, but obviously I have no idea – but Asus should!
It really isn’t practical for me to run a cable between the two routers, or else I’d have done so.
You need to login in order to vote
<noscript>