From: Harald Welte <laforge@netfilter.org>
To: Mikael Pettersson <mikpe@user.it.uu.se>
Cc: linuxppc-dev@ozlabs.org, netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc1: iptables broken on ppc32?
Date: Wed, 18 Jan 2006 16:01:58 +0100 [thread overview]
Message-ID: <20060118150158.GL4603@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <17358.19458.555996.684819@alkaid.it.uu.se>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Wed, Jan 18, 2006 at 03:09:06PM +0100, Mikael Pettersson wrote:
> When trying out kernel 2.6.16-rc1 on a ppc32 box (G4 eMac),
> the kernel refused to load my /etc/sysconfig/iptables. strace
> on /sbin/iptables-restore shows that the kernel returns EINVAL
> instead of accepting the configuration:
thanks for letting us know, you might have catched a very important bug.
We've introduced a number of changes (x_tables) that haven't received
testing on all architectures yet.
I will try to reproduce the bug on my debian ppc box here.
This is not meant as a fix, but you might try it to narrow down the
problem: Try recompiling iptables on your own, and report back whether
that works or not.
Please Follow-up-to netfilter-devel@lists.netfilter.org
--
- Harald Welte <laforge@netfilter.org> http://netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-18 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 14:09 Mikael Pettersson
2006-01-18 15:01 ` Harald Welte [this message]
2006-01-20 0:45 ` [PATCH] x_tables: fix alignment on [at least] ppc32 (was Re: 2.6.16-rc1: iptables broken on ppc32?) Harald Welte
2006-01-20 0:56 ` [PATCH] x_tables: fix alignment on [at least] ppc32 David S. Miller
2006-01-20 9:28 ` Mikael Pettersson
2006-01-20 9:43 ` David S. Miller
2006-01-20 17:28 ` Harald Welte
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=20060118150158.GL4603@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikpe@user.it.uu.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®