GNU bug report logs -
#51440
[PATCH 00/10] Declarative static networking interface
Previous Next
Reported by: Ludovic Courtès <ludo <at> gnu.org>
Date: Wed, 27 Oct 2021 14:00:02 UTC
Severity: normal
Tags: patch
Done: Ludovic Courtès <ludo <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #113 received at 51440 <at> debbugs.gnu.org (full text, mbox):
Hi Vivien,
Vivien Kraus <vivien <at> planete-kraus.eu> skribis:
> Le vendredi 10 décembre 2021 à 11:51 +0100, Ludovic Courtès a écrit :
>> Vivien Kraus <vivien <at> planete-kraus.eu> skribis:
[...]
>> Julien fixed this interesting bug in Guile-Netlink 1.1.1, which is now
>> in ‘master’ (thanks!).
>>
>> I rebased ‘wip-networking-netlink’ to get this fix.
>>
>> Could you give it another try?
>
> The IP seems good.
\o/
>> Any other issues left?
>
> I have a couple:
> - I get an extra IPv6 (inet6 xxxx/64 scope global dynamic mngtmpaddr
> valid_lft forever preferred_lft forever) that I did not ask for and
> that takes precedence as a source for the default route, which defeats
> the purpose. I’m not sure it’s guile-netlink’s fault.
Hmm, what’s that IPv6 address? Is it here even if you do not configure
any IPv6 address in ‘static-networking’?
Julien, could the ‘link-set’ call in ‘network-set-up/linux’ be the
culprit?
#$@(map (lambda (address)
#~(begin
(addr-add #$(network-address-device address)
#$(network-address-value address)
#:ipv6?
#$(network-address-ipv6? address))
;; FIXME: loopback?
(link-set #$(network-address-device address)
#:up #t)))
addresses)
It seems to be the only way to mark the device as “up”, but since it has
arguments that seem redundant with those of ‘addr-add’, I wonder if
something could go wrong here.
Thanks for testing, Vivien!
Ludo’.
This bug report was last modified 3 years and 155 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.