[nzlug] iptables problems...

Steve Holdoway steve at greengecko.co.nz
Mon Feb 18 20:43:22 NZDT 2008


On Mon, 18 Feb 2008 20:25:22 +1300
Robin Sheat <robin at kallisti.net.nz> wrote:

> On Monday 18 February 2008 20:02:43 Hadley Rich wrote:
> > Another idea that works well when you are messing about with a remote
> > server is adding a cron job 5 minutes away to flush iptables after you
> > commit your changes, just incase you manage to lock yourself out.
> In a similar vein, I always use a script like:
> iptables ... # setting stuff up
> iptables ...
> sleep 30
> iptables --flush
> 
> That way, if it works I can ctrl-c to avoid the flush, if not, it'll do it for 
> me.
> 
> -- 
> Robin <robin at kallisti.net.nz> JabberID: <eythian at jabber.kallisti.net.nz>
> 
> Hostes alienigeni me abduxerunt. Qui annus est?
> 
> PGP Key 0xA99CEB6D = 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D
> 
Heh, got a cronjob flushing everything while testing! Thanks for the info everyone. Off to look at firehol and shorewall to make my life much easier, and spare time much longer! 

Steve

-- 
Steve Holdoway <steve at greengecko.co.nz>



More information about the NZLUG mailing list