On Sunday 13 May 2012 02:09:56 pm Tom Eastep wrote: > On 5/12/12 10:12 AM, John McMonagle wrote: > > On Saturday 12 May 2012 09:47:50 Tom Eastep wrote: > >> On 05/11/2012 02:04 PM, Tom Eastep wrote: > >>> On 05/11/2012 11:52 AM, John McMonagle wrote: > >>>> eth2.status did not change. > >>>> Got up email from lsm. > >>>> > >>>> Obviously missed something :-( > >>>> > >>>> Do you see anything or have suggestions on how to debug? > >>> > >>> - Set STARTUP_LOG=/var/log/shorewall-init.log > >>> - Set LOG_VERBOSITY=1 > >>> > >>> Look at the log while testing to see what is going on. > >> > >> I've discovered that the 'disable' command is not altering the .status > >> file. Patch attached. > >> > >> patch /usr/share/shorewall/Shorewall/Providers < STATUS.patch > >> > >> -Tom > > > > Thanks Tom > > > > It may be a week before I can try it. > > It's not the sort of thing I want to try remotely. > > You'll want this patch also. > > patch /usr/share/shorewall/lib.core < ISUSABLE.patch > > -Tom Tom
Seems to work. The provider is removed after about 20 seconds after failure. It returns a bit over 3 minutes after being plugged back in. Seems a bit long. Is that intentional? Thanks again. John ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
