From: Akshat Kakkar <akshat.1984@gmail.com>
To: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: unknown option "--map-set"
Date: Wed, 12 Aug 2015 14:35:01 +0530 [thread overview]
Message-ID: <CAA5aLPiHDNwK_mxiaTVYYCmZpkr1wyyjbMCa4CmQDhPrVVv3Yg@mail.gmail.com> (raw)
In-Reply-To: <CAA5aLPg=UhPp0wODZc8qtx3FwnReM+3Qs4zFm9_8Fgap8LMvtg@mail.gmail.com>
Well, it looks that the Sep 16 Snapshot didnt have the code for
map-set option. But thats strange as the code was committed on Sep 14,
so it should have been there.
Am I missing some very basic thing over here?
On Wed, Aug 12, 2015 at 12:42 PM, Akshat Kakkar <akshat.1984@gmail.com> wrote:
> I am running sl6.3 (i.e. kernel 2.6.32-279). I upgraded the kernel
> using elrepo to kernel 4.1.4.
> I downloaded iptables-20140916.tar.bz2 i.e. Sep 16, 2014 snapshot in
> order to test new functionality of skb-priority added in ipset 6.22.
> Prior to this my iptables version was 1.4.7
>
> I installed ipset .6.25 and create an ipset named test (ipset -N test
> hash:ip skbinfo)
>
>
> Then I Installed above mentioned Sep 16, 2014 iptables snapshot
>
> now it shows my version as 1.4.21
>
> when I execute follwing command
> iptables -t mangle -A POSTROUTING -o eth1 -j SET --map-set test src --map-prio
>
> it gives error
> iptables v1.4.21: unknown option "--map-set"
> Try `iptables -h' or 'iptables --help' for more information.
>
> prior to installing iptables, i execute follwing commands to stop
> iptables and remove iptables modules, so that old modules should not
> confilct.
>
> service iptables stop
> rmmod iptables_mangle
> rmmod iptables_filter
> rmmod iptables_nat
> rmmod ip_tables
>
>
> Please help.
next prev parent reply other threads:[~2015-08-12 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 7:12 unknown option "--map-set" Akshat Kakkar
2015-08-12 9:05 ` Akshat Kakkar [this message]
2015-08-12 9:29 ` Jozsef Kadlecsik
2015-08-12 9:45 ` Akshat Kakkar
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=CAA5aLPiHDNwK_mxiaTVYYCmZpkr1wyyjbMCa4CmQDhPrVVv3Yg@mail.gmail.com \
--to=akshat.1984@gmail.com \
--cc=netfilter@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;
as well as URLs for NNTP newsgroup(s).