On 2023-05-08 20:46, Per Jessen wrote:
Carlos E. R. wrote:
With wicked, the remote DNS information is in /run/wicked/leaseinfo.eth0.auto.ipv6 and leaseinfo.eth0.static.ipv4, but not in a form that can be included in dnsmasq.conf, I think:
But if you change NETCONFIG_DNS_POLICY to 'auto', you can use /run/dnsmasq-forwarders.conf, right? At least that is what I saw working this afternoon.
The file then changes to: nameserver 192.168.1.16 nameserver 2a02:9000::aaaa nameserver 2a02:9000::bbbb which is indeed the contents I need. I will have to check if the file remains static. [... writing after writing other paragraphs in this post] No, it is not. Telcontar:~ # l /run/dnsmasq-forwarders.conf -rw-r--r-- 1 root root 634 May 8 20:54 /run/dnsmasq-forwarders.conf Telcontar:~ # l /run/dnsmasq-forwarders.conf -rw-r--r-- 1 root root 634 May 8 20:54 /run/dnsmasq-forwarders.conf Telcontar:~ # l /run/dnsmasq-forwarders.conf -rw-r--r-- 1 root root 634 May 8 20:54 /run/dnsmasq-forwarders.conf Telcontar:~ # Telcontar:~ # l /run/dnsmasq-forwarders.conf -rw-r--r-- 1 root root 634 May 8 21:04 /run/dnsmasq-forwarders.conf Telcontar:~ # Thus, I can not use NETCONFIG_DNS_POLICY="auto".
/run/wicked/leaseinfo.eth0.auto.ipv6 is constantly being written!
Telcontar:~ # l /run/wicked/leaseinfo.eth0.auto.ipv6 -rw-r--r-- 1 root root 262 May 8 20:03 /run/wicked/leaseinfo.eth0.auto.ipv6 Telcontar:~ # l /run/wicked/leaseinfo.eth0.auto.ipv6 -rw-r--r-- 1 root root 262 May 8 20:04 /run/wicked/leaseinfo.eth0.auto.ipv6 Telcontar:~ #
This is the cause of the current problem that started this thread.
As I suggested in my first reply this morning "Sounds like a lease being renewed.".
But why every minute or so?
Now, why is /run/wicked/leaseinfo.eth0.auto.ipv6 being written every minute, I have no idea. Maybe my router is the culprit again.
It is definitely your router.
Ok, what command or file would tell the timeout? Yes, I'm googling, no success. See later below.
No idea now how to find out.
Old fashioned debugging. Follow the logic and look for when it breaks.
If a lease is being renewed, it is because it has expired. When it expires very quickly, that suggests it was issued with a very short lifetime. You ought to be able to see that in the log, I posted some typical messages earlier today. I get those on TW and leap15.5, but not on leap15.3 - maybe it is a wicked option that needs tweaking.
But those messages, if they are the ones I remember, do not happen in my machine.
Alternatively, run a tcpdump on the interface, only looking for ip6 traffic. Wireshark will probably break it down nicely for you.
My hunch - your router is issuing ipv6 leases with 60second lifetime. Dunno why.
It would suffice for now to prove it. There must be some command that prints the timeout of the lease. If I look on /var/lib/dhcp, the *lease files are dated year 2013. Telcontar:~ # l /var/lib/dhcp/dhclient.leases -rw-r--r-- 1 root root 0 Aug 12 2012 /var/lib/dhcp/dhclient.leases Telcontar:~ # So I hesitate to issue a dhcpclient command to find out the timeout of the lease and break something else.
Maybe it is just a difference between wicked and NM.
I think the key difference is in NETCONFIG_DNS_POLICY.
No, the file /run/NetworkManager/no-stub-resolv.conf has a different structure and purpose than /run/wicked/leaseinfo.eth0.auto.ipv6
cer@Beta:~> cat /run/NetworkManager/no-stub-resolv.conf
What about /run/dnsmasq-forwarders.conf ?
The Beta machine doesn't have dnsmasq.
So install it. That's what I did earlier, to test.
It would be easier to boot the Laicolasse partition, but that would break another unrelated test that I'm doing. I try to keep the Beta partition simple. Configuring dnsmasq would be a further complication. On 2023-05-08 21:03, Per Jessen wrote:
Per Jessen wrote:
lifetime. You ought to be able to see that in the log, I posted some typical messages earlier today. I get those on TW and leap15.5, but not on leap15.3 - maybe it is a wicked option that needs tweaking.
Ignore that - on the leap15.3 system where I see no wicked messages ... I am using NM. Duh. Sorry about the red herring.
I checked a couple of other systems, Leap 15.1 &B TW - I see the wicked log messages.
There are only two messages today from wicked, nothing about a lease changing:
Telcontar:~ # journalctl -b | grep -i wicked
Apr 14 23:42:13 Telcontar systemd[1]: Starting wicked AutoIPv4 supplicant service...
...
May 06 11:56:47 Telcontar wickedd[1571]: route ipv4 0.0.0.0/0 via 192.168.1.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease May 06 19:16:55 Telcontar wickedd[1571]: route ipv4 0.0.0.0/0 via 192.168.1.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease May 07 12:20:11 Telcontar wickedd[1571]: route ipv4 0.0.0.0/0 via 192.168.1.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease May 08 10:40:21 Telcontar wickedd[1571]: route ipv4 0.0.0.0/0 via 192.168.1.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease May 08 19:24:26 Telcontar wickedd[1571]: route ipv4 0.0.0.0/0 via 192.168.1.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease
I have started Ethereal, and run it for a minute or two, till I noticed the file /run/wicked/leaseinfo.eth0.auto.ipv6 changing. There are no dhcpv6 packets. Then I did a filter on IPv6 packets. There aren't many. Most are ICMP. I'll mail that direct to you if you want to have a look. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)