Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Maurice Volaski <mvolaski@aecom.yu.edu>
To: netfilter@lists.netfilter.org, linux-kernel@vger.kernel.org
Subject: Re: iptables is complaining with bogus unknown error 18446744073709551615
Date: Wed, 26 Apr 2006 21:12:38 -0400	[thread overview]
Message-ID: <a06230901c075ca078b8d@[129.98.90.227]> (raw)
In-Reply-To: <200604210738.k3L7cBGO010103@mailgw.aecom.yu.edu>

Automatic kernel module loading! That is an option and it's off by 
default. When it's off, attempts to load kernel modules are ignored 
internally, and that's why iptables was failing. It tried to load 
xt_tcpudp, but was ignored by the kernel.


>
>At least since 2.6.1.16.1, many calls to iptables no longer function
>at least under 64-bit x86, presumably due to a bug in the netfilter
>kernel code.
>
>The problem is still present in 2.6.17-rc2.
>
>The error from iptables is
>iptables: unknown error 18446744073709551615
>
>Examples of rules that give the error are
>
>1) iptables -A INPUT -i bond0 -s 129.98.90.0/24 -p tcp --dport 548 -j ACCEPT
>2) iptables -A INPUT -i bond0 -s 129.98.90.101/32 -p tcp --dport 497 -j ACCEPT
>3) iptables -A INPUT -i bond0 -s 129.98.90.227/32 -p tcp --dport 22 -j ACCEPT
>
>Example of a rule that does not give the error:
>1) iptables -A INPUT -i bond0 -p ICMP --icmp-type echo-request -s
>129.98.90.13/32 -j ACCEPT
>
>The computer is using IPv4 and not IPv6, which has not been compiled into the
>kernel.
>
>iptables is version 1.3.5.
>
>Kernel configuration related to iptables follows:
>



>lsmod shows
>xt_state                4928  0
>ipt_LOG                 8960  0
>ip_conntrack_ftp       10000  0
>ip_conntrack           57880  2 xt_state,ip_conntrack_ftp
>nfnetlink               8520  1 ip_conntrack
>iptable_filter          5440  0
>ip_tables              22168  1 iptable_filter
>x_tables               17800  3 xt_state,ipt_LOG,ip_tables
>

-- 

Maurice Volaski, mvolaski@aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University


       reply	other threads:[~2006-04-27  1:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200604210738.k3L7cBGO010103@mailgw.aecom.yu.edu>
2006-04-27  1:12 ` Maurice Volaski [this message]
2006-04-27 13:51   ` iptables is complaining with bogus unknown error 18446744073709551615 Harald Welte
2006-04-27 15:41     ` Maurice Volaski
2006-04-27 19:24       ` CONFIG_KMOD in x86_64/defconfig (was Re: iptables is complaining with bogus unknown error 18446744073709551615) Harald Welte
2006-04-27 20:00         ` Maurice Volaski
2006-04-27 20:01         ` Arjan van de Ven
2006-04-21  6:21 iptables is complaining with bogus unknown error 18446744073709551615 Maurice Volaski
2006-04-21 11:15 ` Harald Welte
2006-04-21 14:22   ` Maurice Volaski
     [not found]   ` <a06230913c06e96f75f32@129.98.90.227>
2006-04-21 18:26     ` Nick Warne
2006-04-22  0:05       ` Alessandro Suardi
  -- strict thread matches above, loose matches on Subject: below --
2006-04-13 23:19 Maurice Volaski
     [not found] <200604111452.k3BEpxdo019103@mailgw.aecom.yu.edu>
2006-04-11 17:14 ` Maurice Volaski
     [not found] ` <a06230909c06193cea962@129.98.90.227>
     [not found]   ` <876ef97a0604111146m742d75f0gb8240e82ba7426f1@mail.gmail.com>
2006-04-11 19:13     ` Maurice Volaski

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='a06230901c075ca078b8d@[129.98.90.227]' \
    --to=mvolaski@aecom.yu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter@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