I had the same problem and added advansed options in the following command: push "route 192.168.2.0 255.255.255.0"; Look at this guide or introduction to the whole blog http://blog.stefcho.eu/?p=492

Hi, What you're doing might work, I never tried it but I think it's possible. But maybe you might choose a different path. What are you trying to accomplish? You could create a site-to-site VPN from the pfsense to the remote openvpn server. (the remote openvpn server does not have to be a complete subnet, it can be just 1 host) You could try disabling the rules for a short time to see if your OpenVPN connection stays stable. As for the log files, what do you see in your "system" log at the same time? Something else that looks different? Regards, Kristof.

@jimp: That should work, you might also try "push-reset" in your client config, that should make it stop taking the default gateway from the far side. I will give that a shot and report back!

That worked perfectly, thank you very much for your help! I'm slowly learning pfSense but it's clearly a fantastic Firewall OS.

actually, got it.  had the wrong port specificed in my firewall rules.  this post can be used for people having trouble setting up i guess.

Awesome thanks for the quick reply that worked! Just a note I added in a DHCP IP Range when configuring the OpenVPN server or else my client would not receive an local IP when connecting. Cheers!

The export utility is working fine. I tried it today on a VM with pfsense 2.0.1 amd64 - but without the wizard. Delete the OpenVPN server and try again with the wizard or without the wizard.

You'll need a routing protocol for that to work, and to exchange routes with the MPLS routers (usually via OSPF or BGP).

great ! this fixed the problem. thanks for all your help :)

@jspc You should make clear first, which host is the OpenVPN SERVER and which is the OpenVPN CLIENT and which Networks you want to rech. The network(s) behind the SERVER or behind the CLIENT. If the networks behind the SERVER: then you have to push the routes from the networks behind the server to your client. Pushing routes will be configured on the SERVER. If you do not like to push the routes you can add them at the CLIENT config. Both is working but I think the better solution is to push the from the SERVER to the client. the command on SERVER is: push "route 192.168.100.0 255.255.255.0"; If you like to connect to the network(s) behind the CLIENT: then you have to add the route  of the network behind the CLIENT on the SERVER: route 192.168.200.0 255.255.255.0; AND you have to add an "iroute" command on the CLIENT for the network behind the client. But at the irout command I am not 100% sure. iroute 192.168.200.0 255.255.255.0;

hi, i've seen the openvpn+ospf act the way you descibe when you make changes to the wan configuration and save them. restarting openvpn seems to solve that for me. this does not seem to be the case every time. for me this is rarely a problem so i've never bothered to look into it.

Probably would work with something to make the IP static in a client-specific override entry. Not sure what it would be offhand for a tap IP, but I thought it was supported (I know it is for tun, but the syntax is likely different)

Thank you!  In my OpenVPN server.conf I needed to add the appropriate route and iroute ccd entries, like the Thelonious example.

That's not great news. I set my tcp port to 0 which says it will make it dynamic. I noticed an immediate increase in speed, but it's still nowhere near what I had before. Before changing the port I was barely able to break 2mbit, changing it to dynamic puts it at just under 5mbit. Before I was able to break 50mbit with ease. You are correct in the assumption that I have no control over the server, but I suppose I can put in a complaint to see if I can make something change… Thanks for your help cmb, you're a good man.

Group support isn't all there yet. There are some patches out there, but it's still considered an open feature: http://redmine.pfsense.org/issues/1009

@nooblet: now in my troubleshooting I had to edit the server conf file (/var/etc/openvpn/server1.conf  use Diagnostics > edit file > browse to find it) and change the 'ifconfig' option because it would input it as ifconfig 10.0.8.1 10.0.8.2 when instead it should have been ifconfig 10.0.8.1 255.255.255.248, I have since seen it appear to work with this step but it doesn't hurt (and it cleans up the logs). SAVE I don't want to edit file every time I'm open and save openvpn config. And I made litle change in php-file for version pfSense - 2.0.1 1. On console enter digit 8 - Shell 2. Invoke editor to edit file /etc/inc/openvpn.inc with command ee /etc/inc/openvpn.inc 3. Goto line 405 4. Replace 405 line                                 $conf .= "ifconfig $ip1 $ip2\n"; with 4 lines                                 if ($settings['dev_mode'] != "tap")                                         $conf .= "ifconfig $ip1 $ip2\n";                                 else                                         $conf .= "ifconfig $ip1 $mask\n"; 5. Goto line 527 6. Replace 527 line                         $conf .= "ifconfig $ip2 $ip1\n"; with 4 lines                         if ($settings['dev_mode'] != "tap")                                 $conf .= "ifconfig $ip2 $ip1\n";                         else                                 $conf .= "ifconfig $ip2 $mask\n"; That's ALL! Now in openvpn config will be correct line for ifconfig command.

The static route is the only solution, though you should just be able to set a static route for 10.1.2.0/24 on any machine that is dual-homed (the technical term for a machine connected to multiple networks). If that is too much of an overhead, consider removing the direct WAN connection for those hosts.