hi,
I also applied the patch on shorewall 4.5.21.6 using "patch
/usr/share/shorewall/Shorewall/Misc.pm ADMINISABSENTMINDED.patch".
If I use hosts listed in the routestopped file(deprecated) the
traffic is allowed as expected but if I use the stoppedrules file the
connections are refused no matter what rules I put in the
stoppedrules!
In other words with the patch installed I can no longer use the
stoppedrules file to determine which hosts should still have access
through the firewall when it is stopped.
-Matt
On 28 Feb 2014 at 10:13, Tom Eastep wrote:
> On 2/28/2014 9:05 AM, Hervé Werner wrote:
>
> > I'm getting trouble with the ADMINISABSENTMINDED option, it doesn't seem
> > to work as stated in the manual.
>
> >
> > I launched Shorewall with the default ADMINISABSENTMINDED value and
> > stopped it. I then did again the same test with ADMINISABSENTMINDED=No.
> >
> >
> > Do you agree or did I misunderstand the manual ?
> >
>
> I believe that the attached patch will correct the problem.
>
> -Tom
> --
> Tom Eastep \ When I die, I want to go like my Grandfather who
> Shoreline, \ died peacefully in his sleep. Not screaming like
> Washington, USA \ all of the passengers in his car
> http://shorewall.net \________________________________________________
>
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
