From owner-freebsd-current@FreeBSD.ORG Sat Jun 30 18:48:58 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4999416A41F for ; Sat, 30 Jun 2007 18:48:58 +0000 (UTC) (envelope-from sfpoof@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by mx1.freebsd.org (Postfix) with ESMTP id 0890013C45D for ; Sat, 30 Jun 2007 18:48:57 +0000 (UTC) (envelope-from sfpoof@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so413057wxd for ; Sat, 30 Jun 2007 11:48:57 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Q1Xg8NoiSzdZVnWzhewsnSN9kMmHcsk4MuSWSIkqeIH0opcRtxQUAHKwYNc3INCOpdgqe/wxyFiDpp0W6MFNFVnrQGCvaHsF2ZlqNy8RxNfYd2IQhryHS7Zk2wGZ8BlGvAExlrFbeeDDCup7Lgv5ShGZUWwFUQ6kPQ3S6ydbVrI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=iSeXDWdQLR7uJm501EjM7eYhj+8KixToAVXynqOglajM5h4YNvH0iJTDvHdxhHrDnWG7PCMukVMyU/od4yFkGQqyo/TdYVq8KqwhnrVH2V1KVS0VQMnDtLPNKer9Na8VjAo3aQD4A3EtMxTDq1BrYvHtKy3IzJzOllgdx/6jklc= Received: by 10.90.27.13 with SMTP id a13mr4132757aga.1183229337217; Sat, 30 Jun 2007 11:48:57 -0700 (PDT) Received: by 10.90.70.9 with HTTP; Sat, 30 Jun 2007 11:48:57 -0700 (PDT) Message-ID: Date: Sat, 30 Jun 2007 11:48:57 -0700 From: "Kevin Gerry" To: "Sam Leffler" In-Reply-To: <46848C1E.2080404@errno.com> MIME-Version: 1.0 References: <468488B3.7010607@errno.com> <46848C1E.2080404@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: Wireless NICs not obeying 'SSID' setting. 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: Sat, 30 Jun 2007 18:48:58 -0000 Well, I attempted ifconfig ral0 -bgscan and that didn't help as it just switched SSIDs on me... Attempting ifconfig ral0 roaming device now in hopes that will work! =) Thanks for the assistance. On 6/28/07, Sam Leffler wrote: > > Sam Leffler wrote: > > Kevin Gerry wrote: > >> I've noticed that in a recent patch that when you set a NIC with > ifconfig > >> ath0 ssid "This One" that it won't always honor that and jump on the > >> strongest one. > >> > >> Example: > >> > >> 3 WAPs: SSIDs WAP1, WAP2, WAP3 > >> > >> I have set ath0's ssid to "WAP2" and ral0's ssid to "WAP3". They both > will > >> honor the ssid setting for the first connection. However, after a few > >> hours/etc the drivers both associate with WAP1. > >> > >> The settings to require the specific SSID are in > >> /etc/start_if.ral0/start_if.ath0. There aren't any conflicting > >> directives to > >> force it to go blank and select a random AP. > > > > You're probably roaming. wlandebug roam will verify what's going on. > > You can disable roaming several ways: > > > > ifconfig ral0 roaming device > > > > should do the trick (if you set it to manual then you won't do what you > > want if your beacon is turned off). Alternatively you can do > > > > ifconfig ral0 -bgscan > > > > as roaming won't take place w/o bg scanning. > > If you are roaming you can also just fiddle with the roaming thresholds; > e.g. roam:rssi11g and roam:rate11g. I haven't updated the man page > for ifconfig for these yet; they are threshold settings that when > crossed cause the system to consider roaming to a different ap. > > The handling of ssid changed when roaming went in; it's now a "desired > ssid". That is, if the scan doesn't see an ap with the desired ssid > then it'll associate to another ap if possible. Should the ap w/ the > desired ssid re-appear and roaming is enabled then you'll switch over to > it. There is also hysteresis to this algorithm so you don't just bounce > around from one ap to another. > > Sam >