[Official Release] AiMesh Firmware v3.0.0.4.384.20308 for All Supported Products

[Neil62]

Exact same problem here, has always worked before. Maybe ASUS are uploading some new firmwares (AiMesh) to their servers, can only hope.

Well unfortunately it's working again, but NO NEW AiMesh firmware from Asus. More hopes dashed.

 

[arthurlien]

Well unfortunately it's working again, but NO NEW AiMesh firmware from Asus. More hopes dashed.[/QUOTE

If you are looking f/w update issue, this is not firmware issue, No need new firmware to fix it.

 

[Neil62]

Was just hoping/dreaming, that by, not being able to connect to the ASUS firmware update servers via the router web GUI, that maybe a new AiMesh firmware was being released and that the ASUS servers were being updated with a newer AiMesh firmware release. But my dream was wrong, expecting too much too soon from ASUS, I am now again, able to connect to the ASUS firmware updates server/s via the router web GUI and as per usual, on checking, both router and nodes, ALL are on the latest firmwares. Sad....

So, still no new AiMesh firmware available from ASUS...

ASUS are Toooooooooo, Slowwwwwwwww with a firmware upgrade for AiMesh. Why? You would think for a new marketing tool, it should take some priority.

Reading through the Aimesh Marketing info, ASUS always use the word "RELIABLE', seriously, based on what? I for one, know, it can't be based on AiMesh nodes constantly going 'offline'.

ASUS, please Help us AiMesh supporters (I am one), (new firmware), for those users that are still using AiMesh and working with AiMesh.

 

[RandomName23]

Was just hoping/dreaming, that by, not being able to connect to the ASUS firmware update servers via the router web GUI, that maybe a new AiMesh firmware was being released and that the ASUS servers were being updated with a newer AiMesh firmware release. But my dream was wrong, expecting too much too soon from ASUS, I am now again, able to connect to the ASUS firmware updates server/s via the router web GUI and as per usual, on checking, both router and nodes, ALL are on the latest firmwares. Sad....

So, still no new AiMesh firmware available from ASUS...

ASUS are Toooooooooo, Slowwwwwwwww with a firmware upgrade for AiMesh. Why? You would think for a new marketing tool, it should take some priority.

Reading through the Aimesh Marketing info, ASUS always use the word "RELIABLE', seriously, based on what? I for one, know, it can't be based on AiMesh nodes constantly going 'offline'.

ASUS, please Help us AiMesh supporters (I am one), (new firmware), for those users that are still using AiMesh and working with AiMesh.

Not sure what you expect. The firmware releases have been coming pretty fast actually, especially considering how slow they have come in the past from ASUS. If you take into account the Chinese New Year which is essentially 1 - 2 weeks of no work being done it really hasn't been that long since the last release.

In addition, I'm running Aimesh with one router and one node using a wireless backhaul and it is rock solid. My node never goes offline and I have a solid internet connection all the time. Maybe it's something in your environment or your setup.

 

[Ken Atkinson]

Today noticed laptop very sluggish on internet (have 200meg) , app showing cpu1 100% , logged in to ip address got in but unable to navigate menu, as per my post #526 reboot resolved , but im only running a AC88U and node AC66-B1 . i suspect a memory leak (possibly only under certain conditions) , happy to supply any info to arthur if he's not already aware of a bug. Note , system working fine and stable apart from my noticed 100% CPU flat-lining after a period of time.

 

[Skyler LaVey]

Not sure what you expect. The firmware releases have been coming pretty fast actually, especially considering how fast they have come in the past from ASUS. If you take into account the Chinese New Year which is essentially 1 - 2 weeks of no work being done it really hasn't been that long since the last release.

In addition, I'm running Aimesh with one router and one node using a wireless backhaul and it is rock solid. My node never goes offline and I have a solid internet connection all the time. Maybe it's something in your environment or your setup.

I don’t have issues either, but I’m not running AIMesh. The firmwares have not released fast. Before the latest official firmware it had been 5 months, that’s not fast. Now the unofficial betas come once a month or more, but those are hit or miss. 311 is the most rock solid ive been on since owning the router. I’m not complaining but the fact is, updates are slow if you want official firmware.


Sent from my iPhone using Tapatalk

 

[RandomName23]

I don’t have issues either, but I’m not running AIMesh. The firmwares have not released fast. Before the latest official firmware it had been 5 months, that’s not fast. Now the unofficial betas come once a month or more, but those are hit or miss. 311 is the most rock solid ive been on since owning the router. I’m not complaining but the fact is, updates are slow if you want official firmware.


Sent from my iPhone using Tapatalk

That is what I said, in the past releases were slow. So far with Aimesh they have been fast. I'm using the RT-AC5300 and there have been 3 official releases since the 26th of January. In general the fastest software development cycle would be on a 2 week cycle but if we got one firmware a month I would consider that fast for a firmware update.

 

[Ken Atkinson]

