Hi
I am trying to run minidlna (v1.2.1,1) on a FreeBSD 11.1-RELEASE system with a GENERIC kernel. I am not using jails.
The issue I am seeing is that clients do not see the server unless the server is restarted (or maybe a very high timeout is passed?). Once they "find" each other, everything seems to work properly.
My test client is VLC 2.2.8 on OS X.
I found several (very) similar reports on the web, most notably [1] where the explanation that the M-SEARCH messages are not received by MiniDNLA seems to be spot on.
Also, changing "notify_interval" in minidlna.conf (to 30 seconds for example) seems to have an effect (not tested with all clients). Still, the client does not connect "instantly" of course.
My question is: WHY are the messages not received by MiniDLNA?
I see the incoming UDP packets to 239.255.255.250 on port 1900 as well as IGMP packets (192.168.32.14 is my test client)
I am 99.9% sure that the firewall (ipfw) does allow the traffic.
I ran MiniDLNA with ssdp=debug and see that M-SEARCH messages on another interface are rejected (which makes sense). There is no message about M-SEARCH from "my" interface though. The main difference between the two interfaces as far as I can see is that the non-working one is a VLAN interface whereas the other one is not. But to the best of my understanding, VLAN or not should not matter here?
The closest to an indicator of a problem I could get seems to be the output of
The question however is if 239.255.255.250 should be here to make it work or if it would be listed here if SSDP was working properly...
I stumbled upon [2] and [3] which both list 239.255.255.250 in the output of
I am of course happy to provide more information to someone who might be able to help me debug this; I would just need to know what information.
Thanks!
[1] https://sourceforge.net/p/minidlna/bugs/94/#8c8f
[2] http://virtuallyhyper.com/2012/10/i...nnecting-to-it-with-xbmc-from-a-fedora-17-os/
[3] https://groups.google.com/forum/#!topic/mailing.freebsd.net/qDtZupt3yLg
I am trying to run minidlna (v1.2.1,1) on a FreeBSD 11.1-RELEASE system with a GENERIC kernel. I am not using jails.
The issue I am seeing is that clients do not see the server unless the server is restarted (or maybe a very high timeout is passed?). Once they "find" each other, everything seems to work properly.
My test client is VLC 2.2.8 on OS X.
I found several (very) similar reports on the web, most notably [1] where the explanation that the M-SEARCH messages are not received by MiniDNLA seems to be spot on.
Also, changing "notify_interval" in minidlna.conf (to 30 seconds for example) seems to have an effect (not tested with all clients). Still, the client does not connect "instantly" of course.
My question is: WHY are the messages not received by MiniDLNA?
I see the incoming UDP packets to 239.255.255.250 on port 1900 as well as IGMP packets (192.168.32.14 is my test client)
Code:
# tcpdump -n -i re1.32 not port 22 and not port 80 and not port 443
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on re1.32, link-type EN10MB (Ethernet), capture size 262144 bytes
23:12:42.655017 IP 192.168.32.14.49186 > 239.255.255.250.1900: UDP, length 127
23:12:42.756304 IP 192.168.32.14.49186 > 239.255.255.250.1900: UDP, length 127
23:12:43.251303 IP 192.168.32.14 > 224.0.0.22: igmp v3 report, 1 group record(s)
23:12:44.252514 IP 192.168.32.14 > 224.0.0.22: igmp v3 report, 1 group record(s)
I am 99.9% sure that the firewall (ipfw) does allow the traffic.
I ran MiniDLNA with ssdp=debug and see that M-SEARCH messages on another interface are rejected (which makes sense). There is no message about M-SEARCH from "my" interface though. The main difference between the two interfaces as far as I can see is that the non-working one is a VLAN interface whereas the other one is not. But to the best of my understanding, VLAN or not should not matter here?
The closest to an indicator of a problem I could get seems to be the output of
ifmcstat
that lacks (?) 239.255.255.250.
Code:
# ifmcstat -f inet -i re1.32
re1.32:
inet 192.168.32.1
igmpv3 rv 2 qi 125 qri 10 uri 3
group 224.0.0.1 mode exclude
mcast-macaddr 01:00:5e:00:00:01
The question however is if 239.255.255.250 should be here to make it work or if it would be listed here if SSDP was working properly...
I stumbled upon [2] and [3] which both list 239.255.255.250 in the output of
ifmcstat
.I am of course happy to provide more information to someone who might be able to help me debug this; I would just need to know what information.
Thanks!
[1] https://sourceforge.net/p/minidlna/bugs/94/#8c8f
[2] http://virtuallyhyper.com/2012/10/i...nnecting-to-it-with-xbmc-from-a-fedora-17-os/
[3] https://groups.google.com/forum/#!topic/mailing.freebsd.net/qDtZupt3yLg