Comment 0 for bug 21144

Package: dhcp-client-udeb
Version: 2.0pl5-19.1
Severity: serious
Tags: d-i

Installations for 1386 using current daily builds (using 2.6.12) are
failing with a screen saying "no default route could be set".
The cause for this is that in /etc/dhclient the 'ip route add' command is
failing. It returns "ip: RTNETLINK answers: Network is unreachable".

This problem has been seen both on real hardware (like my laptop) and both
qemu and vmware. I'm able to reproduce it consistently. I've never seen
the problem during installations using images based on 2.6.8 or 2.6.11.
It happens both when using DHCP and for static net configuration.

I've been trying to trace the problem using several different daily
netinst images (using 2.6.12) and the official Sarge netinst (using
2.6.8) for comparison and using different network devices/modules.

The error happens both when dhclient is run from netcfg and when it's run
from VT2 in busybox. A log with set -x in /etc/dhclient-script is
attached.

I've also run an strace on the 'ip route add' command. Attached are an
strace for the failed command and one for a successful command from a
2.6.8 install.

Currently I'm unsure whether this is a kernel problem, a d-i problem, a
busybox problem and/or related to other changes in unstable (like gcc
transition). I've reached the end of my skills, somebody else needs to
take over from here.
I'm submitting this bug against dhcp-client-udeb because that's where it
manifests itself, but feel free to add info and reassign.