Tim:
> When you're installing a system, Anaconda gives you the
chance to
> manually configure some network details *for* the installation
> routine to use during installation. These settings are temporary,
> they don't write a configuration for the installed system to use,
> later on. And if you're on a network with a DHCP server that will
> automatically assign working addresses, you don't have to do
> anything at this point, the DHCP system will set things up for you.
>
> During first boot of the installed system, you're given a chance to
> manually control network settings for the newly installed system.
John M. Harris Jr:
Odd, I don't think that's ever been the case before. I might
be
thinking of RHEL/CentOS. I don't use DHCP, but I've never had to do
any manual configuration afterwards..
I've been using Fedora since before it was Fedora, and CentOS since I
don't know when (several years), it's always been the way I described
it. At first I couldn't figure out why, after carefully configuring
network settings when starting off the the installation, the settings
weren't what I expected them to be. But it didn't take long to find
out that they were only used by the installer routine for itself.
What's your network comprised of?
In the absense of DHCP, there's autoconfig, where each device randomly
picks an IP out of the link-local 169.254.0.0 to 169.254.255.255 range
of addresses, checks to see if it's not already use, then adopts it, or
cycles through picking another until it finds one that's free.
And if your PC was a solo computer on no LAN, it would do that, too.
As well as simply using 127.0.0.1 as itself.
--
uname -rsvp
Linux 3.10.0-1127.el7.x86_64 #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.