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 [image: san.jpg] [image: 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

You can create a ticket in https://redmine.pfsense.org/ and assign to me

If you can get to the console, use option 15 to restore the previous configuration, and then it might take a reboot after that to make sure the right settings are active.

It generally works fine. I've probably done it hundreds of times. Still do it often from ISO files in virtual environments. Not sure what malfunctioned for you.

Cool. This is the best thing to do for now, until there are better options for maintaining specific RRD databases, but that is low priority (for me personally) at this point. Glad you got it figured out.

This topic would best be handled in the Web-GUI Forum, but FYI the auto logout settings are at "System->User Manager->Settings" A search of the Wiki Docs for "logout" or "expire session" would find it.

Check: /etc/inc/authgui.inc line 251 Should be easy enough to poke some extra text in there.

I think I may have figured this out - I have a VPN gateway that was having some packet loss.  I had the "Flush all states when a gateway goes down" option set (generally I do want this). I think that the flapping was causing all states (even LAN->localhost) to be killed and caused the AJAX to timeout.  Does that sound right?