From: "Łukasz Nierychło" <nofast@welnowiec.net>
To: netfilter@lists.netfilter.org
Subject: IPSET iptree problem
Date: Tue, 15 May 2007 16:24:05 +0200 [thread overview]
Message-ID: <op.tsdgyfm7343eys@comnetlap2.biuro.lan> (raw)
Hello everyone,
I would like to ask you to help me with ipset tool
because it works other way I expect when I use "timeout"
parameter.
look: (this is OK without "--timeout")
[root@rt ~]# ipset -N ts1 iptree
[root@rt ~]# ipset -A ts1 10.10.10.10
[root@rt ~]# ipset -T ts1 10.10.10.10
10.10.10.10 is in set ts1.
[root@rt ~]# ipset -T ts1 10.10.10.1
10.10.10.1 is NOT in set ts1.
[root@rt ~]# ipset -T ts1 10.10.10.255
10.10.10.255 is NOT in set ts1.
My question is what I did wrong here:
"--timeout" is used:
[root@rt ~]# ipset -N ts2 iptree --timeout 100
[root@rt ~]# ipset -A ts2 20.20.20.20
[root@rt ~]# ipset -T ts2 20.20.20.20
20.20.20.20 is in set ts2.
[root@rt ~]# ipset -T ts2 20.20.20.1
20.20.20.1 is in set ts2.
[root@rt ~]# ipset -T ts2 20.20.20.254
20.20.20.254 is in set ts2.
[root@rt ~]# ipset -T ts2 20.20.1.1
20.20.1.1 is NOT in set ts2.
If I use "timeout" then ipset test returns true
to all IPs on subnet 20.20.20.0/24.
Shouldn't this work the same way ( as without "timeout" )?
Is this ok ?
my linux = kernel-2.6.21.1
+ set patch (pom-ng-20070513)
+ ipset-20070514
Help me please
£ukasz Nierych³o
next reply other threads:[~2007-05-15 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 14:24 Łukasz Nierychło [this message]
[not found] <C9039844-4303-4FD1-9704-41366AFF5884@stanford.edu>
2007-08-23 13:09 ` IPSET iptree problem Łukasz Nierychło
2007-08-23 13:24 ` Jozsef Kadlecsik
2007-08-26 13:12 ` Jozsef Kadlecsik
-- strict thread matches above, loose matches on Subject: below --
2007-08-27 12:56 Re : " nofast
2007-08-27 16:40 ` Jozsef Kadlecsik
2007-08-27 20:52 ` Sami Farin
2007-09-05 10:39 ` Jozsef Kadlecsik
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=op.tsdgyfm7343eys@comnetlap2.biuro.lan \
--to=nofast@welnowiec.net \
--cc=netfilter@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.