AFAIK, during the first setup via interactive setup the “anaconda phase” is “useless” for network and hostname.
Nethserver will consider the networks available as green, and will receive DHCP offers.
Using unattended setup, the documentation should be reliable.
https://docs.nethserver.org/en/v7/installation.html#unattended-mode
and
https://docs.nethserver.org/en/v7/installation.html#fallback-ip-configuration
The “real” network setup goes with the access to Server Manager (now in cockpit). Roles, IP, hostname(s).
When installing, you’re configuring CentOS. But when you’re accessing the Server Manager, you’re populating the configuration DB, that will override/overwrite CentOS system, service, network, firewall settings.
Every modification to system and service configuration will automatically do…
- check of the parameters (sometimes fails, but whatever)
- write the configuration to the DB
- expanding the configuration with also the custom templates created by the sysadmin
- overwrite of the settings of the system and/or services configuration with the one created by the expansion.