Jump to content

OpenVPN Access Control: Difference between revisions

m
Topology and summary
m (Testing added)
m (Topology and summary)
Line 1: Line 1:
<h1>Introduction</h1>
<h1>Introduction</h1>


In this example, we will configure an OpenVPN server, will let Client1 and Client2 communicate, while isolating Client3 only to be able to communicate with OpenVPN server
Normally, OpenVPN Client access is controlled by enabling or disabling the Client to Client button in OpenVPN Servers configuration, however, at times, more granular control is required. In this example, we will configure an OpenVPN server with 3 Clients:
 
<ul>
<li> Client 1 will be able to communicate with Client 2 and OpenVPN server</li>
<li> Client 2 will be able to communicate with Client 1 and OpenVPN server</li>
<li> Client 3 will only be able to communicate with OpenVPN server, but not with any of other clients</li>
</ul>
 
<h1>Topology</h1>
 
[[File:OpenVPN Topology v1.png|none|thumb|alt=|1000x1000px]]
 
 
<ul>
<li> OpenVPN server tunnel address - 10.0.0.1, OpenVPN subnet - 10.0.0.0/27, LAN device address - 192.168.5.114</li>
<li> Client 1 VPN tunnel address - 10.0.0.6, LAN device address - 192.168.10.216</li>
<li> Client 2 VPN tunnel address - 10.0.0.10, LAN device address - 192.168.20.193</li>
<li> Client 3 VPN tunnel address - 10.0.0.14, LAN device address - 192.168.30.178</li>
</ul>


<h1>Generating certificates for an OpenVPN server</h1>
<h1>Generating certificates for an OpenVPN server</h1>
Line 205: Line 223:
<li>[[OpenVPN traffic split]]</li>
<li>[[OpenVPN traffic split]]</li>
<li>[[Configuration file .ovpn upload tutorial]]</li>
<li>[[Configuration file .ovpn upload tutorial]]</li>
<li>[[Firewall traffic rules]]</li>
</ul>
</ul>