From: Alan Ezust <alan.ezust@presinet.com>
To: netfilter@lists.netfilter.org
Cc: fmouse-netfilter@fmp.com, fmouse-m14acd@fmp.com
Subject: Re: iptables: Unknown error 4294967295
Date: Tue, 31 Oct 2006 14:38:00 -0800 [thread overview]
Message-ID: <200610311438.05556.alan.ezust@presinet.com> (raw)
In-Reply-To: <200609260041.k8Q0fikT014394@toshiba.co.jp>
[-- Attachment #1: Type: text/plain, Size: 2303 bytes --]
I was getting this too, and my problem was related to the fact that my kernel
was configued with CONFIG_NETFILTER_NETLINK=m. I changed that to a "y" and my
UNKNOWN ERROR went away. And yes, I was loading the module at the right time
in my /etc/modules, but that didn't seem to make a difference to netfilter.
On Monday 25 September 2006 17:41, Yasuyuki KOZAKAI wrote:
> Hello,
>
> From: Lindsay Haisley <fmouse-netfilter@fmp.com>
> Date: Mon, 25 Sep 2006 19:03:01 -0500
>
> > When I execute the following:
> >
> > iptables -t nat -I PREROUTING -s 10.8.0.1 -i tap0 -j SNAT --to-source
> > 216.110.12.105
> >
> > ... I'm getting the error:
> >
> > iptables: Unknown error 4294967295
> >
> > (4294967295 = an unsigned representation of a signed long int of -1)
> >
> > Running this under strace shows the following:
> >
> >
> > mmap2(NULL, 7648, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
> > 0xb7fbb000
> > mmap2(0xb7fbc000, 4096, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0xb7fbc000 close(3)
> > = 0
> > socket(PF_INET, SOCK_RAW, IPPROTO_RAW) = 3
> > getsockopt(3, SOL_IP, 0x40 /* IP_??? */,
> > "nat\0\1\0\0\0\335g\21\300\0\0\0\0\224\313F\300\1\0\0\0"..., [84]) = 0
> > getsockopt(3, SOL_IP, 0x41 /* IP_??? */,
> > "nat\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., [656]) = 0
> > setsockopt(3, SOL_IP, 0x40 /* IP_??? */,
> > "nat\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 876) = -1
> > EINVAL (Invalid argument) write(2, "iptables: Unknown error 42949672"...,
> > 35iptables: Unknown error 4294967295 ) = 35
> > exit_group(1) = ?
> > Process 10231 detached
> >
> > Apprently the error is originating in a malformed socket option call.
> > What's happening here, and how can I fix it? I'm running kernel
> > 2.6.17-gentoo-r4, iptables v1.3.5.
> >
> > I have about every possible kernel netfilter capability compiled as a
> > module, or built into the kernel.
>
> Is your iptables 32bit binary and do you run it on 64bit kernel ?
> And did syslog output anything ?
>
> -- Yasuyuki Kozakai
--
Alan Ezust www.presinet.com
Presinet, inc alan.ezust@presinet.com
Victoria, BC,Canada
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-31 22:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 0:03 iptables: Unknown error 4294967295 Lindsay Haisley
2006-09-26 0:37 ` Daniel De Graaf
2006-09-26 0:55 ` Lindsay Haisley
2006-09-26 0:41 ` Yasuyuki KOZAKAI
2006-10-31 22:38 ` Alan Ezust [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-30 16:49 KARIM SATTAR
2007-08-30 16:59 ` Rob Sterenborg
2007-08-30 9:42 KARIM SATTAR
2007-08-30 10:58 ` Leonardo Rodrigues Magalhães
2006-05-15 5:21 azeredo
2006-03-31 4:23 Samuel Díaz García
2006-04-01 6:21 ` Samuel Díaz García
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=200610311438.05556.alan.ezust@presinet.com \
--to=alan.ezust@presinet.com \
--cc=fmouse-m14acd@fmp.com \
--cc=fmouse-netfilter@fmp.com \
--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.