Firmware releases unless to address an urgent security notification if they occur more frequently than monthly would suggest an underlying problem with fixes/management. Mesh to me is stable (apart from my suspected memory leak) which will hopefully be resolved in next firmware.

Note. recent android app update reports more accurate on connected devices , not 100% but definately better

 

[OzarkEdge]

Note. recent android app update reports more accurate on connected devices, not 100% but definitely better

I agree!

OE

 

[mogulman]

Rt-AC86u main and RT-AC1900p node.

Disabled AiMesh for now. Maybe I'll re-enable it if a new version comes out .

Partially the issue I was having with Ethernet connections dropping .

Partially my phone dropping 2.4 in an in-between part of my house. I changed Roaming Assistance to -65 in my main router. I watched my signal and it wasn't hitting -65 as far as I could tell, but I would switch networks . I have a feeling that maybe the node setting wasn't -65 for 2.4 GHz even though the main was . I would get disconnected around 50 something.

Hope there is something new to try soon

 

[Flying Dutchman]

I have been managing beta-tests all my working life.
I would have been extremely happy with so many beta- testers, joined in a forum like this.

For Asus it is a golden opportunity to release beta firmware in this forum (so no official firmware) and ask testers to report any issue.
Of course only manual update is possible, but that is no issue for all of us.

I don't understand why Asus leaves this possibility untouched. So many testers,so many specialists, free of charge ...

 

[RMerlin]

I don't understand why Asus leaves this possibility untouched. So many testers,so many specialists, free of charge ...

Asus issued like 5 or 6 beta releases last autumn for AiMesh, so I don't know what you are complaining about here.

Note that sometimes, you can't release beta software because the new features you are working on are still confidential.

 

[OzarkEdge]

I have been managing beta-tests all my working life.
I would have been extremely happy with so many beta- testers, joined in a forum like this.

For Asus it is a golden opportunity to release beta firmware in this forum (so no official firmware) and ask testers to report any issue.
Of course only manual update is possible, but that is no issue for all of us.

I don't understand why Asus leaves this possibility untouched. So many testers,so many specialists, free of charge ...

A good and positive suggestion that does not deserve to be characterized as complaining, imo.

We can only trust that ASUS has things under control to suit their needs. I've never needed a networking forum before, but this AiMesh system roll out for existing product is a different kind of beast. To me, it remains an impressive undertaking by ASUS... I expect a bumpy ride as they fill in the missing pieces. For example, the router app has interface elements that are clearly not implemented yet... streaming through my Chromecast shows zero traffic to that device.

OE

 

[LimJK]

SSH Login to my RT-AC86U AiMesh Nodes from my MacBookPro via Wired Connection to the specific Node(s) has some strange issues, not sure if others have same issue.

• LimJKMacBookPro:~ limjk$ ssh limjk@192.168.1.254
• limjk@192.168.1.254's password:

Sometimes the password prompt happened instantaneously, sometimes I have to wait for 45+ seconds.
After entering password sometimes I have to wait for about a minute to get the following error message.

• packet_write_wait: Connection to 192.168.1.254 port 22: Broken pipe

PS: Ping over the same wired connection, sometimes gets no response as follows:

PING 192.168.1.254 (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: icmp_seq=0 ttl=64 time=0.527 ms
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=0.283 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=0.390 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=64 time=0.404 ms
64 bytes from 192.168.1.254: icmp_seq=8 ttl=64 time=0.297 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=64 time=0.362 ms

--- 192.168.1.254 ping statistics ---
10 packets transmitted, 6 packets received, 40.0% packet loss
round-trip min/avg/max/stddev = 0.283/0.377/0.527/0.080 ms

PS: There is NO problem when Login or Ping over Wireless Connection from my MacBookPro or iPhone X.
PS: I have the same problem on both my RT-AC86U AiMesh Nodes. My workaround is to reboot the AiMesh Nodes, but, same thing happen after an hour or two.
PS: However, normal AiMesh operation is functioning properly

 

[Volfi]

After running fine for 10+ days, my AC88U with lastest firmware froze last night, CPU1 usage at 100%. Not sure why, it is below 10% usually. Reboot fixed that.

 

[Quad80]

Firmware v3.0.0.4.384.20308 deficiencies:

o RT-AC68U firmware and release notes https://www.asus.com/us/Networking/RTAC68U/HelpDesk_BIOS/
o Quick Setup splash screen concatenates "NewNetwork"
o Some list column titles use plurals such as "Clients", some do not such as "Client" (avoid using plurals except for clarity)
o Disabling WPS does not disable WPS push button method on nodes
o Guest networks do not propagate to nodes
o MAC filtering does not work on node
o Client lists refresh sporadically (this behavior settles some over time)
o Node client list does not indicate client band, 2.4 or 5.0 GHz
o Wireless clients listed correctly in the router Wireless Log can be listed as wired or on the wrong band on the Network Map client lists (the Android app does not exhibit these discrepancies)
o Wired node client (OBi202 ata/phone) disappears from node list but reappears when active
o Can not schedule node reboot
? Time Zone DST settings may not be working
o Can not sort Assigned IP list by assigned IP
? Wireless schedule settings are cleared by reboot
o Does not support DNSSEC/DNSCRYPT to prohibit ISP hijacking of DNS resolution

Note that tri-band routers dedicate one of the two 5.0 GHz bands to inter-node communication.

So far, AiMesh has been a worthwhile upgrade. Time will tell... WiFi is hard, its clients can be dumb, neighboring WiFi can be untamed, and AiMesh firmware and app are a work-in-progress.

OE

I'd add two things to this list (2x AC-RT3100, one node in AiMesh):

1) Node is showing as 2x clients for me in the client table. It's at the correct IP address, but shouldn't show up at all, let alone twice for one unit.

