Unable to connect after connection is dropped under Ubuntu

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

 



On Thu, 2010-09-09 at 23:07 -0700, anderson.fang at gmail.com wrote:
> Hi all,
> 
> I met a weird connection problem while using WiMAX service with Intel
> 6250 under Ubuntu.
> 
> Suppose my laptop is connected to WiMAX successfully while the signal
> strength is better than 'Fair', and then I move an area with 'Poor'
> link
> status, the connection will be dropped as expected:
> --------
> [2010/09/08 14:05:34] MESSAGE SYSTEM STATE UPDATE ARRIVED
> System State: Ready
> Connect Progress Info: Not Applicable
> SW Radio: On
> HW Radio: On
> State Reason: Disconnect - Drop
> --------
> 
> But then I go back where I initialized the connection, I cannot
> connect
> to the same NSP anymore even the scanned result is 'Good':
> --------
> Network found.
> NSP : XXXXXX
> ID : xxxx
> Signal : Good
> RSSI : -73 dBm
> CINR : 18 dB
> Network Type: Home Network
> Activated
> --------
> 
> wimax_monitor always shows "Fail to Connect - EAP Auth" connection
> error:
> --------
> [2010/09/08 14:20:32] MESSAGE DEVICE STATUS UPDATE ARRIVED
> Device Status: Connecting
> Connection Progress: EAP Auth (Device)
> [2010/09/08 14:20:52] MESSAGE SYSTEM STATE UPDATE ARRIVED
> System State: Ready
> Connect Progress Info: Not Applicable
> SW Radio: On
> HW Radio: On
> State Reason: Fail to Connect - EAP Aut

Weird -- I am wondering if the firmware (or the daemon) is getting stuck
and remembering only one of the 'poor connectivity' BSs.

Can you try resettting the card and scanning again?

$ wimaxll -i wmx0 reset

[give it a few secs]

$ wimax scan
$ wimax connect network XXX

If this works, then it serves as a workaround and would prove that
somehow it is still trying to connect to a poor connectivity network. If
it doesn't, it might means something else.

> 
> However the scenario does not happen under Windows 7. I can connect to
> the same NSP after my connection is dropped.
> 
> OS: Ubuntu 10.04
> Device: Intel(R) Centrino(R) Advanced-N + WiMAX 6250
> Kernel: 2.6.32-24-generic
> wimaxd: 1.5
> wimax-tools: 1.4.3
> Driver: obtained from
> git://git.kernel.org/pub/scm/linux/kernel/git/inaky/compat-wimax.git

driver version should not affect, but compat-wimax is not being
maintained up to the tree as of now.

> The steps I connect to WiMAX NSP:
> * # compat-wimax/load.sh
> * # wimaxd -b
> * # wimaxcu scan
> * # wimaxcu connect network NSP
> 
> Does anyone have the same problem or the solution of this?
> 
> Thanks,
> Anderson Fang





[Index of Archives]     [Linux Kernel]     [Linux Wireless]     [Linux Bluetooth]     [Linux Netdev]     [Linux Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux