Control: tags -1 + patch Control: severity -1 important El 13/02/23 a las 20:38, Dmytro Kolesnykov escribió: > Package: ifupdown > Version: 0.8.41 > Severity: normal > > Dear Maintainer,
Dear ifupdown user, > > I was doing my network setup, which included statically configured > logical interfaces. So there were dns-nameservers entries in my > /etc/network/interfaces. My configuration files is below (the actual > IPs and MACs is wiped). > > I noted that ifup with my setup is producing error messages like this: > > ... > guessnet: Started tests > guessnet: 3 candidates > guessnet: Got ARP reply from 192.168.0.1 XX:XX:XX:XX:XX:XX > guessnet: ARP reply from 192.168.0.1 XX:XX:XX:XX:XX:XX matches > guessnet: Notified success of scan peer 192.168.0.1 XX:XX:XX:XX:XX:XX > guessnet: Removing candidate enp4s0-direct > guessnet: Keeping candidate enp4s0-router > guessnet: We had changes, notifying the listener > guessnet: Got ARP reply from 192.168.0.1 XX:XX:XX:XX:XX:XX > /etc/network/if-up.d/resolved: 69: DNS: not found > /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-enp4s0: > DNS=192.168.0.1 192.168.0.12: not found > Failed to parse DNS server address: DNS > Failed to set DNS configuration: Invalid argument > > I have found discussion about similar problem there: > https://unix.stackexchange.com/questions/714901/dns-broken-when-using-ifupdown-and-systemd-resolved-after-upgrade-to-ubuntu-22-0 > > Also I had a look into the /etc/network/if-up.d/resolved and I assume > this is a typo in the line 69: > https://salsa.debian.org/debian/ifupdown/-/blob/master/debian/if-up.d/resolved#L69 > [...] Thanks for reporting this issue, and for proposing the patch. Have you had the chance to test an IPv6 configuration? I'll need to change my setup for testing that. And I'd love add tests to check this. Cheers, -- Santiago
signature.asc
Description: PGP signature
