Well unfortunately it's working again, but NO NEW AiMesh firmware from Asus. More hopes dashed.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.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.[/QUOTE
If you are looking f/w update issue, this is not firmware issue, No need new firmware to fix it.
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.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 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.
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.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
Note. recent android app update reports more accurate on connected devices, not 100% but definitely better
I don't understand why Asus leaves this possibility untouched. So many testers,so many specialists, free of charge ...
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 ...
I'd add two things to this list (2x AC-RT3100, one node in AiMesh):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.
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
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.
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 thisThis 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
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!