next »

[torontob]

Wanted to add that the instruction worked for me using CentOS and not Windows 7 as server.crt was coming out as an empty file.

Thanks for the post.

[keeper]

Hi,

Thanks for the guide. I am trying to create the server.crt with command "build-key-server.bat server" and everything seems to be fine except for /keys/server.crt is empty (0 bytes). How can this be? I am using cmd.exe with Administrative privileges.

Any input please?

Thanks

Delete first the old generated files. And try to run again the build-key-server.bat server.

Hope this help

[torontob]

Nah. That doesn't help. I did the key generation on a CentOS server and it worked fine.

[soricel_z]

Nah. That doesn't help. I did the key generation on a CentOS server and it worked fine.

Dear all I am new in PfSense and openVPN.
First thank you a lot for the openVPN guide. Maybe is not the right place here to discuss this but here is the problem:
I installed PfSense with the embedded openVPN server.
I previously generated the certificates un an Ubuntu machine with a compiled openVPN server and I "copy - paste" them into the PfSense interface.
The only problem is that the server works fine but with only one client. (the acces in the network is granted, everything works fine, tunnel is stable)
When the second client try to connect the same IP address will be provided by the server and the first client is kiked off (with "connection was lost").
I tryed to generate more certificates for diferent clients, but the certifiates seems not to have any relation to the IPs.
IP pool for the VPN is 172.16.0.0/24 and the address 172.16.0.6 is the only address given to the clients.
Thanks, Robert

 

[chunger]

Nah. That doesn't help. I did the key generation on a CentOS server and it worked fine.

Dear all I am new in PfSense and openVPN.
First thank you a lot for the openVPN guide. Maybe is not the right place here to discuss this but here is the problem:
I installed PfSense with the embedded openVPN server.
I previously generated the certificates un an Ubuntu machine with a compiled openVPN server and I "copy - paste" them into the PfSense interface.
The only problem is that the server works fine but with only one client. (the acces in the network is granted, everything works fine, tunnel is stable)
When the second client try to connect the same IP address will be provided by the server and the first client is kiked off (with "connection was lost").
I tryed to generate more certificates for diferent clients, but the certifiates seems not to have any relation to the IPs.
IP pool for the VPN is 172.16.0.0/24 and the address 172.16.0.6 is the only address given to the clients.
Thanks, Robert

 

I met the same problem,please give our some help for it ,tks

[soricel_z]

Nah. That doesn't help. I did the key generation on a CentOS server and it worked fine.

Dear all I am new in PfSense and openVPN.
First thank you a lot for the openVPN guide. Maybe is not the right place here to discuss this but here is the problem:
I installed PfSense with the embedded openVPN server.
I previously generated the certificates un an Ubuntu machine with a compiled openVPN server and I "copy - paste" them into the PfSense interface.
The only problem is that the server works fine but with only one client. (the acces in the network is granted, everything works fine, tunnel is stable)
When the second client try to connect the same IP address will be provided by the server and the first client is kiked off (with "connection was lost").
I tryed to generate more certificates for diferent clients, but the certifiates seems not to have any relation to the IPs.
IP pool for the VPN is 172.16.0.0/24 and the address 172.16.0.6 is the only address given to the clients.
Thanks, Robert

 

I met the same problem,please give our some help for it ,tks

I solved it: I made a "small" misstake when I generated the certificates for the clients. The parametrer "common-name" is the one wich makes the diference between the clients. Otherwise the server think that is the same client over and over again and offers the same IP.
So you should put unique names here for the clients, not the same name as I did! It looks like different filenames for the generated keys did not make any difference between the clients.
Thank you all for the support! All the best! Robert

[chunger]

I am a newbie ,when I build the second client key ,it always remind me it can't find the *.old file.  I don't know the use of the *.old。
my first key works well,but I need create more client keys.  so pls help me find the reason,tks.

I have copy the procedure of building the client key.

