Re: [systemd-devel] systemd-resolved/NetworkManager resolv.conf handling

2022-11-08 Thread Thomas HUMMEL
On 11/7/22 18:35, Barry Scott wrote: I do not know enough about how that works. I just tested something like this (as a proof of concept) : f5.sh root:root/0700 in /etc/NetworkManager/dispatcher.d/ #!/bin/bash usage() { local EXIT_VALUE=$1 echo "usage: "$SCRIPT_NAME" " exit

Re: [systemd-devel] systemd-resolved/NetworkManager resolv.conf handling

2022-11-07 Thread Barry Scott
> On 7 Nov 2022, at 10:24, Thomas HUMMEL wrote: > > > > On 11/6/22 22:30, Barry wrote: > > >> So a dirty hack is to replace /sbin/resolvconf with a script that >> does-the-right-thing. >> Uses resolvectl on the correct interface etc. But only when called by F5. > > Hello, > > thanks

Re: [systemd-devel] systemd-resolved/NetworkManager resolv.conf handling

2022-11-07 Thread Thomas HUMMEL
On 11/6/22 22:30, Barry wrote: So a dirty hack is to replace /sbin/resolvconf with a script that does-the-right-thing. Uses resolvectl on the correct interface etc. But only when called by F5. Hello, thanks for your answer. I just do it manually for now. But maybe one could user NM

Re: [systemd-devel] systemd-resolved/NetworkManager resolv.conf handling

2022-11-07 Thread Thomas HUMMEL
On 11/6/22 18:24, Petr Menšík wrote: Oh, understood. Then it is specific problem to Fedora, because I think other distributions do not use systemd's implementation of resolvconf binary. Hello, thanks for your answer I think original Debian resolvconf package does not use -a interface

Re: [systemd-devel] systemd-resolved/NetworkManager resolv.conf handling

2022-11-06 Thread Barry
> On 2 Nov 2022, at 15:20, Thomas HUMMEL wrote: > > On 10/31/22 12:19, Petr Menšík wrote: > > Hello, thank you and Barry as well for your answers > > >> I would suggest using strace to find what exactly it does and what it tries >> to modify. I expect sources for that client are not

Re: [systemd-devel] systemd-resolved/NetworkManager resolv.conf handling

2022-11-06 Thread Petr Menšík
Oh, understood. Then it is specific problem to Fedora, because I think other distributions do not use systemd's implementation of resolvconf binary. I think original Debian resolvconf package does not use -a interface parameter for anything serious. It just uses the same interface identifier

Re: [systemd-devel] systemd-resolved/NetworkManager resolv.conf handling

2022-11-02 Thread Thomas HUMMEL
On 10/31/22 12:19, Petr Menšík wrote: Hello, thank you and Barry as well for your answers I would suggest using strace to find what exactly it does and what it tries to modify. I expect sources for that client are not available. Well, digging a little deeper, here's what I've found out: 1)

Re: [systemd-devel] systemd-resolved/NetworkManager resolv.conf handling

2022-10-31 Thread Petr Menšík
On 10/26/22 20:44, Thomas HUMMEL wrote: Hello, I'm not sure if this is a systemd-resolved or NetworkManager question but it involves both (I know Thomas HALLER is a member of this list too) on Fedora release 36 (Thirty Six) using the following kernel and packages    

Re: [systemd-devel] systemd-resolved/NetworkManager resolv.conf handling

2022-10-27 Thread Barry
> On 26 Oct 2022, at 20:17, Thomas HUMMEL wrote: > > Hello, > > I'm not sure if this is a systemd-resolved or NetworkManager question but it > involves both (I know Thomas HALLER is a member of this list too) > > on > > Fedora release 36 (Thirty Six) using the following kernel and

[systemd-devel] systemd-resolved/NetworkManager resolv.conf handling

2022-10-26 Thread Thomas HUMMEL
Hello, I'm not sure if this is a systemd-resolved or NetworkManager question but it involves both (I know Thomas HALLER is a member of this list too) on Fedora release 36 (Thirty Six) using the following kernel and packages 5.19.16-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC