search for: stoppedrules

...39;${VARDIR}/${PRODUCT}''. When a pre-4.5.8 shorewallrc file is present, VARLIB is set to ${VARDIR} and VARDIR is set to ${VARLIB}/${PRODUCT}. If VARLIB is set in the shorewallrc file and VARDIR is not, then VARDIR also defaults to ${VARDIR}/${PRODUCT}. 2) A new ''stoppedrules'' file has been added and the ''routestopped file is now deprecated. See stoppedrules(5) for details. 3) When the -e option is specified, the current working directory is now included in the CONFIG_PATH. Thank you for testing, -Tom -- Tom Eastep \ When I die, I wa...

...39;${VARDIR}/${PRODUCT}''. When a pre-4.5.8 shorewallrc file is present, VARLIB is set to ${VARDIR} and VARDIR is set to ${VARLIB}/${PRODUCT}. If VARLIB is set in the shorewallrc file and VARDIR is not, then VARDIR also defaults to ${VARDIR}/${PRODUCT}. 2) A new ''stoppedrules'' file has been added and the ''routestopped file is now deprecated. See stoppedrules(5) for details. 3) When the -e option is specified, the current working directory is now included in the CONFIG_PATH. Thank you for testing, -Tom -- Tom Eastep \ When I die, I wa...

Hi, My main gateway is a router running on OpenWrt Barrier Breaker r37816/ Kernel Version3.10.4. I installed shorewall-lite from openwrt''s repo using opkg but while trying to start shorewall-lite I get the folowing errors: The first error i got was "scp: /var/lib/shorewall-lite: No such file or directory" simply resolved by making the folder "shorewall-lite"

Hi, I have a multi-isp configuration both on ppp interfaces. As one of them is 32Mbit/s and the other is 8Mbit/s , I have a weight setting of 4 to 1 as in the following providers file entries: vdsl 1 0x10000 - ppp1 - track,balance=4 adsl 2 0x20000 - ppp0 - track,balance=1 I would also like to have fallback between them so that if one is

...includes a patch from Tuomo Soini that corrects the problem. 8) The ''debug'' keyword is no longer ignored by the ''try'', ''stop'' and ''clear'' command executors. 9) Using the ''NOTRACK'' action in the stoppedrules file was previously broken when $FW was specified in the SOURCE column. In such cases, the generated rule was being placed incorrectly in the filter table rather than in the raw table which resulted in a failure of the ''stop'' and ''clear'' comma...

...includes a patch from Tuomo Soini that corrects the problem. 8) The ''debug'' keyword is no longer ignored by the ''try'', ''stop'' and ''clear'' command executors. 9) Using the ''NOTRACK'' action in the stoppedrules file was previously broken when $FW was specified in the SOURCE column. In such cases, the generated rule was being placed incorrectly in the filter table rather than in the raw table which resulted in a failure of the ''stop'' and ''clear'' comma...