All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Netfilter development mailing list <netfilter-devel@lists.netfilter.org>
Subject: [Fwd: ipt_connlimit.c from pom-ng contains error]
Date: Wed, 16 Feb 2005 18:27:09 +1100	[thread overview]
Message-ID: <1108538829.13398.8.camel@localhost.localdomain> (raw)

-------- Forwarded Message --------
From: Zharovtsev, Anton <warm@stack.ru>
To: rusty@rustcorp.com.au
Subject: ipt_connlimit.c from pom-ng contains error
Date: Wed, 16 Feb 2005 13:02:25 +0600
Hello.

I am sorry for writing this letter directly to You and not to the mail list.
I have no time to subcribe and so on ...


This is from 2.4 linux/netfilter_ipv4/ip_conntrack.h:

        /* Our various nf_ct_info structs specify *what* relation this
           packet has to the conntrack */
        struct nf_ct_info infos[IP_CT_NUMBER];

There is no description of such member of struct ip_conntrack in the 2.6 same file ( linux/netfilter_ipv4/ip_conntrack.h )

I am not a programmer, I only applied pom-ng for 2005-02-14 date onto 2.6.10 kernel and I got error:

  CC [M]  net/ipv4/netfilter/ipt_connlimit.o
net/ipv4/netfilter/ipt_connlimit.c: In function `count_them':
net/ipv4/netfilter/ipt_connlimit.c:100: error: structure has no member named `infos'
net/ipv4/netfilter/ipt_connlimit.c:107: error: structure has no member named `infos'
make[3]: *** [net/ipv4/netfilter/ipt_connlimit.o] Ошибка 1
make[2]: *** [net/ipv4/netfilter] Error 2
make[1]: *** [net/ipv4] Error 2
make: *** [net] Error 2
root@wasp:/usr/src/linux#

I will turn off this module, but I think it is very usefull for many peoples and.
This letter is my small bug report :-).

Sorry again.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman

             reply	other threads:[~2005-02-16  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16  7:27 Rusty Russell [this message]
2005-02-17  1:27 ` [Fwd: ipt_connlimit.c from pom-ng contains error] Samuel Jean

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=1108538829.13398.8.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --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.