I too have noticed this problem. It is very annoying when I'm trying to
do a network console based install.

I've looked at the code and I think the problem is in netcfg-common.c,
function netcfg_get_nameservers. Lines 823-835 appear to try and be
smart by offering the gateway IP address when prompting for a
nameserver. The problem is that they don't look for a preseeded value
first, and appear to simply debconf_set() the gateway IP.

Obviously this isn't useful for preseeding, unless by happy chance your
DNS was on your gateway. I have attached what I think is a patch to the
netcfg (1.08) that appears to fix the problem on my test environment.

It appears to work for both preseeded and unseeded values (defaulting to
previous behaviour correctly, while supplying preseeded values when
preseeded).

Hope this helps,
Christian
--- netcfg-common.c.old	2005-06-21 11:22:27.000000000 -0400
+++ netcfg-common.c	2005-06-21 16:00:18.000000000 -0400
@@ -829,7 +829,11 @@
     }
     else
 	ptr = "";
-    debconf_set(client, "netcfg/get_nameservers", ptr);
+	   // Don't set the value if it already exists (consider preseeds)
+	  debconf_get(client,"netcfg/get_nameservers");
+	  if (!strlen(client->value))
+      debconf_set(client, "netcfg/get_nameservers", ptr);
+    
     
     debconf_input(client, "critical", "netcfg/get_nameservers");
     ret = debconf_go(client);

Reply via email to