On Tue, Jun 07, 2005 at 12:06:46PM +0000, Kacper Wysocki wrote: > 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.
Thanks for your report. #302655 was closed 20 min. ago. Give it a try to see if it solves your problem. I'll have a look at your bug ASAP, but instead of > -else > - /sbin/ifconfig $interface 0.0.0.0 > fi > +/sbin/ifconfig $interface 0.0.0.0 I'd rather use -else - /sbin/ifconfig $interface 0.0.0.0 fi +/sbin/ifconfig $interface up Any comment ? Greetings, -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
