AImesh node requests dhcp, but never receives one...

[ColinTaylor]

It is technically incorrect, for this reason it is not recommended and even not allowed on some servers.

It is not technically incorrect. Point me to any RFC or international standard that says so. Different vendors have different ways of managing DHCP but that doesn't mean one is technically correct and the others aren't.

I made no comment regarding AiMesh so you're just trying to distract.

 

[Tech9]

Untill now , yes, always same node

Was the same happening with the previous version of Asuswrt-Merlin on the main router?

 

[Pergola Fabio]

Was the same happening with the previous version of Asuswrt-Merlin on the main router?

Well. I only have the AX-88u for a few months , before I had the ac-88u , then it never happened, was same config

 

[Tech9]

You may have to give up on some old habits. The RT-AC86U units are EoL and AiMesh component is unchanged for quite some time, but RT-AX88U is still supported and changes in behavior are expected. If your ultimate goal is AiMesh - use stock Asuswrt on all units. If you have no interest in Guest Network propagation to nodes - Router + AP Mode is more stable configuration with potentially higher performance plus options for better Roaming optimization.

 

[bbunge]

Untill now , yes, always same node

As I've said a couple of times here - you have a hardware problem with the AC86U - it is failing! Time to send it to the big recycle bin and get another Aimesh node. If you really need all the WIFI that is...

 

[Tech9]

In my experience this is not a typical RT-AC86U failure symptom. They do have software quirks, but usually not present in AP/Node configuration. Most of RT-AC86U failures were hardware related like port, power circuit, radio IC, etc. This is something the user can catch relatively quickly.