All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Andi Kleen <ak@muc.de>
Cc: netdev@oss.sgi.com, coreteam@netfilter.org
Subject: Re: [PATCH] Fix ipchains/ipfw modules
Date: Fri, 24 Sep 2004 12:15:08 -0300	[thread overview]
Message-ID: <415439FC.10401@conectiva.com.br> (raw)
In-Reply-To: <m3fz57915u.fsf@averell.firstfloor.org>

Patrick McHardy fixed this in a different way in the "Re: [PATCH] Warn 
people that ipchains and ipfwadm are going away." lkml thread :-)

His explanation:

"Fixed by this patch. The conntrack protocols need ip_ct_log_invalid
which is defined in ip_conntrack_standalone, so ip_conntrack is
loaded automatically before ipchains. This patch moves it over to
ip_conntrack_core."

- Arnaldo

Andi Kleen wrote:
> ipchains didn't load anymore because it had a undefined symbol,
> which was satisfied by ipconntrack. This caused ipconntrack to be
> loaded first by modprobe, but the second ipconntrack init in ipchains
> would fail, causing the ipchains load to fail.
> 
> ipfw had the same problem.
> 
> Declare the missing variable.
> 
> Signed-off-by: Andi Kleen <ak@muc.de>
> 
> diff -u linux/net/ipv4/netfilter/ip_fw_compat.c-IPC linux/net/ipv4/netfilter/ip_fw_compat.c
> --- linux/net/ipv4/netfilter/ip_fw_compat.c-IPC	2004-06-16 14:07:34.000000000 +0200
> +++ linux/net/ipv4/netfilter/ip_fw_compat.c	2004-09-24 15:56:55.000000000 +0200
> @@ -28,6 +28,8 @@
>  
>  static struct firewall_ops *fwops;
>  
> +unsigned int ip_ct_log_invalid;
> +
>  #ifdef CONFIG_IP_VS
>  /* From ip_vs_core.c */
>  extern unsigned int
> 
> 
> 
> 
> 
> 

  reply	other threads:[~2004-09-24 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24 14:44 [PATCH] Fix ipchains/ipfw modules Andi Kleen
2004-09-24 15:15 ` Arnaldo Carvalho de Melo [this message]
2004-09-24 18:07   ` David S. Miller

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=415439FC.10401@conectiva.com.br \
    --to=acme@conectiva.com.br \
    --cc=ak@muc.de \
    --cc=coreteam@netfilter.org \
    --cc=netdev@oss.sgi.com \
    /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.