by avvy65 » 21 Oct 2017, 10:23
Hi janui, thanks for the reply.
When Runeaudio was scanning the networks, I would have expected it to see the real IP address of 192.168.0.1, as it sees the ETH0 of 192.168.0.106 connection.
I selected a different network from the list, which is on my lo0cal network, and Rune has spent something like 12 hours scanning and trying to connect to 192.168.x.x to which is my router's ip and also wifi. Then Rune then became not available, so I restarted it, and did a network refresh. It now shows my wlan0 on my local network as 192.168.0.146. But now rune is not available on my android devices which is probably because of the poor wifi of the pi3, as you say, but the wifi on the pi zero w is much better .
When I diagnose the problem on the windows machine , it says that the remote device won't accept the connection. Huh, it did before. Is there some where in the settings that it can be changed.
Thanks