× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

ReadyDLNA is simply not working on a ReadyNAS 312

ngyurov
Aspirant

ReadyDLNA is simply not working on a ReadyNAS 312

This thing is simply not working :evil:

Version:
root@ReadyNAS:~# minidlnad -V
Version 1.1.2


Starting:
root@ReadyNAS:~# /usr/sbin/minidlnad -S -v -f /etc/minidlna.conf.alt 
minidlna.c:1000: warn: Starting ReadyDLNA version 1.1.2.
inotify.c:156: debug: Add watch to /data/images
inotify.c:156: debug: Add watch to /data/music
inotify.c:156: debug: Add watch to /data/videos
minidlna.c:1039: warn: HTTP listening on port 8200
getifaddr.c:328: info: Enabling interface 10.7.7.3/255.255.255.240
Below is only info for added files.

Config file:
root@ReadyNAS:~# egrep -v ^'(#|$)' /etc/minidlna.conf.alt 
port=8200
network_interface=eth0
media_dir=P,/data/images
media_dir=A,/data/music
media_dir=V,/data/videos
friendly_name=ReadyNAS DLNA server
log_level=inotify=off
album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg/AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg/Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg
inotify=yes
enable_tivo=no
strict_dlna=no
notify_interval=900
serial=12345678
model_number=1


It looks like it's listening:
root@ReadyNAS:~# netstat -nap | grep minidlna
tcp 0 0 0.0.0.0:8200 0.0.0.0:* LISTEN 28083/minidlnad
udp 0 0 10.7.7.3:50002 0.0.0.0:* 28083/minidlnad
udp 0 0 0.0.0.0:1900 0.0.0.0:* 28083/minidlnad


However, the device is not discovered (using Samsung Galaxy Note 3 LTE version). The phone is perfectly fine - I have the exact same configuration (except for interface, friendly name and media dirs) on my notebook running Gentoo and minidlna 1.1.0 and it's discovered seconds after I start it. All devices are in the same subnet. Only difference is that the Gentoo is without systemd so minidlnad is started without -S.
Message 1 of 1
Top Contributors
Discussion stats
  • 0 replies
  • 1537 views
  • 0 kudos
  • 1 in conversation
Announcements