Re: minidlna not working with minissdpd

2015-07-13 Thread LÉVAI Dániel
On h, júl 13, 2015 at 11:14:19 +0300, kasak wrote:
> Hello everyone! I'm in trouble with minidlna, installed from pkgs in OpenBSD
> 5.7
> I have installed miniupnpd, minidlna, and minissdpd from packages, added
> "minissdpd_flags=-i em1" in my /etc/rc.conf.local, next i uncommented
> 
> "minissdpdsocket=/var/run/minissdpd.sock" in files /etc/miniupnpd.conf and
> /etc/minidlna.conf
> 
> and started all daemons in next order:
> minissdpd - miniupnpd - minidlna and it seems that miniupnpd works and
> minidlna not :(
> 
> In other words, it is starting and i can open http://192.168.0.1:8200 but it
> does not appear on dlna clients
> 
> Otherwise, if I disable all minissdpd, miniupnpd and start minidlna alone,
> it works well! If I try to start only minissdpd and minidlna it doesn't
> work.

I have the same exact issue with the mini* trio.
My setup is a bit more "complicated", it involves three network
interfaces and a bridge. What is interesting however, is that it seems
this is somehow related to the bridge or one of the NIC's drivers,
because with bge(4) minissdpd+minidlna works, but with fxp(4)+bridge(4)
minissdpd+minidlna does not. The discoveries (multicast) are received
from upnp clients, and the advertisements get sent out from minissdpd
(run it with debug mode enabled, and you'll see), but somehow they get
lost between the software and the hardware.

Shame on me, because I didn't debug it further and reported it, but this
is an older OBSD 5.5, with an old hardware, and I thought I upgrade both
first, and try it out with different NICs and a -current OBSD.
However, seeing that someone else already feels the same pain, I thought
I'll just chime in...

> Here is some log when starting minidlna:
> [2015/07/12 23:51:16] minidlna.c:1026: warn: Starting MiniDLNA version
> 1.1.4.
> [2015/07/12 23:51:16] minissdp.c:114: error: bind(udp): Address already in
> use
> [2015/07/12 23:51:16] minidlna.c:1065: warn: HTTP listening on port 8200
> [2015/07/12 23:51:16] minissdp.c:80: error: setsockopt(udp,
> IP_ADD_MEMBERSHIP): Bad file descriptor
> [2015/07/12 23:51:16] minissdp.c:180: warn: Failed to add multicast
> membership for address 192.168.0.1
> 
> Maybe I'm doing something wrong? Or is it a bug?

The first error ("minissdpd.c:114: error: ...") is actually from minidlna,
and if minissdpd is already running, it just confirms that minissdpd
already binds to the required address, and minidlna should fall back to
the socket that is configured in minidlna.conf to communicate with
minissdpd.

Running minissdpd with the -d option, and minidlna with -d and -v tells
you more information during client discoveries and replies; maybe it
will be useful to post those to the list also (at least for just the
archives), and I'll try to do the same sometime.


Daniel

-- 
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D  650C C69B BE4C 83B6 3A8F



Re: minidlna not working with minissdpd

2015-07-16 Thread LÉVAI Dániel
On h, júl 13, 2015 at 14:22:06 +0200, LÉVAI Dániel wrote:
[...]
> (run it with debug mode enabled, and you'll see), but somehow they get
> lost between the software and the hardware.
Ehm, sorry for this BS.

The problem actually lies inside minidlna:
http://miniupnp.tuxfamily.org/forum/viewtopic.php?p=4413

sthen@, would you like for me to cook up a diff for the port to include
this tiny patch to fix it?


Daniel

-- 
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D  650C C69B BE4C 83B6 3A8F