I found that I was not able to visit vodafonemobile.wifi with google chrome for android. It insisted on doing a search instead, even when I prefixed it with http:// (probably it didn't like that because it likes https). Eventually I got there with firefox using the IP address 192.168.0.1 or 192.168.1.1 , I have forgotten which.
I think Vodafone will need to change their documentation.
This is relating to mobile internet device R228t where vodafonemobile.wifi is meant to be the address of the device's admin page.
If you've changed the dns servers on your android device then those servers will be used to resolve all addresses. Addresses within your home network will mean nothing on the internet.
Even if you haven't changed the dns servers yourself your chrome browser is likely using dns over https which again won't resolve your Internal addresses.
The correct dns server to use for the domain to resolve correctly would be your router, via it's ip.
If you've changed the dns servers on your android device then those servers will be used to resolve all addresses. Addresses within your home network will mean nothing on the internet.
Even if you haven't changed the dns servers yourself your chrome browser is likely using dns over https which again won't resolve your Internal addresses.
The correct dns server to use for the domain to resolve correctly would be your router, via it's ip.
I had forgotten all about this. I was using a new phone but forgot that settings were copied from the old, so Google Chrome was set to use secure DNS from the current provider, but Android was set to use private DNS from Quad9, so I don't know when I did that or why but it explains.
Firefox doesn't seem to have any DNS settings, about:config is disabled.
