More > JRiver Media Center 21 for Linux
MC21 on Raspbian disapears from Playing Now list. PCs connect fine.
mwillems:
--- Quote from: designmule on November 02, 2015, 06:44:59 pm ---Just got the chance to test this. From the windows box I am able to ping the pi by name even when it is not showing up in the playing now window. I also VNC'd into the pi just to double check that JRiver is running, it is. On the pi, under media network I have "Use media network..." checked and under advanced I have only "DLNA Renderer..." checked as I don't think I need any of the other options enabled.
Currently I do not have the pi loading the library from the main server as I prefer to push to it via DLNA. Do you load the library on your pi(s)? I have tried this in the past and felt like the pi connects more frequently but it is not absolute. Additionally, when I ran volumio I only pushed to it.
--- End quote ---
I do both: I have the pi's logged into the server's library and I push to them via DLNA sometimes. Having them logged in makes them easier to control with JRemote (playback is more responsive), but I do also push to them as DLNA renderers (the two methods aren't mutually exclusive). Once upon a time one of my Pi's had issues when more than one JRiver instance in the house was configured as a DLNA controller. It would go dark like you're describing periodically until I disabled some of the extra controllers, but that Pi exhibited the same behavior with Volumio as with JRiver, so we're probably not seeing the same issue.
Maybe someone else has some thoughts, but it sounds like for whatever reason the multi-cast packets are getting eaten, but other traffic is getting through fine which could be a router issue. Either that or the JRiver instance on the Pi is "freezing" periodically and not responding to network traffic.
designmule:
I'll go ahead and have the pi connect to the library and see to what degree that helps.
I felt like disabling IGMP snooping helped (I left it off for 24 hours and the pi was pretty accessible). However, right before I turned the IGMP snooping back on for a 24 hour test the pi disappeared. This led me to believe IGMP snooping is not the issue + I have to have it on or my DVR doesn't work, it and my cable boxes all run over IP (Google fiber) so turning it off isn't a great option for me.
I read that I can test multi-cast on linux by entering netstat -g When I do so eth0 is listed three times. The first address is 239.255.255.250 the second address is 224.0.0.251 which I think is the multicast address and the last is all-systems.mcast.net.
From the Windows box typing in netsh interface ip show joins I get three addresses 224.0.0.1, 224.0.0.252 & 239.255.255.250 the all-systems.mcast.net provided by the pi seems a little out of left field. Maybe that all-systems.mcast.net is the issue. I'll have to look into it. Out of curiosity, if you enter netstat -g on one of your pi(s) what do you get?
mwillems:
I get something similar:
--- Code: ---IPv6/IPv4 Group Memberships
Interface RefCnt Group
--------------- ------ ---------------------
lo 1 all-systems.mcast.net
eth0 1 239.255.255.250
eth0 1 224.0.0.251
eth0 1 all-systems.mcast.net
--- End code ---
JRiver, under services and plugins-->Media Network will show you all the traffic it's sending and receiving so there may be a clue there. Also, you should really run a wireshark trace if you're comfortable with that sort of thing.
Mark_NL:
Could it be a DNS (cache) problem?
Suggesting this seen the same-like behavior while fiddling around using Wifi and Ethernet at the same time;
due to some mistakes I made the armboard had troubles resolving it’s own hostname.
designmule:
--- Quote from: mwillems on November 02, 2015, 07:38:20 pm ---JRiver, under services and plugins-->Media Network will show you all the traffic it's sending and receiving so there may be a clue there. Also, you should really run a wireshark trace if you're comfortable with that sort of thing.
--- End quote ---
I had a chance to look at this briefly before I left for work this AM. I'll have to look more closely this evening. I've run wireshark before but I'm not very familiar with it. Would I run it on my windows PC and look for multicast traffic from the pi?
Mark_NL, thank you for the suggestion. I'm able to ping the pi via DNS name so I think that is sorted out. Am I missing something?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version