fixed, thanks

Fixed, only files that ends with .js will be considered.

Getting the same thing on a 4G Alix 2D13 upgrade..

Status: RRD Summary is wrong again. As of the most recent update.

Screenshots of your rules, or the contents of /tmp/rules.debug, and some details of what was changed recently would help someone to find out why there are errors loading the rules.

I added:

hw.ix.rx_process_limit=1024
hw.ix.tx_process_limit=1024
hw.ix.txd=4096
hw.ix.rxd=4096

For a single thread this made zero difference; I still see just about 2 Gbit/s.  With 4 threads it now hits somewhere between 3.3-4.0Gbit/s (very inconsistent).  Single-threaded bidirectional tests (-c -d & -s) hit about 3Gbit/s and dual-threaded bidirectional tests hit around 4Gbit/s (-c -d -P2 & -s).  For some reason trying to use 4 threads on a bidirectional test makes iperf segfault so I can't try that.

Reverting hw.intr_storm_threshold to the default of 1000 made no difference (I changed this in FreeNAS to get past ~2.5Gbit/s, if memory serves, assumed the same would be required here since it's mentioned in the pfSense Wiki Docs).

Disabling AIM with setting dev.ix.0.enable_aim & dev.ix.1.enable_aim to "0" also didn't have any impact.

Looking at the IP Alias in the raw XML file it appears that the IP Aliases would probably work if I rebooted the firewall or disable and reenable carp on the primary.  They are assigned to the CARP IP as wan_vip1.  I just tested this and it does work after doing that so…

I guess the problem in the scenario above is that changing the CARP IP does not force any aliases assigned to it to be added back again until you manually edit each alias or you disable/reenable carp (or reboot).

There is no need to edit each Alias when you change a CARP IP because the config goes by the interface name and not by IP.

To sum up...  We need IP Aliases assigned to a CARP IP to be added back when you change a CARP IP...  otherwise you can cause the secondary server to get PRIMARY status for the interface that you change.  You end up with primary with MASTER status for all interfaces and the secondary server as MASTER for the interface you change the CARP IP on and BACKUP for all the rest.

EDIT:  I am sure it is easier said than done and I am not sure if there are still other issues.  I looked at the secondary after making a bunch of changes on the primary and the secondary still had an old ip that was changed on the primary.  The secondary had 1 more IP on wan_vip1 than the primary.  A disable and re-enable of CARP on the secondary fixed it.

Nope.

Hi

Is the "j.php", the jumpto redirects to a webserver with problematic php.ini config?