So, finally I have learnt what is a setting.
Current situation is like this:

1. VPN client do not connects with message like this "cannot reach gateway"
2. Later it should connect to remote desktop: of course does not work correctly if VPN not established - connected.

I have bypassed pfsense and plug directly into a modem-router, disabled firewall and it works.
So there must be some trouble with pfsense.

It works on 192.168.4.x - LAN, I used the same IP mask with pfsense and do not work.
I suppose 10.0.0.x will not help.
Any other ideas.

Thanks much for any help.

Hi Sullrich ! please reply!
Thanks!

@sullrich:

#2 - http://wiki.pfsense.com/wikka.php?wakka=SubmittingPatches

Thanks, but maybe I'm a little bit retarded  :)
Is there (I didn't find it) a simple guide like "What to do, from the beginning to the end, to put a new a new page into the project"?
Also i need to cooperate with the person who manages the OpenVPN config page
Bye

the DNS-entry you make on the mainpage is for the PfSense itself. NOT for the clients.
to push DNS entries to the clients you need to the "Custom options" field the following:

push "dhcp-option DNS xxx.xxx.xxx.xxx"

if you want more than one entry you hae to separate the different entries with a ";"

Hello Helix26404,

Afer 2 weeks of forums searchs and configs changing, i find your post and i do the change and all works fine.

Tahnk you very much Helix26404, maybe your post must be introduced to the main pfsense-openvpn tutorials.

HICHAMB

Good news!

See the "OpenVPN Client Bridging" section of http://doc.pfsense.org/index.php/Setting_up_OpenVPN_with_pfSense

Uh oh heh, nevermind.  ;D

on Endian i can put this values:

IP of the server to connect username password Select bridged or routed select if i whant to block DHCP responses coming from tunnel CA certificate

it gives you any idea on how to configure PFsense openvpn server
i got all the certeficates and the keys from my corrent endian server

Thanks, i will try it. :)

hi,
  Would you be kind enough to help me out in configuring multiple OpenVPN-UDP-Tunnels.i am unable to connect two devices at a time.If i disable one, other site-site is connected.i have two site-site on different ports.

Regards,
Upendra

Just curious, but what is on the other side of the tunnel? If you are trying to connect from a Vista computer you need to do the following;

Add to your .ovpn file the following two lines:

route-method exe
route-delay 2

Create a one-line .BAT file to run openvpn on your .ovpn config file like this

“C:\Program Files\OpenVPN\bin\openvpn.exe” [PATH_TO_OVPN_FILE]

To start the VPN, right click on the bat file and choose “Run as Administrator

@battistis:

why it works well with windows and not whit linux (u.dapper)  :'(

Might want to ask that on a Ubuntu forum.  If it works with windows, well…

NOT Working

you must enter a network .99/29 is not a networkadress but a ipadress

.96/29 is the one you are looking for (.96 networkadress .97 till .102 ipadresses .103 broadcastadress)

Thanks for you respone. Pfsense1 is the server site and pfsense2 is the client.
this is the configuration for both sites.

Client site                                                Server site
Protocol        TCP                                      Protocol        TCP     
Srever Add    10.189.137.1                          Dynamic IP      enabled
Server port    1194                                    Address pool    192.168.10.0/24
Interface IP  192.168.2.0/24                        Remote IP      192.168.2.0/24         
Remote network 192.168.1.0/24                   
Proxy port    3128

I already created rule that allow all traffic from WAN to LAN.
Thanks

Nothing great stuff…. it is just to help me in doing my routine and to help my team in easy handling of things.... I do not want them to tamper with something which they do not know.... So, some child stuff.... For this to be shared, I need to go a long way..... I am just crawling....

Btw, It was my mistake in fetching the certificate from Database..... Changed the logic of fetching the certificate.... now it is thorugh and it accepts the certificate without any problems. Still continuing to use the same uuencode -m option.

This is fixed in recent snapshots.

Didn't help in the build I had.  I moved to the latest snap and it's fixed now.

Weird!