From owner-freebsd-rc@FreeBSD.ORG Sat Apr 24 04:54:30 2010 Return-Path: Delivered-To: rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8028D106566C for ; Sat, 24 Apr 2010 04:54:30 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 387508FC15 for ; Sat, 24 Apr 2010 04:54:29 +0000 (UTC) Received: by qyk11 with SMTP id 11so12428115qyk.13 for ; Fri, 23 Apr 2010 21:54:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=+iQ3YUhKef8XwJaBHf1RacjsFH6EoXuRJ7GOiKNBT6c=; b=Q9bqASkvI3axn1gPQdUGbod4IyBRLj51DN2kSG/Fzj583y2sXM+40MXETUyd97R9JC fMSe3JIDly17GAv9ltfJ2Eu1ZkJs+/ajimxXEl6P8ZGcZ1OwKbrWf1xHzyiXdXLf1LnU qdwGfkRK/yO7lIXsMDdx2/TIQtPuBVRftc088= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Ohg0STeCPGivjKTW+QyOroqi892f9aAyT/LFezO8AOcsQntplzJn9EysrKG8Efj18s hlr9N94w/OMaNqoBjJOBd8dUFSFfb08ngxIKmN3x+0IBrLjXRr5YZqImMRBy8mu+ff2D QLxjxA1Wwx6ob/jTK6TDylNW7qBePdwV2UcU0= MIME-Version: 1.0 Received: by 10.229.215.72 with SMTP id hd8mr1221819qcb.43.1272084869435; Fri, 23 Apr 2010 21:54:29 -0700 (PDT) Received: by 10.229.233.11 with HTTP; Fri, 23 Apr 2010 21:54:29 -0700 (PDT) In-Reply-To: <20100423.205923.825269116351824344.imp@bsdimp.com> References: <20100423.205923.825269116351824344.imp@bsdimp.com> Date: Fri, 23 Apr 2010 21:54:29 -0700 Message-ID: From: Garrett Cooper To: "M. Warner Losh" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: rc@freebsd.org Subject: Re: Specifying a precedence order for wireless AP stations in rc.conf? X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Apr 2010 04:54:30 -0000 On Fri, Apr 23, 2010 at 7:59 PM, M. Warner Losh wrote: > In message: > =A0 =A0 =A0 =A0 =A0 =A0Garrett Cooper writes: > : Hi rc folks, > : =A0 =A0 I use my Lenovo laptop at work and at home and it's kind of > : annoying to have to do into rc.conf every time I go to work or go home > : to comment out lines choosing an appropriate network for > : ifconfig_wlan0 in rc.conf(5) to connect to the appropriate wireless > : network. So I figured that I'm probably doing something wrong so I > : should ask. > : =A0 =A0 The documentation for ifconfig_wlan* in the handbook [1] and th= e > : rc.conf(5) manpage [2] for 8-STABLE don't suggest that connectivity > : for multiple networks can be performed whereas multiple networks can > : be specified in wpa_supplicant.conf. Is it at all possible to provide > : a precedence list for what SSID networks to attempt to configure via > : wpa_supplicant(8) by default, or are further enhancements required in > : either wpa_supplicant(8) or rc.network to get this to function? > : Thanks, > : -Garrett > : > : 1. http://www.freebsd.org/doc/en/books/handbook/network-wireless.html > : 2. http://www.freebsd.org/cgi/man.cgi?query=3Drc.conf&sektion=3D5 > > wpa_supplicant will allow you to set the order of SSIDs that it > associates with. =A0It is the order they are in in the > wpa_supplicant.conf file. Ok... I worded the question poorly. If I do: ifconfig_wlan0=3D"WPA DHCP" then stuff doesn't work at work. If I do: ifconfig_wlan0=3D"WPA ssid DHCP" with the way I have wpa_supplicant.conf setup, things work. Otherwise it ifconfig and the driver act dumb and try and associate a bunch of times, and eventually fail. Conversely, if I do: ifconfig_wlan0=3D"ssid DHCP" at home, things work. Otherwise, same old song and dance occurs when it attempts to associate with an open AP in the neighborhood that isn't in the house. So, this may ultimately be a driver problem with how it selects APs, but because I know that and are `trusted' networks that I'm going to attach the laptop to on a regular basis, I'd rather it try and connect to those SSIDs and fail if they're not present, instead of just trying a pool of whacky SSIDs (which those SSIDs may be a part of) instead and failing hard. Thanks, -Garrett