Mea culpa, I completely overlooked this. Big sorry.
And in addition I can confirm this behaviour. Doing this rename manually
does keep the values.
I am just wondering, how can we apply that to the boot behaviour? It
does give some meat to the thesis, that something else is going on, but
how
23.05.2020 11:56, Ede Wolf пишет:
>>
>> tw:~ # systemctl stop NetworkManager.service
>> tw:~ # ip l set dev enp0s5 down
>> tw:~ # cat /proc/sys/net/ipv6/conf/enp0s5/use_tempaddr
>> 1
>> tw:~ # cat /proc/sys/net/ipv6/conf/enp0s5/addr_gen_mode
>> 1
>> tw:~ # echo 3 >
Hi,
I have a setup where my NFS server exports its /export/nfsroot for my
diskless clients.
To ease the deployment of this nfsroot, I'd like to be able to run
ansible roles directly in there to install the packages and
configurations directly in the nfsroot. I thought using an nspawn
container
Given lack of errors after interface rename, settings were most probably
applied correctly.
No. According to the log, the lack of errors after the rename result
simlpy in there are no more settings left that could be applied. Because
they all have been tried before. And failed. sysctl.conf
22.05.2020 22:17, Ede Wolf пишет:
> Am 22.05.20 um 17:58 schrieb Andrei Borzenkov:
>>>
>>> The problem is, that sysctl.conf is being executed before the interfaces
>>> get their eventual names.
>>>
>>
>> That sounds like actual bug. What systemd version do you use?
>
> At least it is, what the
