From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Simon Oosthoek <simon@cal003100.student.utwente.nl>
Cc: Netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: iptables on sparc64 platform?
Date: 15 Sep 2002 14:58:21 +0200 [thread overview]
Message-ID: <1032094701.28097.150.camel@tux> (raw)
In-Reply-To: <20020314153419.GA5152@margo.student.utwente.nl>
[-- Attachment #1.1: Type: text/plain, Size: 727 bytes --]
On Thu, 2002-03-14 at 16:34, Simon Oosthoek wrote:
> The reason I have doubts about the quality of the modules on 64 bit sparc is
> that the iptables command gives an invalid argument error when using the -m
> limit option. The ipt_limit module is in memory (according to lsmod).
Hi Simon, sorry for the very very late reply.
It seems I made a patch for libipt_limit.c when I read this mail but it
seems I never sent it to anyone :( I found it when I was cleaning up a
bit.
Do you still have this problem?
I don't know if this patch will solve the problem but if you want you
can give it a try.
--
/Martin
Never argue with an idiot. They drag you down to their level, then beat
you with experience.
[-- Attachment #1.2: libipt_limit-diff --]
[-- Type: text/plain, Size: 392 bytes --]
--- netfilter/userspace/extensions/libipt_limit.c.orig Tue Jul 30 11:56:40 2002
+++ netfilter/userspace/extensions/libipt_limit.c Tue Jul 30 11:57:28 2002
@@ -183,7 +183,7 @@
"limit",
IPTABLES_VERSION,
IPT_ALIGN(sizeof(struct ipt_rateinfo)),
- offsetof(struct ipt_rateinfo, prev),
+ IPT_ALIGN(sizeof(struct ipt_rateinfo)),
&help,
&init,
&parse,
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
parent reply other threads:[~2002-09-15 12:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20020314153419.GA5152@margo.student.utwente.nl>]
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=1032094701.28097.150.camel@tux \
--to=gandalf@wlug.westbo.se \
--cc=netfilter-devel@lists.netfilter.org \
--cc=simon@cal003100.student.utwente.nl \
/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.