Bridge two LANs (VPN)

[csholmq]

My router has a VPN server built in for easy computer-to-lan connecting. Would it be possible for e.g my brother (different house) to connect to my LAN and stream directly from my Serviio server?

I understand I could easily use MediaBrowser for this, but that would only cut it for him to stream to his laptop. I would like the Serviio server to appear on his Samsung TV. I thought of using VPN and maybe he could use his laptop as some form of relay?

[moltra]

Yes if you setup the vpn so the two computers can see each other. Look at the wiki and i think there is some info there on bridging

Sent from my DROID RAZR using Tapatalk 2

[csholmq]

Thanks. I'll try it out tomorrow. Let's hope multicasting likes bridging

[moltra]

I have bridged two routers in my house. Serviio did finger except for HD

Sent from my DROID RAZR using Tapatalk 2

[atc98092]

VPNing two separate networks is much more dfficult that using a single computer to VPN into another network. If both networks use the same IP address range, it will likely never work. For two separate networks to be visible across a VPN the address range must be different (i.e. they can't both be 192.168.0.x) and the routing tables for each router must know exactly how to reach each other. If the VPN is not part of your default gateway, each device needs the route to be added manually. This can't be done with most consumer video devices, such as TV and disc players.

If you simply want a single computer to VPN into another network and see the Serviio server, the only issue will be to not have matching IP address ranges at both ends. Other than that there should be no issue to view videos from the Serviio box on the computer.

[csholmq]

Why are separate subnetworks important?

I have a Broadcast Direction setting in my VPN server that I've set to "VPN Client to LAN". That way, all TV messages like "Hey, I'm a TV, I'm looking for a DLNA server" should go through. Then, Serviio will return with it's goods and all will be well.

Or, at least in theory

[atc98092]

Why are separate subnetworks important?

I have a Broadcast Direction setting in my VPN server that I've set to "VPN Client to LAN". That way, all TV messages like "Hey, I'm a TV, I'm looking for a DLNA server" should go through. Then, Serviio will return with it's goods and all will be well.

Or, at least in theory

I can't quote the precise technical reason, but two physically separate networks using the same IP address range will have all sorts of problems communicating. Mainly because device A (say your TV) will think device B (the Serviio box on the other network) is on the same physical network and can communicate directly between A and B without going through the VPN gateway. Since it thinks B is on the same local network, it won't send the packet to the VPN.

The other problem is there is a good chance that a device on network A will have the same IP address as a device on network B, and that just doesn't work.

[csholmq]

I've gotten the VPN to work properly, but the SSDP packets won't find their way unfortunately. I've turned on bi-directional broadcasting but when I fire up VLC the SSDP packets only seem to go to the broadcast server listed on my WiFi card rather than bounce through the VPN tunnel, even though all traffic goes there by default.

Here's my specs;
ASUS RT-N56U PPTP VPN server
Bi-directional broadcast enabled
LAN: 192.168.1.*
VPN: 192.168.10.*
Tunnel: 192.168.10.* -> 192.168.1.1

I'm able to ping the Serviio server (192.168.1.2) so the basic routing is there. Any tips?

[atc98092]

I've gotten the VPN to work properly, but the SSDP packets won't find their way unfortunately. I've turned on bi-directional broadcasting but when I fire up VLC the SSDP packets only seem to go to the broadcast server listed on my WiFi card rather than bounce through the VPN tunnel, even though all traffic goes there by default.

Here's my specs;
ASUS RT-N56U PPTP VPN server
Bi-directional broadcast enabled
LAN: 192.168.1.*
VPN: 192.168.10.*
Tunnel: 192.168.10.* -> 192.168.1.1

I'm able to ping the Serviio server (192.168.1.2) so the basic routing is there. Any tips?

I wish I understood routing better than I do, but I've kind of reached my limit of knowledge. I do have some network routing between multiple IP ranges, but I have no need (or desire) for broadcasts to reach the other subnets, so I've ignored that area. When you're self taught, sometimes some valuable areas of expertise are missed. It's possible that broadcasts are not routable outside your local network.

[moltra]

Look for a qos or dlna setting

Sent from my DROID RAZR using Tapatalk 2