All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Austin - Standard Universal <brian@standarduniversal.com.au>
To: Tino Keitel <tkeitel@innominate.com>
Cc: netfilter@vger.kernel.org
Subject: Re: How to use mark and connmark in one rule
Date: Fri, 24 Apr 2009 23:39:44 +1000	[thread overview]
Message-ID: <49F1C120.8090802@standarduniversal.com.au> (raw)
In-Reply-To: <49F1C0B4.8010809@standarduniversal.com.au>

that should be 2 separate lines.. stupid email

iptables -A INPUT -m mark --mark 1

iptables -A INPUT -m connmark --mark 2



Brian Austin - Standard Universal wrote:
> to do this would be faster than patching and etc..
>
> iptables -A INPUT -m mark --mark 1 iptables -A INPUT -m connmark --mark 2
>
> regards
>
> Brian
>
>
> Tino Keitel wrote:
>> Hi folks,
>>
>> when I try to use the mark and connmark extensions in one rule, I get
>> an error:
>>
>> $ iptables -A INPUT -m mark --mark 1 -m connmark --mark 2
>> iptables v1.4.2: mark: "--mark" option may only be specified once
>>
>> Is this intended? If not, is there a way to make this work with a stock
>> iptables, or do I have to patch the source and rename one of the
>> options?
>>
>> Regards,
>>
>>   
> -- 
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-04-24 13:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 13:32 How to use mark and connmark in one rule Tino Keitel
2009-04-24 13:37 ` Brian Austin - Standard Universal
2009-04-24 13:39   ` Brian Austin - Standard Universal [this message]
2009-05-12 13:00     ` Tino Keitel
2009-05-12 13:13       ` Pascal Hambourg
2009-04-24 13:40 ` Gáspár Lajos
2009-04-24 13:49   ` Tino Keitel
2009-04-24 13:55     ` Gáspár Lajos
2009-05-12 13:01       ` Tino Keitel
2009-04-24 14:46   ` Pascal Hambourg
2009-04-24 16:15     ` Gáspár Lajos
2009-04-24 19:13       ` Pascal Hambourg

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=49F1C120.8090802@standarduniversal.com.au \
    --to=brian@standarduniversal.com.au \
    --cc=netfilter@vger.kernel.org \
    --cc=tkeitel@innominate.com \
    /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.