Re: Frequently-changing IPs

johnny bowen
2013-08-19T19:40:44Z

Putting it in the shorewall-init won''t do you any good because that
only
gets called when Shorewall is being started|restarted. Remember Shorewall
is not a daemon process, so there isn''t active monitoring going on. So
if
you''re having IP''s change from time to time you''re
going to have to set up
the monitoring solution.

Cron is an obvious choice, but there are several other implementations.

Thanks for the tip on Ipsets. I wasn''t familiar with it, but I took a
look
at it and I like it. It lead me here:
This looks like the appropriate solution for you:

http://www.shorewall.net/Dynamic.html






On Mon, Aug 19, 2013 at 2:37 AM, Igor Sverkos
<igor.sverkos@googlemail.com>wrote:

> Hi,
>
> I like the idea, but:
>
> 1) I would put it into the ''script'' part of shorewall
(for example the
> "init" file)
>
> 2) Add error checks: dig may fail sometime...
>
> ...and I would use ipsets.
>
> ipsets can be updated from an independent cronjob for example. Almost
> instant, without the need to touch the configuration.
>
>
> --
>
> Regards,
> Igor
>
>
>
>
------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It''s a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
>
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Shorewall-users mailing list
> Shorewall-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shorewall-users
>
>


------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!