[LarryR]

UK Sentinel wrote:

Interesting, what is device [44:a8:fc:de:65:6a] ? and was this event log around the time the Aimesh backhaul dropped to 2.4GHz ? If disabling roaming assistant for you backhaul doesn’t prevent wireless backhaul from dropping to 2.4GHz, I would suggest you factory reset your AiMesh XT8 routers (all) and rebuild all (factory reset all) your mesh system from scratch

Just adding that I have a MACID lookup table and 44:a8:fc is showing as “Apple” device of some kind. And in reference to the May 5 date in the log – that is normal when it reboots until it can connect to NTP to get current date/time.

I also had my node drop to 2.4 after 33-34 days of uptime, which is still great in my mind. I’ve just decided to schedule a once a week 4am reboot and hopefully things stay as stable as they have been for me. I have my backhaul locked to channel 173 and locked to 160 and GUI shows “Great” for connection strength.

Liked by:

You need to login in order to vote

[LarryR]

Had to reboot today after about 34 days uptime. Node was only connecting on 2.4 even though i had it set to fixed channel (173) 5-2. Interestingly enough, rebooting the node did not get it back on 5 backhaul. Had to do a system reboot from the app and then router and node were fine. Still, 30+ days for me is small miracle.

You need to login in order to vote

[LarryR]

3.0.0.4.388_22525 has been the most stable firmware (for me) since I bought my XT8 about 13 months ago.

Now at about 22 days uptime. Memory usage has been stable. My 60ish connections are all happy. Have manually chosen channels and locked the wireless back haul to 160mhz.

Speedtest from the router at a consistent 580+/23+ (I have 500/20 Spectrum).

For me at least….. FINALLY. Saving this firmware as a future fallback if issues.

Liked by:

You need to login in order to vote

[LarryR]

UK Sentinel wrote:

Jacky Decoster wrote:

after the factory reset, everything is working fine. fingers crossed

Great news<noscript></noscript>

Is doing a factory reset from the GUI option the same as any other method? When you do the reset, what is the username/password to login to router or is that preserved?

 

You need to login in order to vote

[LarryR]

UK Sentinel wrote:

How’s the new 3.0.0.4.388_22525 build holding out, I did read that Web & Apps Filters was causing issues with stability ?

So far, stable for me. Uptime only 2 days 12 hours though so time will tell. I don’t use any of the filtering.I have backhaul at 160mhz only and have manually selected channels for all bands.

I removed my twice a week scheduled reboot (which kept things crash free but was annoying).

Liked by:

You need to login in order to vote

[LarryR]

So on 388 release. Have locked channels and selected 80mhz for backhaul. Yesterday, after 3 or 4 days of perfection, I had my node (have a 2 device system, 1 as router, 1 node) flashing blue. What does that mean?

 

You need to login in order to vote

[LarryR]

dodgydrains wrote:

My setup is – ISP Router – XT8 router – XT8 Node 1 – XT8 Node 2 – XT8 Node 3 Wireless speedtest from device connected to Node 1 is basically full speed 750Mbps+. The one in my room is Node 2. From there I get 490Mbps with 160MHz and 340Mbps with 80MHz.

I only have a 1 router, 1 node XT8 system. Wonder if it’s the daisy chaining that slows things down? Have you manually selected a backhaul channel that seems clear of any other interference?

I’m just surprised that being an extra hop away would slow things down that much. Not that 340Mbps isn’t enough for just about anything ^_^.

 

Liked by:

You need to login in order to vote

[LarryR]

dodgydrains wrote:

I will give it a try with 80MHz, in the name of science<noscript></noscript>. Speedtest has gone down from 490Mbps to 340Mbps. Lets see what happens.

Speedtest from a device connected to that node or from the GUI? I know in my case, 80mhz on 802.11ax provides more than enough bandwidth for my 500/20 Spectrum connection at max speed (I speedtest out around 590/24 during “quiet” times).

Liked by:

You need to login in order to vote

[LarryR]

Jonathan Morris wrote:

I’ve been running 3.0.0.4.388_22068 for ages now and not had any issues at all. Can’t even remember the last time I saw the mesh node dropping to 2.4GHz. RAM usage seems fine and so too is the USB flash drive I have hooked up to the main router to share a selection of movies to smart TVs. I have forced 80MHz backhaul and gave up on 160MHz because it seems that with that enabled, I get the problems. As ever, you can never be 100% certain that changing a setting has helped when also changing the firmware, but with this version it is very much a case of ‘set it and forget it’. I too have WPA2-Personal and have a fixed channel rather than auto.

I just decided to try the same as you. Upgraded back to latest official 388 release. WPA2_Personal. Wireless backhaul to 80 only. No more auto for channel selection on all bands. Let’s see how stable we are.

Liked by:

You need to login in order to vote

[LarryR]

I do have one question for the gang here. I’ve always done “dirty” installs – have never done a reset to factory (or whatever the language is in the GUI). Why would it be recommended to do one and can you restore a backup after resetting to avoid manually recreating settings?

 

 

Liked by:

You need to login in order to vote

[LarryR]

I had a horrible go of it with 388 firmware’s as well – both official ASUS and the Gnuton/Merlin. I’ve gone back to the last 386 gnuton release just because I want to stay gnuton.

I’ll go back to latest gnuton as soon as I hear something definitive about fixes.

 

Liked by:

You need to login in order to vote

[LarryR]

dodgydrains wrote:

Not sure what the question is, is it how to ‘bind’ a device to a specific ‘node’. If so, using the browser UI, go to the AiMesh section and you can ‘bind’ a device to only connect to a specific node. There is a icon next to each device that looks like a paper clip. You can use that to bind a device so it always connects to that router or node. You can also go to ‘Professional’ tab under Wireless section and reduce RSSI lowere than the -70 dBm default. That way, when moving around the device will connect to the closest node. I tend to use the manual binding method for devices that stay in one place i.e TV, desktop PC etc

I had found with this past Firmware that devices seemed to “hang” on to the weaker node even though I hadn’t changed any settings. With past firmwares over a day or 2 systems would more naturally find the best node to connect to. I ended up looking for the weaker signals and manually bound them to the other node which is stronger.

You need to login in order to vote

[LarryR]

So running on the latest “pre-Christmas” firmware release on a 1 router, 1 node XT8 system. Usually have between mid 50’s and low 60’s devices connected. Usually over a day or 2 there will be a balance between which node a device is connected to, biased heavily to the main router since it is on our first floor with a lot of the smart stuff.

With this firmware it’s been a couple of days since a reboot and only 4 devices are on the “upstairs” node. Is there some way to have the system optimize itself as to which devices connect to which node?

You need to login in order to vote

[LarryR]

UK Sentinel wrote:

Ok, so have had feedback from a contact at ASUS, even they was not aware of this statement released via Republic of Gamers website, but does think also after reading the above statement, the dates will be Added to Firmware releases once again. Job done<noscript></noscript>

Never doubt that a small group of thoughtful, committed citizens can change the world; indeed, it’s the only thing that ever has.

Liked by:

You need to login in order to vote

[LarryR]

UK Sentinel wrote:

It is the same release as the firmware for hardware V1 ( 3.0.0.4.388.22068) but this time for Hardware V2 only, but exactly same release version number etc. which is most confusing. Exactly the same changelog as V1.

Not 100% sure that is true as I am on V1 hardware and had the previous 388 release and was offered this release in the app and have installed it and all seems good so far.

 

You need to login in order to vote

[Author]

Posts