Have a new android on Spectrum and it connects it’s hotspot with the Raspberry Pi but cannot get these pages to come up:
Any Idea as to why the Raspberry and Kraken do not talk? Oh yes, changed the cable to make sure it did not go bad. The old Android phone was working.
Connect a monitor and keyboard to the pi and check what wifi it has connected to through the wifi config icon and verify what IP address it has received. On the pi desktop connect to http://localhost:8080 and see if you get the page there.
If you’re connecting to a mobile hotspot on your phone, then hostname resolution will not work because it’s a public network, so you cannot use krakensdr:8080.
Is 92.168.43.63 definitely local the IP of your Kraken? You can check by using the WiFi settings on your phone to see what IP address the mobile phone’s hotspot has given it.
Update on the issue I am having. This is a new Pixel 9 Pro XL phone. I can ping the 192.168.59.93 IP address, with my laptop also connected to the hotspot, of the Raspberry Pi found using ifconfig -a on the Pi, as seen below. However, the laptop does not show that address or any address of other connected devices, with an arp -a command. The laptop and my phone cannot connect to 192.168.59.93:8080 as it times out. It is as though the new Pixel 9 does not allow connected devices to see each other as far as communicating with each other. Has anyone else used a Pixel 9 Pro with the Kraken and are they having the same issue?
I found the issue. There is a Network setting in the Pixel 9 called “Adaptive Connection” which when turned on does not allow connections to talk together on the Pixel 9 Hotspot. Turning it off solved my problem. Also the connections now show up on my laptop using the arp -a command.
In addition, the Termux and Network Analyzer solution for picking up neighboring wifi users on the hotspot, no longer works as the Pixel 9 reports something like, “Can not attach to Socket”. Network Analyzer even had a notice that it would not work with Android 10 or later in this fashion. I found that my laptop gave me neighbor IDs using command prompt and the “arm -a” command. Also the info can be found on the Pi using “ifconfig”. Every time the phone is rebooted it comes up with a different IP address for the hotspot to give out, changing the 3rd Hex component.
Does this apply to mDNS host names (i.e. krakensdr.local:8080)?
My Samsung tablet is giving addresses that look NAT’ed - 192.168.9.227. So if it is doing a NAT function, I’d think it could handle mDNS ok.
But it doesn’t as far as I can tell.
Anybody having a .local address work with a hotspot?
I understand that krakensdr.local:8080 does not work for the most part because of DNS issues. It does not work on my Pixel 9.
As far as I know, Chrome on Android does not support mDNS, and hence doesn’t support .local. That’s my knowledge from a couple of years ago, and from recently testing it it still doesn’t work.
I also tried it with Brave browser. I also connected my Mac to the network, and the browsers couldn’t access it either via the .local name.
So apparently mDNS doesn’t work in my Samsung tablet either (and that’s got a lot of customization of Android, compared to a Pixel).
