public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Handbook and question about manual network setup
Date: Fri, 19 Apr 2024 11:26:43 -0500	[thread overview]
Message-ID: <47503270-2e5f-a1c6-d3a4-71efefd3c29d@gmail.com> (raw)
In-Reply-To: <3804873.kQq0lBPeGt@rogueboard>

[-- Attachment #1: Type: text/plain, Size: 3318 bytes --]

Michael wrote:
> On Friday, 19 April 2024 15:05:47 BST Dale wrote:
>
>> Anyway, while investigating this, I realized the network setup is not
>> like on my old rig.  Heck, I couldn't even figure out how to restart it
>> other than switching to the boot runlevel and back to default, or
>> rebooting.  After a bit, I think I can restart DHCP and it restart the
>> network.  I figured out the cable was unplugged before trying that.  I'm
>> wanting to set up the NAS box network the same way as my main rig. 
>> That's the old manual way.  I went back to the install handbook, that's
>> what I followed when installing on my main rig.  Thing is, it has been
>> updated and the old way isn't all there.  I followed what little bit is
>> there but it defaults back to the new way.  I'm sure I'm missing some
>> file I need to edit but I can't figure out which one it is.  So, is
>> there a way to get the old instructions again?  The ones I followed
>> several years ago for my main rig?  I tried searching but it seems they
>> all gone.  Maybe there is a place I'm not aware of tho.  Basically, I
>> want to be able to start/stop/restart enp3s0 as a service and have it in
>> a runlevel. 
> Without knowing what you refer to as 'The Old Way' Vs 'The New Way', or how 
> your 'main rig', Vs your 'old rig' may have been configured, I'll try to make 
> a guess, or two:
>
> 1. Old Way = netifrc
>
> You configure /etc/conf.d/net using the well commented example provided in:
>
> /usr/share/doc/netifrc-*/net.example.bz2
>
> You symlink your interface enp3s0 to the net.lo netifrc init script and add it 
> to the default runlevel:
>
> ln -s /etc/init.d/net.lo /etc/init.d/net.enp3s0
> rc-update add net.enp3s0 default
>
> then (re)start, check the status, or stop your newly configured interface, 
> e.g.:
>
> rc-service -v net.enp3s0 status
> rc-service -v net.enp3s0 restart
>
> More detailed info than you should ever need and all on one page, is provided 
> here:
>
> https://wiki.gentoo.org/wiki/Netifrc
>
>
> 2. New Way = DHCP (?)
>
> Although dhcp can be configured as a fallback option within /etc/conf.d/net in 
> addition to static addresses, gateways, etc., it can also be set up as a 
> standalone service without netifrc.  Emerge dhcpcd and add it to the default 
> runlevel.
>
> If you have set static IP address(es) at your home router for the old box and 
> its MAC address, then that's all you need to do before you run:
>
> rc-service -v dhcpcd restart
>
> If you prefer to not set up a configuration for your old rig on the router, 
> then you can add a static IP address in your /etc/dhcpcd.conf.
>
> Again, more  info than you should need is provided here:
>
> https://wiki.gentoo.org/wiki/Dhcpcd
>
> HTH, otherwise ask if you get stuck.


Rebooting the NAS box improved things.  See reply to Matt.  By old way,
I mean using a symlink to net.lo with the interface/card name such as
enp3s0 to start/stop/restart the service.  It still uses DHCP to get
connection info but I'd also like to specify the IP address if I can.  I
like to set those so that they don't change even if I move cables
around.  Main rig, NAS box, cell phone and printer.  The printer really
gets upset when something changes. 

I think I should have used the word "older" instead of "old".  ROFL  :-D 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 4191 bytes --]

  reply	other threads:[~2024-04-19 16:26 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
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 [this message]
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=47503270-2e5f-a1c6-d3a4-71efefd3c29d@gmail.com \
    --to=rdalek1967@gmail.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