You were right, thank you. When I put net.enp2s0 back in, it came up on
reboot this time - the interface, that is. I guess there was something
else wrong when I still had it in the defaul runlevel. My faith in
openrc is restored :-)
On 08/19/19 22:35, n952162 wrote:
On 08/19/19 20:04, J. Roeleveld wrote:
On 19 August 2019 22:11:04 CEST, n952162<n952...@web.de> wrote:
My eth0/enp2s0 network adapter is configured so:
$ cat /etc/conf.d/net
config_enp2s0="192.168.179.20/24"
...
Why does dhcpcd think it can configure my interface and what's the
connection between /etc/conf.d/net and dhcpcd?
Do you have net.enp2s0 in your default runlevel?
If not, dhcp is used by default.
--
Joost
I had that and took it out in the hope that it wouldn't try to do
anything with the interface until instructed to do so.
What program is it that decides that it has to do something with the
interface if there are no instructions otherwise? That is, the
default case? udev? I don't think so. init?
I see in /etc/inittab:
l3:3:wait:/sbin/openrc default
but surely openrc doesn't service network adapters itself?
I currently have:
00~>rc-status
Runlevel: default
sysklogd [ started ]
sshd [ started ]
wpa_supplicant [ stopped ]
dhcpcd [ crashed ]
netmount [ started ]
virtualbox-guest-additions [ stopped ]
cronie [ started ]
acpid [ started ]
local [ started ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed/wanted
dbus [ started ]
modules-load [ started ]
Dynamic Runlevel: manual
net.enp2s0 [ started ]
I guess the answer to my question is probably that dhcpcd takes that
responsibility on for itself. Is there an option to dhcpcd that says
- "just do as you're told"?
But then, what program is it that reads /etc/conf.d/net? That program
gets to run when dhcpcd crashes?
