From mboxrd@z Thu Jan  1 00:00:00 1970
From: Valters Jansons <valter.jansons@gmail.com>
To: location@lists.ipfire.org
Subject:
 Re: [0.9.12] export --format xt_geoip: (25, 'Inappropriate ioctl for device')
Date: Tue, 29 Mar 2022 17:25:41 +0300
Message-ID:
 <CA+sCei1L5HuvCQ-8f0rxTCndbKso6kzBAcFtAueE38HLJ8=DCQ@mail.gmail.com>
In-Reply-To:
 <CA+sCei0oNVNmD58DvMKmhaYcqZXU+-SHq2emYQ9uoDMTkd2XwA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0950991043645678771=="
List-Id: <location.lists.ipfire.org>

--===============0950991043645678771==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 29, 2022 at 5:16 PM Valters Jansons
<valter.jansons(a)gmail.com> wrote:
> On Tue, Mar 29, 2022 at 5:10 PM Michael Tremer
> <michael.tremer(a)ipfire.org> wrote:
> > Is this reproducible with any of the other formats, too, or is it only xt=
_geoip?
>
> But considering the IPv6 files for xt_geoip are being written
> correctly, it feels to me like others exporters might work. Will
> check.

Indeed, `export --format ipset --directory ~/ipset` works perfectly
fine, and the *v4.ipset files have content.

This seems to be xt_geoip for IPv4 only. Don't see any specific path
difference between IPv6 and IPv4 though, and I doubt that Ubuntu 20.04
has something to do with it, but you never know I suppose.

Will try to dig deeper.

-Valters

--===============0950991043645678771==--