> Any time you are fiddling with iptables, it would be prudent to add > something like this to root's crontab: > > # Min hour DOM month DOW command > */05 * * * * /etc/init.d/iptables stop > > In case you "blow it," you can get back in within 5 minutes.
Or make your changes to the iptables config file, then run: /etc/init.d/iptables restart; sleep 15; /etc/init.d/iptables stop Note: This must all be typed as one line. The "restart" flushes the rules and loads the new ones. Then your script sleeps for 15 seconds. If everything went fine and you haven't shot yourself in the foot, simply hit "control-c" to abort the script. If your foot is bleeding profusely, just wait 15 seconds and you'll have access again when "iptables stop" runs. The crontab trick is neat, but you can set yourself up with some possible race conditions. -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-biz mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-biz
