too

Denny I just went from 2.2.1 to 2.3.2-release

dpinger also stopped for me and no gateways info in the dashboard

Putting in 60000 on each WAN solved it so thanks (they were 3000)

Hey there, I'm not sure if this is related to your issues but I was having trouble with php-fpm crashes a few weeks back while running on 2.3.2, I also read that people on 2.3.1 were having similar problems.  Unfortunately I don't have the logs from back then anymore to compare with your error messages.

If you're still having trouble try removing the IPSec and/or OpenVPN widget from the web console home page.

I don't know which widget was causing the problem for me but I haven't had any issues for almost 3 weeks now, previously was having an incident weekly.

Firefox and Chrome can both sync autocomplete data :-)

Really though, making it store those on the firewall would be impractical (especially as the command list grows over time). It could be done, but I'm not sure the benefits outweigh the extra disk writes, storage use, code to store/load the commands, potential security issues, etc.

Still doesn't make much sense to me. Ideally they should all be different anyhow and tracked separately (and random, secure, etc). Password managers are tailor made for that role. Perhaps that's why I'm not seeing the benefit – doing what you suggest for the reason you suggest would enable poor security practices.

Fixed in```
2.3.3-DEVELOPMENT (i386)
built on Wed Sep 07 19:32:12 CDT 2016
FreeBSD 10.3-RELEASE-p7

ls -al /cf/conf/backup/*.xml | wc -l

32

i have same problem but i am usuing pfsense 2.3.2 so can i apply same solution for 2.2.2 ?
thanks

Glad that fixed it for you. In the next release (or indeed the current snapshot) the fix was further changed to gain the benefit of Phil Davis' work allowing each user to have their own personalized settings.

Look (and comment) here: https://forum.pfsense.org/index.php?topic=117274.0

No. Exposing any data to a user that is not logged in would be an unacceptable security risk.

Didn't watch that whole video but link points to specific spot in the video talking about SAN.. It only showed IPs not any dns, so its actually good practice to set your common name as a san as well if using them.  It is possible from my understanding that some browsers depending how their makers interpret the rfc that is SAN is used to not use the common name.

So if going to create a SAN, you should do san with your IPs you will be using along with your common name, etc..

For example here is my cert on pfsense.  See it has 2 fqdn dns entries and 2 IPs so I can hit pfsense via one of its other interfaces if I wanted too, that was more of a test example for another thread more than actual need.  And it also has a common name set as just the pfsense.local.lan.

If you do want to hit your pfsense via some other fqdn you will have to adjust pfsense to allow that or you will get a rebinding error, etc.  That would be in System / Advanced / Admin / Alternate Hostnames

san.jpg
san.jpg_thumb

I managed to login to pfSense box, attached is the error notification

There were error(s) loading the rules: /tmp/rules.debug:37: cannot define table pfB_Europe_v6: Cannot allocate memory - The line in question reads [37]: table <pfB_Europe_v6> persist file "/var/db/aliastables/pfB_Europe_v6.txt" @ 2016-08-19 10:03:28

Dynamic update for the OpenVPN widget has been completed and will be available in the next snapshot.

Don't know much about how the internals of PfSense are built, but I do know UDP Video quite well.  I assume this is UDP video traffic ??  FYI, there's plenty of mid-range switches out there from well-known high end vendors that also have issues with UDP streams - mostly those that implement the switch / routing logic in SW rather than HW.

Most likely it's the way the graph data is captured doesn't accurately reflect the outbound NIC buffers.  At 60Mbps, they should be full most of the time and streaming close to the source rate.  Also what's the line rate on the two ports, and what other traffic do you have on there ?

First thing would be to capture the inbound & outbound traffic for 30 seconds or so using tcpdump.  Then analyse the files for timing in Wireshark, which will give a better idea of the actual flows.

That should be OK if you update to 2.3.2. Otherwise, see https://forum.pfsense.org/index.php?topic=111836.msg634122#msg634122

PEBKAC.. pure and simple..

So you don't know how to set permissions on files in your OS of choice?

chmod 777 index.php