From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 6 01:42:12 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2C39106566B for ; Mon, 6 Jun 2011 01:42:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id B31C58FC08 for ; Mon, 6 Jun 2011 01:42:12 +0000 (UTC) Received: by gyg13 with SMTP id 13so2034429gyg.13 for ; Sun, 05 Jun 2011 18:42:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=Pg1fSmlpBoxMvQS8do6VvrstMbP1FqquFYoy4A9/tws=; b=OH/ncN+ELjhnoQyCBXOXUD76ki2wJmm8dZNNywvArUeBV7cRNe9rEop6xG9EwYV82V j3g8+/WHtgSGW6LzjjgbqaRwtuEdkNKel2HmYSuVqxmfomt9G3doRoGgWjLhvV303Rjb kfmeiG580F6Ue+hmi1Akgh+y9LC9UXgLYUYOA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=Sxg7j+WktNMna54xEV6srEyxHRX8vy6cGWPQRkfDkB2e7BtI2QOndFfFM4qJZfZDKD tVvKw33h+qrnnqY3TNr10JDFa3x3azEBrk/BPdGAGcWFJWtEMtKBtGK06JLvig9iY3xe vbWVsfCrJlirucX38UKSwp2ttgZ/wN4sHmHx4= MIME-Version: 1.0 Received: by 10.150.72.30 with SMTP id u30mr3835616yba.14.1307324531726; Sun, 05 Jun 2011 18:42:11 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.151.107.15 with HTTP; Sun, 5 Jun 2011 18:42:11 -0700 (PDT) Date: Mon, 6 Jun 2011 09:42:11 +0800 X-Google-Sender-Auth: nSA1jiMlzRvhAi_PP7ayS1-qe64 Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: wishlist: wpa_supplicant should pay attention to the currently forced SSID? X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 01:42:13 -0000 Hi, Something that keeps irking me is that wpa_supplicant will try scanning its config file in order and fail to associate to ssids that don't match the one which is hard-coded. I hard-code SSIDs so I can force the network I'm associating to, without having to reconfigure wpa_supplicant. Is this intended behaviour? Is there another easy way to tell wpa_supplicant what to associate to? Or could we modify wpa_supplicant to only try assocating to APs that match the currently configured SSID? Thanks, Adrian