Please note:
Problem on kernel 2.6.27-7/9/10
with compat wireless 2008-12-11 and last compat wireless 2008-12-26
i use wep.
[ 2807.093457] wlan0: direct probe to AP XX:XX:4b:15:a5:a0 try
1 [ 2807.095392]
wlan0 direct probe
responded
[ 2807.095403] wlan0: authenticate with AP
XX:XX:4b:15:a5:a0
[ 2807.097198] wlan0:
authenticated
[ 2807.097208] wlan0: associate with AP
XX:XX:4b:15:a5:a0
[ 2807.099484] wlan0: RX AssocResp from XX:XX:4b:15:a5:a0 (capab=0x431
status=0 aid=3) [ 2807.099493] wlan0:
associated
[ 2807.120643] wlan0: disassociating by local choice (reason=3)
and wireless not work (ping ap non working and connection is down).
iwlist wlan0 scan found the wireless network.
mohamed salim abbas ha scritto:
> if you connect to the AP manually then make sure NM is not running or
> just use NM to connect.
>
Tank you very much
sorry for disturb
the problem is tath:
i have removed grafical network manager (i use my simple bash script for
rapid wireless connection)
but ubuntu intrepid have startup script for NM and wpa...
if you connect to the AP manually then make sure NM is not running or
just use NM to connect.
On Fri, Dec 26, 2008 at 9:07 AM, techmin <[email protected]> wrote:
> Please note:
> Problem on kernel 2.6.27-7/9/10
> with compat wireless 2008-12-11 and last compat wireless 2008-12-26
> i use wep.
>
> [ 2807.093457] wlan0: direct probe to AP XX:XX:4b:15:a5:a0 try 1
> [ 2807.095392] wlan0 direct probe
> responded
>
> [ 2807.095403] wlan0: authenticate with AP XX:XX:4b:15:a5:a0
>
> [ 2807.097198] wlan0: authenticated
>
> [ 2807.097208] wlan0: associate with AP XX:XX:4b:15:a5:a0
>
> [ 2807.099484] wlan0: RX AssocResp from XX:XX:4b:15:a5:a0 (capab=0x431
> status=0 aid=3) [ 2807.099493] wlan0:
> associated
>
> [ 2807.120643] wlan0: disassociating by local choice (reason=3)
>
> and wireless not work (ping ap non working and connection is down).
>
> iwlist wlan0 scan found the wireless network.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>