Thanks everyone
Seems like it's be easier to just disable it on my two outgoing interfaces.  According to dashboard it is sitting at 81% memory used now with that feature on.

I'll second this issue.  Sometimes I load the Queue's graph and the numbers look reasonable even though smoothing looks too aggressive.  And other times my Wan says it has 200Mbps when the provision is for 5Mbps.  No way to reset the numbers.

Be helpful to know the file that defines the averaging of values in the graph columns.  I'd like the Bandwidth column to average over maybe 3 to 5 samples since the interval is 5 seconds.

Appreciate the help…

I have two tunnels from he.net to two different tunnel servers, one on my DSL, one on Cable, and they both work fine independently or at the same time (NPt helps there).

If they all went down at the same time then one of a few things had to have happened:

Your monitor IP pings were not going over the interface you thought they were Upstream connectivity to the tunnel servers died (Happens a lot when someone decides to DDoS he.net) Something else along the path caused the tunnels to drop

With quite a lot more information about your setup, it may be possible to speculate more accurately about the cause, but there isn't enough to go on there.

the reason i need this is because of another issue not related to this thread, when u create a dyndns entry with interface as wan failover group, sometimes when the wans switch the dns doesnt get updated at all

@phil.davis:

We (a friend at my workplace and myself) are working on some rc.bootup changes to handle low-memory systems better - giving the option to slow down the boot process, checking free memory after each significant process is started and waiting until it stabilises before moving on. We are also thinking about moving the OpenVPN startup until later, as OpenVPN process startups are memory hogs, and it might be best to have all the other essential things up and running before OpenVPN.
Hopefully there will be a proposed code solution later in the week.
If you have any ideas to share to improve the boot process, let us all know.

As i said in the other thread its not openvpn the issue its the php.

If you want to be smart enough you should optimize check_reload_status to check memory conditions or even not fire an similar even if its running.
The simple hack to make all things work on lowmem systems would be to tell check_reload_status to serialize the events and wait for one to finish before starting another.

That will give you predictable behviour on lowmem systems.

Do you mean Firewall Alias?
Firewall Aliases are used in Firewall Rules and other places in the pfSense code. The Firewall Alias name and its associated IP addresses are not added to the DNS hosts file.
(That would be quite difficult to implement generally, because aliases can have other aliases, FQDNs, networks… in them as well as simple IP addresses.)

To get name/IP-address into /etc/hosts, add them to DNS Forwarder, Host Overrides.

@phil.davis:

That code is part of the OpenVPN Client Export package. It sounds like the package did not reinstall after the last firmware update. Look in System->Packages.

You are right! For some reason the last upgrade did not reinstall the packages and had to reinstall them manually, but I completely forgot that the Client Export is a package and not part of the normal install.

Thanks.

Also, pull request has been accepted, so the switch should turn up in the next snapshot.