> - is this Bug not in minidlna itself ? Why requires minidlna IP > address to be set (why do not allow to BIND to ANY address)?
I think this is because minidlna does not only listen on some interface & port number, it also needs to send out SSDP packets (multicast) on relevant network interfaces. So there's a requirement to determine network interfaces where minidlna is supposed to listen to for clients and send out broadcasts (on startup and in regular intervals) through those interfaces so UPnP clients in that network can auto-discover the minidlna server as soon as it comes up. As I understand it, there have been a few improvements in this area by the upstream minidlna developer. I haven't tested it because my network config from the POV of my minidlna serving machine is 100% static, but it sounds like minidlna is now supposed to support dynamic changes of network interfaces (including cases like no active network connection and new connections coming up at runtime). Some of the changes are in 1.1.2 (the minidlna version currently in trusty backports) and some of them are in 1.1.3 (released only 10 days ago, not in Ubuntu yet, probably expect it by 14.10 the earliest). Did anyone test to see if this bug is solved for them using the 1.1.2 version in Trusty backports? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053173 Title: minidlna crashes on boot when no active network connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/minidlna/+bug/1053173/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
