unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: 44571@debbugs.gnu.org, d@divoplade.fr
Subject: bug#44571: Cannot configure a static IPv6 with static-networking-service-type
Date: Wed, 11 Nov 2020 07:03:30 -0500	[thread overview]
Message-ID: <3121D0B2-5320-4232-A968-E68A791F6A80@lepiller.eu> (raw)
In-Reply-To: <1ec636e29d4ab70948fce3cf016d5240977a4423.camel@divoplade.fr>



Le 11 novembre 2020 05:56:24 GMT-05:00, divoplade <d@divoplade.fr> a écrit :
>Dear guix,
>
>My interface should be configured to have 2 static ip addresses, an
>IPv4 address and a global IPv6 address.
>
>The static-networking-service-type will only accept one per device, and
>will reject the IPv6 address (if I drop the IPv4 address) because it
>can't parse it.

Thanks for the report. This is a known issue and I'm working on it. The idea is to implement the netlink interface in guile and use it to configure the network. I currently have the low-level bits for managing interfaces and addresses. I'm missing the routing part. Once I have this, I can think of a high-level interface that will allow us to build a static-network-service-type that understands IPv4 and IPv6.

See https://git.lepiller.eu/guile-netlink

>
>My workaround is to add a shepherd service that runs ip address add dev
>eno1 the-address and ip address delete dev eno1 the-address, with ip
>from iproute2. Maybe static-networking-service-type could do something
>better for me?
>
>Best regards,
>
>divoplade




  reply	other threads:[~2020-11-11 12:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11 10:56 bug#44571: Cannot configure a static IPv6 with static-networking-service-type divoplade
2020-11-11 12:03 ` Julien Lepiller [this message]
2022-01-27 20:56   ` Jack Hill

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3121D0B2-5320-4232-A968-E68A791F6A80@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=44571@debbugs.gnu.org \
    --cc=d@divoplade.fr \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).