08-28-2018, 05:37 AM
(08-27-2018, 04:39 PM)TheOldPresbyope Wrote: @JonPike
You left out a detail. Are you actually trying to use IPv6?
IPv6 is enabled by default in Raspbian so if your router is configured to support IPv6 there's bound to be some interaction going on. I don't use IPv6 on my LAN and it's disabled on my router so I can't comment on the 20-second cycle time on identity assignment you see.
In my case, I can see 4 IPv6 ports open on my moOde player. Ports 139 and 445 are NBT and SMB over IP, respectively; port 22 is SSH; port 111 is the portmapper.
Code:pi@moode:~ $ netstat -lnpt
...<lots of IPv4 ports>...and then
tcp6 0 0 :::139 :::* LISTEN -
tcp6 0 0 :::111 :::* LISTEN -
tcp6 0 0 :::22 :::* LISTEN -
tcp6 0 0 :::445 :::* LISTEN -
Google is your friend if you want to disable IPv6 in Raspbian, hence in moOde.
Regards,
Kent
Other stuff uses it, and I see the moode players getting IPv6 addresses along with their IPv4's. (common behavior for lots of things) It's just this constant renew requests
are not like everything else. Usual for most devices is a short handshake sequence, where a request is one step of, and then nothing for 15min or more.
I don't know what, if any, traffic might go out over the IPv6 interfaces on Moode, and am not certain if it's some Moode (or Raspbian) interface setting that is why the multiple requests are happening. You would expect it to ask for and get assigned an address, then just sit there. They could be not successful in getting the IPv6 address and trying that step repeatedly in a loop.
Thought I'd try to look a bit deeper and use netstat to check those ports, aaaaaaaand I seem to have more router related issues, my currently running player not responding, etc.. Upon resetting the down 2.4Ghz wifi, and rebooting the 4.0 Moode player, I see a normal hookup, and no repeated requests. Dropping that one and firing up the other player running 4.2, I get a similar result, no 20sec requests. (I also get no response on the 4.2 Moode player, but that's another story) Hmmm, wonder if my excessive requests happens only when you have two players on air at the same time? That shouldn't provoke any kind of interaction, either, but...
OK, way too many variables here, with the new router firmware version I'm testing (OpenWRT/LEDE 18.06.1), and a player in a questionable, broken state. So, I'm going to backtrack the router and reflash a player or two here and check this all out again in a day or so. Will let you know what I end up with....
