I don't know what you have now as your office router, but if it is not pfSense already, then I would replace it with pfSense. Then you have 1 router that can do it all easily. If you put a separate pfSense router in your office LAN somewhere, then you will have to add static route/s to your office router telling it about the pfSense and what subnets are reached through that. Also, I would change 192.168.0.0/24 at home to some other less popular private subnet - e.g. use something in 10.0.0.0/8. That will avoid pain when you take your laptop to a cafe that uses 192.168.0.0/24 and try to VPN back home.

Thank you for your feedback :)

Hi, just to make sure what you have: You have one WAN connection and one (or more) LAN connections? Some traffic from LAN to the internet should go through the VPN and other should go through your origin WAN, right? It could be usefull to see your firewall LAN rules and if you have really PortForwarding enabled then the firewall rules on your WAN interface - at least for the PortForwarding rule.

I deactivate the windows firewall and the AVAST firewall. Best regards Thierry

@NOYB: Does not prevent account from WebConfigurator login.  Just restricts access to WebConfigurator pages. Check cmb's post…  that was exactly my point.... don't put them in group that has access. Only works for OpenVPN connection access. You can put those rules on any interface. Not difficult to find the changed and non disclosed WebConfigurator port. So, change it and install firewall rules to harden access.  Not difficult to keep people out with firewall rules.

I was able to figure out a script to replicate the behavior that occurs when the save button is clicked on the client.  This is a little bash script for those who need to restart a client cleanly (i lose 1 ping during the restart).  Save this as a .sh file, chmod +x that file and add it to cron or trigger it however you would like.  I'd like to somehow trigger this by an Apinger Down event, but I don't know how to do that.  Can anyone help with that? #Determine the PID of the running client (assumes there is only one) clientpid=$(pgrep -lf /openvpn/client | awk '{print $1}') #Collect path of openvpn and client openvpnpath=$(pgrep -lf /openvpn/client | awk '{print $2}') clientpath=$(pgrep -lf /openvpn/client | awk '{print $4}') #Kill client process kill $clientpid sleep 2 #Restart the Client $openvpnpath --config $clientpath

If both sites run PFsense, why are you doing Road Warrior and not Site to Site?

That looks like a certificate verification error, so something in the CA/Cert doesn't match or isn't right between the client and server, or it's invalid in some other way.

Never mind. Found it.

Anyone at all? Any opinions?

Thanks for coming back to me. It's now fixed. The issue was laptop privileges, in the end. Once I ran OpenVPN as the administrator, then it worked fine.

Aha… Figured it out from: http://doc.pfsense.org/Create-OpenVPN-client-to-TUVPNcom.pdf I needed to create an extra interface and gateway. All seems to work OK now...

A good place to start is to understand how tunnel networks work. http://openvpn.net/index.php/open-source/faq/75-general/293-what-is-the-principle-behind-openvpn-tunnels.html

The rules on an interface tab apply to traffic coming IN on that interface. The first packet when a "connection/flow/session" is first started is checked by the rules, then if it is permitted, a firewall flow/state is added, and subsequent packets in both directions that match the flow/state are allowed. Thus, to get out from LAN (to the internet…) a suitable pass rule is needed on LAN. For a connect coming from a client on the other end of an OpenVPN link, a rule is needed on OpenVPN to allow the incoming connect. Once the flow is established, the traffic in both directions for that flow "flows":) That might be enough to give you the concept and you will be able to apply it in practice.

Thank you Phil for all your help.  I finally got it up and running with your help and Jim's help.  Once I got the OPTn set to openvpn I had to set outbound nat on SITE A for SITE B to get out to public. All seems to be working good so far.    Now I will work on getting NAT working for the servers in SITE B through SITE A.

@jimp: @CuriousG: Edit2: Site C will not always be up, will this affect communication between site A and B? Avoid using "edit" to ask questions. It does not notify that the post was updated the same way a reply does. If C is just another client, it won't affect anything between And B. If A were down, then B could not reach C, but that is the only failure that would be a problem. Thanks.  It makes perfect sense if A was down since it is the "server".  Only reason I asked is I got a call today that they weren't able to reach A from B but since this user is a handful in the first place I didn't know what to think when I activated site C and everything was fine.