I searched endlessly yesterday for any posts regarding the new builds - so I just missed it.  Awesome, I feel better now, thanks.

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

If you want to fix this issue without downloading a new snapshot, it's a one liner.
if you're on a nano install, you must make the file system writeable first with

#/etc/rc.conf_mount_rw

Look here:

https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/58cbe016de8cd2e88b08529f6272da849251647a

This was it!

Thanks again!

That did a trick even without restart. Thanks

As you promised it works again, thnx!

that VM was acting up, it's fixed.

That still doesn't look quite right.

A single log entry should look like this:

Jun  9 20:09:27 blooper pf: 00:00:00.001246 rule 2/0(match): block in on em0: (tos 0x0, ttl 1, id 46432, offset 0, flags [none], proto UDP (17), length 361) Jun  9 20:09:27 blooper pf:    192.168.10.3.2314 > 239.255.255.250.1900: UDP, length 333

There have been some oddities on the last few days worth of snapshots, first with the pfSense.so PHP module that handles some IP info, and now with OpenSSL. It's possible that what you are seeing is related to some of the other problems.

I'd try new snapshots for a couple days to see if it persists.

Not currently. The transparent redirect can't be overridden in an easy way.

@leap:

i am using 2.0-Beta2 build on Fri May 21.
Can you please give me the detail how to edit config file?

Go to Diagnostics > Backup/Restore, and download a backup. Open it up in a text editor, and search for parts of the config that reference the pfflowd package. This can get a little tricky if you aren't careful, as if you don't remove things properly it can leave you with a broken config. After you have removed the package info, go back to Diagnostics > Backup/Restore and restore that backup file.

I think the problem is with timing or the order of which the ip address is assigned to OPT2, wireless interface. On a fresh boot, i see the following error message.

Jun 8 18:43:22 miniupnpd[63897]: HTTP listening on port 2189 Jun 8 18:43:22 php: miniupnpd: Starting service on interface: lan Jun 8 18:43:22 php: miniupnpd: Interface opt2 has no ip address, ignoring Jun 8 18:43:22 php: : The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /var/dhcpd/etc/dhcpd.conf em2 ath0_wlan0' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server V3.0.7 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ /var/dhcpd/etc/dhcpd.conf line 23: expecting numeric value. subnet netmask ^ Configuration file errors encountered -- exiting'

Notice miniupnpd also thinks there is no ip address for opt2 but later on, it gets an address.

The same situation. In the Gateway Groups Status WAN marked blue and status Unknown.
If I am create a Gateways like on screenshot all working fine.

gw.JPG
gw.JPG_thumb

I spent most of my time in the BIOS and with different USB keyboards to figure out why I couldn't type anything during the bootup sequence when the mounting of the root failed. Gave up and finally tried to set the vfs.root.mountfrom=ufs:/dev/ad4s1a from the pc-bootloader shell and it worked!

I have a nice Lanner 7530 system with a 30GB gen 1 intel SSD and I'm just starting to play with pFsense again!

I tried to debug this with the people who made the driver..

he said this problem shouldnt occur, i think there must be a problem with the version of freebsd8.. are there any restrictions in freebsd for pfsense?

i had to take the src-> base, sys from freebsd 8.0-release, because i couldnt find them for releng_8, is this a possible reason for this problem? are there any possibilities to get this distributions for the right version?

The quick install has nothing to do with VMware. It's an option for full installs as well. It simply finds the first available disk, and uses the whole disk to install.

The logs on pfSense do not grow. They are a circular log file format which stays a constant size. Some packages might have logs which grow, however.

The provisioning of the disk is up to the user when they create the VM.

Thanks for your help!