Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm setting up the OpenVPN server daemon on a Buffalo N600 router which came stock with DD-WRT v.24 SP2.

I'm following the instructions at VPN (The Easy Way) V24+ to set up the server side of things and then set up an OpenVPN client (running on Windows). The instructions start out with:

As of DD-WRT v.24 SP1, it is now possible to set up DD-WRT as an OpenVPN appliance using only the web-based GUI. It is no longer necessary to issue shell commands, or to echo quoted certificates and config files using a shell script.

Sounds good. Here's a screenshot of the router's OpenVPN server configuration screen:

Given the statement about GUI support, I left "Config via" set as "GUI".

Buffalo N600 DD-WRT OpenVPN server configuration section

I followed the "Creating Certificates Using Easy RSA in Windows" section and created my certs with no problems. The documentation then talks about pasting the certs I just created into the relevant fields on the router's config screen:

Certificate Mappings

The first row says that into the "Public Server Cert (CA Cert)" field I should insert the contents of the "ca.crt" file. But there is a "Public Server Cert" field and a "CA Cert" field. And the 3rd row says that into the "Public Server Cert" field I should insert the contents of the "server.crt" file.

The field mappings don't match and are ambiguous. What goes where? Should I really be in GUI mode?

share|improve this question
up vote 2 down vote accepted

Typically, Using Easy RSA in Windows, these would be the files:

Public Server Cert (CA Cert) will be named ca.crt This is the root CA of your personal PKI.

Public Server Cert will be named server.crt This is your server X509 certificate. You are free to name this file as you see fit.

Private server key will be named server.key This is your server private key. You are free to name this file as you see fit.

dh.pem will be named dhxxxx.pem or just dh.pem This is the Diffie Hellman key - xxxx can represent the number of bits used when creating the file eg: 2048

TLS Auth will be named ta.key This is the TLS authorization key or HMAC key. This is highly recommended that you use.

GUI mode looks suitable for this task.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.