How to configure minidlna so it is visible on two networks?

[Bo Berglund]

On Thu, 26 May 2022 19:20:30 +0200, Bo Berglund <bo.berglund at gmail.com> wrote:

>I have two LAN sections (home and remote) joined together using OpenVPN on the
>remote router to a dedicated OpenVPN server on my home LAN.
>They run on addresses 192.168.119.x and 192.168.117.x respectively.
>
>The router on the home LAN is set up to route calls to 192.168.117.x via the
>OpenVPN server, so both LAN sections are effectively connected. I can connect to
>all devices from all devices.
>
>I also have an Ubuntu 20.04.4 server on the home LAN, which is running minidlna
>to act as a DLNA server for a video library on that server.
>When I use devices like a smart-TV or Windows computers on the home LAN they
>see the shared video library.
>
>But not so for devices on the remote LAN...
>
>Is there some configuration either on the minidlna config or elsewhere that
>could be made in order to let the remote LAN devices "see" the minidlna server?
>They are as you see on separate subnets, which are joined together via the VPN
>tunnel.

UPDATE
I realized that this is probably not possible...

So I have decided to go this way instead:

I built a small Linux box using a RaspberryPi4 and installed minidlna on it.
Then I mounted the media share on the Ubuntu Server via nfs on the RPi4.
And I created a dlna directory on the RPi into which I symlinked the media
directories on the server from the mount dir.

Basically I mirrored the minidlna config on the server for the remote LAN using
this RPi4 device. So it serves out from the local device but the data are
supplied via nfs from the main server.

Seems to work fine.


-- 
Bo Berglund
Developer in Sweden