Conundrum

Associate
Joined
24 Nov 2021
Posts
31
Location
Aberdeenshire, Scotland
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
 
Are the devices connected to the same node or spread out over different nodes? It sounds to me like the devices are connecting to a node which in turn isn’t connected back to the base station for whatever reason.
 
Hi,

As the mesh display no longer shows the nodes and their clients it is hard to say. I believe they are spread out because of where the devices are located. The base station alone isn't strong enough to reach all places. 3 of the nodes are ethernet connected, just one wireless.

Although the display doesn't show the nodes, each of the nodes appear to be connected by virtue of the steady light on their fronts.

It's rather a strange one!
 
I’d try turning everything off. Then turn the router on and let it settle for a couple of minutes before turning on one of your nodes and see if it shows up on the GUI. The fact the nodes aren’t showing up indicates that there’s a glitch somewhere that needs to be ironed out that may or may not be connected to the differing IP address issue.
 
Thanks.

I wish I could say I've done all that and sorted the problem. But hasn't!

I agree there must be a glitch, but with access to all the nodes to see what their IPs are, I'm a bit stuck - one of the challenges with a mesh, they're all a cobweb centred on the base unit. Hopefully ASUS will respond and say it's to do with a previous upgrade?

Thanks

Geoff
 
I did, but took them out in favour of the mesh. The house wiring probably not good enough for them to be of use.
 
That's one potential cause ruled out. Powerline adapters can connect between buildings if you aren't careful. That can result in clients picking up IPs from a neighbour's DHCP server.
 
I've got all the nodes switched off, and devices are still connecting through 30.xxx.
It would suggest any glitch is directly on the base unit?
 
I’d switch off the base unit as well and make sure the devices don’t get an IP from somewhere else. They probably won’t, but worth doing for the 5 minutes it’ll take.

Then factory resetting all of the network kit and setting up again from scratch might be the best option.
 
I fear you're probably right. That'll be a popular move ..... :D

It's a wonder ASUS haven't responded, but then Covid is an excuse for all sorts these days!

Thanks for your help and patience...
 
Noticed on the TV set last night, when trying to sort out wireless connection for Internet.
DNS address is 192.168.30.1 which is the same domain as the spurious IP addresses devices are trying to use.
 
Router's connected through FTTC using PPPoE to Zen.

Old router hasn't been used as such since March, and has otherwise been reset to work as a node (but is currently off).

Just been through a hard reset on the router and there are still one or two devices (TV notably) insisting on connecting through 192.168.30.xx. Most settings are as default as I haven't changed anything since the reset.
 
What happens when your try to login in to 192.168.30.1 or 192.168.30.254? If nothing happens then download a network scanner app such as Fine to your phone, set the IP to something on the 192.168.30 range and scan. Something on your network is handing out those addresses and it needs to be found.
 
I just get a time out error.

Fine?

I have WiFi Analyser and that just discovers my main two SSDs linked to the router.
 
Back
Top Bottom