Thanks, both of you. The possibly significant difference in ipset list is
that I have Revision: 6 versus 5. (ipset -v gives v6.29, protocol version:
6)
The output from shorewall show capabilities |grep -i ipset is the same as
the other poster cited:
Ipset Match Counters (IPSET_MATCH_COUNTERS): Available
Ipset Match (IPSET_MATCH): Available
Ipset Match Nomatch (IPSET_MATCH_NOMATCH): Available
ipset V5 (IPSET_V5): Available
Is there something going on here related to the ipset revision number? If
so, how to fix it? ipset has been at v.6.x for years...
On Thu, Mar 30, 2017 at 5:49 PM, PGNet Dev <pgnet....@gmail.com> wrote:
> On 03/30/2017 09:34 AM, Matt Darfeuille wrote:
> > On 3/30/2017 8:34 AM, Norman Henderson wrote:
> >> Thank you Ian. Matt, I've done some more tests and this really looks
> like a
> >> shorewall bug.
>
> Did you update your capabilities?
>
> What's the output of
>
> shorewall-lite show capabilities | grep -i ipset
>
> Here, e.g.,
>
> Ipset Match Counters (IPSET_MATCH_COUNTERS): Available
> Ipset Match (IPSET_MATCH): Available
> Ipset Match Nomatch (IPSET_MATCH_NOMATCH): Available
> ipset V5 (IPSET_V5): Available
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Shorewall-users mailing list
> Shorewall-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shorewall-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
