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

[RandomName23]

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

That’s exactly why you would want to do a factory reset. If there is a bad configuration it might not be reset until you do a factory reset. It’s possible it came from the factory that way.

My guess is your dual IP is a client issue and not an issue with your router.

Still amazes me how people will continue to talk about things not working but refuse to take the 15 minutes to factory reset their router after a major firmware upgrade.

 

[Quad80]

That’s exactly why you would want to do a factory reset. If there is a bad configuration it might not be reset until you do a factory reset. It’s possible it came from the factory that way.

My guess is your dual IP is a client issue and not an issue with your router.

Still amazes me how people will continue to talk about things not working but refuse to take the 15 minutes to factory reset their router after a major firmware upgrade.

Well, if it came with a bum configuration from the factory, that's pretty bad. That aside, it takes more than 15 minutes to reset and get everything back the way it was before reset. And that's even assuming everything goes right, which as we've seen here, isn't always the case. If these issues we're major, yes, I'd reset. But otherwise, it's like poking a bear. I'd rather just leave it alone and not risk making things worse. I can't tell you how many times I've said "this shouldn't take long," then there goes my afternoon.

But given that there are lots of issues with the firmware out of the box that still persist after numerous updates, along with your recommendation to reset a factory fresh router, it should be enough to prove that even simple things can go overlooked by an experienced OEM. It happens.

Maybe it is the client somehow causing the issue, but it seems unlikely that a device can tell the router "I'm the same device, but just go ahead and list me twice," or that it can somehow still request an IP address after the router gives it one, and the router just goes "ok". But, I'm no expert, so, sure. It might be the client.

 

[OzarkEdge]

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

Yes, we are.

Our purpose here is to implement AiMesh firmware. To do this properly, you must factory default reset AiMesh firmware to purge as-shipped firmware settings. We don't care if this does not fix any defects in the as-shipped firmware that we are no longer using. We do care to not have those as-shipped firmware defects/settings continue to affect the operation of AiMesh firmware... and that you will never be able to troubleshoot successfully.

I factory default reset before installing AiMesh firmware; and again after installing AiMesh firmware.

There is not point in disagreeing on this, if you want a clean install of AiMesh. Try it, you might like it!

OE

 

[Quad80]

Yes, we are.

Our purpose here is to implement AiMesh firmware. To do this properly, you must factory default reset AiMesh firmware to purge as-shipped firmware settings. We don't care if this does not fix any defects in the as-shipped firmware that we are no longer using. We do care to not have those as-shipped firmware defects/settings continue to affect the operation of AiMesh firmware... and that you will never be able to troubleshoot successfully.

I factory default reset before installing AiMesh firmware; and again after installing AiMesh firmware.

There is not point in disagreeing on this, if you want a clean install of AiMesh. Try it, you might like it!

OE

But this isn't just an AiMesh issue. I had clients showing double BEFORE AiMesh was ever a thing. That's what you're missing. It has nothing to do with AiMesh and the bug existed out of the box. AiMesh didn't cause the problem. This is a firmware thread, not strictly an AiMesh thread. AiMesh just happens to be the newest and most exciting feature at the moment.

It works, it's a minor annoyance, that's why I'm not at a point where I want to potentially waste an afternoon re-setting up my network. To ignore the bug because of this is to ignore that it existed at the start, when AiMesh was unknown to all of us and still just a thing in the Asus labs (if even that, depending on when they started developing it, which is irrelevant).

I appreciate what you're saying, but I think we've exhausted this.

 

[OzarkEdge]

That’s exactly why you would want to do a factory reset. If there is a bad configuration it might not be reset until you do a factory reset. It’s possible it came from the factory that way.

My guess is your dual IP is a client issue and not an issue with your router.

Still amazes me how people will continue to talk about things not working but refuse to take the 15 minutes to factory reset their router after a major firmware upgrade.

Precisely so. Using my install notes, I could do it in 5 minutes. If you don't clean install, you are never going to have a working AiMesh because no firmware upgrade is going to fix the dirty broken settings in NVRAM.

OE

 

[OzarkEdge]

