From: Patrick McHardy <kaber@trash.net>
To: Salatiel Filho <salatiel.filho@gmail.com>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: iptables -> can't initialize iptables table `filter': Bad file descriptor
Date: Tue, 04 Dec 2007 17:15:00 +0100 [thread overview]
Message-ID: <47557D04.1040101@trash.net> (raw)
In-Reply-To: <beb91d720712040805u7dd0241by2349e9b34c361a87@mail.gmail.com>
Salatiel Filho wrote:
> On 12/4/07, Patrick McHardy <kaber@trash.net> wrote:
>> Salatiel Filho wrote:
>>> ~# iptables -L
>>> iptables v1.3.8: can't initialize iptables table `filter': Invalid argument
>>> Perhaps iptables or your kernel needs to be upgraded.
>>>
>>> # dmesg
>>> ip_tables: (C) 2000-2002 Netfilter core team
>>> translate_table: size 632
>>> Finished chain 1
>>> Finished chain 2
>>> Finished chain 3
>>> table->private->number = 4
>>> get_entries: 668 != 672
>> This looks like an alignment problem. Old kernels required
>> alignof(struct ipt_entry), which should be 4. Userspace
>> compiled against current headers use:
>>
>> struct _xt_align
>> {
>> u_int8_t u8;
>> u_int16_t u16;
>> u_int32_t u32;
>> u_int64_t u64;
>> };
>>
>> #define XT_ALIGN(s) (((s) + (__alignof__(struct _xt_align)-1)) \
>>
>> & ~(__alignof__(struct _xt_align)-1))
>>
>> which I guess is 8 on ARM. Does removing the u_int64_t
>> from the struct above in the iptables source
>> (include/linux/netfilter/x_tables.h) help?
>>
>>
>
> I can not find include/linux/netfilter/x_tables.h in iptables source.
>
> # ls -1 include/linux/netfilter/
> nf_conntrack_common.h
> nf_conntrack_tuple_common.h
> nf_conntrack_tuple.h
> nf_nat.h
Right, we only recently added it. Are you compiling against your
kernel source? Otherwise check in /usr/include/linux/...
next prev parent reply other threads:[~2007-12-04 16:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 19:22 iptables -> can't initialize iptables table `filter': Bad file descriptor Salatiel Filho
2007-12-03 8:07 ` Patrick McHardy
2007-12-03 12:35 ` Salatiel Filho
2007-12-04 8:18 ` Patrick McHardy
2007-12-04 8:51 ` Jan Engelhardt
2007-12-04 8:58 ` Jesper Dangaard Brouer
2007-12-04 9:14 ` Patrick McHardy
2007-12-04 14:16 ` Salatiel Filho
2007-12-04 14:18 ` Patrick McHardy
[not found] ` <beb91d720712040645w76be238bmdd9dc362bf601755@mail.gmail.com>
2007-12-04 15:07 ` Patrick McHardy
2007-12-04 15:40 ` Salatiel Filho
2007-12-04 15:57 ` Patrick McHardy
2007-12-04 16:05 ` Salatiel Filho
2007-12-04 16:15 ` Patrick McHardy [this message]
2007-12-04 16:32 ` Salatiel Filho
2007-12-05 8:05 ` Patrick McHardy
2007-12-05 11:39 ` Salatiel Filho
2007-12-06 9:51 ` Patrick McHardy
2007-12-06 11:25 ` Salatiel Filho
2007-12-09 13:34 ` Salatiel Filho
2007-12-09 14:11 ` Salatiel Filho
2007-12-11 10:29 ` Patrick McHardy
2007-12-13 21:41 ` Laurence J. Lane
2007-12-13 22:14 ` Salatiel Filho
2007-12-14 9:22 ` Patrick McHardy
2007-12-14 12:39 ` Salatiel Filho
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=47557D04.1040101@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=salatiel.filho@gmail.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.