netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Jan Engelhardt <jengelh@medozas.de>, netfilter@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset 6.5 released
Date: Sun, 22 May 2011 22:32:31 +0100	[thread overview]
Message-ID: <4DD980EF.9010901@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1105222319130.27638@blackhole.kfki.hu>


> Thanks, that helped a lot! The ipset binary doesn't handle different sets 
> in a single restore file. I'll fix it in the next days.
>   
Interesting! The file I had with the 3 hash:net sets in it seems to be 
restored OK without any problems after applying the patch I've got from 
you yesterday (the sets I enclosed in the post you quoted were from a 
different file though). The problematic statements seem to be bitmap 
sets (bitmap:ip as well as bitmap:port)- it also looked to be choking on 
IP addresses specified as cidr (i.e. x.x.x.x/x). Anyway, let me know if 
you need anything else from me.

  reply	other threads:[~2011-05-22 21:32 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 13:50 [ANNOUNCE] ipset 6.5 released Jozsef Kadlecsik
2011-05-16 15:41 ` Mr Dash Four
2011-05-17  7:42   ` Jozsef Kadlecsik
2011-05-17 11:03     ` Mr Dash Four
2011-05-17 11:51       ` Jozsef Kadlecsik
2011-05-17 15:23         ` Mr Dash Four
2011-05-17 18:36           ` Mr Dash Four
2011-05-18  7:54             ` Jozsef Kadlecsik
2011-05-18 10:59               ` Mr Dash Four
2011-05-18 11:22                 ` Jozsef Kadlecsik
2011-05-21 19:42     ` Mr Dash Four
2011-05-21 19:45       ` Jozsef Kadlecsik
2011-05-21 19:58       ` Jozsef Kadlecsik
2011-05-21 20:11         ` Mr Dash Four
2011-05-21 21:31       ` Jozsef Kadlecsik
2011-05-21 21:33         ` Jan Engelhardt
2011-05-21 21:41           ` Mr Dash Four
2011-05-21 21:52             ` Jan Engelhardt
2011-05-21 23:08               ` Jozsef Kadlecsik
2011-05-22  1:01                 ` Mr Dash Four
2011-05-22 10:05                   ` Jozsef Kadlecsik
2011-05-22 10:36                     ` Jozsef Kadlecsik
2011-05-22 11:44                       ` Mr Dash Four
2011-05-22 11:44                     ` Mr Dash Four
2011-05-22 21:21                       ` Jozsef Kadlecsik
2011-05-22 21:32                         ` Mr Dash Four [this message]
2011-05-22 15:00                 ` Jan Engelhardt
2011-05-22 13:57               ` Mr Dash Four
2011-05-22 14:05                 ` Mr Dash Four
2011-05-21 21:51           ` Mr Dash Four
2011-05-21 21:41         ` Mr Dash Four
2011-05-21 22:28           ` Jozsef Kadlecsik
2011-05-21 22:41             ` Jozsef Kadlecsik
2011-05-21 22:44               ` Mr Dash Four
2011-05-21 22:42             ` Mr Dash Four
2011-05-22 14:52             ` Mr Dash Four
2011-05-21 22:15 ` Mr Dash Four
2011-05-21 22:31   ` Jozsef Kadlecsik
2011-05-21 22:42     ` Mr Dash Four
2011-05-21 22:49       ` Jozsef Kadlecsik
2011-05-21 22:57         ` Mr Dash Four
2011-05-21 23:25           ` Jozsef Kadlecsik
2011-05-21 23:33             ` Mr Dash Four
2011-05-22  9:56               ` 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=4DD980EF.9010901@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --cc=jengelh@medozas.de \
    --cc=kadlec@blackhole.kfki.hu \
    --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).