Fixed it. https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/056df2d9f0af16083bb0f601cb519e87741f1013

"route" should suffice

locking this thread because people keep hijacking it, the original issue is resolved, start a new thread if you have an issue.

http://forum.pfsense.org/index.php/topic,33937.msg176255.html#msg176255

Have you seen this post yet? http://forum.pfsense.org/index.php/topic,34668.msg182131.html#msg182131

edit* nevermind, it works just fine; just needed a reboot ! it was throwing this error at me: Apr 1 15:11:36 openvpn[35065]: Exiting Apr 1 15:11:36 openvpn[35065]: FreeBSD ifconfig failed: external program exited with error status: 1 ```' +1 jimp thanks !

I cannot change nics that easily but I do not think that is the issue. That message appeared an hour or so before I lost connectivity and in searching the logs it has only appeared today. It has not appeared before the other instances where I have experienced the issue. The nic is a 3Com 3c905C-TX Fast Etherlink XL and I did not have this issue before upgrading to 2.0.

Nat reflection works only for tcp protocol so far.

OK, so the phone didn't last too long.  I'm going to change to manual NAT.

Thanks again, the package installed and works now :-)

I made a other test: I restored a working config (2.0 RC1) from a customer connected via PPPoE having a working IPSec Tunnel. Then i'd setup a Gateway as DefaultGW, switched from WAN PPPoE to WAN Static IP using the Gateway. Changed the LAN IP to my Testnet and the Phase 1 entry from Certs to PSK (PSK = 1234Test) and let the rules unchanged (Allow all incoming IPSec). Same same: Tunnel comes up immediately … but passes NO traffic. This must be some kind of bug! At the moment i have only the alternative to ship an old 1.2.3 to my customer, which is in a foreign country. I hope i can update it at a later time remotely, when 2.0 is released and the issue is solved. But of course i'm interested i a solution to that issue ...

If accessible, snip the wire on the speaker.  If not accessible, maybe there is a hole in it and you can drop a drip of thick honey consistency glue.  Polyurethane (e.g. gorilla glue) would be good because they are moisture cure, and foam up as they cure.  It will expand and hold much of the diaphragm solid.  I expect that you will still hear a noise if you are close enough.

Hi, just to say that I would very much like to have this feature as well!

I was all paranoid that I made a bad decision going with the Intel NIC's so had to do some testing. My test setup is a 3Ghz P4 w/ 1GB with one of yesterday's 2.0 embedded & 2 Intel nic's. 1 onboard Intel 100mbit for LAN & 1 PCI Intel 100mbit for WAN. Speedtest.net showed a burst up to 40+mbit down then held at 21.2mbit down rest of the test & 2.2mbit up (~0.1 CPU & ~2.0 interrupt) so looks like my 20/2 cable line was going full speed & then some with very little effort for the system which I figure means it could do tons more. At this point I'm thinking the Intel drivers are fine for my needs. :D I'll have to search around to read up on the Intel stuff though still as I'm still curious & baffled because over & over I read "go Intel NIC's". Cheers! Bill

@xenta: Thank to this how to, I've configured 3 openVPN client, placed each one on a gateway group in the same tier to have load balancing. With the dashboard's traffic graph I see that traffic pass in only one openVPN interface, it seem like load balancing not work at all. Also on another one openVPN interface I see only DNS traffic with tcpdump. (since I set a DNS on this one) What could be wrong with my configuration ? I found that the OpenVPN client Interfaces have different netmask one with 255.255.255.255 and the others with 255.255.255.0. Does this possible problem ? There is something to do in this case ? Sorry for my ignorance in OpenVPN…