All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Mohit Mehta <mohit.mehta@vyatta.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] iptables: expose option to zero packet and byte counters for a specific rule using iptables/ip6tables
Date: Wed, 18 Feb 2009 19:40:35 +0100	[thread overview]
Message-ID: <499C5623.7060902@trash.net> (raw)
In-Reply-To: <4994336.27091234914681076.JavaMail.root@tahiti.vyatta.com>

Mohit Mehta wrote:
> iptc_zero_counter/ip6tc_zero_counter are functions available in libiptc to zero counters for a rule in a given chain. However, this is not exposed in iptables/ip6tables. The patch below exposes the underlying function to the user to zero out packet and byte counters for a specific rule.

Exposing this seems useful, the patch doesn't apply to the
current git version though:

8 out of 9 hunks FAILED -- saving rejects to file ip6tables.c.rej
8 out of 9 hunks FAILED -- saving rejects to file iptables.c.rej

Please rediff your patch against the current tree.

  reply	other threads:[~2009-02-18 18:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <13574679.27071234914513480.JavaMail.root@tahiti.vyatta.com>
2009-02-17 23:51 ` [PATCH] iptables: expose option to zero packet and byte counters for a specific rule using iptables/ip6tables Mohit Mehta
2009-02-18 18:40   ` Patrick McHardy [this message]
2009-02-18 20:17     ` Mohit Mehta
2009-02-18 20:22       ` Jan Engelhardt
2009-02-18 20:32         ` Mohit Mehta
2009-02-19 10:21       ` Patrick McHardy
2009-02-19 19:41         ` Mohit Mehta
2009-02-19 20:11           ` Patrick McHardy
2009-08-19 17:56             ` Mohit Mehta
2009-08-19 20:41               ` Jan Engelhardt
2009-09-10 14:26                 ` Jan Engelhardt
2009-09-10 16:24                   ` Mohit Mehta

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=499C5623.7060902@trash.net \
    --to=kaber@trash.net \
    --cc=mohit.mehta@vyatta.com \
    --cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.