#1089036 installation-guide-amd64: Installer using manual network configuration did not set up DNS

#1089036#5
Date:
2024-12-04 15:15:31 UTC
From:
To:
Dear Maintainer,

Apologies as this must be the wrong package to report against. I was using the
amd64 net installer, on a network without a DHCP server. So I set up the
network manually, including DNS. Unfortunately the installer did not populate
the /etc/resolv.conf file and I had to do so manually to continue the install.

Otherwise the installer would have been useless.

Kind regards,
Mike

#1089036#10
Date:
2024-12-04 19:34:24 UTC
From:
To:
Which installation image did you use ? debian-12.8.0-amd64-netinst.iso ?
Do you mean /etc/resolv.conf in the installer root or in /target ?
Can you post the network parameters you set in the installer ?

#1089036#15
Date:
2024-12-04 23:54:54 UTC
From:
To:
search parameter. My network parameters were simple

static ip: 10.46.26.15
netmask: 255.255.255.0
gateway: 10.46.26.1
DNS: 10.44.17.11 and 1.1.1.1

#1089036#20
Date:
2024-12-05 08:47:44 UTC
From:
To:
Le 05/12/2024 à 00:54, Michael P. Soulier a écrit :

debian-12.8.0-amd64-netinst.iso ?

Which hostname ?
I cannot reproduce the issue on debian-12.8.0-amd64-netinst.iso with the
above settings. /etc/resolv.conf is populated as expected with two
"nameserver" lines.

#1089036#25
Date:
2024-12-05 15:52:59 UTC
From:
To:
Yes

hostname was io.mitel.com

I went on a virtual terminal and manually fixed the problem and
continued the install.

Also note that there is no dhcp server on this network segment, so it
failed to find one first, at which point I configured manually.

Mike

#1089036#30
Date:
2024-12-05 18:29:14 UTC
From:
To:
With the exact same settings I still cannot reproduce the issue, unless
I use an illegal separator character (other than space).

Which separator character did you use in the name servers input field ?

Can you check if the installer logs (/var/log/installer/syslog on the
installed system) contains a line "Failed to parse <input token> as an
IP address" ?

#1089036#35
Date:
2024-12-05 19:46:37 UTC
From:
To:
I'll see if the logs are still there.

I don't recall if the UI asked for a comma or a space between servers, I
work on too many of them.

Sadly there is no /var/log/installer directory on the box now.

Mike

#1089036#40
Date:
2024-12-05 20:33:56 UTC
From:
To:
Control: reassign -1 netcfg 1.187+deb12u1
Control: retitle -1 Manual network configuration did not set up DNS

The UI asked "Please enter the IP addresses (not host names) of up to 3
name servers, separated by spaces. Do not use commas."

How infortunate. Then I am afraid that all you can do now is boot the
installer again and try to reproduce the issue. You can abort after the
network configuration, so nothing is written to disk. During the
installation, the installer log is in /var/log/syslog.

I am reassigning the bug to netcfg anyway because either you hit some
edge case or used the wrong separator but netcfg did not display an error.

#1089036#51
Date:
2024-12-13 08:16:08 UTC
From:
To:
Control: tags -1 patch

I opened a merge request to address the latter case and other minor
issues in static configuration UI:
<https://salsa.debian.org/installer-team/netcfg/-/merge_requests/13>

#1089036#56
Date:
2024-12-31 13:30:14 UTC
From:
To:
Hello,

Bug #1089036 in netcfg reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/installer-team/netcfg/-/commit/fb586403195f674d6eab86527c7d54a72e805bbb
------------------------------------------------------------------------
Reject invalid input for static nameserver configuration

During static configuration, netcfg checks if the IP address, netmask
and gateway address are valid but not the nameserver address list.
Not only invalid addresses are silently discarded but also addresses
separated with the wrong character (e.g. comma or semicolon) are silently
discarded, resulting in no nameserver options in generated network
configuration files.

So check nameserver input and prompt the user again if invalid.

Closes: #1089036
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1089036