I have a problem with netcfg on start up. I am configured my system to connect automatically using a sequence of configurations:
[saro@wendell ~]$ cat /etc/conf.d/netcfg # Enable these netcfg profiles at boot time. # - prefix an entry with a '@' to background its startup # - set to 'last' to restore the profiles running at the last shutdown # - set to 'menu' to present a menu (requires the dialog package) # Network profiles are found in /etc/network.d #NETWORKS=(@home-eth @home-wifi) NETWORKS=(@groningen_eth @groningen_wifi @eduroam) # Specify the name of your wired interface for net-auto-wired WIRED_INTERFACE="eth0" # Specify the name of your wireless interface for net-auto-wireless WIRELESS_INTERFACE="wlan0" # Array of profiles that may be started by net-auto-wireless. # When not specified, all wireless profiles are considered. #AUTO_PROFILES=("profile1" "profile2")
[saro@wendell ~]$ sudo cat /etc/network.d/groningen_eth CONNECTION='ethernet' DESCRIPTION='Groningen Room connection' INTERFACE='eth0' #IP='dhcp' IP='static' ADDR='192.168.1.44' GATEWAY='192.168.1.1' DNS=('18.104.22.168') ## for DHCPv6 #IP6='dhcp' ## for IPv6 autoconfiguration #IP6='stateless' POST_UP='systemctl restart openntpd'
When I boot my system the wired interface seems loading well, but I can't use internet due missing DNS. So every time I have to edit /etc/resolv.conf manually or just reconnect the interface.
This problem appear only during the start up, if I try to load a configuration after netcfg work properly.
Somebody else had the same issue?
Is there anything relavent in the journal?
I was under the impression that if you are not using something like dhcpcd or dhclient, the file /etc/resolv.conf will not be dynamically created.
You might also want to try netctl (I think it is still in testing) as it appears that it will soon replace netcfg. Though I think that netcfg will still be in [extra] or [community].