[SOVLED] error when enabling dhcpd for an interface

redmaw · 2016-04-10 00:55:02

Hi,

I was following the Beginners' Guide to get familiar with Arch and everything was going smoothly until I tried to bind the dhcpd to my network interface. I have reviewed the dhcpd and Network Configuration wiki pages and forums but I just can't figure out why I am getting this error. Can someone help me figure out what I am doing wrong? The details are below.

FYI this is running on VirtualBox.

[root@archiso /]# ls /sys/class/net
enp0s3    lo

[root@archiso /]# systemctl enable dhcpcd@enp0s3.service
Operation falied: No such file or directory

Thanks,
redmaw

EDIT:
Changed old title from ""No such file or directory" error when enabling dhcpd for an interface" in order to mark it as solved.

Root Cause: Must have been user error as the actual install works and it did not reproduce on the first try.

Last edited by redmaw (2016-04-10 21:02:55)

headkase · 2016-04-10 01:14:15

Does:

ip link

Give the same adapter name? Link is how I always get it.

redmaw · 2016-04-10 01:50:11

Yes, same name.

[root@archiso /]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 08:00:27:85:55:37 brd ff:ff:ff:ff:ff:ff

Last edited by redmaw (2016-04-10 01:51:49)

headkase · 2016-04-10 03:06:18

What is the output of:

ping -c 3 www.google.com

? If you have a wired connection and are booted into the Arch installation medium then it should automatically establish an internet connection and you do not enable the interface until later when you are arch-chroot'ed into your actual installation.

Trying to enable the interface with systemctl is an error until after you are chroot'ed.

Trilby · 2016-04-10 03:18:47

There very well may be some things missing from the iso that are in a normal persistent install. In this case enabling a service doesn't make any sense as it can't have any effect as any change you make in the iso does not remain after a reboot, and "enable" only has an effect after a reboot.

Docbroke · 2016-04-10 04:24:57

can you run this successfully,

dhcpcd enp0s3

before enabling the service

Trilby · 2016-04-10 12:24:35

erm ... again: enabling services in the iso is pointless. Whatever the problem is here, enabling anything in the iso is not the solution. To that end, redmaw, it looks like you have a connection already on your ethernet device, so is there a problem at all?

redmaw · 2016-04-10 20:59:33

Hi all, thanks for the suggestions. I had network connection and I was chrooted into the new install (as per the guide's instructions) so as far as I understand I was not trying to enable the service on the iso. Rebooting and logging into the actual install did work however so there is no real problem. I created another VM this morning to see if I could reproduce the issue however it did not so this was most likely user error, though I have no idea what I might have done differently.

Thanks for the help and apologies for making a thread over something like this.

Trilby · 2016-04-10 21:11:31

redmaw wrote:

I was chrooted into the new install (as per the guide's instructions) so as far as I understand I was not trying to enable the service on the iso.

Not according to the output in your initial post:

[root@archiso /]#

You must have exited the chroot before those commands.

redmaw · 2016-04-10 21:49:56

For me the prompt on the arch iso is

root@archiso ~ #

and when chrooted

root@archiso ~ # arch-chroot /mnt /bin/bash
[root@archiso /]#

root@archiso ~ # arch-chroot /mnt
sh-4.3#

I tried to get a script to show this better but it did not work well: http://pastie.org/private/tyxffp4iuguu74gjuwluiw

Trilby · 2016-04-10 23:48:55

Ah, that could be - sorry. I've never specified bash for the chroot shell. But once you set your hostname - which comes before setting up network services - that prompt should change.

PierreG27 · 2016-10-18 23:30:32

Hello,
I just want to say thank you.
As Redmaw did, i read all the istalation guide.
But i must have miss something, because i always have to restart the dhcpcd service, each time.

i must have not done 'systemctl enable dhcpcd@enp0s3.service', because, i just did it, and this solved my problem!

Thank!

Arch Linux

#1 2016-04-10 00:55:02

[SOVLED] error when enabling dhcpd for an interface

#2 2016-04-10 01:14:15

Re: [SOVLED] error when enabling dhcpd for an interface

#3 2016-04-10 01:50:11

Re: [SOVLED] error when enabling dhcpd for an interface

#4 2016-04-10 03:06:18

Re: [SOVLED] error when enabling dhcpd for an interface

#5 2016-04-10 03:18:47

Re: [SOVLED] error when enabling dhcpd for an interface

#6 2016-04-10 04:24:57

Re: [SOVLED] error when enabling dhcpd for an interface

#7 2016-04-10 12:24:35

Re: [SOVLED] error when enabling dhcpd for an interface

#8 2016-04-10 20:59:33

Re: [SOVLED] error when enabling dhcpd for an interface

#9 2016-04-10 21:11:31

Re: [SOVLED] error when enabling dhcpd for an interface

#10 2016-04-10 21:49:56

Re: [SOVLED] error when enabling dhcpd for an interface

#11 2016-04-10 23:48:55

Re: [SOVLED] error when enabling dhcpd for an interface

#12 2016-10-18 23:30:32

Re: [SOVLED] error when enabling dhcpd for an interface

Board footer