From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= <boskovits@gmail.com>
Subject: Re: Status update on 1.0
Date: Thu, 14 Mar 2019 22:16:42 +0100
Message-ID: <CAE4v=pi6z8zfVZjC3G9HwZ=mW03pWb3KRhmJGbE=tHK7vPBj1w@mail.gmail.com>
References: <871s3a4xd4.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:51139)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <boskovits@gmail.com>) id 1h4Xir-0001iX-5A
	for guix-devel@gnu.org; Thu, 14 Mar 2019 17:17:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <boskovits@gmail.com>) id 1h4Xiq-0003zF-6q
	for guix-devel@gnu.org; Thu, 14 Mar 2019 17:17:05 -0400
In-Reply-To: <871s3a4xd4.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>

Hello Ludo,

Ludovic Court=C3=A8s <ludo@gnu.org> ezt =C3=ADrta (id=C5=91pont: 2019. m=C3=
=A1rc. 13., Sze, 16:21):
>
> Hello Guix!

>   =E2=80=A2 IPv6 support in =E2=80=98static-networking-service=E2=80=99: =
as discussed at the
>     Guix Days, we=E2=80=99ll probably need to Linux Netlink sockets to do=
 that
>     rather than the old ioctls currently used in (guix build syscalls).
>
>     The netlink interface for network config is vaguely documented at
>     <https://wiki.linuxfoundation.org/networking/generic_netlink_howto>.
>     Writing bindings for =E2=80=98sendmsg=E2=80=99 and the associated dat=
a structures
>     looks reasonable=E2=80=A6 it just needs to be done.
>

I am interested in doing this. However, there are a few points that needs
to be clarified:
1. I came to the same conclusion regarding the netlink stuff, but the old i=
octl
cannot be fully dropped. (It still provides funcions that are needed to get
the netlink working)
2. This might be linux specific. What do we do on other kernels?
(It might be reasonable to provide the abstractions in a module, and
from there select an available implementation, or signal an error that
the functionality is not yet implemented for this system...)
Wdyt?

Also a nice low level binding written in C is available as libmnl:
https://netfilter.org/projects/libmnl/index.html

>
> Ludo=E2=80=99.
>

Best regards,
g_bor