2020-05-01, 07:05 PM
Dear NextPVR community,
Today I installed and configured the latest nextpvr/nextpvr_amd64 docker image. Unfortunately I already failed when adding a device. My local network (Subnet A) is connected to a remote network (Subnet B) via a VPN tunnel. The routes are set up correctly so that I can access devices in both the local and remote network from both sides. I can run a SAT>IP client on my mobile device in Subnet A where I enter the IP address of my SAT>IP tuner located in Subnet B and I can receive the video streams from the SAT>IP tuner. Of course, automatic detection of the SAT>IP tuner does not work across the subnet boundaries.
Unfortunately, NextPVR appears to scan only the local network. I failed in finding a function or config file position at NextPVR where I could manually specfy the IP address of my remote tuner, as I could do this in my SAT>IP client app.
Does anybody know how to cope with this situation? Your help is very much appreciated.
Best regards,
Peter
Today I installed and configured the latest nextpvr/nextpvr_amd64 docker image. Unfortunately I already failed when adding a device. My local network (Subnet A) is connected to a remote network (Subnet B) via a VPN tunnel. The routes are set up correctly so that I can access devices in both the local and remote network from both sides. I can run a SAT>IP client on my mobile device in Subnet A where I enter the IP address of my SAT>IP tuner located in Subnet B and I can receive the video streams from the SAT>IP tuner. Of course, automatic detection of the SAT>IP tuner does not work across the subnet boundaries.
Unfortunately, NextPVR appears to scan only the local network. I failed in finding a function or config file position at NextPVR where I could manually specfy the IP address of my remote tuner, as I could do this in my SAT>IP client app.
Does anybody know how to cope with this situation? Your help is very much appreciated.
Best regards,
Peter