linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lars Ericsson" <Lars_Ericsson@telia.com>
To: "'Johannes Berg'" <johannes@sipsolutions.net>
Cc: "'Dan Williams'" <dcbw@redhat.com>,
	<linux-wireless@vger.kernel.org>, <hostap@lists.shmoo.com>
Subject: RE: Roaming problems
Date: Wed, 23 Apr 2008 19:12:14 +0200	[thread overview]
Message-ID: <006b01c8a565$2dd40a10$0b3ca8c0@gotws1589> (raw)
In-Reply-To: <1208969605.31429.88.camel@johannes.berg>


> > Currently this is what happens most of the time, when all 
> ioclts had 
> > been issued from the driver, it drops current 
> > authentication/association atempts and start with the new 
> one. Most of the times that works fine.
> > 
> > But sometimes, when for any reason the 3 ioctls get delayed, the 
> > driver may success to associate with the old BSSID (since that is 
> > still valid in the driver). Then when all 3 ioctls has been 
> received, 
> > including the new BSSID, the driver re-starts the 
> > authentication/association sequence with the new BSSID.
> > 
> > The problem is that the STA already have a valid 
> association with the 
> > first AP. In this case the new BSSID silently ignores any 
> > authentication/association attempts. My believe is that it 
> knows that 
> > the STA already have a valid association.
> 
> Uh huh. Aren't we disassociating when we change to a new bssid?
> 

I think the best way would be check the trace I attached in the first post.

/LaE



  reply	other threads:[~2008-04-23 17:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 15:09 Roaming problems Lars Ericsson
2008-04-23  8:39 ` Lars Ericsson
2008-04-23 11:12   ` Johannes Berg
2008-04-23 13:53     ` Dan Williams
2008-04-23 14:59       ` Johannes Berg
2008-04-23 16:21         ` Dan Williams
2008-04-23 16:39           ` Johannes Berg
2008-04-23 16:44           ` Lars Ericsson
2008-04-23 16:53             ` Johannes Berg
2008-04-23 17:12               ` Lars Ericsson [this message]
2008-04-23 17:59                 ` Johannes Berg
2008-04-23 16:27     ` Lars Ericsson
2008-04-23 16:31       ` Dan Williams
2008-04-23 20:47         ` John W. Linville
2008-04-24  6:45           ` Holger Schurig
2008-04-24  9:55             ` Lars Ericsson
2008-04-24  9:59               ` Johannes Berg
2008-04-24 17:36                 ` Lars Ericsson
2008-04-26 20:54                   ` Johannes Berg
2008-04-28 18:28                     ` Lars Ericsson
2008-04-28 18:34                       ` Johannes Berg
2008-04-28 18:43                         ` Dan Williams
2008-04-28 20:22                         ` Lars Ericsson

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='006b01c8a565$2dd40a10$0b3ca8c0@gotws1589' \
    --to=lars_ericsson@telia.com \
    --cc=dcbw@redhat.com \
    --cc=hostap@lists.shmoo.com \
    --cc=johannes@sipsolutions.net \
    --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).