From: Mikael Pettersson <mikpe@user.it.uu.se>
To: linuxppc-dev@ozlabs.org, netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org
Subject: 2.6.16-rc1: iptables broken on ppc32?
Date: Wed, 18 Jan 2006 15:09:06 +0100 [thread overview]
Message-ID: <17358.19458.555996.684819@alkaid.it.uu.se> (raw)
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:
setsockopt(3, SOL_IP, 0x40 /* IP_??? */, "filter\0\214\0p\0\230\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1664) = -1 EINVAL (Invalid argument)
The exact same configuration is accepted and works on an x86 box
also running 2.6.16-rc1, and of course the configuration worked
in all kernels up to and including 2.6.15 on the ppc32 box.
A much simplified /etc/sysconfig/iptables that fails on ppc32 but
works on x86 is the following:
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -i eth0 -j ACCEPT
COMMIT
My 2.6.16-rc1 kernel configuration includes
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
and the iptable_filter, ip_tables, and x_tables modules were all loaded,
just like they were on the working x86 box.
User-space on the ppc32 box is YDL 4.0 with iptables-1.2.9-2.3.1.
/Mikael
next reply other threads:[~2006-01-18 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 14:09 Mikael Pettersson [this message]
2006-01-18 15:01 ` Harald Welte
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=17358.19458.555996.684819@alkaid.it.uu.se \
--to=mikpe@user.it.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--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®