If you upgraded from 2.3 beta, you may still have 250ms as the polling interval. This was the default earlier in the beta process. The current default is 500ms. FWIW, by default dpinger uses a data payload of 0 bytes, so the packets are much smaller than a standard ping which is a 56 byte payload.

Thank you. I will read and try it. Best,

I had no problem with this board. I followed an instruction in the forum. Gently –-- <soapbox>Just because it worked and you "had no problem" doesn't mean it's a good idea.</soapbox>

I guess that's why people have been asking for the ability for that screen to "remember" what you last used.

Yep, memory test is another good suggestion. Along those lines, you might look in the GFX section of the BIOS, see if you can decrease the shared memory usage (for Video) down to as little as possible. pfSense is a text only console, it doesn't need large amounts of memory for graphics.

Have you tried to shell into the box? Will it respond to pings on either LAN or WAN? Do you have access to the console? Is this bare metal (what type?) or VM?

@cmb: No change between versions there. Guessing maybe you have manual outbound NAT configured and it doesn't cover that VLAN's subnet out WAN. Hmm you are correct, 1 rule has been missing from outbound NAT, must have been due to new GUI and I probably hit the wrong icon to copy+add new. I have another issue I'm investigating, I will update once I figure out if it's a true bug or not.

maybe they stayed at a holiday inn express last night?

Either the disable of rules or uninstall of Snort fixed it temporary. Now I can test the interface at least :)

https://forum.pfsense.org/index.php?topic=110981.msg617964#msg617964 You can look at the current version: https://github.com/pfsense/FreeBSD-ports/pull/120

It looks like disabling SMP is an immediate workaround for the problem while we track down and fix the root cause. https://forum.pfsense.org/index.php?topic=110953.0

"user@user-vivid:~$ nmblookup -M local name_query failed to find name local#1d" Really???  How dense are you?? Where my local example would be the workgroup your using "all computers on one lan 192.168.0.1 to 192.168.0.50" What does that have to do with a bridge setup in pfsense??

Bacula can't pull from the server. It needs a connection from the server to Baculas storage daemon. I did create a rule, but couldn't get it to work. I forgot to move it to the top. After I did that everything is working perfectly.

Went ahead to install Squid, SquidGuard and LightSquid in that order. Seems to work ok.