Configurar OpenVPN en Debian Server
Supongamos varios escenarios….
- Queremos conectarnos a la LAN de casa.
- Dar acceso a usuarios a a la red de la empresa.
- Proporcinar una lan para juegos online.
Para estos y muchos mas casos se utiliza openvpn.
Si lo configuramos para acceder a la red de casa debemos hacer port-fowaring del puerto UDP 1194 desde nuestro router a la maquina dedicada a ofrecer el servicio de vpn.
OpenVPN es una excelente solución de código abierto. Toda la documentación que podáis necesitar la encontrareis aqui.
OpenVPN tambien tiene servicios de pago, pero nosotros usaremos la «community edition», que como ya he dicho antes es de libre uso.
Una vez configurado el servidor VPN tendrá una ip del tipo 10.8.0.1
y los clientes conectados (portatiles, estaciones o moviles con android) se les asignará IP del tipo . 10.8.0.x
.
Si una vez realizado todo el proceso de configuración puedes hacer un ping desde el cliente a la 10.8.0.1, todo esta bien y el servicio esta funcionando.
Pasos:
1) Instalar el paquete OpenVPN en nuestro servidor.
Usando apt-get
1
|
apt-get install openvpn |
2) Creamos el certificado del lado del servidor (RSA keys)
Como usuario root:
1
2
|
mkdir /etc/openvpn/easy-rsa/ cp -R /usr/share/doc/openvpn/examples/easy-rsa/2 .0/* /etc/openvpn/easy-rsa/ |
entonces…
1
|
nano /etc/openvpn/easy-rsa/vars |
Definiremos los datos que contendrá el certificado en la parte del servidor:
1
2
3
4
5
|
export KEY_COUNTRY="ES" export KEY_PROVINCE="GR" export KEY_CITY="Granada" export KEY_ORG="GST" export KEY_EMAIL="you@alejandrosenes.com" |
en otro paso:
1
2
3
4
5
6
7
8
9
10
11
|
cd /etc/openvpn/easy-rsa/ chown -R root:root . chmod g+w . source . /vars . /clean-all . /build-dh . /pkitool --initca . /pkitool --server server cd keys openvpn --genkey --secret ta.key cp server.crt server.key ca.crt dh1024.pem ta.key ../../ |
Los certificados han sido generados en la ruta:
1
|
/etc/openvpn/easy-rsa/keys/ |
Tendremos que proporcinar el certificado ubicado en /etc/openvpn/easy-rsa/keys/ca.crt a cada usuario para asegurar el acceso.
El archivo de configuración del servicio en el lado del Servidor
1
|
nano /etc/openvpn/server .conf |
Deberá tener el siguiente aspecto:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
|
################################################# # Sample OpenVPN 2.0 config file for # # multi-client server. # # # # This file is for the server side # # of a many-clients <-> one-server # # OpenVPN configuration. # # # # OpenVPN also supports # # single-machine <-> single-machine # # configurations (See the Examples page # # on the web site for more info). # # # # This config should work on Windows # # or Linux/BSD systems. Remember on # # Windows to quote pathnames and use # # double backslashes, e.g.: # # "C:\\Program Files\\OpenVPN\\config\\foo.key" # # # # Comments are preceded with '#' or ';' # ################################################# # Which local IP address should OpenVPN # listen on? (optional) ; local a.b.c.d # Which TCP/UDP port should OpenVPN listen on? # If you want to run multiple OpenVPN instances # on the same machine, use a different port # number for each one. You will need to # open up this port on your firewall. port 1194 # TCP or UDP server? ;proto tcp proto udp # "dev tun" will create a routed IP tunnel, # "dev tap" will create an ethernet tunnel. # Use "dev tap0" if you are ethernet bridging # and have precreated a tap0 virtual interface # and bridged it with your ethernet interface. # If you want to control access policies # over the VPN, you must create firewall # rules for the the TUN/TAP interface. # On non-Windows systems, you can give # an explicit unit number, such as tun0. # On Windows, use "dev-node" for this. # On most systems, the VPN will not function # unless you partially or fully disable # the firewall for the TUN/TAP interface. ;dev tap dev tun # Windows needs the TAP-Win32 adapter name # from the Network Connections panel if you # have more than one. On XP SP2 or higher, # you may need to selectively disable the # Windows firewall for the TAP adapter. # Non-Windows systems usually don't need this. ;dev-node MyTap # SSL/TLS root certificate (ca), certificate # (cert), and private key (key). Each client # and the server must have their own cert and # key file. The server and all clients will # use the same ca file. # # See the "easy-rsa" directory for a series # of scripts for generating RSA certificates # and private keys. Remember to use # a unique Common Name for the server # and each of the client certificates. # # Any X509 key management system can be used. # OpenVPN can also use a PKCS #12 formatted key file # (see "pkcs12" directive in man page). ca ca.crt cert server.crt key server.key # This file should be kept secret # Diffie hellman parameters. # Generate your own with: # openssl dhparam -out dh1024.pem 1024 # Substitute 2048 for 1024 if you are using # 2048 bit keys. dh dh1024.pem # Configure server mode and supply a VPN subnet # for OpenVPN to draw client addresses from. # The server will take 10.8.0.1 for itself, # the rest will be made available to clients. # Each client will be able to reach the server # on 10.8.0.1. Comment this line out if you are # ethernet bridging. See the man page for more info. server 10.8.0.0 255.255.255.0 # Maintain a record of client <-> virtual IP address # associations in this file. If OpenVPN goes down or # is restarted, reconnecting clients can be assigned # the same virtual IP address from the pool that was # previously assigned. ifconfig -pool-persist ipp.txt # Configure server mode for ethernet bridging. # You must first use your OS's bridging capability # to bridge the TAP interface with the ethernet # NIC interface. Then you must manually set the # IP/netmask on the bridge interface, here we # assume 10.8.0.4/255.255.255.0. Finally we # must set aside an IP range in this subnet # (start=10.8.0.50 end=10.8.0.100) to allocate # to connecting clients. Leave this line commented # out unless you are ethernet bridging. ;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100 # Configure server mode for ethernet bridging # using a DHCP-proxy, where clients talk # to the OpenVPN server-side DHCP server # to receive their IP address allocation # and DNS server addresses. You must first use # your OS's bridging capability to bridge the TAP # interface with the ethernet NIC interface. # Note: this mode only works on clients (such as # Windows), where the client-side TAP adapter is # bound to a DHCP client. ;server-bridge # Push routes to the client to allow it # to reach other private subnets behind # the server. Remember that these # private subnets will also need # to know to route the OpenVPN client # address pool (10.8.0.0/255.255.255.0) # back to the OpenVPN server. ;push "route 192.168.10.0 255.255.255.0" ;push "route 192.168.20.0 255.255.255.0" # To assign specific IP addresses to specific # clients or if a connecting client has a private # subnet behind it that should also have VPN access, # use the subdirectory "ccd" for client-specific # configuration files (see man page for more info). # EXAMPLE: Suppose the client # having the certificate common name "Thelonious" # also has a small subnet behind his connecting # machine, such as 192.168.40.128/255.255.255.248. # First, uncomment out these lines: ;client-config- dir ccd ;route 192.168.40.128 255.255.255.248 # Then create a file ccd/Thelonious with this line: # iroute 192.168.40.128 255.255.255.248 # This will allow Thelonious' private subnet to # access the VPN. This example will only work # if you are routing, not bridging, i.e. you are # using "dev tun" and "server" directives. # EXAMPLE: Suppose you want to give # Thelonious a fixed VPN IP address of 10.9.0.1. # First uncomment out these lines: ;client-config- dir ccd ;route 10.9.0.0 255.255.255.252 # Then add this line to ccd/Thelonious: # ifconfig-push 10.9.0.1 10.9.0.2 # Suppose that you want to enable different # firewall access policies for different groups # of clients. There are two methods: # (1) Run multiple OpenVPN daemons, one for each # group, and firewall the TUN/TAP interface # for each group/daemon appropriately. # (2) (Advanced) Create a script to dynamically # modify the firewall in response to access # from different clients. See man # page for more info on learn-address script. ;learn-address . /script # If enabled, this directive will configure # all clients to redirect their default # network gateway through the VPN, causing # all IP traffic such as web browsing and # and DNS lookups to go through the VPN # (The OpenVPN server machine may need to NAT # or bridge the TUN/TAP interface to the internet # in order for this to work properly). ;push "redirect-gateway def1 bypass-dhcp" # Certain Windows-specific network settings # can be pushed to clients, such as DNS # or WINS server addresses. CAVEAT: # http://openvpn.net/faq.html#dhcpcaveats # The addresses below refer to the public # DNS servers provided by opendns.com. ;push "dhcp-option DNS 208.67.222.222" ;push "dhcp-option DNS 208.67.220.220" # Uncomment this directive to allow different # clients to be able to "see" each other. # By default, clients will only see the server. # To force clients to only see the server, you # will also need to appropriately firewall the # server's TUN/TAP interface. ;client-to-client # Uncomment this directive if multiple clients # might connect with the same certificate/key # files or common names. This is recommended # only for testing purposes. For production use, # each client should have its own certificate/key # pair. # # IF YOU HAVE NOT GENERATED INDIVIDUAL # CERTIFICATE/KEY PAIRS FOR EACH CLIENT, # EACH HAVING ITS OWN UNIQUE "COMMON NAME", # UNCOMMENT THIS LINE OUT. ;duplicate-cn # The keepalive directive causes ping-like # messages to be sent back and forth over # the link so that each side knows when # the other side has gone down. # Ping every 10 seconds, assume that remote # peer is down if no ping received during # a 120 second time period. keepalive 10 120 # For extra security beyond that provided # by SSL/TLS, create an "HMAC firewall" # to help block DoS attacks and UDP port flooding. # # Generate with: # openvpn --genkey --secret ta.key # # The server and each client must have # a copy of this key. # The second parameter should be '0' # on the server and '1' on the clients. ;tls-auth ta.key 0 # This file is secret # Select a cryptographic cipher. # This config item must be copied to # the client config file as well. ;cipher BF-CBC # Blowfish (default) ;cipher AES-128-CBC # AES ;cipher DES-EDE3-CBC # Triple-DES # Enable compression on the VPN link. # If you enable it here, you must also # enable it in the client config file. comp-lzo # The maximum number of concurrently connected # clients we want to allow. ;max-clients 100 # It's a good idea to reduce the OpenVPN # daemon's privileges after initialization. # # You can uncomment this out on # non-Windows systems. ;user nobody ;group nogroup # The persist options will try to avoid # accessing certain resources on restart # that may no longer be accessible because # of the privilege downgrade. persist-key persist-tun # Output a short status file showing # current connections, truncated # and rewritten every minute. status openvpn-status.log # By default, log messages will go to the syslog (or # on Windows, if running as a service, they will go to # the "\Program Files\OpenVPN\log" directory). # Use log or log-append to override this default. # "log" will truncate the log file on OpenVPN startup, # while "log-append" will append to it. Use one # or the other (but not both). ;log openvpn.log ;log-append openvpn.log # Set the appropriate level of log # file verbosity. # # 0 is silent, except for fatal errors # 4 is reasonable for general usage # 5 and 6 can help to debug connection problems # 9 is extremely verbose verb 3 # Silence repeating messages. At most 20 # sequential messages of the same message # category will be output to the log. ;mute 20 |
Si queremos tener acceso a la red interna de nuestra casa
Imaginemos que la red interna de casa tiene configurado el rango de direcciones 192.168.1.xAl cliente debemos decirle que haga un push route add a la red interna de nuestra red de casa, para que la tabla de direcciones de nuestro cliente se actualice y los paquetes sepan que camino tienen que llevar.
136
|
push "route 192.168.1.0 255.255.255.0" |
Si queremos tener acceso a la red interna de nuestra casa
Si queremos tener acceso con el mismo certificado simultaneamente en con dos dispositivos o queremos que los clientes comparan el certificado tenemos descomentar la linea 217
217
|
duplicate-cn |
server.conf
El archivo de configuración sin comentarios queda de la siguiente manera:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|
port 1194 proto udp dev tun ca ca.crt cert server.crt key server.key # This file should be kept secret dh dh1024.pem server 10.8.0.0 255.255.255.0 ifconfig -pool-persist ipp.txt keepalive 10 120 comp-lzo persist-key persist-tun status openvpn-status.log verb 3 |
A probar!
Iniciamos el servicio en nuestro debian,
1
|
service openvpn start |
Podemos ver que tenemos una nueva tarjeta de red tun0
interface,
en un terminal usando ifconfig
1
2
3
4
5
6
7
8
|
... tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:71163 errors:0 dropped:0 overruns:0 frame:0 TX packets:86759 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:15156918 (14.4 MiB) TX bytes:55682217 (53.1 MiB) |
Also, try to ping server
1
|
ping 10.8.0.1 |
Creando usuarios:
Creando al usuario user1
1
2
3
|
cd /etc/openvpn/easy-rsa/ source . /vars . /pkitool --pass user1 |
Podemos encontrarno al generar un segundo usuario que pkitool nos muestra el error
«failed to update database TXT_DB error number 2»
Es debido a que el Certificado del ciente tiene que tener un único identificador de CN
1
|
KEY_CN=idUnicaparaelCliente ./pkitool client2
|
El certificado del cliente lo encontraremos en:
1
|
/etc/openvpn/easy-rsa/keys/ |
ATENCION: Debemos proporcionar a los usuarios los archivos user1.crt and user1.key para que la conexión se haga posible.
Borrando usuarios
Para dar de baja al usuario user1:
1
2
3
|
rm /etc/openvpn/easy-rsa/keys/user1 .crt rm /etc/openvpn/easy-rsa/keys/user1 .key rm /etc/openvpn/easy-rsa/keys/user1 .csr |
Borrar la linea refenrente a «user1» de index.txt (Es un índice de los usuarios)
1
|
nano /etc/openvpn/easy-rsa/keys/index .txt |
Asignar una IP estática a los usuarios
Para el servicio OpenVPN
1
|
service openvpn stop |
Edota ipp.txt
1
|
nano /etc/openvpn/ipp .txt |
Asigna las diferentes IPs a los usuarios:
1
2
3
4
|
user1,10.8.0.10 user2,10.8.0.11 user3,10.8.0.12 ... |
Inicia el servicio OpenVpn
Ojo al dato y para evitar problemas
Tanto cliente como servidor se deben encontrar en la misma zona horaria y sincronizados con un servidor NTP.
1
|
apt-get install ntp |
Configuración en el lado del Cliente
Podéis usar el cliente oficial de OpenVPN pero yo recomiendo el uso en Windows del cliente de OpenVPN portable, ya que nos da la versatilidad de poder llevarlo en un pendrive o guardarlo en una drive en la nube y conectarnos la red de casa desde cualquier lugar.
Lo primero que necesitamos es tener las llaves cliente que hemos generado con anterioridad (en nuestro caso para user1=
- El certificado del servidor:
ca.crt
(Explicado adrriba: Creando el certificado del servidor) - El certificado del cliente
user1.crt
yuser1.key
que obtuvimos al crear nuestro cliente
Crea un fichero de texto con nombre client.ovpn como sigue:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
|
############################################## # Sample client-side OpenVPN 2.0 config file # # for connecting to multi-client server. # # # # This configuration can be used by multiple # # clients, however each client should have # # its own cert and key files. # # # # On Windows, you might want to rename this # # file so it has a .ovpn extension # ############################################## # Specify that we are a client and that we # will be pulling certain config file directives # from the server. client # Use the same setting as you are using on # the server. # On most systems, the VPN will not function # unless you partially or fully disable # the firewall for the TUN/TAP interface. ;dev tap dev tun # Windows needs the TAP-Win32 adapter name # from the Network Connections panel # if you have more than one. On XP SP2, # you may need to disable the firewall # for the TAP adapter. ;dev-node MyTap ;dev-node OpenVPN # Are we connecting to a TCP or # UDP server? Use the same setting as # on the server. ;proto tcp proto udp # The hostname/IP and port of the server. # You can have multiple remote entries # to load balance between the servers. ;remote my-server-2 1194 remote SERVER_IP or ADDRESS 1194 // AQUI PONED LA IP/NOMBRE DEL HOST DE VUESTRO SERVER # Choose a random host from the remote # list for load-balancing. Otherwise # try hosts in the order specified. ;remote-random # Keep trying indefinitely to resolve the # host name of the OpenVPN server. Very useful # on machines which are not permanently connected # to the internet such as laptops. resolv-retry infinite # Most clients don't need to bind to # a specific local port number. nobind # Downgrade privileges after initialization (non-Windows only) ;user nobody ;group nobody # Try to preserve some state across restarts. persist-key persist-tun # If you are connecting through an # HTTP proxy to reach the actual OpenVPN # server, put the proxy server/IP and # port number here. See the man page # if your proxy server requires # authentication. ;http-proxy-retry # retry on connection failures ;http-proxy [proxy server] [proxy port #] # Wireless networks often produce a lot # of duplicate packets. Set this flag # to silence duplicate packet warnings. ;mute-replay-warnings # SSL/TLS parms. # See the server config file for more # description. It's best to use # a separate .crt/.key file pair # for each client. A single ca # file can be used for all clients. ca ca.crt cert user1.crt key user1.key # This file should be kept secret # Verify server certificate by checking # that the certicate has the nsCertType # field set to "server". This is an # important precaution to protect against # a potential attack discussed here: # # To use this feature, you will need to generate # your server certificates with the nsCertType # field set to "server". The build-key-server # script in the easy-rsa folder will do this. ;ns-cert- type server # If a tls-auth key is used on the server # then every client must also have the key. ;tls-auth ta.key 1 # Select a cryptographic cipher. # If the cipher option is used on the server # then you must also specify it here. ;cipher x # Enable compression on the VPN link. # Don't enable this unless it is also # enabled in the server config file. comp-lzo # Set log file verbosity. verb 3 # Silence repeating messages ;mute 20 # WINDOWS 7: Cannot ping server without these statements # WINDOWS XP: not needed #route-method exe #route-delay 2 |
Resumiendo y sin comentarios
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
|
client dev tun proto udp remote SERVER_IP or ADDRESS 1194 resolv-retry infinite nobind persist-key persist-tun ca ca.crt cert user1.crt key user1.key # This file should be kept secret comp-lzo verb 3 |
CONECTANDO CON NUESTRO SERVIDOR
OpenVPN portable. Funciona en arquitecturas de 32bit y 64bit. copia el fichero y los certificados generados en la carpeta /data/config . Run OpenVPNPortable.exe to connect (OJO DEBE SER EJECUTADO COMO ADMINISTRADOR, o en Windows7 y 8 Ejecutar como Administrador).