SageTV Community

SageTV Community (http://forums.sagetv.com/forums/index.php)
-   SageTV Placeshifter (http://forums.sagetv.com/forums/forumdisplay.php?f=39)
-   -   Placeshifter over VPN (http://forums.sagetv.com/forums/showthread.php?t=63921)

wayner 01-09-2017 12:44 PM

Placeshifter over VPN
 
I have OpenVPN running on my router. My LAN has an address range of 192.168.1.X. When I attach via VPN I get a range of 10.8.0.X.

I am connected with my laptop now and the VPN works fine. But when I run Placeshifter it is giving me a login as if I am a remote user. Should it be doing that? How does it now that I am not on the LAN? By the IP address?

EnterNoEscape 01-09-2017 02:34 PM

Quote:

Originally Posted by wayner (Post 598358)
I have OpenVPN running on my router. My LAN has an address range of 192.168.1.X. When I attach via VPN I get a range of 10.8.0.X.

I am connected with my laptop now and the VPN works fine. But when I run Placeshifter it is giving me a login as if I am a remote user. Should it be doing that? How does it now that I am not on the LAN? By the IP address?

It knows because the IP addresses are not on the same subnet.

wayner 01-09-2017 02:40 PM

What if I changed my VPN subnet to 192.168.0.X and mask to 255.255.254.0 and changed the mask on the SageTV server as well. Would they then be on the same subnet?

I guess it doesn't really matter, I was just wondering how it made that determination.

Fuzzy 01-09-2017 05:53 PM

Quote:

Originally Posted by wayner (Post 598378)
What if I changed my VPN subnet to 192.168.0.X and mask to 255.255.254.0 and changed the mask on the SageTV server as well. Would they then be on the same subnet?

I guess it doesn't really matter, I was just wondering how it made that determination.

This would prevent the routing from working correctly between the subnets, because the 192.168.0.x client would think it's on the same subnet as the 192.168.1.x server, so it would not even try to route through anything.

The only way to make a VPN truly on the same subnet is to have the VPN sit below the TCP/IP level. OpenVPN does this via a TAP interface instead of TUN. The easiest way to understand the different, is that TUN connects the two sides of the VPN tunnel through a virtual TCP/IP router. TAP connects the two sides of the VPN tunnel through a virtual ethernet switch. Both sides of the TAP tunnel would then reside on the same IP subnet (192.168.1.x).


All times are GMT -6. The time now is 02:18 AM.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.