Do you have this box checked?

Dynamic IP Allow connected clients to retain their connections if their IP address changes.

Generated new files and it worked.  Thanks!

Anyone have any ideas?

I have started a tutorial topic:

http://forum.pfsense.org/index.php/topic,35292.0.html

@trinybwoy:

After some more research i found this.

Every locally connected subnet, whether defined and reachable via a static route or attached to a LAN or OPT interface, will have its outbound traffic leaving any WAN interfaces NATed to that WAN interface's IP. You can change this behavior by enabling Advanced Outbound NAT (AON) but this is usually unnecessary and adds unneeded complexity.
For OpenVPN if you want the OpenVPN subnet NAT'ed to WAN, you will have to use AON.

I Did some adjustments. I enabled the advances Outbound Nat and i put in rules for the following

Interface : WAN Source : 10.10.10.0/24 (which is my local lan)
the Source port, destination, destination port, Nat address, nat port are *'s

i also did the same for my VPN address pool 10.10.11.0/24

i am still unable to get internet on my local machines :-(

That would be needed if you are going to route all traffic through the VPN, including regular internet traffic. If you do want to do this, I would suggest installing the OpenVPN enhancement package for 1.2.3 and check the "Redirect Gateway" option. If you are running pfSense version 2.0-rc1, the Redirect Gateway option is already present.

If you do not want to route all traffic through the VPN, rather only the traffic that needs to go through it (like the above mentioned RDP and slingbox management), then you are wanting to setup split VPN. Regular internet traffic (for example youtube or google) doesn't go through the VPN, but when you try managing your slingbox, that will go over the VPN.

What OS and/or distro are you running on the client? I noticed a similar issue with split VPN that ended up being due to a setting in Ubuntu's Network Manager. Basically, the more info you give, the easier it will be to help you.

I too am glad to have found this thread. I have the same problem and will try the latest version of the firmware later today. Thanks Jimp!

If you're using OpenVPN in shared key mode, it's usually as easy as just running Avahi on both ends of the tunnel. I haven't used it lately, but it has worked for me in the past.

Odds are some router ahead of you will rewrite that port anyhow.

Even if windows kept it the same, any router in front of that doing NAT would likely randomize the source port when doing translation.

What do your config files look like?

Okay so the fix was pretty simple.  For anyone with a similar setup, you need to put

local 1.2.3.4 (your WAN IP address)

into the "Custom Options" field in the OpenVPN configuration page to bind the service to the specific interface.

Ah ok, i was under the impression that the server is running on a pfSense.

Do you control the server?
Because if it reply has a different source IP than what you connect to, there is not much you can do to get it working.

Downloaded RC1 that fixed all of bugs and looked like that fixed all of my problems with OpenVpn

This was fixed a couple weeks ago, it should be fine in current snapshots.

I have a rough draft of the OSPF method that I've sent to some of our commercial support subscribers before, but it's still a little rough around the edges.

The other method hasn't had any documentation at all yet, I'm not sure anyone has ever done that exactly as I described.

You could put up a bounty for the documentation if you want to speed it up. It will happen eventually, whether it ends up on the Doc Wiki, in our 2.0 book (when that gets going), but funding always speeds up the process.

Could you let me know what exactly you did to get vyprvpn working? maybe a screenshot of the entire openvpn client settings page or something like that?

thanks for your help, my pfsense is right working since my last post  ;D

Now I'm able to use my windows 2008R2 server as authentications server for pfsense, openVPN and squid using a LDAP connection.

Fixed it by enabling arp proxing for the the /24 vpn subnet.

Solved using viscosity. Nice piece of software.