From: Amin Azez <azez@ufomechanic.net>
To: Henrik Nordstrom <henrik@henriknordstrom.net>
Cc: netfilter-devel@lists.netfilter.org,
Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: [PATCH 1/1] Re: dangerous? Setting mark in nat table
Date: Wed, 14 Mar 2007 12:52:55 +0000 [thread overview]
Message-ID: <45F7F027.9050300@ufomechanic.net> (raw)
In-Reply-To: <1173876211.26913.73.camel@henriknordstrom.net>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
* Henrik Nordstrom wrote, On 14/03/07 12:43:
> ons 2007-03-14 klockan 12:02 +0100 skrev Patrick McHardy:
>
>
>> Thats true, routing by nfmark in the OUTPUT chain needs the rerouting
>> done by the mangle table, but nowadays there are other uses for nfmark,
>> so if someone feels motivated to send a patch to get rid of this pretty
>> arbitary restriction I think I would take it.
>>
>
> If you do, please remove the same restriction from CONNMARK restore
>
Let it at least be said that some of my patches are used :-)
(Henrick, are you interested in my per-flow patch for connmark, so that
each side of the flow can have a seperate mark? Also dumped thus out of
/proc/net/ip-conntrack and libnfnetlink)
Signed-off-by: Sam Liddicott <azez@ufomechanic.net>
Sam
[-- Attachment #2: mark-mangle.patch --]
[-- Type: text/x-patch, Size: 2052 bytes --]
Index: linux-2.6.17.1/net/netfilter/xt_CONNMARK.c
===================================================================
--- linux-2.6.17.1.orig/net/netfilter/xt_CONNMARK.c
+++ linux-2.6.17.1/net/netfilter/xt_CONNMARK.c
@@ -133,13 +133,6 @@ checkentry(const char *tablename,
{
struct xt_connmark_target_info *matchinfo = targinfo;
- if (matchinfo->mode == XT_CONNMARK_RESTORE) {
- if (strcmp(tablename, "mangle") != 0) {
- printk(KERN_WARNING "CONNMARK: restore can only be called from \"mangle\" table, not \"%s\"\n", tablename);
- return 0;
- }
- }
-
if (matchinfo->mark > 0xffffffff || matchinfo->mask > 0xffffffff) {
printk(KERN_WARNING "CONNMARK: Only supports 32bit mark\n");
return 0;
Index: linux-2.6.17.1/net/netfilter/xt_MARK.c
===================================================================
--- linux-2.6.17.1.orig/net/netfilter/xt_MARK.c
+++ linux-2.6.17.1/net/netfilter/xt_MARK.c
@@ -116,7 +116,6 @@ static struct xt_target ipt_mark_reg_v0
.name = "MARK",
.target = target_v0,
.targetsize = sizeof(struct xt_mark_target_info),
- .table = "mangle",
.checkentry = checkentry_v0,
.me = THIS_MODULE,
.family = AF_INET,
@@ -127,7 +126,6 @@ static struct xt_target ipt_mark_reg_v1
.name = "MARK",
.target = target_v1,
.targetsize = sizeof(struct xt_mark_target_info_v1),
- .table = "mangle",
.checkentry = checkentry_v1,
.me = THIS_MODULE,
.family = AF_INET,
@@ -138,7 +136,6 @@ static struct xt_target ip6t_mark_reg_v0
.name = "MARK",
.target = target_v0,
.targetsize = sizeof(struct xt_mark_target_info),
- .table = "mangle",
.checkentry = checkentry_v0,
.me = THIS_MODULE,
.family = AF_INET6,
next prev parent reply other threads:[~2007-03-14 12:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 15:25 dangerous? Setting mark in nat table Amin Azez
2007-03-13 15:36 ` Jan Engelhardt
2007-03-13 16:12 ` Amin Azez
2007-03-13 16:18 ` Jan Engelhardt
2007-03-14 10:35 ` Henrik Nordstrom
2007-03-14 11:02 ` Patrick McHardy
2007-03-14 12:43 ` Henrik Nordstrom
2007-03-14 12:52 ` Amin Azez [this message]
2007-03-14 13:08 ` [PATCH 1/1] " Patrick McHardy
2007-03-14 13:21 ` Jozsef Kadlecsik
2007-03-14 14:09 ` Jozsef Kadlecsik
2007-03-14 20:35 ` Patrick McHardy
2007-03-14 20:45 ` Henrik Nordstrom
2007-03-14 20:48 ` Jan Engelhardt
2007-03-14 22:21 ` Henrik Nordstrom
2007-03-14 22:58 ` Carl-Daniel Hailfinger
2007-03-14 23:02 ` Patrick McHardy
2007-03-14 23:12 ` Jan Engelhardt
2007-03-14 23:15 ` Patrick McHardy
2007-03-15 13:12 ` Roberto Nibali
2007-03-16 12:31 ` Patrick McHardy
2007-03-15 0:41 ` Henrik Nordstrom
2007-03-14 14:11 ` Amin Azez
2007-03-14 14:32 ` One unified table of nat/mangle/filter Henrik Nordstrom
2007-03-14 14:47 ` [PATCH 1/1] Re: dangerous? Setting mark in nat table Jozsef Kadlecsik
2007-03-14 16:47 ` Jan Engelhardt
2007-03-14 13:14 ` Henrik Nordstrom
2007-03-14 12:43 ` Amin Azez
2007-03-14 10:27 ` Henrik Nordstrom
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=45F7F027.9050300@ufomechanic.net \
--to=azez@ufomechanic.net \
--cc=henrik@henriknordstrom.net \
--cc=jengelh@linux01.gwdg.de \
--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.