Thanks for your answer. You are right i use pdfsense 2.1.3. I will try to install pfsense 2.2  :)

@jimp:

update again (pfctl -d and then run the upgrade if you're broken)

I backed out the changes from yesterday and made a new snap, looks to be ok so far.

Looks good here. I'm now running on 20140513-0829 and not seeing any issues.

That will be the general packages issue that Jim posted about at https://forum.pfsense.org/index.php?topic=76632.0 - I guess @MarcelloC might get it fixed, or you could make the necessary changes and submit a pull request on GitHub.

@jimp:

See the many other threads on packages here on this board. You have to disable package signing checks at the moment.

Ok, It done.

Thank you

Ok. Thanks, sorry for the dupe.

And a fine addition it is…  :) . It just makes things clearer when all times in the GUI refer to the same time(zone), I think.

While 6rd does not work yet (see other reports and posts, effectively boiling down to https://redmine.pfsense.org/issues/2882), setting up the 6rd config on wan does no longer cause spontaneous reboots. This thread can be retired.

While 6rd does not work yet (see other reports and posts, effectively boiling down to https://redmine.pfsense.org/issues/2882), setting up the 6rd config on wan does no longer cause spontaneous reboots. This thread can be retired.

Thanks, yes.

While 6rd does not work yet (see other reports and posts, effectively boiling down to https://redmine.pfsense.org/issues/2882), setting up the 6rd config on wan does no longer cause spontaneous reboots.

What could be the manual process to add the u3g0 interface as a virtual ethernet interface on my testing device ?

ok thanks

Yes, provided you use the new "pfsense_ng_fs" theme.

It was working but had broken again… This morning it appears to be OK. The rule lookup code is fixed in the repo now, the current snapshot will do rule lookups when you click on the action icon, but the row/column description display doesn't work until the commit I pushed a few minutes ago.

So by the next snapshot (or current snap + gitsync to master) it should be OK all around.

Shows correct date now. Will try this image tonight.

(Edit: Thanks for giving me a reason to reply, turns out this post made me go from Newbie to Jr. :-)

Yes known issue.
That screen will rather change a bit for 2.2

@JoelC707:

Why did it change in the first place?

Because it was broken in the first place?  :D

https://redmine.pfsense.org/issues/3484

Hey all.
I know this says version 2.1.3, but this person is having the same exact problem as I am with the x64 build.
https://redmine.pfsense.org/issues/3635

Looks like a BIOS issue with that board/chip. A BIOS update or tweaking the ACPI options in there may help.