Hi All,
If I may ask for some assistance...
I have an ASUS DSL-AX82U - it's 8 months old. It's connected through AiMesh with 4 CT8 as nodes; 9 and 6 months age (bought in pairs).
The base IP4 is 192.168.50.1 - as delivered. All IP addresses are automatic, except for security cameras which I have fixed. IP6 is off as is VPN. SSD for 2.4 and 5 have differing names.
Apart from a few niggles the system has done me well since it was set up, it doesn't fully spread its mesh as wide as needed, so an older ASUS DSL-AC68U is a fifth node, but not always switched on. Firmware on all the units is kept to date.
In recent weeks I've had various devices around my network connecting through 192.168.30.xxx - obviously unable to access the Internet. For most of the devices I can get around this through taking a static IP. Some devices such as the Alexa Show units have no obvious means of bypassing the auto IP connection.
The main question, whilst I wait for something from ASUS, is has anyone encountered this strange situation where devices try to connect to the router/nodes by SSD and pick up a different IP address to what is supposed to be in the allocation?
It might be tied in with any recent firmware upgrade, in which case I would assume I'm not alone in seeing this. The most recent upgrade has resulted in neither the web gui nor the android app showing the nodes on the display, but the IP address issue is an older beast.
Geoff
If I may ask for some assistance...
I have an ASUS DSL-AX82U - it's 8 months old. It's connected through AiMesh with 4 CT8 as nodes; 9 and 6 months age (bought in pairs).
The base IP4 is 192.168.50.1 - as delivered. All IP addresses are automatic, except for security cameras which I have fixed. IP6 is off as is VPN. SSD for 2.4 and 5 have differing names.
Apart from a few niggles the system has done me well since it was set up, it doesn't fully spread its mesh as wide as needed, so an older ASUS DSL-AC68U is a fifth node, but not always switched on. Firmware on all the units is kept to date.
In recent weeks I've had various devices around my network connecting through 192.168.30.xxx - obviously unable to access the Internet. For most of the devices I can get around this through taking a static IP. Some devices such as the Alexa Show units have no obvious means of bypassing the auto IP connection.
The main question, whilst I wait for something from ASUS, is has anyone encountered this strange situation where devices try to connect to the router/nodes by SSD and pick up a different IP address to what is supposed to be in the allocation?
It might be tied in with any recent firmware upgrade, in which case I would assume I'm not alone in seeing this. The most recent upgrade has resulted in neither the web gui nor the android app showing the nodes on the display, but the IP address issue is an older beast.
Geoff