Invalid resolv.conf configuration is generated
Bruce Schultz
Mon May 27 10:40:50 2019
Hi,
I'm getting the following line in my resolv.conf file after connecting
to my wifi. It seems like the interface name is appended after the ipv6
nameserver. DNS lookups have been failing
nameserver fe80::a62b:b0ff:fea5:6f5c%wlp3s0
It's coming from /run/resolvconf/interfaces/wlp3s0.ra, but that file
seems to be somewhat stale:
ls -lh /run/resolvconf/interfaces/
total 8.0K
-rw-r--r-- 1 root root 100 May 27 19:49 wlp3s0.dhcp
-rw-r--r-- 1 root root 100 May 21 20:42 wlp3s0.ra
Here's the latest dhcpcd log messages:
May 27 19:49:37 danger kernel: wlp3s0: authenticate with 00:26:5a:1b:02:5a
May 27 19:49:37 danger kernel: wlp3s0: send auth to 00:26:5a:1b:02:5a
(try 1/3)
May 27 19:49:37 danger kernel: wlp3s0: authenticated
May 27 19:49:37 danger kernel: iwlwifi 0000:03:00.0 wlp3s0: disabling HT
as WMM/QoS is not supported by the AP
May 27 19:49:37 danger kernel: iwlwifi 0000:03:00.0 wlp3s0: disabling
VHT as WMM/QoS is not supported by the AP
May 27 19:49:37 danger kernel: wlp3s0: associate with 00:26:5a:1b:02:5a
(try 1/3)
May 27 19:49:37 danger kernel: wlp3s0: RX AssocResp from
00:26:5a:1b:02:5a (capab=0x411 status=0 aid=4)
May 27 19:49:37 danger kernel: wlp3s0: associated
May 27 19:49:37 danger dhcpcd[1997]: wlp3s0: carrier acquired
May 27 19:49:37 danger dhcpcd[1997]: wlp3s0: IAID 5a:6e:31:f8
May 27 19:49:37 danger dhcpcd[1997]: wlp3s0: adding address
fe80::578:7f5c:bb45:f2c9
May 27 19:49:38 danger dhcpcd[1997]: wlp3s0: soliciting an IPv6 router
May 27 19:49:38 danger dhcpcd[1997]: wlp3s0: rebinding lease of
192.168.1.216
May 27 19:49:38 danger dhcpcd[1997]: wlp3s0: probing address
192.168.1.216/24
May 27 19:49:39 danger dhcpcd[1997]: wlp3s0: Router Advertisement from
fe80::a62b:b0ff:fea5:6f5c
May 27 19:49:39 danger dhcpcd[1997]: wlp3s0: soliciting a DHCPv6 lease
May 27 19:49:39 danger dhcpcd[1997]: wlp3s0: dropping DHCPv6 due to no
valid routers
...
May 27 19:49:43 danger dhcpcd[1997]: wlp3s0: leased 192.168.1.216 for
86400 seconds
May 27 19:49:43 danger dhcpcd[1997]: wlp3s0: adding route to 192.168.1.0/24
May 27 19:49:43 danger dhcpcd[1997]: wlp3s0: adding default route via
192.168.1.1
...
May 27 19:54:55 danger dhcpcd[1997]: wlp3s0: Router Advertisement from
fe80::a62b:b0ff:fea5:6f5c
May 27 19:54:55 danger dhcpcd[1997]: wlp3s0: soliciting a DHCPv6 lease
May 27 19:54:55 danger dhcpcd[1997]: wlp3s0: dropping DHCPv6 due to no
valid routers
I couldn't see any log messages at that time when the ra file was
generated. This laptop would have suspended and resumed several times in
the past week. I've noticed this behaviour in the past, but always
assumed it was something in the network config for this wifi point; but
that doesn't make sense for it to include the local interface name. I
don't think I've seen this with the other access point that I usually
use though. It seems to be more persistent in the past few days, maybe
because of the stale resolvconf file?
Running gentoo with
net-misc/dhcpcd-7.1.1-r3
net-dns/openresolv-3.9.0
Let me know if there's any details that might be relevant. Also, I'm
upgrading to dhcpcd-7.2.2 now to see if that helps.
Cheers
Bruce
Archive administrator: postmaster@marples.name