DHO900: Cannot set Static IP for WiFi(Solved)

[moffy]

I searched the forum but couldn't find a working answer. I can connect to my ASUS router with my DHO914s(FW 1.03) but the MAC address is randomly generated so I cannot assign a fixed IP in the router. I have tried assigning a static IP on the scope, both through the scopes utility menu and the Web interface, but once the 'static IP' box is checked with an appropriate address entered etc. and DHCP and AutoIP disabled, upon reboot, it fails to connect to the wireless router. I then need to reenable DHCP and AutoIP and reboot. Is there any workaround? I would prefer to disable the random MAC address generation for WIFI in Android but that doesn't appear to be available.

[Sorama]

I have never heard of a random generated MAC address: they are owned by the manufacturer and distributed accordingly among them.

Show me the up numbers the scope gets when in dhcp and also what you have put in manually in the scope when choosing static.

 Chances are big that you did not choose a proper ip and its settings.

[moffy]

I have never heard of a random generated MAC address: they are owned by the manufacturer and distributed accordingly among them.

Show me the up numbers the scope gets when in dhcp and also what you have put in manually in the scope when choosing static.

 Chances are big that you did not choose a proper ip and its settings.

It's an Android thing: https://www.howtogeek.com/722653/how-to-disable-random-wi-fi-mac-address-on-android/
unfortunately the Rigol doesn't have the facility to disable it.

[Sorama]

Still, static addressing should work, so tell me what you get when using dhcp and what you tried putting manually in it.

[Jeroen3]

Does it fail to associate with the wifi on static IP? That would be highly unlikely.

Most likely is a misconfiguration, eg: wrong dns or gateway, causing android to reject the wifi as "there is no internet here".

[moffy]

Still, static addressing should work, so tell me what you get when using dhcp and what you tried putting manually in it.

On the scope:
DHCP: IP:-         192.168.50.118
          Subnet:    255.255.255.0
          Gateway: 192.168.50.1
          DNS:        192.168.1.1
Static: IP:           192.168.50.51
           Subnet:    255.255.255.0
           Gateway: 192.168.50.1
           DNS:        192.168.1.1

[moffy]

Does it fail to associate with the wifi on static IP? That would be highly unlikely.

Most likely is a misconfiguration, eg: wrong dns or gateway, causing android to reject the wifi as "there is no internet here".

I'm running the router without internet, purely as a local connection.

[Sorama]

Have you tried to ping that ip address before assigning it to the Rigol?

Maybe another device already has it (but then you should get a message that this ip is already in use)

[moffy]

Have you tried to ping that ip address before assigning it to the Rigol?

Maybe another device already has it (but then you should get a message that this ip is already in use)

I've checked the connections in the router interface, the address is free, only 1 connection and that's my PC on another IP address.

[Sorama]

If this address is static, you won’t see it in the router, so please, ping it.

[moffy]

If this address is static, you won’t see it in the router, so please, ping it.

Results:

Pinging 192.168.50.51 with 32 bytes of data:
Reply from 192.168.50.63: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.50.51:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Users\Daddy\Desktop>ping 192.168.50.52

Pinging 192.168.50.52 with 32 bytes of data:
Reply from 192.168.50.63: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.50.52:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

P.S. I have tried a number of static addresses in the 192.168.50.xxx range, all failed.

[Sorama]

It seems your router cannot capture the macc address of the scope.
Have you tried to put a simple switch/hub between the scope and the router?
I would try that and see if you can ping the static address you’ve put in the scope.

Also, most routers/switches. An show you a list of the macc addresses they have captured : you may want to check if that specific macc addresses of the scope is listed in the router (even without a bonded ip )

[moffy]

Thank you both for your help, it looks like the problem is solved. I hit 'WIN + N' keys on the scope to pull up the settings, entered WiFi and a long press on the router network shown. That pulled up a list of options for IP configuration, including static which I then filled out and rebooted. It now connects with the same IP address but doesn't show up as a client in the router interface. But still I can connect through my browser at the static address.

[Sorama]

Good!

[tooki]

I have never heard of a random generated MAC address: they are owned by the manufacturer and distributed accordingly among them.

Yes, for physical MAC addresses.

iOS has also defaulted to using randomly-generated MAC addresses since 2020. It’s also available in Android, but also in Windows 10 and later, and macOS 15 and later. So it is a very widely supported anti-tracking feature.

[Jeroen3]

Does it fail to associate with the wifi on static IP? That would be highly unlikely.

Most likely is a misconfiguration, eg: wrong dns or gateway, causing android to reject the wifi as "there is no internet here".

I'm running the router without internet, purely as a local connection.

This is key information. Android does not like this and may not show the wifi symbol at all, but it will be connected.

Try to use gateway 0.0.0.0 to indicate there isn't one.
Do point DNS to the router.

It may be stuck probing for captive portals

[moffy]

Does it fail to associate with the wifi on static IP? That would be highly unlikely.

Most likely is a misconfiguration, eg: wrong dns or gateway, causing android to reject the wifi as "there is no internet here".

I'm running the router without internet, purely as a local connection.

This is key information. Android does not like this and may not show the wifi symbol at all, but it will be connected.

Try to use gateway 0.0.0.0 to indicate there isn't one.
Do point DNS to the router.

It may be stuck probing for captive portals

Now that it is working, and I look at the 'Network Status' over the web interface, it shows:

IP Address:   192.168.50.111
Subnet Mask:   0.0.0.0
Default Gateway:   192.168.50.1
DNS Server:   0.0.0.0
IP Mode:   DHCP
DHCP Server:   192.168.50.111

I think there is a disconnect between the WiFi settings via Android, and what the scope displays. The adition of WiFi is a shortcut hack and the scope really only expects a LAN connection, not the Android WiFi.

[Sorama]

this is static, right?
(dhcp server is the ip of the scope itself).

Strange that the subnet mask is not filled in.
Did you?

[Jeroen3]

That subnet mask is a problem.

If it has working ethernet, buy a device bridge.
eg: if you're in the unifi ecosystem https://eu.store.ui.com/eu/en/products/udb-iot

[moffy]

I powered off and restarted the router and powered off and restarted the DHO914s and I was able to connect with it via my PC over WiFi at the same static address.
On the scope:
DHCP: IP:-         192.168.50.111
          Subnet:    255.255.255.0
          Gateway: 192.168.50.1
          DNS:        192.168.1.1

So the reporting on the Web Status is definitely confused.