But this isn't just an AiMesh issue. I had clients showing double BEFORE AiMesh was ever a thing. That's what you're missing. It has nothing to do with AiMesh and the bug existed out of the box.

I've seen no other reports here of multiple IPs being assigned to the same DHCP client. If you had corrupted NVRAM issues/weird behaviors for whatever reason... there are more than one possible cause for this... then you should have solved it by clean installing a firmware upgrade, imo... then as in now.

OE

 

[Quad80]

I've seen no other reports here of multiple IPs being assigned to the same DHCP client. If you had corrupted NVRAM issues/weird behaviors for whatever reason... there are more than one possible cause for this... then you should have solved it by clean installing a firmware upgrade, imo... then as in now.

OE

And I've seen lots of reports of issues with AiMesh syncing, speeds, stability, etc, and I don't have any of those. Doesn't make them less real. Maybe I should have factory reset a factory fresh router, but that seems pretty counterintuitive, since it doesn't get more "factory" then taking it out of the box, but, okay.

 

[RandomName23]

And I've seen lots of reports of issues with AiMesh syncing, speeds, stability, etc, and I don't have any of those. Doesn't make them less real. Maybe I should have factory reset a factory fresh router, but that seems pretty counterintuitive, since it doesn't get more "factory" then taking it out of the box, but, okay.

Yeah just like all those times things like computers and what not came fresh from the factory with viruses and malware already installed.

 

[Ronald Schwerer]

That’s exactly why you would want to do a factory reset. If there is a bad configuration it might not be reset until you do a factory reset. It’s possible it came from the factory that way.

My guess is your dual IP is a client issue and not an issue with your router.

Still amazes me how people will continue to talk about things not working but refuse to take the 15 minutes to factory reset their router after a major firmware upgrade.

Backup the router's configuration then do the factory reset (or nvram erase). Then, if things don't improve you can quickly restore the old settings. Otherwise don't restore those settings because you'll just reintroduce the conflict.
These problems are not caused directly by the firmware since they aren't universally reported. So that leaves config or hardware. If it were me, I'd hope it was a problem with the config.

 

[OzarkEdge]

Maybe I should have factory reset a factory fresh router, but that seems pretty counterintuitive, since it doesn't get more "factory" then taking it out of the box, but, okay.

You clearly did not read and understand the NVRAM FAQ that resident router guru, RMerlin, posted. I suggest your try again:
https://www.snbforums.com/threads/faq-nvram-and-factory-default-reset.22822/

You must factory default reset after installing the AiMesh firmware to put its factory defaults into play in NVRAM. Simply upgrading existing firmware to AiMesh firmware does not replace the existing firmware settings in NVRAM with the factory default settings of the AiMEsh firmware. And under the circumstances, the AiMesh factory default settings in total are wildly new and different.

Intuition has nothing to do with this other than dissuading you from meeting requirements. If you did not factory default reset after upgrading to AiMesh firmware, then you have conflicting garbage settings in your router leftover from the pre-AiMesh firmware and will never enjoy a healthy AiMesh network.

OE

 

[Quad80]

You clearly did not read and understand the NVRAM FAQ that resident router guru, RMerlin, posted. I suggest your try again:
https://www.snbforums.com/threads/faq-nvram-and-factory-default-reset.22822/

You must factory default reset after installing the AiMesh firmware to put its factory defaults into play in NVRAM. Simply upgrading existing firmware to AiMesh firmware does not replace the existing firmware settings in NVRAM with the factory default settings of the AiMEsh firmware. And under the circumstances, the AiMesh factory default settings in total are wildly new and different.

Intuition has nothing to do with this other than dissuading you from meeting requirements. If you did not factory default reset after upgrading to AiMesh firmware, then you have conflicting garbage settings in your router leftover from the pre-AiMesh firmware and will never enjoy a healthy AiMesh network.

OE

I'm not going to argue, but when the issue was present BEFORE AiMesh, I don't think AiMesh is the problem. That is my point, and one you seem to overlook. It has been a consistent problem for me since the thing came out of the box. Whether or not anyone else has reported it doesn't matter, because we're all seeing different things to some degree.

