Scríobh Dan Williams:
> Any chance you could try with latest wpa_supplicant git of either the
> trunk or hostap_0_5_branch branches? Jouni just cherry-picked a commit
> from trunk that works around a race condition with madwifi
Same results with wpa_supplicant trunk. For what it's worth, I'm
attac
On Fri, 2007-12-28 at 10:45 -0500, Dan Williams wrote:
> On Tue, 2007-12-25 at 20:29 -0700, Seán de Búrca wrote:
> > I'm currently attempting to connect to a network configured with
> > 128-bit WEP with current SVN. When prompted for the key, I make sure to
> > select the 128-bit Hexadecimal option
On Fri, 2007-12-28 at 13:17 -0700, Seán de Búrca wrote:
> Scríobh Dan Williams:
> > That means that the wireless driver failed to send the 'connect' signal
> > in time. What version of wpa_supplicant are you using, and would it be
> > possible to add the '-ddd' option to the supplicant's command l
Scríobh Dan Williams:
> That means that the wireless driver failed to send the 'connect' signal
> in time. What version of wpa_supplicant are you using, and would it be
> possible to add the '-ddd' option to the supplicant's command line and
> get some logs out of it? I've been using WEP+SVN+ipw2
On Tue, 2007-12-25 at 20:29 -0700, Seán de Búrca wrote:
> I'm currently attempting to connect to a network configured with
> 128-bit WEP with current SVN. When prompted for the key, I make sure to
> select the 128-bit Hexadecimal option. However, after a short wait, it
> asks me for the key again.
I'm currently attempting to connect to a network configured with
128-bit WEP with current SVN. When prompted for the key, I make sure to
select the 128-bit Hexadecimal option. However, after a short wait, it
asks me for the key again. The log reads:
NetworkManager: Activation (ath0/wireless)
