09-02-2018, 10:10 PM
OK, have gotten back to this, and have learned a few things...
The Moode 4.2 Pi 3B system did have issues, and has been behaving better after the reflash. But, both it and the 4.0 Pi 1B+ system still do the same repeated refresh request attempts for IPv6 addresses. Sometimes it takes a while for one to start, sometimes the rate slows down to 1-2 times a minute, but it's there. Doesn't seem to need two players to start up, either.
I have had a few instances of trying to open the web page of a player, and it not responding right away. Usually on the Android, which does tend to be a bit more problematic. Not sure about that. But it doesn't seem to be the difficult to impossible to access players situation with the OpenWRT 18.06.1 router firmware, that I thought it might have been, so I doubt interaction between the two now.
Just to clarify, I'm not actively trying to connect Moode via IPv6, and I'm not trying to run DHCPV6 on the Pi, unless it's an out of the box thing in Raspbian. It's my router that is running it, and the Moode player that seems to be overly intent on making requests. Still don't understand the full picture, but something is borken, as they say, that we don't have a clean handshake, and Moode/Raspbian thinks it should keep requesting. (don't know why, it DOES end up with an IPv6 addy)
I see just those same ports, using netstat, thanks TOP! Nothing funny going on there. Looking at some of the IPv4 ports, I see a few ones I had to figure out, turns out the Raspotify service I run adds a few. Was wondering about the bc.googleusercontent.com address and port, that the Spotify traffic seems associated with, especially since it seems like a private IP in front of the name? Hope that's valid, sounds fishy, seems to be active only when Spotify data is being received. But, that's another rabbit hole, and apparently in the arena of the Raspotify/Librespotify stuff, not Moode.
So, will try disabling IPv6 on the Moode end altogether, and see if I miss anything. Seems like at this point, it's probably just "there" and not being used. At least that will keep it from filling my router logs and leave space for other events. As well as saving some CPU time and unnecessary network traffic. On my Pi 1B at least, that might mean something. Ideally, it gets fixed someday, by whoever the offending part/config belongs to. If you don't look in your router logs, you probably wouldn't know it's going on. But, in the interests of the philosophy of a audio network appliance should be doing as little as it needs to be doing, I'll let you know if turning IPv6 off is a viable option, and how to go about it.
The Moode 4.2 Pi 3B system did have issues, and has been behaving better after the reflash. But, both it and the 4.0 Pi 1B+ system still do the same repeated refresh request attempts for IPv6 addresses. Sometimes it takes a while for one to start, sometimes the rate slows down to 1-2 times a minute, but it's there. Doesn't seem to need two players to start up, either.
I have had a few instances of trying to open the web page of a player, and it not responding right away. Usually on the Android, which does tend to be a bit more problematic. Not sure about that. But it doesn't seem to be the difficult to impossible to access players situation with the OpenWRT 18.06.1 router firmware, that I thought it might have been, so I doubt interaction between the two now.
Just to clarify, I'm not actively trying to connect Moode via IPv6, and I'm not trying to run DHCPV6 on the Pi, unless it's an out of the box thing in Raspbian. It's my router that is running it, and the Moode player that seems to be overly intent on making requests. Still don't understand the full picture, but something is borken, as they say, that we don't have a clean handshake, and Moode/Raspbian thinks it should keep requesting. (don't know why, it DOES end up with an IPv6 addy)
I see just those same ports, using netstat, thanks TOP! Nothing funny going on there. Looking at some of the IPv4 ports, I see a few ones I had to figure out, turns out the Raspotify service I run adds a few. Was wondering about the bc.googleusercontent.com address and port, that the Spotify traffic seems associated with, especially since it seems like a private IP in front of the name? Hope that's valid, sounds fishy, seems to be active only when Spotify data is being received. But, that's another rabbit hole, and apparently in the arena of the Raspotify/Librespotify stuff, not Moode.
So, will try disabling IPv6 on the Moode end altogether, and see if I miss anything. Seems like at this point, it's probably just "there" and not being used. At least that will keep it from filling my router logs and leave space for other events. As well as saving some CPU time and unnecessary network traffic. On my Pi 1B at least, that might mean something. Ideally, it gets fixed someday, by whoever the offending part/config belongs to. If you don't look in your router logs, you probably wouldn't know it's going on. But, in the interests of the philosophy of a audio network appliance should be doing as little as it needs to be doing, I'll let you know if turning IPv6 off is a viable option, and how to go about it.
