The daily snapshots are not signed. Only the releases on the mirrors are signed. This is normal behaviour. If you want/need to use the latest snapshots you need to check the 'Allow auto-update firmware images with a missing or invalid digital signature to be used' box in System: Firmware: Updater Settings. Steve

Awesome!  Thanks a lot for looking in to the issue!   Pfsense 1.3 and 2.0 has been running great for the past several years now (until the old hardware kicked the bucket)!   Can't wait to see  Pfsense running on this 11 year newer Atom PC!

I would let the OpenVPN server up. So you do not have to reconfigure the laptops. I think it will be enough work to put all iphones into IPsec.

I had once the same problem, then i updated pfsense and it was gone. Have you manual outbound nat in use?

I completely understand that I was incorrectly configuring it.  User error!  I have changed the ServerIP to something else (within my internal range) and the IPSEC tunnels stay up when a user disconnects.  I shall keep everything running now to see if it is resolved 100%

@NOYB: Cannot seem to get this to work.  Have it working on a Linux machine (CentOS 5.5 i386), but cannot get it to work on pfSense 2.0 RC3 (FreeBSD 8.1 i386). Is the syntax different? pfSense/FreeBSD is not Centos/Linux. So syntax is quite likely to be different. @NOYB: Shouldn't this work? /etc/inc/interfaces.inc  (wan interface section that creates dhcleint_wan.conf) /var/etc/dhclient_wan.conf option V-I-Vendor-Specific-Information code 125 = string;   send V-I-Vendor-Specific-Information 00:00:0d:e9:1f:01:06:30:30:30:46:42:33:02:0c:30:30:31:38:30:31:35:31:45:42:33:34:03:07:4d:49:34:32:34:57:52; See previous answer. On PfSense many of the individual application configuration files are regenerated on startup from the system master configuration file. Since you are apparently modifying /etc/inc/interfaces.php you should be able to get around this issue. You should consult the FreeBSD man page for dhclient (in FreeBSD 8.1 and ports) and the linked pages especially dhclient.conf and dhcp-options for information on how to specify dhcp options to dhclient. Your changes to interfaces.inc will be lost on every firmware update so it will probably be worthwhile looking for a more robust solution to your particular problem.

@jits: The ISP told me they hard coded for 100MB Full Duplex That means you must set your interface for 100 full, otherwise you end up with a duplex mismatch.

Okay, so this issue could be due to VirtualBox VM connectivity issue, but I had someone at work complain Friday evening and Saturday that they would get kicked off after about 15 minutes using their pc.  I tried to test things on "PC" since I use macbook to connect via VPN and have never had a problem.  I tested it on another pc at home and was on for almost 40 minutes with no problems, so I'm chalking up to VirtualBox and maybe that I needed to reboot the pfSense system.  Other than that one person I have not heard of anymore problems, but I made the last update Friday evening and not many people have got on since then.  If no one else is having this problem, then it's probably my setup. Thanks!

Will the virtio driver be included in the final release of PfSense 2.0? It's mentioned in this (http://forum.pfsense.org/index.php/topic,34911.0.html) thread that it's included since 2.0 but I won't get it working only by installing it manually. "We have added this driver to 2.0.  Please test a new snapshot and it should be present sometime tomorrow."

Think I found some similar issues today. We created a new machine yesterday with the latest RC. We have a ppoe connection and set it up.  We did not check the dial on demand box and made no entry in the time out box. It connects with no problem.  Surf the web just fine.  Then we started setting up our vpn connections.  Never could get it to connect. Looked back in the support notes and had similar problems at this location before.  We were told to use an mtu of 1492 by the isp in the past so we decided to try that.  Then the fun begins.  When we entered the mtu sized and tried to save we were now required to enter a timeout value. So we checked the on demand and used 0 as it suggests.  Then we are able to save.  At this point things are still fine you can surf but not vpn yet.  So we decided to shut it all down and reboot.  When it comes back up the WAN interface is disabled.  Look at the screen for the wan and it does not show disabled but dashboard shows disabled and no internet connections. The only way I got around it was to use the console and reset to factory defaults.  The console shows the lan and wan ports still attached to their original settings. We went through this for several hours and as long as we did not change the mtu settings no problems with shutdowns and reboot.  As soon as we set a value in the mtu setting boom wan disabled. We have around 30 astaro and endian boxes out there and really want to move to pfsense.  What other information can we provide to help with this. THX LW Then we were having problems with vpn connections and in the past had used an mtu of 1492 for this provider. System showed no errors and conn

@dfwbt: Ok, Using the info found in here, and an old x500 laying around my house, I have come up with this "Band Aid" solution…. ... wget http://www.cps-texas.com/serialbandaid.sh Great! Thanks a lot!

Hi, Thanks for you answer, I read about that when I try in put back my configuration, and I check for it. I don't found any special character. Totoux

Just fyi - the unbound package is updated. Which now correctly listens on the loopback address when it has been selected.

@johnpoz: what about ability to add ipv6 in the ACLs? ;) heh :) the page is here in my repo. I just need to polish it off before i submit it to the masses.

@ermal What is the best procedure for you ? and where i can put the file ?

Fixed thanks.

Removed the wrongly slipped in 'ms' text :) For the weight it does not hurt to be in advanced options for now. Maybe it can be changed later on but for now an extra click is needed.

Zoneedit support responded with No known ddns issues at this point. They have never let me down in the past but there is always a first. I replyed back and told them I did another force update and checked my zones, nothing changed. What I did was I made a change to a few of my domains and Dynamic DNS did a resend System log tells me that my current IP extracted from checkip.dyndns.org updating cache file /conf/dyndns_wanzoneedit"–my domaines-- .cache: current IP (Success) IP Address Updated Successfully! Is the local cache being updated or is it telling me it thinks the zoneedit domins have been updated? I ask because everything was working untill the reboot after this morning's pfSense update.