From: Curby <curby@cur.by>
To: Mistick Levi <gmistick@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Check for rule existence
Date: Mon, 14 Jun 2010 11:23:39 -0600 [thread overview]
Message-ID: <AANLkTimA4wYL8mouRjiygbldj9rLui_vhh1zemVRcmQK@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim0fkO6mhQqBlhAsW-I2blxkP36ld0Hk-W3kF42@mail.gmail.com>
On Mon, Jun 14, 2010 at 11:16 AM, Mistick Levi <gmistick@gmail.com> wrote:
> Hi,
> Does anyone know of a good way to check for a rule existence?
> So far I'm doing it with grep, and text manipulation...
Just a quick note that you might want to look at iptables-save instead
of vanilla iptables if you aren't already. The former command gives
the rules in a sort of canonical form that is used for restoring
rulesets. You'll have fewer spacing issues and such. Hopefully others
will have more to add. =)
--Mike
next prev parent reply other threads:[~2010-06-14 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 17:16 Check for rule existence Mistick Levi
2010-06-14 17:23 ` Curby [this message]
2010-06-14 18:22 ` Grant Taylor
2010-06-14 18:24 ` Grant Taylor
2010-06-14 18:25 ` Grant Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimA4wYL8mouRjiygbldj9rLui_vhh1zemVRcmQK@mail.gmail.com \
--to=curby@cur.by \
--cc=gmistick@gmail.com \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).