Thank you.  That seems to have fixed the problem and the settings restore went very smoothly.  pfSense is happy again.

@rcampbell:

This problem still is ongoing for me, I'm using the standard install as a VM on VMWare.  I read the patch was to fix the Nano version, but I believe it still affects the standard version.  Are there any logs I can provide to help get to the root cause?

Nano was OK, the most recent patch was to fix bandwidthd startup on a full install.  Please clarify which pfSense version you installed, and what is shown for the version of your bandwidthd package.

removed myself, just rant :-\

A simple Ctrl+F5 (i.e. refresh of page + dependencies such as CSS) fixed this issue for me. No patches necessary.

Yep. Seems to be working fine as of the Wed Sep 03 16:56:44 CDT 2014 Snapshot. Thanks!

I haven't seen that before. You can check the actual config in /var/etc/openvpn/ to see if the setting is still there.

Make it isn't in your advanced options, too.

I fired up a amd64 VM to test install of packages..

squid-dev3 has starting issues as mattmon pointed out… I'm pretty sure this is due to its last binary update
squid3 pbi package not even on files.pfsense.org, I started a new thread for that
squid2 installed and works (which I was expecting it to work out of the box since its maintained by jimp
dansguardian installed and started up right away. I was able to have it upstream to squid2

@jimp:

Try it now with nrpe-2.15_3

Yay it works!

Beginning package installation for NRPE v2 .
Downloading package configuration file… done.
Saving updated package information... done.
Downloading NRPE v2 and its dependencies...
Checking for package installation...
Downloading https://files.pfsense.org/packages/10/All/nrpe-2.15_3-amd64.pbi ...  (extracting)
Loading package configuration... done.
Configuring package components...
Loading package configuration... done.
Additional files... done.
Loading package instructions...
Custom commands...
Executing custom_php_install_command()...done.
Executing custom_php_resync_config_command()...done.
Menu items... done.
Services... done.
Writing configuration... done.

Installation completed.  Please check to make sure that the package is configured from the respective menu then start the package.

/var/log/dhcpd.log contains a lot of:

dhcp6c[13008]: XID mismatch dhcp6c[13008]: no responses were received dhcp6c[13008]: status code for PD-0: no prefixes dhcp6c[13008]: status code for NA-0: no addresses cat /etc/version.buildtime Wed Aug 27 00:08:55 CDT 2014 cat /etc/version.lastcommit d47fac4a6ffef04e55884ada3066b532e765ba88

I've replicated this on both 2.2 alpha and 2.1.4.

Unticking the dhcp6 box within interface config solves this for me, but I'm not using ipv6.

@mattmon:

I installed from ISO and have an upgrade option on the landing page when I login to pfsense.

Though that might not be an option given the precautions for limiting flash writes on the ALIX…

If the 'live upgrade' feature isn't available, path of least resistance is probably to reflash an updated image.

That's what I wanted to avoid by asking here.
If I have to reflash I might as well go back to stable 2.1.4.
I will instead dig through the changelogs and see if I can patch it on the live machine.

Edit: and I have the latest image from http://snapshots.pfsense.org/FreeBSD_stable/10/i386/pfSense_HEAD/nanobsd/?C=M;O=D installed, just checked that now.

Hey Guys (and Gals?),

I appreciate the feedback, but…

VLANs are OSI layer 2 and firewalls operate at layer 3 - HTTP operates at layer 7...

The 503 response received from the HTTP server indicates both layer 2 and 3 are functional.

That said...

I just reinstalled from the latest ISO and everything is working as expected.

I'll chalk it up to cruft in my pfSense config, lol :-)

Admins - please feel free to delete!

Thank you, upgraded today from last weeks build and it is resolved.

Thought I'd mention I'm experiencing this as well. Have an ISP with native IPv6 through DHCPv6+PD… the WAN interface would get its address (it shows in the interface status page), but the LAN wouldn't, and the IPv6 gateway always showed as down. This happens whether I request a /64 or a /60 from my ISP.

As another data point, this worked fine in the latest 2.1 release version on a different computer... I had to use the 2.2 alpha on my current system due to the new version of FreeBSD resolving a kernel panic issue with my new hardware.

I was able to set up a GIF tunnel with static IPv6 on the LAN and it worked just fine, though. So it seems to be something about IPv6 and DHCP.

EDIT: My issue was not related to this; I had a stray IPv6 tunnel gateway left from importing my 2.1.x config. After removing it, IPv6 with DHCP+PD from my ISP is working properly.

Thanks for the workarounds.  I will give it a try & report back.

It should be fixed on coming snaps.

It seems something on yuor configuration is not proper.

freeradius2 does not start.

/usr/pbi/freeradius-amd64/etc/rc.d/radiusd: WARNING: /usr/local/etc/raddb is not a directory.
/usr/pbi/freeradius-amd64/etc/rc.d/radiusd: WARNING: failed precmd routine for radiusd