netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Patrick McHardy <kaber@trash.net>
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: Sun, 4 Jun 2006 15:39:35 +0300 (EEST)	[thread overview]
Message-ID: <Pine.SOC.4.61.0606041528250.2191@math.ut.ee> (raw)
In-Reply-To: <44804379.60808@trash.net>

> Please enable DEBUG_IP_FIREWALL_USER in net/netfilter/x_tables.c as well
> and retry. Results of the raw or mangle table would also be interesting
> because they contain a different number of built-in chains.

Sorry it took so long, I was away. Adding this define does not seem to 
do much (table->private->number prints only):

On boot (1 nat rule):
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
Finished chain 0
Finished chain 3
Finished chain 4
table->private->number = 4
t->private->number = 4
translate_table: size 800
Bad offset cba528d4

modprobe iptable_nat succeeded in manual modprobe.

modprobe iptable_filter:
translate_table: size 632
Bad offset cbbd910c

modprobe iptable_mangle:
translate_table: size 936
Bad offset cbbd80dc

modprobe iptable_raw:
translate_table: size 480
Bad offset cb8abd44

Retrying ifup and ifdown that tried to do iptables -D and iptables -I:
t->private->number = 4
t->private->number = 4
t->private->number = 4
translate_table: size 800
Bad offset cbbd80dc
t->private->number = 4

And retrying it more (succeeded this time):

t->private->number = 4
t->private->number = 4
translate_table: size 800
Finished chain 0
Finished chain 3
Finished chain 4
ip_tables: Translated table
do_replace: oldnum=4, initnum=4, newnum=5
t->private->number = 5

-- 
Meelis Roos (mroos@linux.ee)

      reply	other threads:[~2006-06-04 12:39 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
2006-06-02 13:18             ` Meelis Roos
2006-06-02 13:56               ` Patrick McHardy
2006-06-04 12:39                 ` Meelis Roos [this message]

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=Pine.SOC.4.61.0606041528250.2191@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=akpm@osdl.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=kaber@trash.net \
    --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).