From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Spurious error messages at boot up from the new dhcpcd
Date: Wed, 23 Aug 2023 10:48:06 +0000 [thread overview]
Message-ID: <ZOXj5qx5uPeiZx6p@ACM> (raw)
In-Reply-To: <23193355.6Emhk5qWAg@rogueboard>
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).
next prev parent reply other threads:[~2023-08-23 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 9:56 [gentoo-user] Spurious error messages at boot up from the new dhcpcd Alan Mackenzie
2023-08-22 11:29 ` Michael
2023-08-22 13:00 ` Alan Mackenzie
2023-08-22 15:03 ` Michael
2023-08-23 10:48 ` Alan Mackenzie [this message]
2023-08-22 21:41 ` [gentoo-user] " Nuno Silva
2023-08-23 10:44 ` Alan Mackenzie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZOXj5qx5uPeiZx6p@ACM \
--to=acm@muc.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox