All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Maurice Volaski <mvolaski@aecom.yu.edu>
Cc: netfilter@lists.netfilter.org, linux-kernel@vger.kernel.org
Subject: Re: iptables is complaining with bogus unknown error 18446744073709551615
Date: Fri, 21 Apr 2006 08:15:30 -0300	[thread overview]
Message-ID: <20060421111530.GE5286@rama> (raw)
In-Reply-To: <a06230910c06e2510acfa@[129.98.90.227]>

[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]

Hi Maurice.

Didn't you report this bug already to bugzilla.netfilter.org (and maybe
eben to the bugme.osdl.org)?  Reporting a bug in three distinct places,
even though it has been replied to at one place is not really going to
use developer resources efficiently, don't you think?

On Fri, Apr 21, 2006 at 02:21:17AM -0400, Maurice Volaski wrote:
> 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.

It probably was since 2.6.16 then, that was when the x_tables patches
were merged, the code most likely to have affected any such
incompatibility of the binary interface.  It was tested thoroughlt,
especially on x86_64, whihc is my main development platform.

However, your problem seems to be something different.  I suspect that
all rules with '-p tcp' or '-p udp' don't work, whereas others do.  You
seem to be missing the xt_tcpudp.ko module, which implements that
feature in 2.6.17-rcX kernels. 

Please refer to
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=467

-- 
- 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 --]

WARNING: multiple messages have this Message-ID (diff)
From: Harald Welte <laforge@netfilter.org>
To: Maurice Volaski <mvolaski@aecom.yu.edu>
Cc: linux-kernel@vger.kernel.org, netfilter@lists.netfilter.org
Subject: Re: iptables is complaining with bogus unknown error 18446744073709551615
Date: Fri, 21 Apr 2006 08:15:30 -0300	[thread overview]
Message-ID: <20060421111530.GE5286@rama> (raw)
In-Reply-To: <a06230910c06e2510acfa@[129.98.90.227]>

[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]

Hi Maurice.

Didn't you report this bug already to bugzilla.netfilter.org (and maybe
eben to the bugme.osdl.org)?  Reporting a bug in three distinct places,
even though it has been replied to at one place is not really going to
use developer resources efficiently, don't you think?

On Fri, Apr 21, 2006 at 02:21:17AM -0400, Maurice Volaski wrote:
> 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.

It probably was since 2.6.16 then, that was when the x_tables patches
were merged, the code most likely to have affected any such
incompatibility of the binary interface.  It was tested thoroughlt,
especially on x86_64, whihc is my main development platform.

However, your problem seems to be something different.  I suspect that
all rules with '-p tcp' or '-p udp' don't work, whereas others do.  You
seem to be missing the xt_tcpudp.ko module, which implements that
feature in 2.6.17-rcX kernels. 

Please refer to
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=467

-- 
- 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 --]

  reply	other threads:[~2006-04-21 11:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21  6:21 iptables is complaining with bogus unknown error 18446744073709551615 Maurice Volaski
2006-04-21 11:15 ` Harald Welte [this message]
2006-04-21 11:15   ` Harald Welte
2006-04-21 14:22   ` Maurice Volaski
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
2006-04-22 11:59         ` Nick Warne
     [not found] <200604210738.k3L7cBGO010103@mailgw.aecom.yu.edu>
2006-04-27  1:12 ` Maurice Volaski
2006-04-27 13:51   ` Harald Welte
2006-04-27 15:41     ` Maurice Volaski
  -- 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=20060421111530.GE5286@rama \
    --to=laforge@netfilter.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mvolaski@aecom.yu.edu \
    --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 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.