linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Cheng Renquan <crquan@gmail.com>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: linux 3.2-rcX iwlwifi driver's problem (wifi link unstable when moving between multiple APs)
Date: Tue, 20 Dec 2011 15:46:05 -0800	[thread overview]
Message-ID: <1324424765.13074.281.camel@wwguy-huron> (raw)
In-Reply-To: <CAH5vBdJLHkFLQCHHYOczXQt1Hwwe3e-Ct0MUjyTRU0vgodAPOg@mail.gmail.com>

Hi Renquan,

Thanks you for reporting the issue.It will be greatly appreciated  if
you can enter a bug report in http://bugzilla.intellinuxwireless.org/.
Then we can assign engineer to look into the issue , also keep track of
the progress.

Thanks
Wey

On Tue, 2011-12-20 at 15:20 -0800, Cheng Renquan wHi Intel Linux
Wireless group,
> 
> Since 3.2-rcX, it seems no more iwlagn driver? This iwlwifi driver
> seems not stable
> when I hold laptop moving inside a large office, between multiple APs,
> everytime I moved to a new place, the wifi link becomes inactive, and
> I need to wait
> 5 minutes or longer to wait iwlwifi stable, networkmanager get a new
> ip address; quite annoying,
> 
> 
> [root@archtop ~]# lspci -D -nn -k -d 8086:4238
> 0000:03:00.0 Network controller [0280]: Intel Corporation Centrino
> Ultimate-N 6300 [8086:4238] (rev 35)
> 	Subsystem: Intel Corporation Centrino Ultimate-N 6300 3x3 AGN [8086:1111]
> 	Kernel driver in use: iwlwifi
> 	Kernel modules: iwlwifi
> 
> in the large office, it's using WPA2 enterprise encryption with
> MSCHAPv2 domain user/pass authentication,
> 
> 
> Last iwlagn driver in my Ubuntu-10.10 default kernel (linux-2.6.35.X)
> on the same computer
> same networkmanager/wpa_supplicant software same office working wonderful,
> moving smoothly between multiple APs,
> 
> At home, even I set wireless router to no any
> encryption/authentication, this new kernel
> would becomes wifi link down every couple of hours, while another
> laptop and same Ubuntu-10
> on this laptop could work smoothly,
> 
> 
> 
> 
> Thanks,



  reply	other threads:[~2011-12-21  0:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 23:20 linux 3.2-rcX iwlwifi driver's problem (wifi link unstable when moving between multiple APs) Cheng Renquan
2011-12-20 23:46 ` Guy, Wey-Yi [this message]
2011-12-21  2:37   ` Cheng Renquan
2011-12-21  6:22     ` Sedat Dilek
2011-12-21  8:03       ` Cheng Renquan
2011-12-21  8:53         ` Sedat Dilek
2011-12-21  9:06           ` Cheng Renquan
2011-12-21  9:20             ` Sedat Dilek
2011-12-21 10:36               ` Cheng Renquan
2011-12-21 11:14                 ` Sedat Dilek
2011-12-21 16:14                   ` Guy, Wey-Yi
2011-12-21 23:28                     ` Cheng Renquan
2011-12-22  1:40                       ` wwguy
2012-01-10 23:17                         ` Cheng Renquan
2012-01-10 22:27                           ` Guy, Wey-Yi
2012-01-11  0:01                             ` Cheng Renquan
2012-01-10 23:20                               ` Guy, Wey-Yi
2012-01-11  1:30                                 ` Cheng Renquan
2012-01-11  2:28                                   ` wwguy
2012-01-11 16:37                                   ` wwguy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1324424765.13074.281.camel@wwguy-huron \
    --to=wey-yi.w.guy@intel.com \
    --cc=crquan@gmail.com \
    --cc=ilw@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).