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:16:41 +0300
Message-ID:
 <CA+sCei0oNVNmD58DvMKmhaYcqZXU+-SHq2emYQ9uoDMTkd2XwA@mail.gmail.com>
In-Reply-To: <F89458DE-0F1F-4ED2-829A-CA5B2B50B837@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8252633850302834920=="
List-Id: <location.lists.ipfire.org>

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

On Tue, Mar 29, 2022 at 5:10 PM Michael Tremer
<michael.tremer(a)ipfire.org> wrote:
> Hmm, this should not happen like this.
>
> I am not even sure why this is trying to do any ioctls for terminals on the=
 output file.
>
> Is this reproducible with any of the other formats, too, or is it only xt_g=
eoip?

Indeed, I could not find what seems to cause this, and have not been
able to work around it.

I did not yet try other exporters - I have been focusing on xt_geoip
as we use it for a system's firewall rules.
But considering the IPv6 files for xt_geoip are being written
correctly, it feels to me like others exporters might work. Will
check.

Wanted to bring this to your attention before spending more time on
it, as you maybe were aware.

-Valters

--===============8252633850302834920==--