From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: wip-netlink
Date: Wed, 05 Jun 2019 15:23:13 +0200 [thread overview]
Message-ID: <87lfyg2mke.fsf@gnu.org> (raw)
In-Reply-To: <87woi278uk.fsf@devup.no> (Marius Bakke's message of "Mon, 03 Jun 2019 21:43:47 +0200")
Hello,
Marius Bakke <mbakke@fastmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> If you’ve ever experienced the shortcomings of
>> ‘static-networking-service’ and had to work around it, please share the
>> interface that you’d 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’s a separate “routes” service, perhaps the ‘routes4’ and
‘routes6’ fields could even be removed from
‘network-interface-configuration’?
We’d also need a ‘name-servers’ service I guess.
Also, in your example, ‘ipv4’ specifies both the IP and the netmask,
right? Perhaps we should separate the two?
Thanks,
Ludo’.
prev parent reply other threads:[~2019-06-05 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 20:44 wip-netlink Gábor Boskovits
2019-03-26 17:11 ` wip-netlink Ludovic Courtès
2019-04-08 15:20 ` wip-netlink Ludovic Courtès
2019-04-10 6:18 ` wip-netlink Gábor Boskovits
2019-04-10 21:03 ` wip-netlink Ludovic Courtès
2019-06-03 19:43 ` wip-netlink Marius Bakke
2019-06-05 13:23 ` Ludovic Courtès [this message]
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=87lfyg2mke.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.