All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Birchinger <joker@netswarm.net>
To: netfilter-devel@lists.netfilter.org
Subject: limit rule on sparc-linux
Date: Thu, 9 Jan 2003 09:58:40 +0100	[thread overview]
Message-ID: <20030109085840.GA1086@netswarm.net> (raw)

Hello
Is there a known patch for the non-working limit rule on
sparc/linux? The last version Kernel i've tested is 2.4.20
and it still refuses limit rules.

I'm not sure if the problem has been reported on this list.
I saw it on many places (Google also found it on some Debian
mailinglists).

Heres a quick example of a rule which perfectly works on x86 but
fails on sparc64:
# iptables -A INPUT -j ACCEPT -p icmp -m limit --limit 120/minute
iptables: Invalid argument
#

If it helps, here are the last lines of a strace with this
command:
open("/lib/iptables/libipt_limit.so", O_RDONLY) = 3
read(3,"\177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\22\0\0\0\1\0\0\6"... ,1024) = 1024
fstat64(3, {st_mode=S_IFREG|0755, st_size=5758, ...}) = 0
mmap(NULL, 69552, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x701b8000
mprotect(0x701ba000, 61360, PROT_NONE)  = 0
mmap(0x701c8000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x701c8000
close(3)                                = 0
socket(PF_INET, SOCK_RAW, IPPROTO_RAW)  = 3
getsockopt(3, SOL_IP, 0x40 /* IP_??? */, [1718185076], [84]) = 0
getsockopt(3, SOL_IP, 0x41 /* IP_??? */, [1718185076], [672]) = 0
rt_sigtimedwait(ptrace: umoven: Input/output error
[?], 0x3)               = -1 EINVAL (Invalid argument)
write(2, "iptables: Invalid argument\n", 27iptables: Invalid argument
) = 27
exit(1)                                 = ?

-- 
Christian Birchinger

             reply	other threads:[~2003-01-09  8:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09  8:58 Christian Birchinger [this message]
2003-01-09 20:00 ` limit rule on sparc-linux 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=20030109085840.GA1086@netswarm.net \
    --to=joker@netswarm.net \
    --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 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.