FIT123 - CASS - Clear a single state - in pfsense 2.0?
-
Hi,
im eager to try pfsense 2.0 on my alix board, there is only one thing holding me back. It is the "Clear a single state" feature from the FIT123 package which is required for my voip adapter to work properly. Does the package work with pfsense 2.0 or is there a feature in 2.0 that does the same?
-
Don't know if this is exactly what you mean, but in the new "Diagnostics: Show States" you can filter states and delete individual ones.
-
thanks for the reply but what CASS in the 1.2.3 package actually does is to monitor your wan-ip address and automatically clears the states for your voip-adapter if the wan-ip changes.
if not i wouldn't be able to receive phone calls after a wan-ip change. (as the old states are still open) i know that there was some talk about to implement such a feature in 2.0 back in 2009 i think, but i'm unable to find it. :( -
A solution has been added to pfSense 2.0 to solve the state problem though it doesn't cover all situation with voip it would be great if you could test and report back.
As the solution isn't working for me I will probably add a CASS for pfSense 2.0 at some point. -
in 2.0 there is:
"Gateway Monitoring
–-----------------
StatesBy default the monitoring process will flush states for a gateway that goes down. This option allows to override this setting by not clearing states for existing connections.
"
under System: Advanced: MiscellaneousIt clears ALL states for the gateway when it goes down though.
-
A solution has been added to pfSense 2.0 to solve the state problem though it doesn't cover all situation with voip it would be great if you could test and report back.
As the solution isn't working for me I will probably add a CASS for pfSense 2.0 at some point.thx for making that clear to me. i will do so in the next week or the week after :)
just in case i would like to use the CASS script manually (/usr/local/pkg/Fit123/CASS.sh) for 2.0. could i simply run it on 2.0 without bigger problems?
as far as i understand its simply executed by cron to run every minute, right?