[prev in list] [next in list] [prev in thread] [next in thread]
List: gentoo-user
Subject: Re: [gentoo-user] Handbook and question about manual network setup
From: Dale <rdalek1967 () gmail ! com>
Date: 2024-04-22 14:34:52
Message-ID: dd9bd3ea-e050-f923-59f4-82add5ec209e () gmail ! com
[Download RAW message or body]
Michael wrote:
> Hi Dale,
>
> On Sunday, 21 April 2024 03:32:32 BST Dale wrote:
>
>> OK. I did my weekend OS updates on my main rig, fireball. That
>> involves me switching to boot runlevel and back again. When the network
>> started, no message about going to default. It just showed it starting
>> up and using DHCP. Looks like this:
>>
>>
>> * Bringing up interface enp3s0
>> * dhcp ...
>> * Running dhcpcd ...
>>
>>
>>
>> I thought of something. My NAS box is shutdown right now so can't
>> check. I bet DHCP is set to start in the default runlevel. On my main
>> rig it is not set to start the DHCP service at all. I suspect the NAS
>> box finds the DHCP service first and starts the network and then finds
>> the network service but it is already started. When it starts the
>> network with the DHCP service, it does the default thing. I'll test
>> that next time I boot up the NAS box.
> On one box here I have neither netifrc configured, nor dhcpcd, although both
> are installed. I have also made sure networkmanager is not installed.
>
> However, netmount is in the default runlevel and netmount has the default net
> dependency enabled:
>
> $ grep -v "^#" /etc/conf.d/netmount
> rc_need="net"
>
> $ rc-update show -v | grep -i net
> local | default nonetwork
> net-online |
> net.lo |
> netmount | default
>
> I believe this is what kicks in on my system first and brings up dhcpcd, which
> in turn obtains an IP address from my router. I mostly configure static IP
> addresses for known devices in my LAN on the router.
>
> You can compare which network services are configured to come up on your NAS
> Vs your main PC and also check any differences in /etc/rc.conf. Finally
> search for "rc_need=" dependencies defined in your /etc/conf.d/*.
>
> https://wiki.gentoo.org/wiki/OpenRC#Dependency_behavior
>
>
>> I guess no one else found a way to get the install handbook on a single
>> page. I'll have to copy and paste I guess. That's gonna take a while.
>> O_O
>>
>> Dale
>>
>> :-) :-)
> To save you copying:
>
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation
>
> but note the warning about links redirecting to individual pages:
>
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Full
My thought was right. My main rig does not have dhcpcd in any
runlevel. I booted up the NAS box and checked to see if dhcpcd was
listed anywhere. Sure enough, it was in the default runlevel. I
removed it and then rebooted. There was no mention of defaulting to
anything, the network just came up. So, I guess dhcpcd was trying to
start the network first which means it never really saw any of the
config files I was adding info too. It was starting before those came
into the picture. So, now both rigs work the same and I can
start/stop/restart the network on both machines the same way.
I suspect if I edited some dhcp config file and set up the ethernet the
proper way, it would just come up like it does now, after the change.
Also, nothing against dhcp on my part. My main rig uses it. I wanted
the NAS box to use it as well, just the same as my main rig. It works
great, even if one doesn't do anything to it. Having it set up tho does
give more consistent results, as in the same IP address. I can't recall
the last time I had dhcp to fail actually.
Thanks for the links on the full docs on one page. I already copy and
pasted it to a LOo doc and am editing out parts I won't ever use. It's
116 pages and I'm sure there are parts in there that won't ever apply to
me, systemd for example. Maybe I can get the page count down to 100 or
so. If I'm lucky.
Is there anyway to know when the doc changes and what changes? And how
did you find that link? I looked everywhere. :/
Dale
:-) :-)
[Attachment #3 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Michael wrote:<br>
</div>
<blockquote type="cite" cite="mid:1966149.PYKUYFuaPT@rogueboard">
<div class="moz-text-plain" wrap="true" graphical-quote="true"
style="font-family: -moz-fixed; font-size: 12px;"
lang="x-unicode">
<pre class="moz-quote-pre" wrap="">Hi Dale,
On Sunday, 21 April 2024 03:32:32 BST Dale wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre class="moz-quote-pre" wrap="">OK. I did my weekend OS updates on my \
main rig, fireball. That involves me switching to boot runlevel and back again. \
When the network started, no message about going to default. It just showed it \
starting up and using DHCP. Looks like this:
* Bringing up interface enp3s0
* dhcp ...
* Running dhcpcd ...
I thought of something. My NAS box is shutdown right now so can't
check. I bet DHCP is set to start in the default runlevel. On my main
rig it is not set to start the DHCP service at all. I suspect the NAS
box finds the DHCP service first and starts the network and then finds
the network service but it is already started. When it starts the
network with the DHCP service, it does the default thing. I'll test
that next time I boot up the NAS box.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">On one box here I have neither netifrc \
configured, nor dhcpcd, although both are installed. I have also made sure \
networkmanager is not installed.
However, netmount is in the default runlevel and netmount has the default net
dependency enabled:
$ grep -v "^#" /etc/conf.d/netmount
rc_need="net"
$ rc-update show -v | grep -i net
local | default nonetwork
net-online |
net.lo |
netmount | default
I believe this is what kicks in on my system first and brings up dhcpcd, which
in turn obtains an IP address from my router. I mostly configure static IP
addresses for known devices in my LAN on the router.
You can compare which network services are configured to come up on your NAS
Vs your main PC and also check any differences in /etc/rc.conf. Finally
search for "rc_need=" dependencies defined in your <i class="moz-txt-slash"><span \
class="moz-txt-tag">/</span>etc/conf.d<span class="moz-txt-tag">/</span></i>*.
<a class="moz-txt-link-freetext" \
href="https://wiki.gentoo.org/wiki/OpenRC#Dependency_behavior" \
moz-do-not-send="true">https://wiki.gentoo.org/wiki/OpenRC#Dependency_behavior</a>
</pre>
<blockquote type="cite" style="color: #000000;">
<pre class="moz-quote-pre" wrap="">I guess no one else found a way to get \
the install handbook on a single page. I'll have to copy and paste I guess. That's \
gonna take a while. O_O
Dale
<span class="moz-smiley-s1" title=":-)"><span>:-)</span></span> <span \
class="moz-smiley-s1" title=":-)"><span>:-)</span></span> </pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">To save you copying:
<a class="moz-txt-link-freetext" \
href="https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation" \
moz-do-not-send="true">https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation</a>
but note the warning about links redirecting to individual pages:
<a class="moz-txt-link-freetext" \
href="https://wiki.gentoo.org/wiki/Handbook:AMD64/Full" \
moz-do-not-send="true">https://wiki.gentoo.org/wiki/Handbook:AMD64/Full</a> </pre>
</div>
</blockquote>
<br>
<br>
My thought was right. My main rig does not have dhcpcd in any
runlevel. I booted up the NAS box and checked to see if dhcpcd was
listed anywhere. Sure enough, it was in the default runlevel. I
removed it and then rebooted. There was no mention of defaulting to
anything, the network just came up. So, I guess dhcpcd was trying
to start the network first which means it never really saw any of
the config files I was adding info too. It was starting before
those came into the picture. So, now both rigs work the same and I
can start/stop/restart the network on both machines the same way. <br>
<br>
I suspect if I edited some dhcp config file and set up the ethernet
the proper way, it would just come up like it does now, after the
change. Also, nothing against dhcp on my part. My main rig uses
it. I wanted the NAS box to use it as well, just the same as my
main rig. It works great, even if one doesn't do anything to it.
Having it set up tho does give more consistent results, as in the
same IP address. I can't recall the last time I had dhcp to fail
actually. <br>
<br>
Thanks for the links on the full docs on one page. I already copy
and pasted it to a LOo doc and am editing out parts I won't ever
use. It's 116 pages and I'm sure there are parts in there that
won't ever apply to me, systemd for example. Maybe I can get the
page count down to 100 or so. If I'm lucky. <br>
<br>
Is there anyway to know when the doc changes and what changes? And
how did you find that link? I looked everywhere. :/ <br>
<br>
Dale <br>
<br>
:-) :-) <br>
</body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic