Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31480 - [netcfg] resolv.conf does not list any nameservers after switching from sysvinit to systemd

Attached to Project: Arch Linux
Opened by Andrej Podzimek (andrej) - Sunday, 09 September 2012, 15:12 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 03 October 2012, 14:31 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

The summary says it all. Starting the netcfg.service connects to my WiFi network and configures both IPv6 and IPv4 addresses as expected. However, resolv.conf doesn't contain any nameserver lines (or any other uncommented lines). Both DHCP client daemons (dhcpcd and dhclient, for IPv4 and IPv6, respectively) are running.

Automatic DNS server configuration worked fine (with exactly the same configuration) before the switch from sysvinit to systemd.

A quick workaround of adding the DNS variable to the network's config file (and updating it manually) works fine. However, this information should be obtained automatically from DHCP and from router advertisements.

Additional info:

* package version(s)
netcfg 2.8.10-1
systemd 189-4
dhclient 4.2.4.1-2
dhcpcd 5.6.0-1

* config and/or log files etc.
The configuration file for netcfg is attached.

Steps to reproduce:
Try to connect to a network with DHCP (both v6 and v4) using netcfg.service.
   home6 (0.5 KiB)
This task depends upon

Closed by  Gaetan Bisson (vesath)
Wednesday, 03 October 2012, 14:31 GMT
Reason for closing:  No response
Comment by Gaetan Bisson (vesath) - Sunday, 09 September 2012, 15:59 GMT
Do you really have to blame four packages here? It's your DHCP client(s) who is/are supposed to update /etc/resolv.conf; what if you run them manually?

Loading...