@chpalmer: I copied from my(release) config file and pasted to the config file for the snapshot.  That may have not been a good idea so Im going to start over later when I get some time. Probably not a good idea!  I don't know what might have changed but you never know.  I's suggest that you create it from scratch on teh new GUI.  If you really wanted to you could compare the .xml files to see any changes … Cheers Jon

Thanks for reply, GruensFroeschli @GruensFroeschli: 1: I suppose it's possible. If one of the connections goes down your other balancer will put the attempt to reestablish the connection just on the second link. 2: I'm not sure what you're trying to ask. Do you mean if it's better to let theRV042 do the loadbalancing or pfSense? If you want failover for OpenVPN i think it's better to let the RV042 do the loadbalancing the job. I dont think you can create failover-pools for pfSense itself, since pfSense uses outbound only its WAN for services running on it. I need site-to-site OpenVPN Loadbanace not fail over. :) [pfSense Box]-WAN-192.168.1.2< –--->192.168.1.1-LAN- [RV042 Loadbalance Router]-WAN1-[IP by ISP]–---Modem1---> [ OpenVPN  ]                                                              [                                  ]-WAN2-[IP by ISP]–---Modem2---> Sompong

You don't say what OS you are using on your laptop. I would suggest that you run a local DNS server on your laptop.  Configure it to forward to your work DNS for their internal domains and at your home system for its domains.  Then point it at what ever can get out of the door for everything else (can be both).  Finally, point your laptop at its own DNS server on 127.0.0.1. Cheers Jon

@razor2000: When running OpenVPN on your OPT1/OPT2 lines, be sure to use TCP instead of the default UDP for your port.  pfSense has issues when trying to connect to any port that runs on the UDP protocol when not using the WAN interface. Give it a try and good luck! :) You sir a genius!  I think I saw that posted somewhere but must have ignored it. OpenVPN received wisdom is that TCP over TCP is a bad idea, something to do with a double exponential stand off which can cause serious performance snags.  Funnily enough I've been running it like that for years prior to putting in pfSense but thought I'd do the right thing this time - oh well! I have (briefly) tested all three of my external connections to my office LAN via this and they work very well.  I'm nearly ready to bin the many IPSEC tunnels which are a constant pain - regularly dropping and not recovering, unlike OVPN which has always struck me as far more robust.

Well you "could" "try" to uninstall snort and see if it works again. If this is the case you can start looking for how you missconfigured snort that this happened.

Yes, I've waded through all available docs.  It seems to be a Fedora rawhide specific problem, FC9 works.

Please read the stickies and the howtos since there are step-by-step guides.

I assume your mobile warriors dont get NATed to the internet. http://forum.pfsense.org/index.php/topic,7001.0.html Per default for every local "real" interface a rule will be installed that NAT's from this interface to WAN. If you want to have Internet access from multiple LAN subnets (ie. you have a router behind pfSense with another subnet) enable Advanced outbound NAT and create a rule for every IP range you want to be NAT'ed. The same goes for OpenVPN if you want the OpenVPN subnet NAT'ed to WAN. You need to create a rule for every subnet you want NAT'ed. Alternatively you can change the source of single existing rule from LAN to "any" thus NAT'ing everything. (screenshots to clarify: http://forum.pfsense.org/index.php/topic,7693.0.html ) This might create a problem for FTP with multiWAN more here: http://forum.pfsense.org/index.php/topic,7096.msg40810.html#msg40810 Try this. I'm not sure, but i think this should help.

This isn't too hard. The point is that you have to have your wins server announce on the subnet where the VPN hosts are too. This requires a few changes in the setup. 1. You need to make the WINS server know it has another subnet to relate to: in smb.conf: make sure hosts allow contains the subnet hosts allow = 127.0.0.1 10.23.23.0/24 wins support = yes 2. The you have to add the following options to the openvpn server: push "dhcp-option NBT 2" push "dhcp-option DNS <your dns="" ip="">"    push "dhcp-option WINS <your wins="" server="" ip="">" I find browsing a bit slow. I am not sure why, so if anyone has some input on that, I would be greatfull.</your></your>

