DVBViewer over VPN (wireguard)

[fre_]

Hi,

 

I'm having an issue with DVBViewer over VPN (wireguard).

 

When I use my laptop on the same LAN as my DVBViewer Media Server 3.2.4.0, I can watch TV or listen to the radio, no problem.

When I use the same laptop over VPN (wireguard), I can see EPG data, but there is no video or audio in DVBViewer coming through.  (just a black screen).

When I'm on VPN, my laptop gets an IPadress in the range 10.10.10.0/24 and has no problem to access the PC where DVBmedia server is installed (access to networkshares works perfectly).

 

 

What i've checked so far:

 

- (windows settings server) network & internet > ethernet > private

 

- (windows firewall server) inbound rules:

DVBViewer Media Server:

Scope - remote IP address - Any IP address

 

- (windows firewall server) inbound rules: 

File and Printer Sharing (SMB-In) - profile Private:

Scope - remote IP address - 10.10.10.1-10.10.10.255

 

- Svcuserdata.xml (http://de.DVBViewer.tv/wiki/Svcuserdata.xml)

<section name="TrustedDevices">
     <entry name="TrustedIPs">10.10.10.1-10.10.10.255</entry>
     <entry name="LocalIPs">192.168.1.1-192.168.1.255</entry>
    </section>

 

 

 

Does anyone have an idea what I need to check more?

I'm sure it has worked some time ago, when I was still using openvpn instead of wireguard.

I don't know if it is relevant to mention that I use opnsense as router.

Portforwarding shouldn't be an issue here since I use VPN.

 

 

Any help is greatly appreciated.

 

 

[Griga]

How does DVBViewer receive video/audio from the server? Via Sat>IP / RTSP network devices? If you don't know how to answer this question, please attach a support.zip created on the client laptop.

 

If yes, you may want to update to the current DVBViewer and Media Server versions (7.3.2.0 and 3.3.2.0). Since 7.3.1.9 / 3.3.1.9 beta there are facilities that make it easier to let DVBViewer connect via Sat>IP to the Media Server under unfavourable conditions (particularly caused by firewalls), particularly the TCP interleaved transport mode for sending video/audio. Please read more about it here.

 

Usually Sat>IP conists of a bunch of different protocols. The client sends requests via an outbound TCP connection to the server and receives video/audio as separate UDP streams. Missing video/audio may be due to the video/audio streams being blocked by the firewall on your notebook, because it regards your VPN as public network and the UDP stream that is supposed to be received by DVBViewer as inbound and unsolicited (!), which is quite suspicious. The firewall doesn't recognise that it has been requested before via a TCP connection.

 

On the opposite, TCP interleaved is more like a single outbound HTTP connection initiated by the client, which presumably works through your VPN (e.g. opening the Media Server web interface in a browser), even if your VPN appears as public network. Video/audio is coming in through the same connection.

 

An alternative to Sat>IP is downloading a HTTP channel list as M3U file from the Media Server webinterface on the client notebook (see Links page) and importing it by drag & drop into the DVBViewer channel editor. However, this method entails some drawbacks, compared to Sat>IP, because it is working with static HTTP URLs instead of dynamic data requests. More about it on demand. But for just watching TV on your notebook it will be fine.

 

[fre_]

Thank you very much Griga for your prompt reply.

I got it working now after updating and using TCP instead of UDP.