Carlos E. R. wrote:
El 2023-05-09 a las 09:05 +0200, Per Jessen escribió:
AND, I can not use a file that changes every minute, even if I wanted what it contains!
Well, although it is of course too much, it would still work.
(with a lot of noise in the logs. I can not stand that, it drives me nuts. I was trained to analyze logs, it was my job. That is the problem that started this thread, noise in the logs).
Well, if that is your primary focus, log messages can be suppressed. :-)
Per, I'll try to explain again. The way dnsmasq works, it *has* to be configured this way (if using wicked):
There is really no need to explain, I am perfectly well aware of how it works. The man page is very comprehensive.
To achieve the above, I need this /etc/sysconfig/network/config:
NETCONFIG_DNS_POLICY='STATIC' NETCONFIG_DNS_FORWARDER='dnsmasq' NETCONFIG_DNS_STATIC_SEARCHLIST='valinor' NETCONFIG_DNS_STATIC_SERVERS='127.0.0.1 ::1' NETCONFIG_DNS_FORWARDER_FALLBACK="yes"
It *has* to be done this way or it doesn't work properly.
I beg to differ. On my office laptop, the only place I use dnsmasq, I have the following: NETCONFIG_DNS_POLICY='auto' NETCONFIG_DNS_FORWARDER='dnsmasq' NETCONFIG_DNS_STATIC_SEARCHLIST='' NETCONFIG_DNS_STATIC_SERVERS='' NETCONFIG_DNS_FORWARDER_FALLBACK="yes" It works just fine, so clearly it doesn't *have* to be done your way. Local nameservers are included from /etc/resolv.conf, added to the dnsmasq config.
/etc/resolv.conf must point only to the local dnsmasq service.
I disagree. This works perfectly fine for me: search local.net z.local.net i.local.net nameserver 127.0.0.1 nameserver 192.168.2.254 nameserver 2001:db8:4c68:1::1000
It must not be allowed to point to external servers, because that means that programs (say firefox) may bypass dnsmasq and waste time waiting for the remote server to answer.
I suggest that is plainly wrong. Most applications do not "bypass" dnsmasq, they are not even aware. Applications use the glibc resolver, which works in a well-defined way. For instance, nameservers are tried in the order they are listed. (unless you have specified "options rotate").
The only remaining issue is finding out why the router sends advertisements that causes Linux to rewrite the "/run/wicked/leaseinfo.eth0.auto.ipv6" to be written every minute, despite nothing apparently changing.
FWIW, mine also changes quite often, but it varies - sometimes after 30 seconds, sometimes 3 minutes.
Which to me means the fault is not my router, but Linux, ie, wicked. NM works properly.
Well, as you are excluding the router, I guess it is something specific to your machine, so we can close with "unable to reproduce". I have 25-30 machines with wicked, one with NM. Hmm, I might have a Raspi with NM, not sure. -- Per Jessen, Zürich (23.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes