Date: Fri, 14 Sep 2001 15:44:57 -0700 From: "Kevin Oberman" <oberman@es.net> To: Lars Eggert <larse@ISI.EDU> Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Odd card removal events on stable Message-ID: <200109142244.f8EMivR26965@ptavv.es.net> In-Reply-To: Your message of "Fri, 14 Sep 2001 15:03:25 PDT." <p05100300b7c82e9bcb6f@[128.9.176.131]>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Fri, 14 Sep 2001 15:03:25 -0700
> From: Lars Eggert <larse@ISI.EDU>
> Sender: owner-freebsd-mobile@FreeBSD.ORG
>
> > > : dhclient: receive_packet failed on wi0: Device not configured
> >>
> >> This is a bug in dhclient.
> >
> >Yes, but I simply see it as dhclient telling my that the interface is
> >gone (over and over). I realize it has no further significance.
>
> Haven't seen the behavior Kevin described, but I am mostly using a
> wired network, and only use the wireless link sporadically.
>
> I have seen dhclient choke and blast thousands of the messages above
> into the syslog ("last message repeated 432423 times" :-)
>
> I'll see if I can come up with a patch.
I've thought about doing the same. I'm not sure that dhclient is the
place to fix it, though. dhclient has no concept of a removable
interface that may, with no advance notice, simply cease to exist.
pccard_ether should kill of dhclient and seems to do so. It just takes
a while.
I see no reason that dhclient should not simply treat a report of a
non-existent interface as a request for termination, but dhclient is
contributed software and it might be best to contact Ted Lemon, the
author, nd see what he thinks.
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net Phone: +1 510 486-8634
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109142244.f8EMivR26965>