Default route doesn't change to wireless device (ath0)

Sam Leffler sam at
Thu Sep 8 08:25:53 PDT 2005

Brooks Davis wrote:
> On Thu, Sep 08, 2005 at 01:11:38AM -0600, M. Warner Losh wrote:
>>In message: <20050907211811.GA19570 at>
>>            Brooks Davis <brooks at> writes:
>>: Hmm, upon further testing, I think there may be a problem with the
>>: fxp(4) driver.
>>You mean like the driver never asynchronously querries the miibus to
>>find out what the state of the link is when it isn't in the UP state?
> I certainly see that on the em nics on my laptop and I've heard claims
> of a similar problems with fxp nics.  I don't see it with other em
> nics.  Sam reports that it seems to be a bug specific to the em hardware
> in thinkpads.  That's not the only issue in this case, but it's one of
> them.

Ah, I don't believe I said there was a bug specific to thinkpads; I only 
said that I had observed issues with the em devices on my thinkpads.

> I suspect think we may need to poll the media state periodicly on
> some devices and fake up link state notifications as a workaround for
> incorrect drivers.

Some drivers do some form of polling but I believe we could correct many 
issues with a little documentation and some TLC.  The drivers I've 
looked at typically are plastered with comments about workarounds for 
detecting link state changes.


More information about the freebsd-current mailing list