From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Handbook and question about manual network setup
Date: Fri, 19 Apr 2024 17:38:11 +0100 [thread overview]
Message-ID: <23478664.6Emhk5qWAg@rogueboard> (raw)
In-Reply-To: <bee5cea7-343b-9ff8-d1da-f4281048ec53@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1937 bytes --]
On Friday, 19 April 2024 17:20:44 BST Dale wrote:
> Matt Connell wrote:
> > On Fri, 2024-04-19 at 09:05 -0500, Dale wrote:
> >> Basically, I want to be able to start/stop/restart enp3s0 as a
> >> service and have it in a runlevel.
> >
> > You should just need to create a symlink at /etc/init.d/net.enp3s0 that
> > points to /etc/init.d/net.lo and then you can do the usual rc-service
> > stuff with it.
>
> I did that and went from default to boot runlevel and back to default
> again but I still couldn't restart with the net.enp3s0 file. Luckily, I
> shut the rig down a bit ago. I went to mow some grass. Using push
> mower since battery went bad on riding mower. Anyway, when I booted it
> back up just now, it worked. I can start/stop/restart with the enp3s0
> file like on my main rig. It still says it is defaulting to DHCP which
> makes me think I'm still missing something. It says, I'm typing this in
> manually.
>
>
> Bringing up interface enp3s0
> config_enp3s0 not specified; defaulting to DHCP
>
>
> Then it continues bringing up the network. I have this set:
>
> nas / # cat /etc/conf.d/net
> config_enp3s0="dhcp"
> dns_servers_enp3s0="8.8.8.8 8.8.4.4"
> nas / #
>
>
> Since I have it set to use DHCP already, why is it saying it is
> defaulting to it? Did I miss a file or something? Shouldn't it just
> use it without saying it is defaulting to it? I don't recall seeing
> this on my main rig.
>
> Dale
>
> :-) :-)
Normally you would use netifrc to configure a gateway and static IP address.
DHCP is a fallback, in case the static IP subnet has changed - e.g. because
you changed your home router.
If you *are* using dhcpcd to obtain an IP address from the router then
arguably your don't need netifrc at all, as I explained in my other message
earlier.
Regarding the messages you see on your main rig Vs the old rig, you can
compare the two PC's conf.net files for any differences.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-19 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 14:05 [gentoo-user] Handbook and question about manual network setup Dale
2024-04-19 14:22 ` Matt Connell
2024-04-19 16:20 ` Dale
2024-04-19 16:38 ` Michael [this message]
2024-04-19 17:04 ` Dale
2024-04-19 17:13 ` Michael
2024-04-21 2:32 ` Dale
2024-04-21 9:52 ` Michael
2024-04-22 14:34 ` Dale
2024-04-19 15:16 ` Michael
2024-04-19 16:26 ` Dale
2024-04-19 16:34 ` Michael
2024-04-19 16:47 ` Matt Connell
2024-04-21 19:36 ` J. Roeleveld
2024-04-22 7:36 ` Michael
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=23478664.6Emhk5qWAg@rogueboard \
--to=confabulate@kintzios.com \
--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