From owner-freebsd-current@FreeBSD.ORG Thu Jun 16 18:20:58 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7920616A41C for ; Thu, 16 Jun 2005 18:20:58 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 455E943D1F for ; Thu, 16 Jun 2005 18:20:58 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j5GIKuc8002205; Thu, 16 Jun 2005 11:20:56 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j5GIKuld002204; Thu, 16 Jun 2005 11:20:56 -0700 Date: Thu, 16 Jun 2005 11:20:56 -0700 From: Brooks Davis To: Darren Pilgrim Message-ID: <20050616182056.GF21733@odin.ac.hmc.edu> References: <000001c57259$01a259c0$0b2a15ac@SMILEY> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001c57259$01a259c0$0b2a15ac@SMILEY> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: current@freebsd.org Subject: Re: Is anyone working on /etc/rc.d/wpa_supplicant? 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: Thu, 16 Jun 2005 18:20:58 -0000 On Thu, Jun 16, 2005 at 02:51:44AM -0700, Darren Pilgrim wrote: > Is anyone working on the proposed /etc/rc.d/wpa_supplicant script (as > mentioned in /etc/network.subr? If not, I'll get started on one. I'm planning to work on it, but if I don't do it my tomarrow it will have to wait for the week of the 27th as I will be without electronic devices next Sunday-Friday. > Also if not, what are some guidelines for what the script should do? Is > just terminating wpa_supplicant sufficient, or should the script stop > dhclient, de-configure and down the interface as well? The script should have no knowledge of dhclient and should act like the dhclient script for the most part. One could argue though that it actually has to be more complicated than the dhclient script because in some really weird configurations you might not have /usr mounted when netif is run and as a result you need to support starting supplicants after mountcritremote. In normal configurations, the script should see the already started wpa_supplicants and not do anything when it is run. I can't actually think of a good reason to have a machine with a remote /usr be a wireless station, but I'm sure some crazy person will come up with one. :) -- Brooks