From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 4170D15800A for ; Wed, 23 Aug 2023 10:48:14 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7152C2BC112; Wed, 23 Aug 2023 10:48:09 +0000 (UTC) Received: from mx3.muc.de (mx3.muc.de [193.149.48.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D2CF72BC101 for ; Wed, 23 Aug 2023 10:48:08 +0000 (UTC) Received: (qmail 15216 invoked by uid 3782); 23 Aug 2023 12:48:07 +0200 Received: from acm.muc.de (p4fe15b37.dip0.t-ipconnect.de [79.225.91.55]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Wed, 23 Aug 2023 12:48:07 +0200 Received: (qmail 7330 invoked by uid 1000); 23 Aug 2023 10:48:06 -0000 Date: Wed, 23 Aug 2023 10:48:06 +0000 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Spurious error messages at boot up from the new dhcpcd Message-ID: References: <3254408.44csPzL39Z@rogueboard> <23193355.6Emhk5qWAg@rogueboard> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <23193355.6Emhk5qWAg@rogueboard> X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Archives-Salt: 03672712-a9a0-4da7-ace8-655f8e5a8977 X-Archives-Hash: 34939e5e44414693d11c6b3d19c2b1da Hello, Michael. On Tue, Aug 22, 2023 at 16:03:16 +0100, Michael wrote: > Hello Alan, > On Tuesday, 22 August 2023 14:00:26 BST Alan Mackenzie wrote: > > I don't understand what I just did, by deleting net.enp38s0, though it > > appeared to have fixed the problem. That worries me. Could you possibly > > explain to me a bit more what that removal did? Thanks! > There are different ways to configure and bring up your network interface. > If you have a complicated network configuration, with static address(es), > bridges, multihoming, etc. then using netifrc scripts is a convenient method > to automate default runlevel service(s) to manage your setup. OK. > For simpler network requirements a dhcp client, like dhcpcd, is adequate for > bringing up and configuring your network interface. Which is appropriate for my setup. > In absence of any manual settings netifrc will also bring up dhcpcd to try to > obtain an IP address from the router. > You had both a netifrc service and a dhcpcd service starting up, each trying > to negotiate an IP address from your router and tripping over themselves. Ah, so that was it! Thanks! > > On removing dhcpcd from default, the maching just has no network > > connection on booting up. > OK, sometimes a service which requires a network connection can bring in > dhcpcd - I have neither netifrc nor dhcpcd services starting here on their > own: > $ rc-update -s -v | grep 'dhcpcd|net' > dhcpcd | > local | default nonetwork > net-online | > net.lo | > netmount | default > but in my case I think chronyd starts dhcpcd to connect to the network. OK. > In your case, dhcpcd launched as a default service is needed to set up your > connection. Yes. Thanks again for the explanation. -- Alan Mackenzie (Nuremberg, Germany).