Unfortunately i'm away till the 23rd so i can't test.
But i assume it will be ok since gori's install works.
Thanks for the speedy fix !

Just tested if outgoing session through IPsec tunnel stays up if a PPTP clients disconnects with 2.0 BETA4 from 30th of August.

The answer is: No it doesn't (but reconnecting works without restarting racoon).

It's a problem with packages in general.

IIRC, It wasn't as much of a problem on 1.2.3 since the OS packages were a bit older so the ones installed by the newer packages didn't conflict since they were different versions of the underlying libraries.

There has been some discussion about how best to fix it, but nothing done yet.

Problem resolved I believe. there was an extra widget in the widget directory with an .orig extension. Probably residuals from a gitsync or something

Thanks

@ermal:

Can you give me output of:
ifconfig -g openvpn

ovpns1

That happens with apinger every once in a while. Ermal is working on a utility to replace apinger since that seems to be a problem with the program in general.

you can install virtualbox on you server,it`s free and you can use intel server net card (virtual card). :)

I understand the DHCP now, :) ,i try it on my virtualbox.

if you open " Enable DHCP server on LAN interface "  every client can get ip address from pfsense .and every client can access LAN ip.

if you open " Deny unknown clients " just the client in the " DHCP lease table " can get ip address from pfsense.if you are a geust of the LAN , pfsense don`t do anything for you .

if you open  " Enable Static ARP entries " the client can not change ip manual ,if changed client will can not access LAN ip and WAN.

i know why binding IP–MAC must need DHCP service now , focus in " Deny unknown clients " . pfsense think the guest pc should not be get ip from pfsense , but whois guest ? Except the  " DHCP lease table " !

thanks every one answer my topic !! and thanks pfsense open source firewall team .

I've just checked /tmp/rules.debug, all seems to be ok:

# Gateways GWGWFBX = " route-to ( em0 192.168.0.254 ) " ... # User-defined rules follow pass  out log  quick  $GWGWFBX  from any to  74.86.XX.XX keep state  label "USER_RULE"

However traffic is not send to em0 but to ovpnc1

I'm pretty sure there is a bug, can any admin answer me ?

Thanks again!

Hi jimp,
Should this have fixed the failover issue as well? Since updating to BETA4 WAN failover is no longer working correctly.
I have the same issue posted here: http://forum.pfsense.org/index.php/topic,28415.0.html
When a link goes down it will not automatically flick over… im guessing because its not retrieving the info for the gateways?
This is the error appearing in the logs:

php: : Gateways status could not be determined, considering all as up/active.

Also i am running the latest snapshot:

2.0-BETA4  (i386)
built on Sat Sep 18 23:15:00 EDT 2010

Cheers.

I opened a ticket for the alias (really a rule) bug.

http://redmine.pfsense.org/issues/906

redmine repo browsing should be good now.

I'm now up to three screens filled with the above message. It's probably a minor/cosmetic issue concerning the gateway group status, but it sure is annoying. I haven't experienced the cron issue. I rarely get disconnects to determine if it reconnects properly. Probably just a PPOE issue (which I don't use)

Um, current snapshot doesn't even show the captive portal screen. :)

I'm using 2.0-BETA4  (i386) built on Fri Sep 17 14:32:23 EDT 2010

That should work fine.

I'm at Fri Sep 17 14:32:23 EDT 2010 snapshot and the problem (high latency) remains.