From owner-freebsd-current@FreeBSD.ORG Mon Jul 11 20:44:44 2005 Return-Path: X-Original-To: freebsd-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 7783C16A41C for ; Mon, 11 Jul 2005 20:44:44 +0000 (GMT) (envelope-from bakul@bitblocks.com) Received: from gate.bitblocks.com (bitblocks.com [209.204.185.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31C1E43D49 for ; Mon, 11 Jul 2005 20:44:44 +0000 (GMT) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost [127.0.0.1]) by gate.bitblocks.com (8.13.3/8.13.1) with ESMTP id j6BKicbk046767; Mon, 11 Jul 2005 13:44:40 -0700 (PDT) (envelope-from bakul@bitblocks.com) Message-Id: <200507112044.j6BKicbk046767@gate.bitblocks.com> To: Brooks Davis In-reply-to: Your message of "Tue, 05 Jul 2005 15:42:09 PDT." <20050705224209.GC28034@odin.ac.hmc.edu> Date: Mon, 11 Jul 2005 13:44:38 -0700 From: Bakul Shah Cc: Sam Leffler , freebsd-current@freebsd.org Subject: Re: minor WPA problem on a Thinkpad R40 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: Mon, 11 Jul 2005 20:44:44 -0000 > > IMO wpa_supplicant should exit when the interface goes down/away but it > > does not. I sent mail to Jouni about this but he hasn't responded yet. > > > I was going to check if there was a way to make it work this way. Not > > sure why it works this way except to avoid recalculating various crypto > > state or perhaps to avoid linux hotplug issues. If it matters may be the state can be saved? On restart wpa_supplicant can use it as a hint. The problem seems to be generic in that suspend/resume needs to save more state than shutdown/boot (or may be, the only difference between the two is state saving). > I've we're going to do that, I think we may want either a new target in > /etc/rc.d/netif or a new /etc/rc.d/linkstate script. That's probably > the right way to go though. You mean targets like suspend/resume? Not sure if you guys need me to test anything.... Thanks for looking into this!