On 06/21/2017 09:37 AM, Norman Henderson wrote: > Thanks very much Tom, see further comments below. > > On Wed, Jun 21, 2017 at 4:15 PM, Tom Eastep <[email protected] > <mailto:[email protected]>> wrote: > > On 06/20/2017 11:21 PM, Norman Henderson wrote: > > Thank you for this Tom. The "persistent" option is a good help, although > > it has the side effect that on reload etc. Shorewall will try to > > re-enable the provider, which is not desirable if it is flaky e.g. can > > be enabled but won't pass traffic. > > That isn't intentional. I'll take a look. > > > I was basing the comment on the following > from shorewall.net/manpages/shorewall-providers.html > <http://shorewall.net/manpages/shorewall-providers.html>: > > > Note > > The generated script will attempt to reenable a disabled persistent > provider during execution of > the *start*, *restart* and *reload* commands. When |persistent| is not > specified, only the *enable* and *reenable* commands can reenable the > provider. >
That behavior is overridden by the isusable extension script shown in the Multi-ISP documentation. -Tom -- Tom Eastep \ Q: What do you get when you cross a mobster with Shoreline, \ an international standard? Washington, USA \ A: Someone who makes you an offer you can't http://shorewall.org \ understand \_______________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
