1 #################################################
2 # Sample OpenVPN 2.0 config file for #
3 # multi-client server. #
5 # This file is for the server side #
6 # of a many-clients <-> one-server #
7 # OpenVPN configuration. #
9 # OpenVPN also supports #
10 # single-machine <-> single-machine #
11 # configurations (See the Examples page #
12 # on the web site for more info). #
14 # This config should work on Windows #
15 # or Linux/BSD systems. Remember on #
16 # Windows to quote pathnames and use #
17 # double backslashes, e.g.: #
18 # "C:\\Program Files\\OpenVPN\\config\\foo.key" #
20 # Comments are preceded with '#' or ';' #
21 #################################################
23 # Which local IP address should OpenVPN
24 # listen on? (optional)
27 # Which TCP/UDP port should OpenVPN listen on?
28 # If you want to run multiple OpenVPN instances
29 # on the same machine, use a different port
30 # number for each one. You will need to
31 # open up this port on your firewall.
38 # "dev tun" will create a routed IP tunnel,
39 # "dev tap" will create an ethernet tunnel.
40 # Use "dev tap0" if you are ethernet bridging
41 # and have precreated a tap0 virtual interface
42 # and bridged it with your ethernet interface.
43 # If you want to control access policies
44 # over the VPN, you must create firewall
45 # rules for the the TUN/TAP interface.
46 # On non-Windows systems, you can give
47 # an explicit unit number, such as tun0.
48 # On Windows, use "dev-node" for this.
49 # On most systems, the VPN will not function
50 # unless you partially or fully disable
51 # the firewall for the TUN/TAP interface.
55 # Windows needs the TAP-Win32 adapter name
56 # from the Network Connections panel if you
57 # have more than one. On XP SP2 or higher,
58 # you may need to selectively disable the
59 # Windows firewall for the TAP adapter.
60 # Non-Windows systems usually don't need this.
63 # SSL/TLS root certificate (ca), certificate
64 # (cert), and private key (key). Each client
65 # and the server must have their own cert and
66 # key file. The server and all clients will
67 # use the same ca file.
69 # See the "easy-rsa" directory for a series
70 # of scripts for generating RSA certificates
71 # and private keys. Remember to use
72 # a unique Common Name for the server
73 # and each of the client certificates.
75 # Any X509 key management system can be used.
76 # OpenVPN can also use a PKCS #12 formatted key file
77 # (see "pkcs12" directive in man page).
80 key server.key # This file should be kept secret
82 # Diffie hellman parameters.
83 # Generate your own with:
84 # openssl dhparam -out dh1024.pem 1024
85 # Substitute 2048 for 1024 if you are using
90 # Should be subnet (addressing via IP)
91 # unless Windows clients v2.0.9 and lower have to
92 # be supported (then net30, i.e. a /30 per client)
93 # Defaults to net30 (not recommended)
96 # Configure server mode and supply a VPN subnet
97 # for OpenVPN to draw client addresses from.
98 # The server will take 10.8.0.1 for itself,
99 # the rest will be made available to clients.
100 # Each client will be able to reach the server
101 # on 10.8.0.1. Comment this line out if you are
102 # ethernet bridging. See the man page for more info.
103 server 10.8.0.0 255.255.255.0
105 # Maintain a record of client <-> virtual IP address
106 # associations in this file. If OpenVPN goes down or
107 # is restarted, reconnecting clients can be assigned
108 # the same virtual IP address from the pool that was
109 # previously assigned.
110 ifconfig-pool-persist ipp.txt
112 # Configure server mode for ethernet bridging.
113 # You must first use your OS's bridging capability
114 # to bridge the TAP interface with the ethernet
115 # NIC interface. Then you must manually set the
116 # IP/netmask on the bridge interface, here we
117 # assume 10.8.0.4/255.255.255.0. Finally we
118 # must set aside an IP range in this subnet
119 # (start=10.8.0.50 end=10.8.0.100) to allocate
120 # to connecting clients. Leave this line commented
121 # out unless you are ethernet bridging.
122 ;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
124 # Configure server mode for ethernet bridging
125 # using a DHCP-proxy, where clients talk
126 # to the OpenVPN server-side DHCP server
127 # to receive their IP address allocation
128 # and DNS server addresses. You must first use
129 # your OS's bridging capability to bridge the TAP
130 # interface with the ethernet NIC interface.
131 # Note: this mode only works on clients (such as
132 # Windows), where the client-side TAP adapter is
133 # bound to a DHCP client.
136 # Push routes to the client to allow it
137 # to reach other private subnets behind
138 # the server. Remember that these
139 # private subnets will also need
140 # to know to route the OpenVPN client
141 # address pool (10.8.0.0/255.255.255.0)
142 # back to the OpenVPN server.
143 ;push "route 192.168.10.0 255.255.255.0"
144 ;push "route 192.168.20.0 255.255.255.0"
146 # To assign specific IP addresses to specific
147 # clients or if a connecting client has a private
148 # subnet behind it that should also have VPN access,
149 # use the subdirectory "ccd" for client-specific
150 # configuration files (see man page for more info).
152 # EXAMPLE: Suppose the client
153 # having the certificate common name "Thelonious"
154 # also has a small subnet behind his connecting
155 # machine, such as 192.168.40.128/255.255.255.248.
156 # First, uncomment out these lines:
157 ;client-config-dir ccd
158 ;route 192.168.40.128 255.255.255.248
159 # Then create a file ccd/Thelonious with this line:
160 # iroute 192.168.40.128 255.255.255.248
161 # This will allow Thelonious' private subnet to
162 # access the VPN. This example will only work
163 # if you are routing, not bridging, i.e. you are
164 # using "dev tun" and "server" directives.
166 # EXAMPLE: Suppose you want to give
167 # Thelonious a fixed VPN IP address of 10.9.0.1.
168 # First uncomment out these lines:
169 ;client-config-dir ccd
170 ;route 10.9.0.0 255.255.255.252
171 # Then add this line to ccd/Thelonious:
172 # ifconfig-push 10.9.0.1 10.9.0.2
174 # Suppose that you want to enable different
175 # firewall access policies for different groups
176 # of clients. There are two methods:
177 # (1) Run multiple OpenVPN daemons, one for each
178 # group, and firewall the TUN/TAP interface
179 # for each group/daemon appropriately.
180 # (2) (Advanced) Create a script to dynamically
181 # modify the firewall in response to access
182 # from different clients. See man
183 # page for more info on learn-address script.
184 ;learn-address ./script
186 # If enabled, this directive will configure
187 # all clients to redirect their default
188 # network gateway through the VPN, causing
189 # all IP traffic such as web browsing and
190 # and DNS lookups to go through the VPN
191 # (The OpenVPN server machine may need to NAT
192 # or bridge the TUN/TAP interface to the internet
193 # in order for this to work properly).
194 ;push "redirect-gateway def1 bypass-dhcp"
196 # Certain Windows-specific network settings
197 # can be pushed to clients, such as DNS
198 # or WINS server addresses. CAVEAT:
199 # http://openvpn.net/faq.html#dhcpcaveats
200 # The addresses below refer to the public
201 # DNS servers provided by opendns.com.
202 ;push "dhcp-option DNS 208.67.222.222"
203 ;push "dhcp-option DNS 208.67.220.220"
205 # Uncomment this directive to allow different
206 # clients to be able to "see" each other.
207 # By default, clients will only see the server.
208 # To force clients to only see the server, you
209 # will also need to appropriately firewall the
210 # server's TUN/TAP interface.
213 # Uncomment this directive if multiple clients
214 # might connect with the same certificate/key
215 # files or common names. This is recommended
216 # only for testing purposes. For production use,
217 # each client should have its own certificate/key
220 # IF YOU HAVE NOT GENERATED INDIVIDUAL
221 # CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
222 # EACH HAVING ITS OWN UNIQUE "COMMON NAME",
223 # UNCOMMENT THIS LINE OUT.
226 # The keepalive directive causes ping-like
227 # messages to be sent back and forth over
228 # the link so that each side knows when
229 # the other side has gone down.
230 # Ping every 10 seconds, assume that remote
231 # peer is down if no ping received during
232 # a 120 second time period.
235 # For extra security beyond that provided
236 # by SSL/TLS, create an "HMAC firewall"
237 # to help block DoS attacks and UDP port flooding.
240 # openvpn --genkey --secret ta.key
242 # The server and each client must have
243 # a copy of this key.
244 # The second parameter should be '0'
245 # on the server and '1' on the clients.
246 ;tls-auth ta.key 0 # This file is secret
248 # Select a cryptographic cipher.
249 # This config item must be copied to
250 # the client config file as well.
251 ;cipher BF-CBC # Blowfish (default)
252 ;cipher AES-128-CBC # AES
253 ;cipher DES-EDE3-CBC # Triple-DES
255 # Enable compression on the VPN link.
256 # If you enable it here, you must also
257 # enable it in the client config file.
260 # The maximum number of concurrently connected
261 # clients we want to allow.
264 # It's a good idea to reduce the OpenVPN
265 # daemon's privileges after initialization.
267 # You can uncomment this out on
268 # non-Windows systems.
272 # The persist options will try to avoid
273 # accessing certain resources on restart
274 # that may no longer be accessible because
275 # of the privilege downgrade.
279 # Output a short status file showing
280 # current connections, truncated
281 # and rewritten every minute.
282 status openvpn-status.log
284 # By default, log messages will go to the syslog (or
285 # on Windows, if running as a service, they will go to
286 # the "\Program Files\OpenVPN\log" directory).
287 # Use log or log-append to override this default.
288 # "log" will truncate the log file on OpenVPN startup,
289 # while "log-append" will append to it. Use one
290 # or the other (but not both).
292 ;log-append openvpn.log
294 # Set the appropriate level of log
297 # 0 is silent, except for fatal errors
298 # 4 is reasonable for general usage
299 # 5 and 6 can help to debug connection problems
300 # 9 is extremely verbose
303 # Silence repeating messages. At most 20
304 # sequential messages of the same message
305 # category will be output to the log.