On Sun, May 14, 2006 at 11:29:38PM -0400, Dan Williams wrote:
On Mon, 2006-05-15 at 00:29 +0100, Daniel Drake wrote:
When SIWESSID happens, softmac drops association/authentication with the
current network and then starts a scan for the requested SSID. When
found, softmac authenticates
On Mon, 2006-05-15 at 06:16 -0700, Jouni Malinen wrote:
On Sun, May 14, 2006 at 11:29:38PM -0400, Dan Williams wrote:
On Mon, 2006-05-15 at 00:29 +0100, Daniel Drake wrote:
When SIWESSID happens, softmac drops association/authentication with the
current network and then starts a scan for
On Sun, May 14, 2006 at 11:29:38PM -0400, Dan Williams wrote:
On Mon, 2006-05-15 at 00:29 +0100, Daniel Drake wrote:
Hi Jean,
Hi,
Nice discussion you got going here ;-)
I'd just like to check my understanding (and softmacs implementation)
of SIWESSID and SIWAP behaviour,
On Mon, May 15, 2006 at 01:28:13PM -0700, Jean Tourrilhes wrote:
I believe the BSSID has to be unique. HP APs can also offer
multiple ESSID for the same BSSID, but they do so using different
BSSID. If you look at the 802.11 spec, I can't see how two different
virtual cells can have the
On Mon, May 15, 2006 at 02:40:14PM -0700, Jouni Malinen wrote:
On Mon, May 15, 2006 at 01:28:13PM -0700, Jean Tourrilhes wrote:
I believe the BSSID has to be unique. HP APs can also offer
multiple ESSID for the same BSSID, but they do so using different
BSSID. If you look at the
Hi Jean,
I'd just like to check my understanding (and softmacs implementation)
of SIWESSID and SIWAP behaviour, for managed mode.
When SIWESSID happens, softmac drops association/authentication with the
current network and then starts a scan for the requested SSID. When
found, softmac
