All of lore.kernel.org
 help / color / mirror / Atom feed
From: borg@uu3.net
To: netfilter-devel@lists.netfilter.org
Subject: Re[2]: ipt_limit patch for iptables-1.3.1 and linux-2.4.22
Date: Fri, 23 Dec 2005 21:13:01 +0100	[thread overview]
Message-ID: <036110574.20051223211301@uu3.net> (raw)
In-Reply-To: <43AC4F57.8090702@trash.net>

Well.. patching only kernel or only userland is pointless indeed.
I still dont understand "brakes userspace"
I assume that we patch both iptables + kernel.
Where is the problem then?

Back to adding that to mainline...
First, ppl must have add this to kernel.
and after kernel.. you can add it to new iptables
its easy to detect what kernel is in use
by #ifdef and you can add/remove support for !
in libipt_limit.c.

Regards,
Borg

----- Original Message -----
From: kaber@trash.net
To: borg@uu3.net
Date: 23-12-2005, 20:26
Subject: ipt_limit patch for iptables-1.3.1 and linux-2.4.22

borg@uu3.net wrote:
> What do you mean it brakes userspace?
> Can you please explain me that?
> I've patched both iptables (userland),
> and kernel ipt_limit.c and header.
> The only mistake I see for now, is that I wrongly
> modified include/linux/netfilter_ipv4/ipt_limit.h
> I should add that char invert at the end of structrue.
> 
> The only userspace program using that is iptables.
> Or I am wrong?

You seem to forget about old versions that don't have your
patch. 2.4 doesn't support revisions, so we can't make
that change.

  reply	other threads:[~2005-12-23 20:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-23 13:12 ipt_limit patch for iptables-1.3.1 and linux-2.4.22 borg
2005-12-23 13:40 ` m.innocenti
2005-12-23 15:43   ` Re[2]: " borg
2005-12-23 19:26     ` Patrick McHardy
2005-12-23 20:13       ` borg [this message]
2005-12-23 20:19         ` Phil Oester
2005-12-23 20:35           ` Re[2]: " borg
2005-12-23 20:57             ` Phil Oester
2005-12-27  9:21               ` m.innocenti
2005-12-24  6:27             ` Patrick Schaaf

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=036110574.20051223211301@uu3.net \
    --to=borg@uu3.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.