Solved minidlna issue

zsolt

zsolt

Hi,

I discovered an issue with minidlna. After a couple of days of running, minidlna is starting to listen on all of my network interfaces and using multiple ports although I configured to listen on only the internal network interface.

I don't know what to do with it!

I am thinking to create a jail system and install minidlna in there. It is possible to set it up so that my devices to be able to access it on the internal network? Also, it is possible for minidlna to access my media outside jail? or do I have to move them in the jail? I never ever used jails before.
 
I have no idea about the problem you see with listening config of minidlna...

But I can tell you it works perfectly fine jailed. That was my configuration from the very beginning. I have minidlna in a VNET jail, its epair interface is bridged only into the one network I want minidlna to be available in.

As for how to access media to be shared: see nullfs(5). I'm using a read-only (there's no reason minidlna should ever write something) null-mount for the ZFS dataset containing my media files in the jail's fstab like this:
/mnt/shared /var/jail/media/jail/usr/local/share/netshares/shared nullfs ro 0 0
 
I have no idea about the problem you see with listening config of minidlna...
Click to expand...
If I start the service I got this:
Code: 
root@ryzen:~ # sockstat -4 -l
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS   
dlna     minidlnad  92332 6  udp4   *:1900                *:*
dlna     minidlnad  92332 7  tcp4   *:8200                *:*
dlna     minidlnad  92332 8  udp4   192.168.2.1:32860     *:*
After a couple of days I got this:
Code: 
root@ryzen:~ # sockstat -4 -l
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS   
dlna     minidlnad  92332 6  udp4   *:1900                *:*
dlna     minidlnad  92332 7  tcp4   *:8200                *:*
dlna     minidlnad  92332 8  udp4   192.168.2.1:32860     *:*
dlna     minidlnad  92332 16 tcp4   wan_address:6881     *:*
dlna     minidlnad  92332 18 udp4   wan_address:6881     *:*
dlna     minidlnad  89105 6  udp4   *:1900                *:*
dlna     minidlnad  89105 7  tcp4   *:8200                *:*
dlna     minidlnad  89105 8  udp4   192.168.2.1:32860     *:*
dlna     minidlnad  89105 16 tcp4   wan_address:6881     *:*
dlna     minidlnad  89105 18 udp4   wan_address:6881     *:*
It spreads like a virus... and interfere with my bittorrent client which listens on wan_address on 6881
 
I have a bridge0 with two local interfaces (wlan0 and em1). From what I read upstairs if I have minidlna to listen on such then will start to listen on every device because don't like virtual interfaces.
All right then. I set up to listen on only ath0 and will see later...
 
Above doesn't fix the issue so jail is the way to go! I started to read the documentation and I am stuck already. I have this in rc.conf:

Code: 
#ezjail
ezjail_enable="YES"
cloned_interfaces="lo1"

but lo1 is not created after restart nor if I type this:

Code: 
root@ryzen:~ # service netif cloneup
root@ryzen:~ # ifconfig lo1
ifconfig: interface lo1 does not exist

What am I doing wrong?
 
Sorry, I already had in my rc.conf an entry: cloned_interfaces="bridge0" so I added lo1 next to bridge0 and its ok now after a reboot.

Code: 
cloned_interfaces="bridge0 lo1"
 
You must log in or register to reply here.
Back
Top