I:\Program Files\OpenVPN\easy-rsa>build-key.bat
Loading 'screen' into random state - done
Generating a 1024 bit RSA private key
........++++++
..........++++++
writing new private key to 'keys\.key'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [US]:
State or Province Name (full name) [CA]:
Locality Name (eg, city) [SanFrancisco]:
Organization Name (eg, company) [OpenVPN]:
Organizational Unit Name (eg, section) []:
Common Name (eg, your name or your server's hostname) []:vpn1
Email Address [mail@host.domain]:chunger_qin@163.com

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:
Using configuration from openssl.cnf
Loading 'screen' into random state - done
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
countryName           :PRINTABLE:'US'
stateOrProvinceName   :PRINTABLE:'CA'
localityName          :PRINTABLE:'SanFrancisco'
organizationName      :PRINTABLE:'OpenVPN'
commonName            :PRINTABLE:'vpn1'
emailAddress          :IA5STRING:'chunger_qin@163.com'
Certificate is to be certified until Sep  3 00:55:48 2020 GMT (3650 days)
Sign the certificate? [y/n]:y


1 out of 1 certificate requests certified, commit? [y/n]
CERTIFICATION CANCELED
can't find  I:\Program Files\OpenVPN\easy-rsa\keys\*.old

[rsn]

um, this doesn't work at all.


24) Copy the WHOLE content of server.crt into the "Server Certificate" window
25) Copy the WHOLE content of server.key into the "Server Key" window
26) Copy the WHOLE content of dh1024.pem into the "DH parameters" window

Those files do not exist

[Bai Shen]

Awesome guide! I got this working over TCP port 443 since we have a blanket port block here at work. If anyone else is trying to do this using TCP, remember to change the guide/defaults:

1. On the OpenVPN Add tab in pfSense.
2. On the WAN-LAN rule.
3. In the config file for the OVPN client install.
4. Change the pfSense web port from 443 to something else (4443) if using HTTPS.

I forgot to change the proto line in #3 from UDP to TCP, and I forgot about #4 -- that wasted 20 minutes of my life.

I'm trying the same, using 443.  I did all four of these steps.

Now I'm getting a TLS handshake not found error.

Also, I'm a bit confused about step 32 in the OP.  Could that be why I'm getting the TLS handshake error?

I know I'm not having ports blocked as I was getting an address in use error until I changed my pfSense GUI port.

Also, I'm not getting anything in the OpenVPN log.

[dekopolis]

I'm not sure what command to issue when i want to invalidate one of my clients. In other words, if one of my users leaves the company and I don't want him/her to be able to access the vpn what do I need to do?

Thanks all!

[GruensFroeschli]

http://openvpn.net/index.php/open-source/documentation/howto.html#revoke

[trentdk]

Note for 64-bit Vista / 7 users:

If OpenVPN is installed in c:\Program Files (x86), then you need to change the vars.bat:

Code:

change line 6 in vars.bat from:
set HOME=%ProgramFiles%\OpenVPN\easy-rsa

to:
set HOME=%ProgramFiles(x86)%\OpenVPN\easy-rsa

[jai23155]

thanks for the document. i followed the document, but setup using TCP. anyway, i can connect to the pfsense box, but neither ping pfsense box nor browse network. when i check ipconfig /all, i get 255.255.255.252 rather than 255.255.255.0. i spent a week sorting this out myself, now i am posting here, i am almost throwing pfsense out of the window. apart from openVPN, it is great though.

[ivalerio]

Hi, I have a small problem here. This tutorial changes a bit with pFsense 2.0. You can't add the server entry without creating the certificate first. Also the latest version of OpenVPN fails to coincide with the instructions and I had to use the second to latest openVPN package.

Anyone here able to help me set this up for a basic VPN package. I've done everything except the addition of the server entry in 2.0 which is not allowing further movement till certificates are defined first. Thanks guys and gals.

[Aziz]

I have the same problem with 2.0RC1, it doen't allow one to enteer the keys (steps 23-26). Can anyone help?