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.