From owner-freebsd-current@FreeBSD.ORG Tue Oct 19 06:30:45 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60E1110656A4 for ; Tue, 19 Oct 2010 06:30:45 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id E81F88FC23 for ; Tue, 19 Oct 2010 06:30:44 +0000 (UTC) Received: by bwz16 with SMTP id 16so95276bwz.13 for ; Mon, 18 Oct 2010 23:30:43 -0700 (PDT) Received: by 10.204.76.80 with SMTP id b16mr1588997bkk.160.1287469843468; Mon, 18 Oct 2010 23:30:43 -0700 (PDT) Received: from jessie.localnet (p5B0E17C5.dip0.t-ipconnect.de [91.14.23.197]) by mx.google.com with ESMTPS id y19sm17616651bkw.6.2010.10.18.23.30.41 (version=SSLv3 cipher=RC4-MD5); Mon, 18 Oct 2010 23:30:41 -0700 (PDT) From: Bernhard Schmidt To: Buganini Date: Tue, 19 Oct 2010 08:30:37 +0200 User-Agent: KMail/1.13.2 (Linux/2.6.32-25-generic; KDE/4.4.2; i686; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201010190830.37974.bschmidt@freebsd.org> Cc: FreeBSD Current Subject: Re: wpa_supplicant and ssid X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 06:30:45 -0000 On Monday, October 18, 2010 18:55:34 you wrote: > It seems that wpa_supplicant iterate through all scanned ssids and try to > associate with each, > and that cause two problem for me. > > 1) in my school, there are many AP, and connection is not stable, when > disconnect, > it take many time to try and fail to associate with those ssids until the > one I want. You can add a 'priority' statement to each network block in wpa_supplicant.conf. > 2) i can't associate with a non-discoverable ssid > > but probably it is my wireless driver's problem, > i'm using bwn0 and currently I need to force it to use mode 11b or it is > unusable. Tried different options for the scan_ssid parameter? > or should I complain to upstream ? Before doing so, can you capture the output of 'wlandebug 0xffffffff' while trying to get a connection? -- Bernhard