Thank you.  Think that is clearer.
 

[alarm will fire]

 
Is there a difference between “alarm will fire” and “gateway is down”?  Seems that would be the only way both statements could be true when frequency probe (interval) is something other than 1.
 
Agree the probe interval would be better label.
 

 
Go back to bed and get up on the other side.
 
Saw the fix.  Will test it later.  Fully expect that it will correct the issue.
 

 
Noticed recently after a reboot that the RRD backup file /cf/conf/rrd.tgz was gone.  However the DHCP leases file /cf/conf/dhcpleases.tgz was still there.  Seems like this would be vulnerable to RRD loss if there were a system crash before the next backup cycle completes.
 

 
http://www.freebsd.org/
Documentation - Manual Pages is your friend...
 
http://www.freebsd.org/cgi/man.cgi?query=date&apropos=0&sektion=0&manpath=FreeBSD+8.3-RELEASE&arch=default&format=html
 

[Warning]

 
Warning - The following rrdtool commands will reset the gateway quality RRD and all existing data will be lost.
 
Apinger sets the gateway quality RRD's like this.  Which is not consistent with the other pfSense RRD's.

Code:

rrdtool create /var/db/rrd/WAN_DHCP-quality.rrd \
DS:loss:GAUGE:600:0:100 \
DS:delay:GAUGE:600:0:100000 \
RRA:AVERAGE:0.5:1:600 \
RRA:AVERAGE:0.5:6:700 \
RRA:AVERAGE:0.5:24:775 \
RRA:AVERAGE:0.5:288:796 \

To make the gateway quality RRD's consistent with the other pfSense RRD's, you might try this:

Code:

rrdtool create /var/db/rrd/WAN_DHCP-quality.rrd \
--step 60 \
DS:loss:GAUGE:120:0:100 \
DS:delay:GAUGE:120:0:100000 \
RRA:AVERAGE:0.5:1:1000 \
RRA:AVERAGE:0.5:5:1000 \
RRA:AVERAGE:0.5:60:1000 \
RRA:AVERAGE:0.5:720:3000 \

Replace "WAN_DHCP" with the target gateway's name.
 

 
System: Advanced: Miscellaneous - RAM Disk Settings
 
Would it be possible to also backup the Firewall Logs?
 

 
Says down value is "The number of seconds of failed probes before the alarm will fire. Default is 10."
 
Then at the bottom of the Advanced section it says this.  "The total time before a gateway is down is the product of the Frequency Probe and the Down fields. By default this is 1*10=10 seconds."
 
If the default frequency probe value (1) is used, then both of those statements are true.  But if it is changed from the default value, then both of those statements cannot be true.
 
Which one is true?  And shouldn't the other one be corrected or removed?
 
 
Some previous discussion:
Gateway Monitoring (Advanced - Down)
http://forum.pfsense.org/index.php/topic,51604.0.html
 

 
1) Does not prevent account from WebConfigurator login.  Just restricts access to WebConfigurator pages.
 
2) Only works for OpenVPN connection access.
 
3) Not difficult to find the changed and non disclosed WebConfigurator port.
 

 
Is it possible to turn off Web Configurator login capability for OpenVPN user accounts?
 

 
Have done this one several times with no problem.
 
2.1-RC0  (i386)
built on Sat Jun 8 06:42:11 EDT 2013
 
(USB memstick image installed to USB Flash drive)
 

 
It really is RAM rich.  An old notebook with 2 GB.
 
What started the thinking about this is that the Quick/Easy install creates a 2 GB swap space, and was thinking about using a 2 GB USB Flash stick.  And 2GB swap space seemed kind of excessive considering it will never get used under normal circumstances (except for a crash dump).  Can’t remember the last time that happened aside of me doing something stupid.
 
But the 2GB USB Flash stick is off the table now anyway, because the ones I have write too slow.  Read is marginal.
 

 
What are the advantages and disadvantages of running a full install with no swap space on system with plenty of physical memory such that everything fits and swap space should never be needed?
 
Would there be any advantage for say USB Flash drive longevity running full install?  Would swap space even get written to at all?
 
The obvious disadvantages I guess is no crash dump reports with no swap space.
 
What are others?
 

 
Figure that since the http-proxy option is already there it shouldn't be to much to just make proxy type selectable.  (http proxy or socks proxy)
 

 
Yup that's what I thought.  Thanks for the confirmation.  Sure would be nice, and cleaner, if a single instance could be used for both.
 
So if allow connected clients to communicate is enabled will the clients of each instance be able to also communicate with clients of the other instance?