In fact, I'd say my network is actually more stable than many here, based on how many people are reporting dropped/throttled connections and/or disappearing nodes. If things glitch to a point where the network suffers, I'll do a full reset. Until then, I'm just reporting an ongoing issue. I dunno what else to say, so that's all I'll say. Be well, friend.

 

[Ken Atkinson]

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

Was it loaded with the AIMESH firmware out of the box ? (if so what version) , if not the instruction say that after the firmware update you MUST factory reset, understand it may seem odd but this could be the root of your issues , and doing the reset is not tremendously time consuming.

Edit just read other post , C'est la vie

 

[Quad80]

Was it loaded with the AIMESH firmware out of the box ? (if so what version) , if not the instruction say that after the firmware update you MUST factory reset, understand it may seem odd but this could be the root of your issues , and doing the reset is not tremendously time consuming.

No. It had pre AiMesh firmware and the problems still existed. That's the point. The addition of AiMesh did not cause the problem. It was there from whatever was installed at the factory (I don't recall which version).

 

[Ken Atkinson]

No. It had pre AiMesh firmware and the problems still existed. That's the point. The addition of AiMesh did not cause the problem. It was there from whatever was installed at the factory (I don't recall which version).

Sorry but until you factory reset , can't see how anyone can help and if you log a problem with ASUS that will be the first thing they will tell you to do so unless you comply and report on status after reset no-one including the manufacturer can help.

 

[indark]

No. It had pre AiMesh firmware and the problems still existed. That's the point. The addition of AiMesh did not cause the problem. It was there from whatever was installed at the factory (I don't recall which version).

I personally always do both power cycle and hold wps to factory reset (to clear NVRAM) every time I update/swap firmware.

It always help solve weird issue that I have had experienced when a simply factory reset can't fix.

Just like couple version back, I was experience 100% CPU regardless how many time I reset. It wasn't fixed till I both power cycle and reset.
And just like this firmware, I had issue that the ai-protection signature version went crazy and wont update at all.
Again, it wasn't fixed till I powercycle and reset. (#5 post in this thread)

So it pretty much become a thing for me to do it whenever I experience weird stuff / update/ swap between merlin and official.
And if it's something can't be fixed, I report the error with syslog

 

[Flying Dutchman]

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.

No complaining, just wondering ....

 

[Flying Dutchman]

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

Indeed.

It is rather clear that the current public release is not yet ready. By publishing intermediate beta-releases to testers only it takes away the ground for complaining about Asus, which I see often on this forum. If you agree to use beta-firmware you also agree to only talk about issues. Like what Merlin is doing with his firmware.... . I have never read anything negative about him.

 

[Flying Dutchman]

WARNING MESSAGE: CONFLICTING IP

It happens every day at least once that I get a warning from my ESET anti virus tool that I have two devices connected with the same IP. It is always my NODE which is causing this warning message, in my case 192.168.0.2.

I have hard-wired my NODE, the setting of the backhaul is :
Connection Priority : Ethernet
Connection Type: Wired

@asus, please investigate.

 

[OzarkEdge]

Indeed.

It is rather clear that the current public release is not yet ready. By publishing intermediate beta-releases to testers only it takes away the ground for complaining about Asus, which I see often on this forum. If you agree to use beta-firmware you also agree to only talk about issues. Like what Merlin is doing with his firmware.... . I have never read anything negative about him.

Please take the 'er... what?' icon out of your quote... I did not say that.

OE

 

[Ronald Schwerer]

WARNING MESSAGE: CONFLICTING IP

It happens every day at least once that I get a warning from my ESET anti virus tool that I have two devices connected with the same IP. It is always my NODE which is causing this warning message, in my case 192.168.0.2.

I have hard-wired my NODE, the setting of the backhaul is :
Connection Priority : Ethernet
Connection Type: Wired

@asus, please investigate.

Even with a wired backhaul, AiMesh sets-up identical 2.4 and 5G IPs to the node (each with its own MAC). Probably for self-healing in case the wired goes down. So you can ignore that warning. I don't think Asus is going to re-engineer AiMesh for them.

Oddly,the wired IP to the node doesn't show in the client list. It also has the same IP. Maybe because its MAC is the same as 2.4Ghz.