2018-04-05 2:03 GMT+03:00 Mick <michaelkintz...@gmail.com>: > On Wednesday, 4 April 2018 23:02:20 BST Grant Taylor wrote: >> On 04/04/2018 02:18 PM, gevisz wrote: >> > A friend of mine asked me to recommend him an open-source VPN-server >> > for Linux but unfortunately I never used one. >> >> That's a loaded ask. >> >> > After some googling, I have found OpenVPN but do not know if it is the >> > best choice that suits his purposes, namely to access local network that >> > does not have its own fixed IP from the outside. >> >> Okay.... > > This may be solvable, if the public facing gateway can be configured to > forward the requisite ports/protocols to the LAN where the host is located.
If you mean port forfarding from OR to IR and then to the Host, it is impossible because we have no control over OR. >> > To be more precise: the local network to be accessed to from the outside >> > is part of another local network. The latter (outer) network has its >> > own fixed IP but the former (inner) network gets its IP via DHCP. So, >> > it is impossible to connect to a computer in the inner network from the >> > outside directly. >> >> Is this toplolgy accurate? >> >> (Client)---(Internet)---(OR)---(IR)---(Host) > > The OR can port forward the incoming VPN connection to the IR. The IR can > then act as a VPN gateway for the inner LAN. No, port forwarding from the OR to the IR is impossible. >> I'm guessing that your friend (client) wants to access something (host) >> on the inner network. But to do so requires passing through the >> Internet through Outer Router (with a static IP on the outside (left)) >> and through the Inner Router (which has a dynamic IP on the outside >> (left) obtained via DHCP)). Is that correct? >> >> What sort of control does your friend have on the OR & IR? >> >> Is NAT in use on either OR or IR? >> >> What sort of >> >> > The computer in local network to be connected runs Windows. The said >> > friend of mine have tried to run some VPN server from Windows but it >> > somehow hangs the "inner" computer when his "outer" computer has problems >> > connecting to the Internet. >> >> Are you saying that the Host in the diagram above is running Windows? >> Or are you referring to a different system? >> >> > So, now his idea is >> > 1) to run a virtual machine in the "inner" (Windows) computer, >> > 2) to install into this virtual machine very lightweight Linux server >> > only to run in it a VPN-server that should help him to connect from the >> > outside to the "inner" host (Windows) computer, which has its fixed IP >> > within the inner local network. >> >> The VM may or may not be needed. >> >> Assuming that NAT is in play on OR and IR (worst case), then just about >> /any/ form of VPN initiating from the outside will be fraught with >> uphill battles. >> >> It is likely possible that your friend can reconfigure both OR and IR to >> forward a port from the Internet to Host. But that will likely mean >> that IR will need to have a static IP on it's outside interface. - I'm >> guessing this can't be done or that it would have already been done. >> >> I think that your friend's best bet is to have the IR initiate an >> outbound VPN to something on the Internet that the Client can then >> initate connections to. (I'm happily using a $5/month Linode VPS to do >> this.) >> >> There may be ways to make this work without having the Host initiate >> outbound connections, but I'm not sure what they would be. >> >> As for which VPN, a number of people like OpenVPN. I personally prefer >> OpenSSH's ability to do a routed (L3) (or bridged L2) VPN. (I've got >> SSH exposed already, so it's one less port to expose.) I see a number >> of people bragging about WireGuard. Of course there are the old PPTP / >> L2TP / IPSec, though I would avoid them for this install. I'm sure >> there are a number of other VPN technologies that I'm not thinking of. > > PPTP has been insecure for years and best be avoided. > > L2TP within IPSec is OK, but check what crypto the MSWindows uses. Last time > I looked Win7 was not strong enough. > > IKEv2 + IPSec with strong crypto for both, is my personal preference for > gateway-to-gateway VPNs. > > MSWindows also has SSTP (because MSoft had to create their own clone of > OpenVPN). I think there's a Linux VPN client which will work with that: > > net-misc/sstp-client > > but have never tried it. > > Of course, if the above network topology suggested by Grant is correct, then > you will likely be limited by whatever VPN software comes with IR. > > In all cases, make sure you use TLS RSA/SHA2 certificates for both client and > VPN gateway authentication. > > Finally, check out Wireguard. It was designed from the ground up to overcome > the complexity of previous VPN solutions. I have not tried it out yet, but > will be next time I have to set up a VPN tunnel with a non-legacy router. Thank you. I will just forward these your adviced to the friend.
