bug#44571: closed (Cannot configure a static IPv6 with static-networking-service-type)

[GNU bug Tracking System]

Your message dated Thu, 27 Jan 2022 15:56:50 -0500 (EST)
with message-id <alpine.DEB.2.21.2201271554470.9433@marsh.hcoop.net>
and subject line Re: bug#44571: Cannot configure a static IPv6 with 
static-networking-service-type
has caused the debbugs.gnu.org bug report #44571,
regarding Cannot configure a static IPv6 with static-networking-service-type
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
44571: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44571
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Cannot configure a static IPv6 with static-networking-service-type
>
>
>
>
> Date: 
>
> Wed, 11 Nov 2020 11:56:24 +0100
>
>
>
>
> User-agent: 
>
> Evolution 3.34.2 
>
>
>
>
> 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
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#44571: Cannot configure a static IPv6 with static-networking-service-type
>
>
>
>
> Date: 
>
> Thu, 27 Jan 2022 15:56:50 -0500 (EST)
>
>
>
>
> User-agent: 
>
> Alpine 2.21 (DEB 202 2017-01-01)
>
>
>
>
> 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
>
>
>
> --- End Message ---