public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <CA+sCei1L5HuvCQ-8f0rxTCndbKso6kzBAcFtAueE38HLJ8=DCQ@mail.gmail.com> (raw)
In-Reply-To: <CA+sCei0oNVNmD58DvMKmhaYcqZXU+-SHq2emYQ9uoDMTkd2XwA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 767 bytes --]

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

  reply	other threads:[~2022-03-29 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+sCei11=+qTjjeWT+D0_8VRJZQhg+mwZn_BGcMmfSxHriKViw@mail.gmail.com>
2022-03-29 14:10 ` Michael Tremer
2022-03-29 14:16   ` Valters Jansons
2022-03-29 14:25     ` Valters Jansons [this message]
     [not found] <CA+sCei3rpFGm=5QYxP-tsG4bjZL6+NQHG07XG540QGVkng5U4w@mail.gmail.com>
2022-03-29 15:03 ` Michael Tremer
2022-03-30 15:36   ` Michael Tremer
2022-03-30 15:59     ` Valters Jansons
2022-03-30 16:04       ` Michael Tremer

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='CA+sCei1L5HuvCQ-8f0rxTCndbKso6kzBAcFtAueE38HLJ8=DCQ@mail.gmail.com' \
    --to=valter.jansons@gmail.com \
    --cc=location@lists.ipfire.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