SourceForge has been redesigned. Learn more.
Close

#13 Minidlna not working in routed setup

open
nobody
None
5
2014-07-15
2011-12-28
alphalt
No

Hello to all,

I'm new here and decided to find some help because I like minidlna very much, but have problem. I have my router set up as router, not as bridge so my LAN and WiFi are on different nets. I've set up PIM routing on my router and open all needed ports, but my LG-BD390 player can't see minidlna server. My network setup is as follows:

MiniDLNA server (192.168.0.0/24)<----LAN---->ROUTER<---WiFi--->LG BD390 (172.16.3.0/24)

So in that configuration, I can't use minidlna on LG player. Also I've tried to disable firewall (accept everything) on router, but no success. If I use ushare DLNA server in the same config then all works flawlessly. Also, if I install minidlna on notebook on WiFi then everything works ok as well. If I use option 'rescan server' on LG player then I get there debug messages from minidlna:

[2011/12/28 14:38:57] minissdp.c:677: debug: Ignoring SSDP M-SEARCH on other interface [172.16.3.104]
[2011/12/28 14:38:57] minissdp.c:677: debug: Ignoring SSDP M-SEARCH on other interface [172.16.3.104]
[2011/12/28 14:38:57] minissdp.c:677: debug: Ignoring SSDP M-SEARCH on other interface [172.16.3.104]

172.168.3.104 is a LG blu ray player. So maybe someone can help me to setup this configuration ?

Discussion

  • Craig Chambers

    Craig Chambers - 2012-01-06

    You can use a different server in the same configuration, so it sounds as though routing is not an issue. Have you configured the interfaces to listen on in minidlna.conf?

    /Craig

     
  • alphalt

    alphalt - 2012-01-06

    Yes, sure. Also I've added route like this:
    route add -net 239.0.0.0 netmask 255.0.0.0 eth0

    Nothing helps. My router has PIM routing enabled. By the way, address you see in the log (172.16.3.104) is DLNA player's wifi address.

     
  • alphalt

    alphalt - 2012-05-29

    Ok, I've found solution to a problem. And the problem was that original minissdp.c file didn't like receiving packets from other subnet, different to the one minidlna is bound to. So I've made changes to the program so that it will receive packets from different subnet, but only in the case if one ethernet interface is bound in /etc/minidlna.conf. So if you have routed setup, please bound minidlna only to one interface and apply the patch attached. If you will have more than one interface bound to minidlna then it will wait for packets on all interfaces, but will not accept packets from other subnets.
    One more problem I've found is that my LG BD-390 plaayer is recognized by server only on startup. Later, if I rescan servers with my LG BD-390 player I don't see minidlna anymore. The problem was too short pause between sending SSDPAnnounces. So I've made this pause longer and now there is no problems with my LG player. This fis is also included in the provided patch.

     
  • alphalt

    alphalt - 2012-05-29

    For minidlna version 1.0.24

     

Log in to post a comment.