[arch-general] dhcpcd not working after install from custom iso
I had internet connection when installing from an iso I built using the archiso tools, but dhcpcd isn't connecting any more (starting via sytemd). I've also had internet access in previous installs of archlinux and FreeBSD, so I don't think there's anything wrong with the hardware. [dmesg output] http://pastebin.com/vtVRid1Y [ip link output] http://pastebin.com/gaZxUCmf The device I'm using is listed as enp2s0. It hangs, even though it's set up (pastebin for proof). Waiting for carrier? I also noticed that at the bottom of my dmesg, it reports only IPv6, not IPv4. Is this normal behavior? I think my network only supports IPv4, for dhcp anyway. Since I have to register the addresses of the NICs with the ISP, only enp2s0 should hypothetically be able to connect, not enp1s0. This is also the first time I've had a problem with dhcpcd. If it makes a difference, I built a custom iso (base) and dropped the bcache-tools package in /etc so I could set that up. I made no other modifications to the bulid. dhcpcd is at version 6.6.4-1 and is fully up-to-date. == LOG SNIPPET == dhcpcd@enp2s0.service - dhcpcd on enp2s0 Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; disabled) Active: failed (Result: exit-code) since Wed 2014-12-17 09:15:46 EST; 51s ago Process: 542 ExecStart=/usr/bin/dhcpcd -q -w %I (code=exited, status=1/FAILURE) Dec 17 09:15:16 vss dhcpcd[542]: version 6.6.4 starting Dec 17 09:15:16 vss dhcpcd[542]: enp2s0: waiting for carrier Dec 17 09:15:46 vss systemd[1]: dhcpcd@enp2s0.service: control process exited, code=exited status=1 Dec 17 09:15:46 vss systemd[1]: Failed to start dhcpcd on enp2s0. Dec 17 09:15:46 vss systemd[1]: Unit dhcpcd@enp2s0.service entered failed state. Dec 17 09:15:46 vss systemd[1]: dhcpcd@enp2s0.service failed. -- vixsomnis
On 17/12/14 09:22, Christian Demsar wrote:
I had internet connection when installing from an iso I built using the archiso tools, but dhcpcd isn't connecting any more (starting via sytemd). I've also had internet access in previous installs of archlinux and FreeBSD, so I don't think there's anything wrong with the hardware.
[dmesg output] http://pastebin.com/vtVRid1Y [ip link output] http://pastebin.com/gaZxUCmf
You say you configured your connection with systemd. Do you mean you enabled dhcpd@enp2s0.service? I suggest you disable it and use systemd-networkd instead. It is very simple. Create a file called /etc/systemd/network/enp2s0.network that contains: [Match] Name=enp2s0 [Network] DHCP=v4 Enable and start systemd-networkd.service and reboot. Your link should come up online. -- Pedro Alejandro López-Valencia https://about.me/palopezv
On December 17, 2014 2:46:07 PM EST, "P. A. López-Valencia" <vorbote@outlook.com> wrote:
I had internet connection when installing from an iso I built using
On 17/12/14 09:22, Christian Demsar wrote: the
archiso tools, but dhcpcd isn't connecting any more (starting via sytemd). I've also had internet access in previous installs of archlinux and FreeBSD, so I don't think there's anything wrong with the hardware.
[dmesg output] http://pastebin.com/vtVRid1Y [ip link output] http://pastebin.com/gaZxUCmf
You say you configured your connection with systemd. Do you mean you enabled dhcpd@enp2s0.service? I suggest you disable it and use systemd-networkd instead. It is very simple.
Create a file called /etc/systemd/network/enp2s0.network that contains:
[Match] Name=enp2s0 [Network] DHCP=v4
Enable and start systemd-networkd.service and reboot. Your link should come up online.
Thanks for the suggestion, but it turned out to be user error. I rechecked the hardware addresses, and enp1s0 was actually the dedicated nic I have registered. This is odd, since I tried both devices initially, and neither worked. It's working now, at any rate. Nothing wrong with dhcpcd at all. -- vixsomnis
Hi On Wed, Dec 17, 2014 at 10:22 PM, Christian Demsar <vixsomnis@fastmail.com> wrote:
I had internet connection when installing from an iso I built using the archiso tools, but dhcpcd isn't connecting any more (starting via sytemd). I've also had internet access in previous installs of archlinux and FreeBSD, so I don't think there's anything wrong with the hardware.
[dmesg output] http://pastebin.com/vtVRid1Y [ip link output] http://pastebin.com/gaZxUCmf
The device I'm using is listed as enp2s0. It hangs, even though it's set up (pastebin for proof). Waiting for carrier? I also noticed that at the bottom of my dmesg, it reports only IPv6, not IPv4. Is this normal behavior? I think my network only supports IPv4, for dhcp anyway.
Since I have to register the addresses of the NICs with the ISP, only enp2s0 should hypothetically be able to connect, not enp1s0. This is also the first time I've had a problem with dhcpcd.
If it makes a difference, I built a custom iso (base) and dropped the bcache-tools package in /etc so I could set that up. I made no other modifications to the bulid.
dhcpcd is at version 6.6.4-1 and is fully up-to-date.
== LOG SNIPPET ==
dhcpcd@enp2s0.service - dhcpcd on enp2s0 Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; disabled) Active: failed (Result: exit-code) since Wed 2014-12-17 09:15:46 EST; 51s ago Process: 542 ExecStart=/usr/bin/dhcpcd -q -w %I (code=exited, status=1/FAILURE)
This log does not provide enough information information about the failure. Run dhcpcd manually with debug enabled sudo dhcpcd -q -w enp2s0 -d And you'll have better luck to debug this problem by sending your questions upstream maillist.
Dec 17 09:15:16 vss dhcpcd[542]: version 6.6.4 starting Dec 17 09:15:16 vss dhcpcd[542]: enp2s0: waiting for carrier Dec 17 09:15:46 vss systemd[1]: dhcpcd@enp2s0.service: control process exited, code=exited status=1 Dec 17 09:15:46 vss systemd[1]: Failed to start dhcpcd on enp2s0. Dec 17 09:15:46 vss systemd[1]: Unit dhcpcd@enp2s0.service entered failed state. Dec 17 09:15:46 vss systemd[1]: dhcpcd@enp2s0.service failed. -- vixsomnis
participants (3)
-
"P. A. López-Valencia"
-
Anatol Pomozov
-
Christian Demsar