Last time it came up there was nothing special to do at all.

The warning about mixing tagged and untagged traffic on pfSense was something we said many years ago because it would cause problems with Captive Portal, among other things. There haven't been any pfSense issues with it in years. That said, there could possibly be something about the switch that makes it impractical or undesirable. That's completely up to the switch, however. Given the choice I'd still avoid it, but that isn't always practical.

No easy way from the GUI, but from the shell (or Diag > Command): pfctl -vvsr | grep xxxxxxx Where xxxxxxx is the ID or any description text

Unfortunately, the panics point to bad hardware, most likely memory: db:0:kdb.enter.default>  bt Tracing pid 3499 tid 100150 td 0xfffff8006a6834b0 kdb_enter() at kdb_enter+0x3e/frame 0xfffffe012113f730 vpanic() at vpanic+0x146/frame 0xfffffe012113f770 panic() at panic+0x43/frame 0xfffffe012113f7d0 pmap_remove_pages() at pmap_remove_pages+0x736/frame 0xfffffe012113f8b0 vmspace_exit() at vmspace_exit+0x9c/frame 0xfffffe012113f8f0 exit1() at exit1+0x65f/frame 0xfffffe012113f980 sys_sys_exit() at sys_sys_exit+0xe/frame 0xfffffe012113f990 amd64_syscall() at amd64_syscall+0x40f/frame 0xfffffe012113fab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe012113fab0 --- syscall (1, FreeBSD ELF64, sys_sys_exit), rip = 0x8008fa14a, rsp = 0x7fffffffec48, rbp = 0x7fffffffec60 --- panic: bad pte va 8008a2000 pte 0 cpuid = 1 KDB: enter: panic The crash is in memory manipulation, an area high unlikely to be a software fault. Furthermore, that panic string indicates a memory location within a page table has spontaneously changed to 0, which wouldn't have happened via software. I checked a couple of the other panics and they were different, but still in random low-level areas that generally point to hardware faults.

@jimp, Changed RAM 5 days ago. pfSense has not crashed once in the past 5 days so it looks like the problem has been solved. I put the suspect RAM in another computer and its been running fine since then as well. My guess is that the old RAM is good, but was not seated well. In changing the RAM, I happened to fix the problem by seating the new RAM properly. Thanks for the help jimp.

My guess is that the USB NIC is the main suspect, I've yet to see one that works well on FreeBSD.

@robi: @jdillard: There is an export to CSV Anybody has an idea what are the values in the first column? The next columns are "packet loss", "delay average", ""delay std. dev.", but the first column header is missing. I was guessing it's Unix timestamp, but it's not, because a calculation from that number gives errorneous results. I need to present a log to my boss, and I can't decode timestamps to absolute time values… It's UNIX time with three extra digits on the end for sub-second precision (not that RRD really needs it…)

@iTestAndroid: What do you mean? NAS is connected to the pfSense firewall and thats the way I want it to be, so data in NAS will be secured and I will have some good controls over it's network and its activities and who's accessing it via pfSense. Do you mean to say that the NAS is on a separate network than your internal users? If the NAS is on the same network as your users, then all traffic forwards at the switch level and shouldn't be affected by pfSense.

Thanks for your reply JorgeOliveira, i saw the post you are linking and i will try it, im just thinking that it must be a bug. The firewall did not have internet access when i upgraded it and i think that may have resulted it this situation.

Thanks so much Derelict :) Working now. Used to be able to do this without gateway groups , hmmmm. Anyways, really appreciate the feedback.

ive used pfblocker to resolve all the google asn numbers via whois and used it in the rules to allow this ASN destinations…not to block...

@peter808: The solution does not work if u have enabled "two-factor-authentification" (so we did) in your Google-Apps-account. The "apps-password" we have generated do not work, showing "Error: 535-5.7.8 Username and Password not accepted.". We tried several different generated apps-passwords, no luck. Any hints? Hi I also have two  factor authentication enabled but unable to send email. I disabled it and enabled access to less secure apps now while m able to relay emails but all are landing in my Gmail address not in mailbox which I specified in  Notification E-Mail address. No email is being sent there. I tried multiple addresses.

Disregard. I missed a firewall rule and resolved my own error.

Outstanding. Thanks for letting us know.

@jwt: We invest tens of thousands of man hours every year developing pfSense.  Do you remember the complaints about how pfSense was always lagging the FreeBSD releases (by a lot)?  Did you notice that we're running FreeBSD 11-ALPHA5 here? Yes I remember.  I was one of the complainers.  Thank you for picking up the pace.

Thanks ! but I don't see the Kernel config files.

Yes,you can use pfBlockerNG.

Gateway IP is automatically assigned when "dynamic" word is written. Go System>Routing New , choose OPT1 and put your gateway there. Or go to Interfaces>OPT1 and put your gateway. if that didn't work try to put static IP for OPT1 interface not DHCP

If you are using google chrome, just try different browser or update pfSense to the latest version 2.3.2_1 which is released yesterday. 2.3.2_1 Features & Changes Worked around a Chrome bug with regular expression parsing of escaped characters within character sets. Fixes "Please match the requested format" on recent Chrome versions.