Differences

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

--- informatica:linux:vpn:pptp [2012/05/09 14:38] – javi
+++ informatica:linux:vpn:pptp [2015/04/13 20:19] (current) – external edit 127.0.0.1
@@ Line 3: / Line 3: @@
 http://www.howtogeek.com/51237/setting-up-a-vpn-pptp-server-on-debian/
-===== Instalar y configurar el servidor =====
-Server Setup
-Install the pptp server package:
-    sudo aptitude install pptpd
+===== Instalar y configurar el servidor =====
-Edit the “/etc/pptpd.conf” configuration file:
+. Install the pptp server package:
-    sudo vim /etc/pptpd.conf
+  sudo aptitude install pptpd
-Add to it:
+. Edit the "/etc/pptpd.conf" configuration file:
-    localip 192.168.1.5
+  sudo vim /etc/pptpd.conf
-    remoteip 192.168.1.234-238,192.168.1.245
+Add to it:
-Where the “localip” is the address of the server, and the remoteip are the addresses that will be handed out to the clients, it is up to you to adjust these for your network’s requirements.
+  localip 192.168.1.5
+  remoteip 192.168.1.234-238,192.168.1.245
+  debug
-Edit the “/etc/ppp/pptpd-options” configuration file:
+Where the "localip" is the address of the server, and the remoteip are the addresses that will be handed out to the clients, it is up to you to adjust these for your network's requirements.
-    sudo vim /etc/ppp/pptpd-options
+. Edit the "/etc/ppp/pptpd-options" configuration file:
+  sudo vim /etc/ppp/pptpd-options
 Append to the end of the file, the following directives:
-    ms-dns 192.168.1.1
+  ms-dns 192.168.1.1
+  nobsdcomp
+  noipx
+  mtu 1490
+  mru 1490
-    nobsdcomp
+Where the IP used for the ms-dns directive is the DNS server for the local network your client will be connecting to and, again, it is your responsibility to adjust this to your network's configuration.
-    noipx
+. Edit the chap secrets file:
-    mtu 1490
+  sudo vim /etc/ppp/chap-secrets
-    mru 1490
+Add to it the authentication credentials for a user's connection, in the following syntax:
-Where the IP used for the ms-dns directive is the DNS server for the local network your client will be connecting to and, again, it is your responsibility to adjust this to your network’s configuration.
+  username <TAB> * <TAB> users-password <TAB> *
-Edit the chap secrets file:
+. Restart the connection's daemon for the settings to take affect:
-    sudo vim /etc/ppp/chap-secrets
+  sudo /etc/init.d/pptpd restart
-Add to it the authentication credentials for a user’s connection, in the following syntax:
+If you don't want to grant yourself access to anything beyond the server, then you're done on the server side.
-    username <TAB> * <TAB> users-password <TAB> *
-Restart the connection’s daemon for the settings to take affect:
-    sudo /etc/init.d/pptpd restart
-If you don’t want to grant yourself access to anything beyond the server, then you’re done on the server side.
 Enable Forwarding (optional)
 While this step is optional and could be viewed as a security risk for the extremely paranoid, it is my opinion that not doing it defeats the purpose of even having a VPN connection into your network.
-By enabling forwarding we make the entire network available to us when we connect and not just the VPN server itself. Doing so allows the connecting client to “jump” through the VPN server, to all other devices on the network.
+By enabling forwarding we make the entire network available to us when we connect and not just the VPN server itself. Doing so allows the connecting client to "jump" through the VPN server, to all other devices on the network.
-To achieve this we will be flipping the switch on the “forwarding” parameter of the system.
+To achieve this we will be flipping the switch on the "forwarding" parameter of the system.
-Edit the “sysctl” file:
+. Edit the "sysctl" file:
-    sudo vim /etc/sysctl.conf
+  sudo vim /etc/sysctl.conf
-Find the “net.ipv4.ip_forward” line and change the parameter from 0 (disabled) to 1 (enabled):
+Find the "net.ipv4.ip_forward" line and change the parameter from 0 (disabled) to 1 (enabled):
-    net.ipv4.ip_forward=1
+  net.ipv4.ip_forward=1
 You can either restart the system or issue this command for the setting to take affect:
-    sudo sysctl -p
+  sudo sysctl -p
 With forwarding enabled, all the server side settings are prepared.
-We recommend using a “Split Tunnel” connection mode for the VPN client.
+We recommend using a "Split Tunnel" connection mode for the VPN client.
-A more in depth explanation about the recommended “Split Tunnel” mode, as well as instructions for Ubuntu Linux users can be found in the “Setting up a “Split Tunnel” VPN (PPTP) Client on Ubuntu 10.04” guide.
+A more in depth explanation about the recommended "Split Tunnel" mode, as well as instructions for Ubuntu Linux users can be found in the "Setting up a "Split Tunnel" VPN (PPTP) Client on Ubuntu 10.04" guide.
 http://sysadmingeek.com/articles/setting-up-a-split-tunnel-vpn-pptp-client-on-ubuntu-10-04/
@@ Line 93: / Line 90: @@
 Escojo la opcion por defecto 'PPTP'. Parece ser que abre el puerto TCP 1723
 ===== (Opcional) Comprobar que los paquetes llegan =====
+Comprobar que el servicio pptpd escucha en el puerto 1723:
+  sudo netstat -nlp | grep 1723
+  tcp        0      0 0.0.0.0:1723            0.0.0.0:*               LISTEN      1080/pptpd
 Desde el cortafuegos o el servidor pptpd:
-  tcpdump -i any | grep "1723"
+  sudo tcpdump -i any | grep "1723"
 Aparecen lineas como:
@@ Line 116: / Line 120: @@
 :31:04.006802 IP jj.com.1723 > IP_PUBLICA_CLIENTE_VPN.42024: Flags [R.], seq 0, ack 4001792755, win 0, length 0
 </code>