From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?utf-8?Q?Ludovic_Court=C3=A8s?= <ludo@gnu.org>
Subject: Re: wip-netlink
Date: Wed, 05 Jun 2019 15:23:13 +0200
Message-ID: <87lfyg2mke.fsf@gnu.org>
References: <CAE4v=pj4S-adVXDJ6uBw-_p5zdhLd_NoN0-zauD5_N6P+c9TLA@mail.gmail.com>
	<875zrov80a.fsf@gnu.org>
	<CAE4v=pi4+1rLnZE59u=ePLhUfa+A=HX-kNJ8SxHZ3PcLEvxkMg@mail.gmail.com>
	<87mukx8tew.fsf@gnu.org> <87woi278uk.fsf@devup.no>
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]:59796)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1hYVsq-0005z5-52
	for guix-devel@gnu.org; Wed, 05 Jun 2019 09:23:17 -0400
In-Reply-To: <87woi278uk.fsf@devup.no> (Marius Bakke's message of "Mon, 03 Jun
	2019 21:43:47 +0200")
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: Marius Bakke <mbakke@fastmail.com>
Cc: Guix-devel <guix-devel@gnu.org>

Hello,

Marius Bakke <mbakke@fastmail.com> skribis:

> Ludovic Court=C3=A8s <ludo@gnu.org> writes:
>
>> If you=E2=80=99ve ever experienced the shortcomings of
>> =E2=80=98static-networking-service=E2=80=99 and had to work around it, p=
lease share the
>> interface that you=E2=80=99d like to see!
>
> Hey, that's me!

Yay!

> I *think* what I want is control over network interfaces.  Something
> along the lines of
>
> (service network-interface-service-type
>   "eth0"
>   (network-interface-configuration
>     (dhcp? #f)
>     (ipv4 '("10.1.1.1/24" "172.16.30.4/22"))
>     (ipv6 '(...))
>     (routes4 '(("default" . "10.1.1.254")))
>     (routes6 '(...))
>     (requirement '(vswitchd))))
>
> Ideally, this service would extend "network-route-service-type" and
> "network-address-service-type" so that one could compose configurations
> from other services too.  E.g. a custom VPN service that extends
> network-route-service-type.

Interesting!  That sounds like a plan.

If there=E2=80=99s a separate =E2=80=9Croutes=E2=80=9D service, perhaps the=
 =E2=80=98routes4=E2=80=99 and
=E2=80=98routes6=E2=80=99 fields could even be removed from
=E2=80=98network-interface-configuration=E2=80=99?

We=E2=80=99d also need a =E2=80=98name-servers=E2=80=99 service I guess.

Also, in your example, =E2=80=98ipv4=E2=80=99 specifies both the IP and the=
 netmask,
right?  Perhaps we should separate the two?

Thanks,
Ludo=E2=80=99.