oh… is not a best solution for me, btw, i will investigate a bit... and then will decide what to do.

Thank you so much for your help, your support and your time!
Stefano.

@Xefan:

I can successfully connect to my pfSense 1.2.3 server through OpenVPN from a remote computer, but not from LAN the server belongs to.
I get the following error in the logs: TCP/UDP: Incoming packet rejected from 192.168.10.1:1194[2], expected peer address: XX.XXX.XX.XXX:1194 (allow this incoming source address/port by removing –remote or adding --float)
I don't have the --remote option in the client config.
Please help!

same problem I had also. when i was using UDP Port. But if you use TCP. You can connect your opnvpn client to your openvpn server from lan.
I dont know the reason why i couldnt use UDP. BUt same setting if i use tcp It works.
make sure your opnvpn client config file has those lines…...

float
port 1194
dev tun
dev-node tap0
proto tcp-client
remote your wan ip
1194
ping 10
persist-tun
persist-key
tls-client
client
ca ca.crt
cert whatever your clint name.crt
key whatever your clint name.key
ns-cert-type server
comp-lzo
verb 4
I hope it will help you....

@kpa:

Server:
ca.crt
server.crt
server.key
dh1024.pem

Client:
ca.crt
client1.crt
client1.key

Worked like a champ thanks (PS - Client1 was actually "frodo" in my situation)

yes sir. i am running it without any problem. and yes i open both tcp and udp. Yes i follow that tutorial and this tutorial also "http://www.scribd.com/doc/8142908/pfSense-OpenVPN-Tutorial".

my problem was as i said "server.crt". actually i couldn't get the code correctly. thats why i couldn't put correct code one pfsense openvpn server.crt field.

And now i know why i couldn't get the correct code. it was typing mistake. Something like this "build-key-server.bat"

Actually it should be like this "build-key-server.bat server"

but i am very happy now. thank you very much sir.

take care and ba bye…..

@cmb:

2.0 already has the equivalent of OpenVPN Access Server for free, and better in some ways.

I can't wait to put my hands on it.  :P

Thanks

This is just a repost i have from another topic but it may help you.

To me it sounds like you are not pushing your routes from your remote site to your client when it connects. Look under the "Custom Options" section of your openVPN config. You can add in something like…
push "route 10.10.10.0 255.255.255.0"

This will let the remote openvpn server push the correct routes needed to talk over the VPN to your client. I believe you must also have the "pull" option specified in your custom options for your "client". Using the openvpn gui client my config lists "pull ; Pull route data/DNS from server."

Let me know if this fixes it for you!

@completetech:

I have pfSense set up as the server.  the client is of course my windows xp laptop.

For the record, got working the 3-site routed VPN with this changed topology:
Site1 <-> Site2 <-> Site3 <-> Site1

The missing bit was to add routes for the Site2 FW before redirecting the default gw on the other two sites.

FW1 LAN1: 192.168.1.0 WAN: 10.10.1.2 --> intersite gw: 10.10.1.1 LAN2: 192.168.2.0 OPT1: 10.10.2.2 --> intersite gw: 10.10.2.1 WAN: Internet LAN3: 192.168.3.0 WAN: 10.10.3.2 --> intersite gw: 10.10.3.1

Site1 as client:

route 10.10.2.0 255.255.255.252 10.10.1.1; route 10.10.3.0 255.255.255.252 10.10.1.1; route 0.0.0.0 128.0.0.0; route 128.0.0.0 128.0.0.0; dev tun12;

Site1 as server:

route 192.168.3.0 255.255.255.0; dev tun13;

Site2 as client:

route 192.168.1.0 255.255.255.0; dev tun21;

Site2 as server:

route 192.168.3.0 255.255.255.0; dev tun23;

Site3 as server:

route 10.10.1.0 255.255.255.252 10.10.3.1; route 10.10.2.0 255.255.255.252 10.10.3.1; route 0.0.0.0 128.0.0.0; route 128.0.0.0 128.0.0.0; dev tun32;

Site3 as client:

route 192.168.1.0 255.255.255.0; dev tun31;

Thanks a lot to GruensFroeschli for the tip about redirecting default gw. Just out of curiosity, the two routes for that trick do the same as "redirect-gateway def1"?

I think this thread has all the current information about the problems with bridging and OpenVPN:
http://forum.pfsense.org/index.php/topic,1990.0.html

Afaik the problem only appears if you use CARP and an OpenVPN bridge together.

yes

Fixed it, turns out then encryption had nothing to do with it, that was setup fine all the time, I needed a little extra config on the server side.

To allow clients on the lan behind the pfsense client firewall (192.168.3.0/24) to access machines on server side lan (192.168.4.0/24)  I added this to the server config

client-config-dir ccd route 192.168.3.0 255.255.255.0

then in a directory called ccd I created a file with the same name as the client cert in use and in it I put

iroute 192.168.3.0 255.255.255.0

And everything stared working.

All this is probably obvious when you understand the inner workings properly but it took me a little while to understand so hopefully this will help anyone else in my position.

Post both the client and server side configs, or screen shots of each. It will make it a lot easier to figure out. I'm assuming this is a shared key site-to-site tunnel?

ok so i downloaded the development iso of pfSense, downloaded ykclient (yubico-c-client) as required by yubico pam

while running ./configure it states it needs curl, found a freebsd package of this. Installed it and running curl it states it needs libssl. I cant find this anywhere, package management in freebsd seems screwed or something.

Arent there ANYONE out there with a nice freebsd server up which can compile these things and put it up somewhere?

nice work!thanks!

You would only want that on the client I believe, it could otherwise cause the server to shut down. May be able to push that option, I'm not entirely sure offhand. Never tried that option before.

Though I do question if it's really necessary. Unless you have a very large number of simultaneous clients, and very slow hardware (less than 500 MHz), the load if they aren't doing anything is inconsequential. The load with VPN is primarily when you're pushing traffic and it has to do crypto on that.

jimp/kpa,

Thanks for the advice, the thing I was missing was the extra route statement in the server configuration. Just to close the loop on this thread, here's the final settings that worked.

Public IP: YYY.YYY.YYY.YYY
Net 1: 192.168.1.0/24
Net 2: 192.168.2.0/24
Net 3: 192.168.3.0/24
OpenVPN Pool: 192.168.100.0/24
Local Network: Left blank
Custom Options: push "redirect-gateway def1"; push "route 192.168.1.0 255.255.255.0"; push "route 192.168.2.0 255.255.255.0"; push "route 192.168.3.0 255.255.255.0";route 192.168.101.0 255.255.255.0;

Client-Specific Configurations:

Interface IP: 192.168.101.0/30 Push Reset: Unchecked Custom Options: iroute 192.168.101.0 255.255.255.0

Problem solved!

Amazing, isn't it?  :D

^ What he said.

If you want a "backup" VPN server that's routed, it would have to assume the role of default gateway. With pfSense you can use CARP for multiple firewalls, but if your other firewall isn't pfSense, you probably can't do that.

If you use bridged VPN, it shouldn't matter because the clients will get an address on your LAN, so no worries about routing.