Got it.. Thanks for clearing that up.  I finally got everything working with PKI.  PFSense rocks..

Cheers

EB

http://doc.pfsense.org/index.php/OpenVPN_Bridging

Correct, no custom options are needed when going from pfSense to pfSense because on both sides the GUI has a field to list the remote side network.

Then so long as the pfSense routers doing OpenVPN are the default gateway of the internal networks on both sides, everyone can talk back and forth.

That should be just a routing problem - ensure that you push the appropriate routes so that all nodes know how to reach all others (or at least their default gateways do).

Finally I didn't try this solution because I used the 2.0 beta version and I am totally excited with the openvpn configuration !

1. It has OPENVPN Firewall seperately from the physical interfaces !
2. You can create certificates inside pfsense easily without using easy-rsa !
3. You can provide configuration to the client very easy by using an amazing package !

There is nothing more for someone to ask !!!!!!!

;D ;D ;D ;D ;D ;D ;D

Thanks for the real world information.  I knew that some VPN clients did not play nice at all and was hoping this was not the case with Juniper and OpenVPN.
Mike

hi, i have read the guide in the book you have wrote "pfsense the definitive guide" and i have solved my issue because the process is explained very well.

Thanks for all advice.

From what you have posted, yes.

If it can't access HTTP, but can access other protocols, then it's either a proxy configuration setting on the client that's wrong or a configuration issue with the proxy server(s).

Thanks this worked for the most part, I changed the OpenVPN client address pool to 172.17.255.0/25 and I did have to do a route push in the form of….....

push "route 192.168.20.0 255.255.255.0 172.17.255.5";push "route 10.10.10.0 255.255.255.0 172.17.255.5"

....in the OpenVPN Client-Specific configuration but other then that, works like a champ :)

Thanks mate!

This is for a 1.2.3 system. I will give AON a try and see if that fixes it.
Thanks.

It happens on both. I have re-downloaded and re-installed and re-did configurations from scratch and I end up the same place again.  :'(

UDP isn't likely to be the problem.  When you connect from this 10. network, what does the client log show?  Are you by any chance also use a 10. network for your VPN or your remote network?

i am new at this, but would like to learn how to setup this option, can you show me how
Thanks

Aw man, here I was all comfortable in a state of ignorant bliss and you come along talking about disk failures.  :)

Thank you for the tip. I will give the disk a close look. I've been thinking about trying out 2.0 so this will give me an excuse.

Thanks jimp, I ended up restarting pfSense and the problem cleared up. I am interested in finding a way to reload the config without doing a full reboot and I'll try your suggestion if the problem pops up again.

@eureka, Thanks for the suggestions.
I will try out your suggestions & get back to you with the results.

Before I try out though, I would like to tell you that sub-domain to search into is not known @ deployment time. Sub-domains & Users in that sub-domain are getting added dynamically, there could be hundreds of sub-domains in one root domain so fixing group BaseDN wont be possible. I had commented out <group>…</group> section completely when I had tested.

Also, I would like to know what exactly "%u" does in filter (&(uid=%u)).

OpenVPN automatically reconnects. It doesn't wait for traffic, it tries constantly. There is a 60-second timeout (but that can be tweaked in the custom options).

When you save on the server end, the process restarts which disconnects the client, which can then take up to a minute to reconnect.

When you save on the client, the process restarts and it will reconnect right away.

There is nothing wrong with OpenVPN when setup properly, I use it all over the place every day and have zero issues. I have far more issues with IPsec tunnels on a weekly basis.