GNU bug report logs - #44571
Cannot configure a static IPv6 with static-networking-service-type

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 44571 in the body.
You can then email your comments to 44571 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: divoplade <d <at> divoplade.fr>
To: bug-guix <at> gnu.org
Subject: Cannot configure a static IPv6 with static-networking-service-type
Date: Wed, 11 Nov 2020 11:56:24 +0100

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.

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

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Julien Lepiller <julien <at> lepiller.eu>
To: bug-guix <at> gnu.org,divoplade <d <at> divoplade.fr>,44571 <at> debbugs.gnu.org
Subject: Re: bug#44571: Cannot configure a static IPv6 with
 static-networking-service-type
Date: Wed, 11 Nov 2020 07:03:30 -0500

Le 11 novembre 2020 05:56:24 GMT-05:00, divoplade <d <at> 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

Message #18 received at 44571-done <at> debbugs.gnu.org (full text, mbox):

From: Jack Hill <jackhill <at> jackhill.us>
To: 44571-done <at> debbugs.gnu.org
Subject: Re: bug#44571: Cannot configure a static IPv6 with
 static-networking-service-type
Date: Thu, 27 Jan 2022 15:56:50 -0500 (EST)

Hi,

I believe this was fixed in c8609493ba6fd36c05815cad198060e54ea8c4f9 (and 
related commits before and after). See the manual about the new 
static-networking-service-type and welcome to the future!

Cheers,
Jack

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.