netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Meelis Roos <mroos@linux.ee>
Cc: Andrew Morton <akpm@osdl.org>,
	bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc)
Date: Fri, 02 Jun 2006 15:08:44 +0200	[thread overview]
Message-ID: <4480385C.7080405@trash.net> (raw)
In-Reply-To: <Pine.SOC.4.61.0606012346350.28838@math.ut.ee>

Meelis Roos wrote:
>> Then lets try something different. Please enable the
>> DEBUG_IP_FIREWALL_USER define in net/ipv4/netfilter/ip_tables.c and
>> post the results, if any.
> 
> 
> On bootup I get this in dmesg (one Bad offset has been added):
> 
> ip_tables: (C) 2000-2006 Netfilter Core Team
> Netfilter messages via NETLINK v0.30.
> ip_conntrack version 2.4 (1536 buckets, 12288 max) - 224 bytes per
> conntrack
> translate_table: size 632
> Bad offset cb437924
> ip_nat_init: can't setup rules.
> 
> And on iptables -t nat -L
> 
> translate_table: size 632
> Bad offset cb4368f4
> ip_nat_init: can't setup rules.
> translate_table: size 632
> Bad offset cb4368f4
> ip_nat_init: can't setup rules.
> 
> Seems iptable_nat does not load at all this time.
> 
> Modprobe iptable_filter still fails, dmesg contains
> translate_table: size 632
> Finished chain 1
> Finished chain 2
> Finished chain 3
> 
> Next modprobe iptable_nat gives
> 
> translate_table: size 632
> Bad offset c8e01944
> ip_nat_init: can't setup rules.


Very strange, this means that the initial table data must somehow
be wrong, but for some reason it still seems to get past the
size and offset checks for the filter table. I can't see how
loading the filter table could fail after the "Finished chain .."
messages without another message. Which kernel version did you
perform these test on?


  reply	other threads:[~2006-06-02 13:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200605251004.k4PA4Lek007751@fire-2.osdl.org>
2006-05-25 14:03 ` [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc) Andrew Morton
2006-05-25 18:52   ` Patrick McHardy
2006-05-25 19:12     ` Meelis Roos
2006-05-25 20:15     ` Meelis Roos
2006-05-26  7:11     ` Meelis Roos
2006-05-26 12:29       ` Safe remote kernel install howto (Re: [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc)) Ingo Oeser
2006-05-26 12:34         ` Meelis Roos
2006-05-31 20:25           ` Bill Davidsen
2006-05-26 12:42         ` Michael Tokarev
2006-05-26 12:42         ` Andi Kleen
2006-05-26 13:21           ` Ingo Oeser
2006-06-01  7:03     ` [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc) Meelis Roos
2006-06-01 17:44       ` Patrick McHardy
2006-06-01 20:50         ` Meelis Roos
2006-06-02 13:08           ` Patrick McHardy [this message]
2006-06-02 13:18             ` Meelis Roos
2006-06-02 13:56               ` Patrick McHardy
2006-06-04 12:39                 ` Meelis Roos

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=4480385C.7080405@trash.net \
    --to=kaber@trash.net \
    --cc=akpm@osdl.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=mroos@linux.ee \
    --cc=netdev@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).