03-16-2024, 08:21 PM
(This post was last modified: 03-16-2024, 08:40 PM by TheOldPresbyope.
Edit Reason: fing, not Android itself
)
@Sehnsucht
Maybe it's the result shown in my test case 3) which is tripping you up.
Test 1)
I just loaded moOde 8.3.9 (configured with hostname "zerotest") to a uSD card, stuck it in a Pi Zero W, and booted. Opened the WiFi settings on my Google Pixel 6a phone.
After about 2-1/2 minutes "zerotest" appeared in the Pixel's list of available WiFi access points. Connected the Pixel to it (and, when alerted that this connection had no Internet access, told it to stay connected).
Opened the Chrome browser on the Pixel and gave it the mDNS URL "zerotest.local". Chrome opened the moOde WebUI, fresh as paint.
Test 2)
Configured the moOde player for a WiFi connection to a non-existent WiFi access point (this to approximate the situation of your player being configured for your home network but started up away from the house). Rebooted. After a rather longer time lapse than before (sorry, I didn't time it), "zerotest" again appeared in my Pixel's list of available WiFi access points.
I can proceed to connect and open the moOde WebUI to "zerotest.local" as before.
Test 3)
Configured the moOde player for a connection to my Pixel as access point. Rebooted it. Also, disconnected my Pixel from my home WiFi network so it was connected solely to the cellular data network. After about 2+ minutes, the moOde player is connected to my Pixel. This time, however, I am unable to access the moOde WebUI by the mDNS URL "zerotest.local". Why? Because of the way Android treats address space. The phone's IP address (10.115.x.x) and the moOde player's IP address (192.168.x.x) are in different networks, and mDNS does not cross network boundaries.
Just as you did, I can use yet another device to connect to my phone and locate the IP address of the moOde player. This address works fine in the Chrome browser on the Pixel because Android does route IP.
Trying to find the connected moOde player using the Android app "fing" fails because Android fing doesn't think the phone is connected to a WiFi network.
I don't know offhand why Android has assigned the phone an IP address in the 10.115.x.x range when it's running on the cellular data network. Both 10.x.x.x and 192.1668.x.x are in the IETF/IANA reserved IP address blocks for "local communications within a private network".
Regards,
Kent
Maybe it's the result shown in my test case 3) which is tripping you up.
Test 1)
I just loaded moOde 8.3.9 (configured with hostname "zerotest") to a uSD card, stuck it in a Pi Zero W, and booted. Opened the WiFi settings on my Google Pixel 6a phone.
After about 2-1/2 minutes "zerotest" appeared in the Pixel's list of available WiFi access points. Connected the Pixel to it (and, when alerted that this connection had no Internet access, told it to stay connected).
Opened the Chrome browser on the Pixel and gave it the mDNS URL "zerotest.local". Chrome opened the moOde WebUI, fresh as paint.
Test 2)
Configured the moOde player for a WiFi connection to a non-existent WiFi access point (this to approximate the situation of your player being configured for your home network but started up away from the house). Rebooted. After a rather longer time lapse than before (sorry, I didn't time it), "zerotest" again appeared in my Pixel's list of available WiFi access points.
I can proceed to connect and open the moOde WebUI to "zerotest.local" as before.
Test 3)
Configured the moOde player for a connection to my Pixel as access point. Rebooted it. Also, disconnected my Pixel from my home WiFi network so it was connected solely to the cellular data network. After about 2+ minutes, the moOde player is connected to my Pixel. This time, however, I am unable to access the moOde WebUI by the mDNS URL "zerotest.local". Why? Because of the way Android treats address space. The phone's IP address (10.115.x.x) and the moOde player's IP address (192.168.x.x) are in different networks, and mDNS does not cross network boundaries.
Just as you did, I can use yet another device to connect to my phone and locate the IP address of the moOde player. This address works fine in the Chrome browser on the Pixel because Android does route IP.
Trying to find the connected moOde player using the Android app "fing" fails because Android fing doesn't think the phone is connected to a WiFi network.
I don't know offhand why Android has assigned the phone an IP address in the 10.115.x.x range when it's running on the cellular data network. Both 10.x.x.x and 192.1668.x.x are in the IETF/IANA reserved IP address blocks for "local communications within a private network".
Regards,
Kent
