Hello again; Yes agreed that this is not driver related per say as I ran test with various wired cards too.
An I agree that a bug report is in order. Since you were first affected by this, I will let you do the honors of filing a report. (Besides the Mandrake bugzilla was too cranky for me to successfully file a report the last time I tried to use it.) Thanxs for the sane replies and kind attitudes during them. Best regards; Bob On Sunday 27 July 2003 05:30 am, Adam Williamson wrote: > On Sun, 2003-07-27 at 06:07, w9ya wrote: > > Hey Adam and the gang; > > > > Yes, in fact ifplugd starts and successfully determines the eth0 info > > (after dhclient DHCPACKS from the server). > > > > Then, as you suggest, ifplugd about a minute (or so) later brings down > > the interface (eth0), and then exits. > > > > If I then execute: /etc/ifplugd/ifplugd.action eth0 up (from a prompt), > > the interface successfully comes up and works fine from that point > > forward. > > > > So it appears that when your situation was remedied concerning ifplugd, > > mine was broken. > > As I followed up, it wasn't actually resolved for me - it still happens, > and now I can confirm it happens on both WLAN and wired cards. Maybe the > time is ripe to file a bug report. BTW, all you need to run to fix it is > "ifup eth0", that does the job.
