From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: Status update on 1.0 Date: Fri, 15 Mar 2019 14:51:35 +0100 Message-ID: <87zhpw2ql4.fsf@gnu.org> References: <871s3a4xd4.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:40171) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4nSr-0002se-Ju for guix-devel@gnu.org; Fri, 15 Mar 2019 10:05:38 -0400 In-Reply-To: (=?utf-8?Q?=22G=C3=A1bor?= Boskovits"'s message of "Thu, 14 Mar 2019 22:16:42 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?utf-8?Q?G=C3=A1bor?= Boskovits Cc: Guix-devel Hi, G=C3=A1bor Boskovits skribis: > Ludovic Court=C3=A8s 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 d= o that >> rather than the old ioctls currently used in (guix build syscalls). >> >> The netlink interface for network config is vaguely documented at >> . >> Writing bindings for =E2=80=98sendmsg=E2=80=99 and the associated da= ta structures >> looks reasonable=E2=80=A6 it just needs to be done. >> > > I am interested in doing this. Awesome! > 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 ioctl > cannot be fully dropped. (It still provides funcions that are needed > to get the netlink working) Yes, I think we can keep it. > 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? For now, we=E2=80=99ll have to ignore the other kernel. Longer-term, I suppose we should provide an abstraction over network configuration and have it translated to Netlink messages or Hurd RPCs. > Also a nice low level binding written in C is available as libmnl: > https://netfilter.org/projects/libmnl/index.html Or libnl also. Though if it=E2=80=99s not too hard, I=E2=80=99d rather hav= e us directly bind to =E2=80=98sendmsg=E2=80=99, =E2=80=98struct msghdr=E2=80=99, and so = on. Thanks, Ludo=E2=80=99.