Re: dhclient-${IFNAME}.conf stopped working after upgrade FC32 -> FC34

2021-06-01 Thread Thomas Haller via networkmanager-list
Hi, First of all, as always: enable level=TRACE logging and look at the logs and have them ready for inspection. Read [1] for hints about logging. [1]

Re: dhclient-${IFNAME}.conf stopped working after upgrade FC32 -> FC34

2021-05-31 Thread Jason Vas Dias via networkmanager-list
I did try : 'set ipv4.dns 127.0.0.1 save persistant ' in 'nmcli c e $uuid', but this did not work either after an up / down - /etc/resolv.conf was not updated to contain only '127.0.0.1' - it did ALSO contain '127.0.0.1', but as a suffix, not a prefix - this is not what I want . This did

dhclient-${IFNAME}.conf stopped working after upgrade FC32 -> FC34

2021-05-31 Thread Jason Vas Dias via networkmanager-list
Good day - On an FC32 x86_64 box, which I just successfully upgraded to FC34 , now running NM 1.30.4-1.fc34.x86_64 : I had some custom dhclient configuration files, which used to be honored by NM - ie. they took effect before upgrade, but not after: