Asus AiMesh Node static IP assignement

[Supermatico]

Hello, for my AiMesh master I already done

Is there a way to give a static IP also to the node (RT-AX88U)? Note that my node is in Backhaul connection (wired)

In LAN/DHCP Server/Manually Assigned IP around the DHCP list there all the peripherals, not the node

Sorry, I did a forum search unsuccessful, now I did the same search on google and I found the solution in this thread https://www.snbforums.com/threads/change-ip-on-node.87997/

Thanks in advance

 

[Tech9]

What's the problem that needs a solution in first place?

Don't mess with AiMesh, it's a black box and fragile enough already.

 

[Supermatico]

What's the problem that needs a solution in first place?

Don't mess with AiMesh, it's a black box and fragile enough already.

Hi Tech9

Nothing special: when you have to manually upload the new firmware on the node, a little window pop up asking for user and password to login.
I have a password manager software to store identities and passwords since 2003, but if I store those data on a node login web page like http://192.168.1.210/Main_Login.asp and the next time, for any reasons, the node IP has changed and that page will be http://192.168.1.5/Main_Login.asp, my password manager will not recognize it and I'll have to looking for the user and password manually to fill the corresponding fields

With a static IP instead my password manager will always recognize the stored data for that http page and it will fill them automatically, nothing else

Thanks

 

[jksmurf]

Sorry, I did a forum search unsuccessful, now I did the same search on google and I found the solution in this thread https://www.snbforums.com/threads/change-ip-on-node.87997/

Hi somewhat related is something I’ve been trying to do here, but even after I assigned the node an IP address using the MAC address, it didn’t change the IP.

Looking at your referenced thread I think it’s because the node (at least mine) is using an Ethernet MAC even though it’s a wireless backhaul. I will try assigning that as well as the Wifi MACs (which were for another purpose, see thread).

[EDIT] That does indeed work. Using the MAC address that AIMesh assigned.

 

[OzarkEdge]

Nothing special: when you have to manually upload the new firmware on the node, a little window pop up asking for user and password to login.

I would let AiMesh manage its nodes... one less thing to mess with. You can manually upload firmware to a connected node from within the root node/router webUI. If the node is no longer connected to your AiMesh, then manage it like any standalone router.

OE

 

[bbunge]

Hi Tech9

Nothing special: when you have to manually upload the new firmware on the node, a little window pop up asking for user and password to login.
I have a password manager software to store identities and passwords since 2003, but if I store those data on a node login web page like http://192.168.1.210/Main_Login.asp and the next time, for any reasons, the node IP has changed and that page will be http://192.168.1.5/Main_Login.asp, my password manager will not recognize it and I'll have to looking for the user and password manually to fill the corresponding fields

With a static IP instead my password manager will always recognize the stored data for that http page and it will fill them automatically, nothing else

Thanks

The user and password for the nodes are the same as the router and once in a network, the nodes IP address (and other DHCP clients) seldom change their IP address. Yes, you can manually assign an IP address to a node based on its MAC address.
But, it is better to not set Ethernet backhaul but to let the router and node choose what backhaul to use. That way you have a fallback should one fail. I write from experience ...

 

[Supermatico]

The user and password for the nodes are the same as the router and once in a network, the nodes IP address (and other DHCP clients) seldom change their IP address. Yes, you can manually assign an IP address to a node based on its MAC address.
But, it is better to not set Ethernet backhaul but to let the router and node choose what backhaul to use. That way you have a fallback should one fail. I write from experience ...

Yes, I always left that setting in AUTO. Tks

 

[kildare]

In my experience with 3 wired XT8 nodes with backhaul set to "2.5G WAN first" , even if the cable/switch is disconnected, anyway the nodes switch to the wireless backhaul.
In this case the key is "Backhaul Connection Priority" and the word "first"...

 

[Tech9]

In your case it may be different. ZenWiFi XT8 is a 3-radio model with one intended for dedicated wireless backhaul by default. Dual-band 2-radio models have Ethernet Backhaul Mode On/Off in AiMesh settings, no Priority. When set the AiMesh restarts/reconnects and doesn't use Wi-Fi anymore.