Re: Still not fixed ipup problem. (solved)

2005-07-11 Thread Alan Chandler
On Monday 11 July 2005 10:50, Arias Hung wrote: > removing the package: > > zeroconf > > solved this issue for me. > > On Fri, 08 Jul 2005, Alan Chandler delivered in simple text monotone: > > On Friday 08 July 2005 07:54, Arias Hung wrote: ... > > > the auto ifup always assigns me that bogus 169.2

Re: Still not fixed ipup problem. (solved)

2005-07-11 Thread Arias Hung
removing the package: zeroconf solved this issue for me. On Fri, 08 Jul 2005, Alan Chandler delivered in simple text monotone: > On Friday 08 July 2005 07:54, Arias Hung wrote: > > Okay, I've been having this exact same problem the last week or two and > > have had to resort to manually bringin

Re: Still not fixed ipup problem.

2005-07-08 Thread Alan Chandler
On Friday 08 July 2005 07:54, Arias Hung wrote: > Okay, I've been having this exact same problem the last week or two and > have had to resort to manually bringing up eth0 with dhclient. > > the auto ifup always assigns me that bogus 169.254.x.x address too ... very > annoying. > > What I think thi

Re: Still not fixed ipup problem.

2005-07-07 Thread Arias Hung
Okay, I've been having this exact same problem the last week or two and have had to resort to manually bringing up eth0 with dhclient. the auto ifup always assigns me that bogus 169.254.x.x address too ... very annoying. What I think this is related to though for me is a recent aborted install

Still not fixed ipup problem.

2005-07-04 Thread Alan Chandler
I am still finding that ipup is failing to bring up my ethernet interface with the correct ip address. Its still the same problem I raised approx a month ago. Effectively I get two RTNETLINK answers failures during the /etc/init.d/networking start sequence as shown from /var/log/boot snippet