Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Fabian Gervan <fabian1@inter-k.com.ar>
To: lartc@vger.kernel.org
Subject: [LARTC] problems with IMQ + Netfilter IP_LIMIT patch from netfilter CVS
Date: Thu, 14 Feb 2002 22:49:36 +0000	[thread overview]
Message-ID: <marc-lartc-101377247813750@msgid-missing> (raw)

Martin:
I have problems after apply those patchs to kernel 2.4.17
"make modules" can't compile any "shed" modules.
Here I write a fragment for iplimit.patch

+ * netfilter module to limit the number of parallel tcp
+ * connections per IP address.
+ *   (c) 2000 Gerd Knorr <kraxel@bytesex.org>
+ *
+ * based on ...
+ *
+ * Kernel module to match connection tracking information.
+ * GPL (C) 1999  Rusty Russell (rusty@rustcorp.com.au).
+ */
+#include <linux/module.h>
+#include <linux/skbuff.h>
+#include <linux/list.h>
+#include <linux/netfilter_ipv4/ip_conntrack.h>
+#include <linux/netfilter_ipv4/ip_conntrack_core.h>
+#include <linux/netfilter_ipv4/ip_conntrack_tcp.h>
+#include <linux/netfilter_ipv4/ip_tables.h>
+#include <linux/netfilter_ipv4/ipt_iplimit.h>
+
+#define DEBUG 0
+
+/* we'll save the tuples of all connections we care about */
+struct ipt_iplimit_conn
+{
+        struct list_head list;
+       struct ip_conntrack_tuple tuple;
+};
+
[...]
Could be that IMQ conflict with this patch, and make modules fail?

-- 
Saludos,
 Fabian Gervan


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

             reply	other threads:[~2002-02-14 22:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-14 22:49 Fabian Gervan [this message]
2002-02-15 11:36 ` [LARTC] problems with IMQ + Netfilter IP_LIMIT patch from Martin Devera
2002-02-15 20:46 ` Re[2]: [LARTC] problems with IMQ + Netfilter IP_LIMIT patch from netfilter CVS Fabian Gervan

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=marc-lartc-101377247813750@msgid-missing \
    --to=fabian1@inter-k.com.ar \
    --cc=lartc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox