Subject: Re: DAD verbosity
To: Michael Graff <explorer@flame.org>
From: Jason Thorpe <thorpej@nas.nasa.gov>
List: tech-kern
Date: 02/18/2000 10:44:24
On 17 Feb 2000 23:35:19 -0800
Michael Graff <explorer@flame.org> wrote:
> I think the DAD code is broken anyway... It doesn't make certain the
> query packet is actually sent, for instance.
...and the DHCP code, and...
The same thing happens when you're attempting to bring up a link. I
noticed this if you use a hammer to force autonegotiation to occur. Some
PHYs flake for a couple of seconds, and e.g. the DHCP code says "oh, no
response", even though its packet hasn't actually gone out on the wire
(even tho the driver transmits once the link goes up).
There needs to be some sort of upcall mechanism for link state changes
for things which need to know this.
-- Jason R. Thorpe <thorpej@nas.nasa.gov>