665
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 62:
Line 62: + + + + + + + + + + + + +
→Configuration
On the next page, we have to enter the same key we've used on SME1
On the next page, we have to enter the same key we've used on SME1
Here are the explanation of some settings:
* '''Daemon ID''': just a unique identifier for this connection.
* '''Description''': a human readable description (eg link between SME1 and SME2)
* '''Status''': you can disable a VPN connection if you want, but most of the time you'll want it enabled
* '''Authentication mechanism''': How both ends will authenticate. The easier solution is the Shared Key. You can also use TLS if you want, but it's usually for power users (you need to manage a PKI, you can use [[PHPki]] for this if you want)
* '''Remote Host''' (available on client only): IP or FQDN to the remote peer
* '''Remote Port''' (available on client only): port used by the remote server
* '''Local Port''' (available on server only): port on which the openvpn server will bind, waiting for connection of the remote peer. Remote Port on the client and Local Port on the server should be the same
* '''Local Virtual IP''': the IP used internally by OpenVPN. You should choose a IP outside of any local networks
* '''Remote Virtual IP''': the IP used internally by OpenVPN on the other side. Those two virtual IP should be reversed between the client and the server
{{Note box|You don't really need to remember the virtual IP, as once the connection is established, you'll use the internal IP to access the remote server through the VPN. You just need to choose two IP address which won't clash with any other local networks, then, just forget about it}}
* '''Remote Networks''': Enter in this field the networks reachable through the other end point. For example, on SME1, you'll enter the local networks of SME2: 192.168.11.0/255.255.255.0, on SME2, you'll enter the local network of SME1: 192.168.9.0/255.255.255.0
=== Features ===
=== Features ===
