Differences

This shows you the differences between two versions of the page.

--- userdoc:tt_openvpn_client_networks [2013/03/15 20:37] – abelbeck
+++ userdoc:tt_openvpn_client_networks [2013/03/16 03:45] (current) – abelbeck
@@ Line 9: / Line 9: @@
 The best way to describe this configuration is by an example:
-===== Assumptions =====
+===== Example Assumptions =====
 For this example, the Server Network IPv4 NetMask is ''10.8.1.0 255.255.255.0''
@@ Line 17: / Line 17: @@
 Let us assume the client has a local network of 192.168.222.1/24 that we want the server endpoint to access.
-!!Tip ->!! While it should not matter in general, if all your clients support a Topology of subnet, specify that.
+!!Tip ->!! While it should not matter in general, if all your clients support a Topology of subnet, it is suggested to specify that.
 {{:userdoc:openvpn-client-net-topology.jpg?nolink|}}
@@ Line 28: / Line 28: @@
-!!Note ->!! It is important to specify the ''route-gateway'' to the first (''.1'') address of your server IPv4 network. Recent versions of OpenVPN (AstLinux 1.1.1 and later) use the ''ip'' system command to apply network settings, rather than the older ''ifconfig'' system command, which has the side effect of requiring the ''route-gateway'' to be specified.
+!!Note ->!! If you are using Topology "subnet" it is important to specify the ''route-gateway'' to the first (''.1'') address of your server IPv4 network. If you are not using Topology "subnet", defining ''route-gateway'' is not necessary and it will create the route properly by default.
 ===== OpenVPN CCD File Configuration =====
@@ Line 51: / Line 51: @@
 !!Tip ->!! If a ccd file of ''DEFAULT'' exists, all non-matching CommonName clients will use it's file contents, though not required.
-Finally, after all the above steps are completed substituting your network values, restart the OpenVPN Server, the proper routes should be in place when the OpenVPN client connects.  If you still can't reach the client endpoint's network, read the next section on configuring the firewall at the client.
+Finally, after all the above steps are completed substituting your network values, restart the OpenVPN Server, the proper routes should be in place when the OpenVPN client connects.  If you still can't reach the client endpoint's network, read the next section on configuring the firewall at the client endpoint.
@@ Line 64: / Line 64: @@
 {{:userdoc:openvpn-client-net-firewall.jpg?nolink|}}
-In this example, at the client endpoint, the 1st LAN Interface has a 192.168.222.1/24 network defined.
+In this example, at the client endpoint, the "1st LAN Interface" has a 192.168.222.1/24 network defined.