OpenVPN
From DD-WRT Wiki
Revision as of 16:17, 29 July 2006 (edit) AlReece45 (Talk | contribs) (→Enabling OpenVPN in server mode with static Key(DD-Wrt acts as OpenVPN server)) ← Previous diff |
Revision as of 10:21, 2 August 2006 (edit) (undo) Krikkit (Talk | contribs) (→Enabling OpenVPN in server mode with certificates (DD-Wrt acts as OpenVPN server)) Next diff → |
||
Line 85: | Line 85: | ||
we use bridging to integrate the clients into the local lan, so we need no routes... | we use bridging to integrate the clients into the local lan, so we need no routes... | ||
- | you need | + | you need dd-wrt Firmware: '''DD-WRT v23 SP1 Final (05/30/06)''' vpn ...newer buildts may NOT work because missing/broken brctl command |
Basically this is what you need to do: | Basically this is what you need to do: |
Revision as of 10:21, 2 August 2006
Contents |
Introduction
OpenVPN is a full-featured SSL VPN solution which can accomodate a wide range of configurations, including road warrior access, home/office/campus telecommuting, WiFi security, secure branch office linking, and enterprise-scale remote access solutions with load balancing, failover, and fine-grained access-controls.
There are two methods how to get OpenVPN on your router:
- use firmware with OpenVPN client included (starting from 23b2 from 2005-11-21 there is separate firmware). (easy method)
- install openvpn package to jffs partition
Using VPN firmware
Web interface of this firmware supports operation as a client to single server only. But using custom initialization commands it may be possible to add connections to more servers or even run a server on this router.
Enabling OpenVPN in Client mode (DD-Wrt connects to remote OpenVPN server)
OpenVPN client can be enabled via web menu at Administration/Services/OpenVPN Client. Choose "enable" and "Save Settings", then fill in parameters and press "Save Setting" again. Parameters:
- Server IP address
- IP address of the OpenVPN server you want to work with
- Port
- port which OpenVPN server listens on
- Use LZO Compression
- where to use or not compression on vpn traffic; must be the same value as on server
- Tunnel protocol
- what transport to use to transfer VPN traffic; default is udp, but if routers/nat devices causes problems, choose tcp; must be the same as on server
- Public Server Cert
- Certificate of OpenVPN CA in pem form; only part between (and including) -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- is necessary; as it is stored in nvram, everything else from that file should be removed to conserve space
- Public Client Cert
- Client certificate issued by CA for this particular router; also only part between 'BEGIN' and 'END' is required
- Private Client Key
- Key associated with certificate above; should be kept secret because anybody who knows this key can successfully authenticate as this client
Enabling OpenVPN in server mode with static Key(DD-Wrt acts as OpenVPN server)
with DD-WRT v23 SP1 Final (05/16/06) vpn this allows only 1 client connection!! ( see http://forum.bsr-clan.de/ftopic5111-0-asc-45.html for detail why...) for multiple client connections SSL/TLS authentication must be used (see instructions below)
The easiest way is to use bridging. Basically this is what you need to do:
1) Create a static.key file on your computer Code:
linux) openvpn --genkey --secret static.key Windows) Start -> OpenVPN -> Generate a static OpenVPN key
- OpenVPN for windows can be downloaded at http://www.openvpn.se
FYI: All the commands below are entered using the web method to setup the scripts on the router. See Startup_Scripts.
2) Take the rc_firewall script from my post: http://forum.bsr-clan.de/viewtopic.php?p=40508#40508 Code:
iptables -I INPUT 1 -p tcp --dport 443 -j ACCEPT
Enter the above command in the commands field and click "Save firewall"
3) Enter the below code in the commands field changeing the "...INSERT YOUR OWN CONTENT HERE..." with the contents from the file you created on step 1.Click "Save Startup"
openvpn --mktun --dev tap0 brctl addif br0 tap0 ifconfig tap0 0.0.0.0 promisc up echo " -----BEGIN OpenVPN Static key V1----- ...INSERT YOUR OWN CONTENT HERE... -----END OpenVPN Static key V1----- " > /tmp/static.key ln -s /usr/sbin/openvpn /tmp/myvpn /tmp/myvpn --dev tap0 --secret /tmp/static.key --comp-lzo --port 443 --proto tcp-server --verb 3 --daemon
4) reboot your router. Login with ssh and check that "myvpn" is running (ps -fe | grep vpn)
5) Create an openvpn config file on your computer with the content from my post. You need to replace the "XXXX.dyndns.org" with your router's internet address (or a dynamic dns hostname pointing to that address). http://forum.bsr-clan.de/viewtopic.php?p=40508#40508 Code:
remote XXXX.dyndns.org port 443 dev tap secret static.key proto tcp-client comp-lzo
6) try to connect
That should do it. (i have tested this on DD-WRT v23 SP1 Final (05/16/06) vpn) --Krikkit 21:01, 22 May 2006 (CEST)
If everything is ok you should get an IP address from your router (only if you have a running dhcp server) when you connect and that IP address will be in your internal LAN so now you just connect to your home PC the same way you would do it from inside your LAN.
-Windows support and rewording added by [Matt K 07/19/06] (Fully tested on DD-WRT v23 SP1 Final (05/16/06) vpn) ~enjoy
Enabling OpenVPN in server mode with certificates (DD-Wrt acts as OpenVPN server)
This describes howto enable openvpn server mode with the use of certificates, for better security than with static key, it also allows multiple client connections... we use bridging to integrate the clients into the local lan, so we need no routes...
you need dd-wrt Firmware: DD-WRT v23 SP1 Final (05/30/06) vpn ...newer buildts may NOT work because missing/broken brctl command
Basically this is what you need to do:
1) Create all the required certificates and keys. You should create a set of keys for each individual client that will connect to your OpenVPN server. Basically you follow this guide: http://openvpn.net/howto.html#pki
afterwards you should have the following files:
ca.crt ca.key dh{n}.pem server.crt server.key client1.crt client1.key client2.crt client2.key
2) now the rc_startup script for dd-wrt:
openvpn --mktun --dev tap0 brctl addif br0 tap0 ifconfig tap0 0.0.0.0 promisc up echo " -----BEGIN CERTIFICATE----- ...INSERT YOUR OWN CONTENT HERE... -----END CERTIFICATE----- " > /tmp/ca.crt echo " -----BEGIN RSA PRIVATE KEY----- ...INSERT YOUR OWN CONTENT HERE... -----END RSA PRIVATE KEY----- " > /tmp/server.key chmod 600 /tmp/server.key echo " -----BEGIN CERTIFICATE----- ...INSERT YOUR OWN CONTENT HERE... -----END CERTIFICATE----- " > /tmp/server.crt echo " -----BEGIN DH PARAMETERS----- ...INSERT YOUR OWN CONTENT HERE... -----END DH PARAMETERS----- " > /tmp/dh1024.pem ln -s /usr/sbin/openvpn /tmp/myvpn sleep 5 /tmp/myvpn --dev tap0 --tls-server --ca /tmp/ca.crt --cert /tmp/server.crt --key /tmp/server.key --dh /tmp/dh1024.pem --comp-lzo --port 44044 --proto tcp-server --mode server --client-to-client --keepalive 15 60 --verb 3 --daemon
the last line starting with "tmp/myvpn..." has to be on one line!
3) now add the following to your rc_firewall script for dd-wrt:
/usr/sbin/iptables -I INPUT -p tcp --dport 44044 -j ACCEPT
this allows connections from the outside to the openvpn server
4) Change the "...INSERT YOUR OWN CONTENT HERE..." with the content from the files you created in step 1
5) Use the web method to set the rc_firewall and the rc_startup script on the router. See this: http://wrt-wiki.bsr-clan.de/index.php?title=Startup_Scripts
6) reboot your router. Login with ssh/telnet and check that "myvpn" is running (ps | grep vpn)
7) Create an openvpn config file on your client-computer with the content from below. You need to replace the "XXXX.dyndns.org" with your router's internet address (or a dynamic dns hostname pointing to that address). Code:
tls-client dev tap proto tcp-client remote XXXX.dyndns.org 44044 resolv-retry infinite nobind persist-key persist-tun ca ca.crt cert client1.crt key client1.key ns-cert-type server comp-lzo verb 3
8) try to connect
That should do it. (i have tested this on Firmware: DD-WRT v23 SP1 Final (05/30/06) vpn) --Krikkit 22:03, 7 Jun 2006 (CEST)
If everything is ok you should get an IP address from your router (only if you have a running dhcp server) when you connect and that IP address will be in your internal LAN so now you just connect to your home PC the same way you would do it from inside your LAN.
--ADDITIONAL NOTES FOR IMPROVED JFFS INSTALLATION, AND SECURITY WITH PUBLIC HOTSPOTS--
19:10, 30 Jun 2006 (CEST) pagedude
i) The instructions above confine the OpenVPN server configuration entirely into a rc_startup script. This is elegant when openvpn is installed in RAM, since there's no convenient place to put a configuration file for openvpn (RAM contents are not persistent). However, if the user instead installs openvpn into persistent storage (e.g. the jffs partition), then instead of configuring OpenVPN on the command-line, a config file can be used. There are several advantages to doing this; not only is RAM space usage minimized (key files dont need to be copied to rc_startup, command line options get transferred to the config file etc.), but the config file allows the description of more complicated openvpn server configurations .. e.g. ii) below ...
ii) One interesting capability of the openvpn tunnel is to optionally allow the client to pass *all* traffic through the VPN when connected. (E.g. when you are at an unsecure WIFI hotspot, you might want to ensure that eavesdroppers are not able to monitor your wifi traffic; one way to do this is to ensure all your wifi traffic flows through the encrypted VPN tunnel). This is achievable via the "redirect-gateway" option, definable on either the server or client. When defined on the server, all clients *always* reroute all their traffic through the VPN. When defined on just the client, clients have the choice to act either way. However, "redirect-gateway" requires the "pushing" of two pieces of information from the server to the client, viz. the remote gateway and DNS IP's. My example config file below in iii) shows how to do this ...
iii) Here are my example rc_startup, server and client config files. Note that I installed openvpn in /jffs/tmp, and copied the certificate/key files ca.crt, server.crt, server.key, dh1024.pem and the server config file server.conf there.
rc_startup:
cd /jffs/tmp ./openvpn --mktun --dev tap0 brctl addif br0 tap0 ifconfig tap0 0.0.0.0 promisc up sleep 5 ;I had to install this library, since my ddwrt distro didnt have it ;See Troubleshooting section at the bottom of this wiki for JFFS installations export LD_PRELOAD=/jffs/sbin/libuClibc-0.9.28.so ./openvpn --config server.conf --daemon
server.conf:
mode server tls-server port 44044 proto tcp-server dev tap0 ca ca.crt cert server.crt key server.key dh dh1024.pem #These IP addresses need to be changed to be *your* ddwrt LAN addresses ... push "route-gateway 192.168.3.1" push "dhcp-option DNS 192.168.3.1" client-to-client keepalive 15 60 comp-lzo persist-key persist-tun status openvpn-status.log verb 3
client.conf:
tls-client dev tap proto tcp-client resolv-retry infinite nobind persist-key persist-tun ca ca.crt cert client.crt key client.key ns-cert-type server comp-lzo verb 3 #Pull info from server, viz. server-side LAN IP's for gateway and DNS pull # Uncomment the following to send all traffic through VPN redirect-gateway
19:10, 30 Jun 2006 (CEST) pagedude
76472429234521330421186
Installing into jffs partition
old method only recommended for non-vpn firmware
This no longer works with the latest firmware version, please download the new VPN inclusive version. !!However, with at least some new firmware versions (I'm using V23SP1 6/5/06 VOIP), the hurdle can be overcome with some extra effort ... details are provided below in the Troubleshooting section... 19:22, 30 Jun 2006 (CEST)!!
Prerequisites
You should already have: -a Linksys WRT54G/GS product -DD-WRT installed as the firmware -SCP or some other way to copy files to and from your desktop setup -some knowledge of using ipkg to install packages -jffs already configured if you don't want to install to ram
If you are running Windows on your desktop: -TextPad or Win32Pad
(or other *nix friendly text editor. DO NOT USE NOTEPAD)
Install the OpenVPN ipkg package
-Find the openvpn package in the THIS LINK DOES NOT WORK ANY MORE OpenWRT Package Tracker.
You will need the URI of package to install it.
-telnet or ssh shell into the router -run the command ipkg -d <dest_name> install <URI of package>
<dest_name> should be root to install to /jffs <dest_name> should be ram to install to /tmp *Remember, /tmp is deleted on router reboot* Ex: ipkg -d root install http://nthill.free.fr/openwrt/ipkg/experimental/20050420/openvpn-static_2.0-1_mipsel.ipk
EDIT: Can't find the right package? Yeah, neither can anyone else. Don't bother. The best strategy is to download and flash the distro with the built-in VPN and copy the binary off of that then re-flash with another distro and copy the binary to the jffs partition. The packages on the openWRT tracker don't seem to work for v23 on WRT54Gv3 ("Bus Error"). The version originally linked above and the version in the VPN firmware are statically compiled. I had to do it this way because the nvram startup script only ran the first command in the variable and I needed the VPN to survive a WRT reboot. Not enough room for jffs on all but the mini distro... so no shell scripts for me! YMMV. Note to the powers that be: How about posting this stuff with the mini firmware so we don't have to do it this way?????
Create the openvpn config file
-Using your method of choice, copy the file /<dest_name>/etc/openvpn/office.conf
to your desktop machine -Using a *nix friendly text editor, edit office.conf (the config file in my setup).
See http://openvpn.net for more informations and examples.
19:16, 30 Jun 2006 (CEST) pagedude
- NOTE : openvpn is highly configurable. Distinct from the original writer of this portion of the wiki, I setup my configuration files much more along the lines of the earlier section in this Wiki on configuring the OpenVPN server with certificates in bridging mode. Certificates provide a more robust dynamic configuration scheme, but take a little bit more time up-front to generate (but the http://www.openvpn.net site has an excellent, easy-to-follow guide on how to generate them). Bridging mode is very convenient in that the remote VPN client effectively appears to be part of the remote(server) LAN, plus much less routing configuration (i.e. use of ifconfig, route etc.) is required on either the OpenVPN server or the OpenVPN client.
19:16, 30 Jun 2006 (CEST) pagedude
############################################################################## # this is a sample configuration file for openvpn # it should be changed to contain your values and # placed in /jffs/etc/openvpn # remote servername.domain.com rport 5000 dev tap ifconfig 10.0.1.2 255.255.255.252 secret /jffs/etc/openvpn/key.txt ping 10 ping-restart 60 ping-timer-rem persist-tun persist-key resolv-retry 86400 verb 1 mute 10 route-up "route add -net 192.168.1.0 netmask 255.255.255.0 gw 10.0.1.1" # ##############################################################################
This is the OpenVPN config file of the other side (a Linux server or another WRT54G/GS)
############################################################################## # dev tap secret /etc/openvpn/key.txt persist-key persist-tun ifconfig 10.0.1.1 255.255.255.252 ping-restart 60 ping 10 verb 5 mute 10 lport 5000 route-up "route add -net 192.168.2.0/24 gw 10.0.1.2" # ###############################################################################
Usage & Troubleshooting
Launching the Client
-cd to the install folder (/<dest_name>/usr/sbin) -run ./openvpn --config ./../../etc/openvpn/office.conf --log openvpn.log
See openvpn.log for debugging
Load on router startup
-Using a *nix friendly text editor, create openvpn.startup as:
#!/bin/sh killall -q openvpn /jffs/usr/sbin/openvpn --config /jffs/etc/openvpn/office.conf
-Follow the instructions in Startup Scripts#Shell Script Method to make your script load on startup.
Troubleshooting
Correct time
OpenVPN requires client and server to have more or less synchronized time. Therefore make sure that router has correct time. To check it use command date and if you get info about year 1970, you should enable NTP client. Also, ntp server has to be outside of your VPN as time should be corrected before VPN is established. If you have syslog enabled (to local server, or the server outside your VPN), errors like TLS Error: Unroutable control packet received from server_ip:1194 may indicate this problem. (This error message may appear if your certificates are not valid or have expired, too.)
openvpn does not start, gives error message " ... can't resolve symbol 'fopen64' "
19:13, 30 Jun 2006 (CEST) pagedude
I have V23SP1 5/6/06 VOIP, extracted the openvpn executable from V23SP1 5/6/06 VPN and copied it to my jffs partition as outlined above, and set everything up as outlined above, except that I setup my own configuration files, of course. Then I got the above error message. The reason for this error message is that the openvpn executable requires an updated version of the libuClibc library. For my build, this should be libuClibc-0.9.28.so. Fortunately the package for this library can be located on the dd-wrt downloads page. Look for the "packages" folder at http://www.dd-wrt.com/dd-wrtv2/downloads.php, and retrieve the package named uclibc_0.9.28-6_mipsel.ipk. Install this package on the jffs partition - refer to the ipkg documentation for details. After installation, note down the exact path for libuClibc-0.9.28.so .. e.g. I installed mine at /jffs/sbin/liuClibc-0.9.8.so. Now you need to ensure that when openvpn is launched as a daemon, the executing environment has the variable LD_PRELOAD set to point to the path to this library. In simpler language, what you need to do is insert the following line:
export LD_PRELOAD=<replace_this_whole_angle_bracketed_region_with_your_full_path_to_library>
at the start of the script that launches the openvpn server. openvpn will then use this library, instead of the older one that exists in the non-vpn OpenVPN distributions.
19:13, 30 Jun 2006 (CEST) pagedude