I'll test this now with creating and revoking certs and see how I go. Good to see I wasn't insane and others couldn't revoke as well! Update Creating certs works ok, you can't do a ./pkitool on its own now to get the usage message because the CN is now defined in the vars (so it generates a passwordless cert called whatever you set that variable to) but if you define your own CN on the command line it overrides vars. After playing around it seems to revoke the certs but not actually use the CRL?  I tried a few different things stop start service manually add the crl to the config page etc… but cant do a system restart at the moment. What needs to be done to get them to actually be revoked on login?  At the moment they just time out after seemingly verifying ok.  Logs also dont mention revoke. Jul 11 12:15:15 openvpn[90005]: xxxxxxxxxxxx:1194 TLS Error: TLS handshake failed Jul 11 12:15:15 openvpn[90005]: xxxxxxxxxxxx:1194 TLS Error: TLS object -> incoming plaintext read error Jul 11 12:15:15 openvpn[90005]: xxxxxxxxxxxx:1194 TLS_ERROR: BIO read tls_read_plaintext error: error:140890B2:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:no certificate returned Jul 11 12:15:15 openvpn[90005]: xxxxxxxxxxxx:1194 Re-using SSL/TLS context Jul 11 12:14:16 openvpn[90005]: xxxxxxxxxxxx:1194 TLS Error: TLS handshake failed Jul 11 12:14:16 openvpn[90005]: xxxxxxxxxxxx:1194 TLS Error: TLS object -> incoming plaintext read error Jul 11 12:14:16 openvpn[90005]: xxxxxxxxxxxx:1194 TLS_ERROR: BIO read tls_read_plaintext error: error:140890B2:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:no certificate returned Jul 11 12:14:13 openvpn[90005]: xxxxxxxxxxxx:1194 Re-using SSL/TLS context

Yep, I have that rule

ok, i've found it in /cf/conf/config.xml thanks

have been using asterisk locally for above 2 years. i just only set up broadhand access to remote site. so sip over vpn is all new for me !! cannot say it has worked and stop or run !! up to now it runs well  (1week) !! so i have pfsense in main site and dd-wrt on the remote site. openvpn server with pfsense remote site use pap2 adapter and is connect via vpn tunnel to asterisk server. just need to create extension on freepbx. once tunnel is up and route ok, work is done ! d

IT WORKS i told openvpn to listen on TCP 80,  the standard ports (udp and tcp) must have been blocked by my providers network. its also the expected speed (fast) thanks for your help TUNNEL THROUGH 80 for those who are having problems with openvpn

@GruensFroeschli: Glad to hear it works :) I assume this is a testnetwork. So your two WAN's are in the same subnet. If you move this into production you will have to add a static route for the WAN of the server. Something like route x.x.x.x 255.255.255.255 y.y.y.y with x.x.x.x being the WAN of your server and y.y.y.y the gateway of your client. Otherwise your client does not know how to send the VPN packets to the server after the tunnel is up. I'll be moving to production within a month. Thanks alot again! :)

Hello thanks for explanation my other site have only one computer so maybe it could consider as roadwarrior connection. i will test different solution. i choose PKI cause it look like more secure dd-wrt config with PKI use gui , shared key use script ;-) PKI allow client-to-client connection ( i think) but not tested yet ! i hope have not to use IPSEC for firewall rules over vpn ! so maybe i should contribute to the project to stay using openvpn…

What Valhalla1 said :) If you set up OpenVPN yourself you would have to write these files yourself. But on pfSense they will get created automatically if you just create a client specific configuration on the respective tab in the GUI.

Hi, drbowen, Congratulation that you successful make the tunnel and works fine. If u plan long term running pfsense, better build with a best condition hardware. Ya, you are running the vpn tunnel for files access or bridging? From what i know, you should not able to do bridging if doing shared key method. Correct me if i m wrong. kelvin