Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Jul 2010 13:05:24 +0200
From:      Hans Petter Selasky <hselasky@c2i.net>
To:        PseudoCylon <moonlightakkiy@yahoo.ca>
Cc:        Ganbold Tsagaankhuu <ganbold@mobicom.mn>, freebsd-current@freebsd.org, Ganbold <ganbold@gmail.com>
Subject:   Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
Message-ID:  <201007071305.24179.hselasky@c2i.net>
In-Reply-To: <67219.44880.qm@web51808.mail.re2.yahoo.com>
References:  <16641.96608.qm@web51806.mail.re2.yahoo.com> <201007060854.31192.hselasky@c2i.net> <67219.44880.qm@web51808.mail.re2.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 07 July 2010 12:49:37 PseudoCylon wrote:
> ----- Original Message ----
> 
> > From: Hans Petter Selasky <hselasky@c2i.net>
> > To: freebsd-current@freebsd.org
> > Cc: PseudoCylon <moonlightakkiy@yahoo.ca>; Ganbold Tsagaankhuu
> ><ganbold@mobicom.mn>; Ganbold <ganbold@gmail.com>
> > Sent: Tue, July 6, 2010 12:54:31 AM
> > Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
> 
> Hello
> 
> PseudoCylon is here.
> 
> Unfortunately it successfully associates without an error.
> 
> > Hi,
> >
> > PseudoCylon: Can you try to reproduce this:
> >
> > 1) Setup OPEN HOST  AP (ssid = xxx).
> >
> > 2) Configure WLAN client  with:
> >
> > ssid=xxx
> > auth_alg=SHARED
> > key_mgmt=NONE
> >
> > Wait until  wpa_cli announces that it tries to associate, but fails.
> 
> This didn't happen. wpa_cli didn't say anything, just keep re-scanning.
>  There was a change in wpa. So, I'll rebuilt world and retry
> 
> > 3) Then update  wpa_supplicant.conf:
> >
> > ssid=xxx
> > auth_alg=OPEN
> > key_mgmt=NONE
> >
> > 4)  Enter: "reconfigure" in wpa_cli (panic should happen shortly due to
> > callback  from IEEE802.11 layer which appears to refer a NULL pointer).
> >
> > --HPS
> 
> For now, do you have any error message?
> 
> And, are you using committed version of the driver or testing the patch?
> 

Hi,

I tested using the RUM driver in 9-current. I will try to collect some more 
details on the panic. I think that RUN is also affected.

--HPS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201007071305.24179.hselasky>