Richard Falken  wrote:
>   Re: Re: Simplest 3G/4G connection for Pi, must work headless and stand-alo
>   By: Chris Green to druck on Mon Dec 28 2020 12:46 pm
>
>  > If a router 'supports VPN' what does that actually mean?
>  >
>  > Presumably it doesn't mean that the router runs as a VPN server, or
>  > does it?
>  >
>  > If my router supports VPN (which it does, a Draytek 2860N) and I
>  > enable it what else needs to happen to make it useful?  ... and what
>  > does my LAN behind the router look like, is it *all* on the VPN by
>  > default or what?  ... and how do I connect a remote system to the VPN?
>
> VPN capable routers are used mainly for enterprise /small businesses.
>
> The idea is that you have an office in Berlin with LAN A, and an office in
> Washington with LAN B. You configure your routers to establish a virtual
> private network between them so both LANS are merged (sort of).
>
> ie:
>
> LAN A has subnet 192.168.10.0/
>
> LAN B has 192.168.20.0/
>
> The router generated VPN makes it so a computer in LAN A can use a network
> printer with ip 192.168.20.5 in LAN B, access a file server which is not
> allowed traffic to the open internet at 192.168.20.11 (LAN B) etc as if both
> networks where directl??y connected, instead of separated by the whole
> Internet. In fact the connection between the two networks is encrypted and
thus
> deemed private.
>
> This is the most common scenario that you find documented for VPN enabled
> routers, followed by the road-warrior setup (you use VPN in order to allow a
> laptop using an insecure LAN connect to your office in Berlin and access
> resources in LAN A as if the laptop was in Berlin's office).
>
Thanks for that beautifully clear explanation, it's this sort of thing
that is *far* from obvious when you look at how tos for VPNs.

I guess it's the 'road-warrior setup' is nearest to what I want to do
though in reality the 'insecure LAN' involved is just one computer.

--
Chris Green
·

--- SoupGate-Win32 v1.05