Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: iwn, wpa_supplicant, and wpa2 enterprise

To: Roy Marples <roy%marples.name@localhost>
Subject: Re: iwn, wpa_supplicant, and wpa2 enterprise
From: Martin Husemann <martin%duskware.de@localhost>
Date: Sat, 5 Jun 2010 00:46:09 +0200

On Fri, Jun 04, 2010 at 08:17:26PM +0100, Roy Marples wrote:
> Kernel notifies link is up, dhcpcd reacts to this and attempts to query
> the interface. So any failure must be within the driver.

Why does it signal link up to the routing socket while still loading firmware?

Martin

Follow-Ups:
- Re: iwn, wpa_supplicant, and wpa2 enterprise
  - From: Sverre Froyen

References:
- iwn, wpa_supplicant, and wpa2 enterprise
  - From: Pouya D. Tafti
- Re: iwn, wpa_supplicant, and wpa2 enterprise
  - From: Roy Marples
- Re: iwn, wpa_supplicant, and wpa2 enterprise
  - From: Sverre Froyen
- Re: iwn, wpa_supplicant, and wpa2 enterprise
  - From: Sverre Froyen
- Re: iwn, wpa_supplicant, and wpa2 enterprise
  - From: Roy Marples

Prev by Date: Re: iwn, wpa_supplicant, and wpa2 enterprise
Next by Date: Strange USB crash
Previous by Thread: Re: iwn, wpa_supplicant, and wpa2 enterprise
Next by Thread: Re: iwn, wpa_supplicant, and wpa2 enterprise
Indexes:

Home | Main Index | Thread Index | Old Index