Might be an issue with your storage media.
Check logs to find read/write errors

if you are still running 2.2.x you might be running the liveCD

Agree to this. So you can have multiple alias in one rule, would have saved a lot of time. FortiGate does this as well.

Use the "Notify" button.

You, also, have "some" settings about "Notifications" at you "Profile"

Notify.png
Notify.png_thumb
Notifications.png
Notifications.png_thumb

I too had a frictionless upgrade, mine from v2.2.6.  The new dashboard widget for the nut package works great, too.

Dpinger itself logs an alarm when one or more of the alarm thresholds are crossed. The alarm could be triggered by latency, loss, or both. Another log entry occurs when all alarm thresholds have cleared. Regardless of the trigger for the log entry, current values for latency, stddev, and loss are included in the log message.

In the first example below, the alarm was triggered by loss alone. The second was triggered by latency, and the third by latency and loss simultaneously.

May 6 01:23:45 dpinger Wan X.X.X.X: Alarm latency 8558us stddev 0us loss 50% May 6 01:23:55 dpinger Wan X.X.X.X: Clear latency 10303us stddev 2179us loss 0% Apr 2 09:20:35 dpinger Wan X.X.X.X: Alarm latency 7348934us stddev 9549263us loss 0% Apr 2 09:21:28 dpinger Wan X.X.X.X: Clear latency 46087us stddev 75340us loss 0% Apr 2 09:08:46 dpinger Wan X.X.X.X: Alarm latency 9501506us stddev 11277451us loss 22% Apr 2 09:10:05 dpinger Wan X.X.X.X: Clear latency 39669us stddev 56618us loss 1%

Note that the alarm threshold and alarm decay for latency and loss are tracked independently, so it is also possible to see multiple alarm messages without an intervening clear message. I don't have a good example of that to hand.

If you are seeing alarm messages in the gateway log, but no corresponding clear messages, it is likely that the system is restarting the dpinger instance prior to the clear message being logged. If this is the case, you should see the dpinger startup entry in the log.

If you have packages installed that are outdated, yes they'll also be updated in the process. We'll have to clarify that in the future, showing which packages will be upgraded.

People tend to react against change. IIRC something with Newton's 3rd law

The other famous quote that could be applied in this particular case: "If it ain't broke, don't fix it"

I do like the general concept of keeping the forum and product "in sync" as far as look and feel.

The problem for me is that I personally find the White on Black format harder on the eyes.

For pfSense:the product I can set up the themes the way it works best for me and carry on.
For pfSense:the Forum, presumably we're all stuck with whatever format gets picked as the consensus.

Unless there's an option to change the forum "theme" to what you personally prefer (translate: what's easier on your eyes) I vote, leave well enough alone.

Just my $.02

If you have to disable IPv6 to get Google Play downloads to function, then it sounds like there might be an issue with the IPv6 settings on your WAN or LAN interfaces, or your ISP is having issues.

Some ISP's in the US are still in the process of deploying IPv6 (and there are some that still haven't even started rolling it out). You might get an address, but it may not be a stable connection as they continue to roll it out throughout an area. Or if you have an ISP that isn't supporting it, you might need to disable it on your LAN interface to make sure that the router isn't advertising itself as an IPv6 router.

How to remove references to old packages:
https://forum.pfsense.org/index.php?topic=110096.msg613137#msg613137

Actually probably a better post if it was put either in general or packages forums but-

https://forum.pfsense.org/index.php?topic=8640.msg48501#msg48501

so in other words, everyone is saying. your feedback is stupid, you are dumb and get the hell off my forums.

You're entitled and encouraged to offer feedback.  Others can either agree or disagree, with reasons.  That's how public discourse works.  If you can't handle differing opinions expressed civilly without feeling like you're under attack, well… I don't know what to tell you because nobody said your feedback was stupid nor did anyone ask you to leave.  My belief is that pfSense is aimed at professional environments under the control of professional network staff.  You have to know what you're doing or you're not going to get the desired results.  You can only simplify complex subjects so much.  Wizards just either get in the way or limit your options.

Same here - love it! Great work.

@jimp:

pfSense logs are only stored in /var/log, not "all over the place". There may be some packages that break that convention but they are the exception, not the rule, and the packages should be fixed if they are doing that (where possible), or at least under /var/.

A custom install allows for creating multiple partitions and such, though using a second disk isn't so simple. We have plans to revamp the installer soon, so that might show up, but it's too soon to say.  For those that need/want to use a second disk, formatting and adding it to fstab is fairly easy for the technically inclined.

What I meant for "All over the Place" was in the GUI. You have to click around through some of the different functions to find the logs. My suggestion; which is still valid by the way, is to move the log directory to a secondary disc that has a catalogued files system specifically for logs and create a central location in the GUI to manage and clear ALL logs.

@maverick_slo:

Lol.
But my solution works you know…
Tested :)

Truthfully the only way I see my firewall having problems while Im out of town is a hardware failure. Since my wife nor any of our kids will probably not be trying be configuring the firewall in my absence.    ;D

Your solution seems the most logical.

But in any event.  jbhowlesr -  download putty and learn it while you have a chance.

https://www.youtube.com/watch?v=krNuKDGEjvQ

@jdillard:

@jwaz:

It seems I'm not able to access anything but the latest Hangout

It is most likely an issue with a browser plugin that you are running.

Indeed, in this case it was EFF's Privacy Badger. Thanks j