yes, one of the parallel threads here gives the answer already TODAY (search function is right upper; makes always sense to use it before posting ;)) http://doc.pfsense.org/index.php/CARP_Secondary_Unreachable_Over_VPN

I was just able to solve the problem. My server side config had "ping restart" configured, which I replaced by "keepalive", now the connection is not restarted anymore :)

I resolve this by configuring the router?

I use the OpenVPN Client Export Utility package and there is an option "Use a password to protect the pkcs12 file contents or key in Viscosity bundle. " under VPN:OpenVPN:Client Export. Does that work for you? (I haven't tried myself)

For the configs, just post the text.  For the firewall rules… take screen shots, upload them to photobucket and post using img tags.

No one can help me?

What version of PFsense? Post a network map. Post your server1.conf Post your firewall rules.

There are threads/howtos here for StrongVPN and I think VyprVPN. Anything OpenVPN-based should work similarly.

I've never seen any situation that called for that syntax. Only this: push "route x.x.x.0 255.255.255.0";

thank you very much

DEar Friend, I m having the same issue.. CAn you help me how u sort of the issue?

Anyone had experience with setting up LDAP with OpenVPN?  :-\

Ah, good to here. I suspect that the OpenVPN connection is stealing the default gateway when it is brought up. There is an option to allow the default gateway to change but I can't remember where it is off hand.  ::) I think it's disabled by default anyway. More likely is that the VPN adds a default route when it comes up. I think that is a changeable setting also. VPNs are not strong point of mine to be honest.  :) Steve

I am very intrested in this!! Please provide instructions! Best regards Kostas

Hi, Wondered if you can help. Do you know of any instructions I can use as a template to try and work out how to get my VPN service working? Thanks

Jimp, Thanks so much.  This did fix this issue.

i would advice updating to 2.0.3 which is the latest stable. Since 1.2.3 there have been numerous improvements, also making it much easier to setup openvpn.

@dhel: I'd suggest a few things to try- Add "tun-mtu 1500;" and "mssfix 1400;" to the OpenVPN "Advanced Configuration" Move off port 1194… it might be shaped on the provider's end. Wow, this did cause a dramatic difference once applied to both ends. I max out his upload receiving on my end perfectly fine testing with both SMB and HTTP, and he can now get around 1 to 1.1MB/sec from me, which is great in comparison to before. I technically can push out 5MB/sec with the fluff on the upload from FiOS and he should be able to receive that since he has 45Mbps down, but I guess it's better than nothing!