2) Devices that are assigned a static IP using MAC address are still being assigned a second IP address from DHCP pool. Device responds/functions at both IP addresses, but it shouldn't be assigning a second IP. This device also shows up twice in the client list.

These problems persist on all firmwares I've tried.

 

[OzarkEdge]

I'd add two things to this list (2x AC-RT3100, one node in AiMesh):

1) Node is showing as 2x clients for me in the client table. It's at the correct IP address, but shouldn't show up at all, let alone twice for one unit.

2) Devices that are assigned a static IP using MAC address are still being assigned a second IP address from DHCP pool. Device responds/functions at both IP addresses, but it shouldn't be assigning a second IP. This device also shows up twice in the client list.

These problems persist on all firmwares I've tried.

I hear you.

1) When I had my node listed as client ASUS and my cable modem listed as a client, I also knew my first install was weird and did not feel solid. So, that's when I backed off, reset the routers, manually re-installed the firmware, and initialized each to factory defaults. I have not seen such odd things since. So, I'm now skeptical of installs by other.

2) See 1). I just can't imagine ASUS releasing firmware that would fail to perform the most basic task of assigning IP addresses correctly. So, I remain skeptical of your installation... nothing personal!

When you re-installed the AiMesh firmware on each of your routers... surely you've done this by now, yes?... did you initialize each router to factory defaults afterward?

OE

 

[Quad80]

I hear you.

1) When I had my node listed as client ASUS and my cable modem listed as a client, I also knew my first install was weird and did not feel solid. So, that's when I backed off, reset the routers, manually re-installed the firmware, and initialized each to factory defaults. I have not seen such odd things since. So, I'm now skeptical of installs by other.

2) See 1). I just can't imagine ASUS releasing firmware that would fail to perform the most basic task of assigning IP addresses correctly. So, I remain skeptical of your installation... nothing personal!

When you re-installed the AiMesh firmware on each of your routers... surely you've done this by now, yes?... did you initialize each router to factory defaults afterward?

OE

I've had the second problem since I installed the router with whatever firmware it came with, so that was fresh out of the box. In fact, if I reset the router for any reason, it will show the device once at the IP I assigned it. At some point, it goes to two devices at whatever address it feels like (even though it also works at the assigned IP, too). I couldn't tell you when it switches exactly, but it does, and I'm not doing anything I can think of to cause it.

For the first problem, it never did this right after I installed the first mesh firmware. Somewhere along the way, like my other problem, it just started happening. I couldn't tell you if they are related or not.

That said, I did not do a factory reset since AiMesh dropped, because both "problems" aren't really affecting the functionality of the system, so it doesn't really bother me that much. At some point when I get time, I'll try a factory reset like I know I should. However, given that the one problem existed out of the box, I can't say that would resolve the problem.

It's not that hard to believe they could have a bug. After all, the client list has also been screwed up since I set this whole thing up. It refreshes like crazy, doesn't always assign the correct band/connection to the various clients, and often lists clients after they've disconnected. Though these things seem to be improving, they're still an ongoing issue, and I'd consider client lists to be a pretty basic thing. I never had an issue with my old DDWRT router with any of that.

 

[OzarkEdge]

That said, I did not do a factory reset since AiMesh dropped, because both "problems" aren't really affecting the functionality of the system, so it doesn't really bother me that much. At some point when I get time, I'll try a factory reset like I know I should.

This is a good read https://www.snbforums.com/threads/faq-nvram-and-factory-default-reset.22822/

Note the importance of performing a factory default reset after installing the AiMesh firmware and before configuring it for use. I suggest using the Initialize option instead of the Restore option in the router GUI.

Until this is done, I see no use for ancillary observations and troubleshooting.

OE

 

[Quad80]

This is a good read https://www.snbforums.com/threads/faq-nvram-and-factory-default-reset.22822/

Note the importance of performing a factory default reset after installing the AiMesh firmware and before configuring it for use. I suggest using the Initialize option instead of the Restore option in the router GUI.

Until this is done, I see no use for ancillary observations and troubleshooting.

OE

I see no reason to reset if at least one of these problems existed since it came out of the box from the factory, so I guess we're in disagreement about this