Hi,I got bitten by this as well. My take on the problem is that if you have the resolvconf package installed, the script
/etc/udhcpc/default.deconfig(called upon invocation by udhcpc) instead of running ifconfig runs resolvconf, which does not put the network device in the state required for udhcpc to work, resulting in bind() and such things returning ENETDOWN.
The solution is to either apply the attached patch, which simply makes sure ifconfig brings up the device regardless of whether you have resolvconf installed, or not use the resolvconf package.
This and the companion bug (#302655) are two months old, and should be attended to.
-K
--- default.deconfig 2005-04-01 16:05:50.000000000 -0500
+++ default.deconfig.new 2005-06-07 07:45:51.877221416 -0400
@@ -3,6 +3,5 @@
if [ -x /sbin/resolvconf ] ; then
resolvconf -d "${interface}.udhcpc"
-else
- /sbin/ifconfig $interface 0.0.0.0
fi
+/sbin/ifconfig $interface 0.0.0.0
pgpjr7kt1NtEr.pgp
Description: PGP signature
