All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Gervasio Bernal <gervasiobernal@speedy.com.ar>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: New target: can't delete rule
Date: Tue, 13 Sep 2005 01:24:21 +0200	[thread overview]
Message-ID: <43260E25.6020600@eurodev.net> (raw)
In-Reply-To: <1126553016.15667.0.camel@Pentium>

Gervasio Bernal wrote:
>     I did what you said, but I cannot make walk it. 
> 
> This is my libipt_CRYPT.c 
> 
> static struct iptables_target CRYPT 
> = { 
>     .name            = "CRYPT", 
>     .version         = IPTABLES_VERSION, 
>     .size            = IPT_ALIGN(sizeof(struct ipt_CRYPT_info)), 
>     .userspacesize   = offsetof(struct ipt_CRYPT_info,
> table_alloc_ptr),        
>     .help            = &help, 
>     .init            = &init, 
>     .parse           = &parse, 
>     .final_check     = &final_check, 
>     .print           = &print, 
>     .save            = &save, 
>     .extra_opts      = opts 
> }; 
> 
> 
> This is my ipt_CRYPT.h 
> 
> struct ipt_CRYPT_info 
> { 
>         char key[MAX_KEY_SIZE]; 
>         unsigned int block_size; 
>         unsigned int key_size; 
> 
>         struct tabla_alloc* table_alloc_ptr; 
> }; 
> 
> struct tabla_alloc 
> { 
>         struct crypto_tfm *tfm; 
>         struct tabla_alloc* next; 
>         struct tabla_alloc* ant; 
> }; 

It looks fine. Which iptables version are you using? If my mind servers
well, I remember that there was a bug related with targets and the use
of userspacesize in old iptables versions (<= 1.3.1). If so, please try
with the lastest update.

--
Pablo

  reply	other threads:[~2005-09-12 23:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 18:09 New target: can't delete rule Gervasio Bernal
2005-09-07 22:30 ` Pablo Neira
2005-09-07 22:34   ` Patrick McHardy
2005-09-07 23:58     ` Pablo Neira
2005-09-12 19:23   ` Gervasio Bernal
2005-09-12 23:24     ` Pablo Neira [this message]
2005-09-12 20:45       ` Gervasio Bernal

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=43260E25.6020600@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=gervasiobernal@speedy.com.ar \
    --cc=netfilter-devel@lists.netfilter.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.