From owner-freebsd-questions@FreeBSD.ORG Fri Aug 19 19:11:33 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0A161065676 for ; Fri, 19 Aug 2011 19:11:33 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vulpes.vvelox.net (vulpes.vvelox.net [99.69.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id 47A2E8FC0C for ; Fri, 19 Aug 2011 19:11:32 +0000 (UTC) Received: from vixen42.vulpes.vvelox.net (vixen42.vulpes.vvelox.net [192.168.15.2]) (Authenticated sender: kitsune) by vulpes.vvelox.net (Postfix) with ESMTPA id 7FC083F50D; Fri, 19 Aug 2011 14:11:32 -0500 (CDT) Date: Fri, 19 Aug 2011 14:09:53 -0500 From: "Zane C. B-H." To: Dan Nelson , freebsd-questions@freebsd.org Message-ID: <20110819140953.372949bf@vixen42.vulpes.vvelox.net> In-Reply-To: <20110819175115.GA11383@dan.emsphone.com> References: <20110819072234.38e655d6@vixen42.vulpes.vvelox.net> <201108191414.p7JEEsgA069695@mail.r-bonomi.com> <20110819092653.422f2b9b@vixen42.vulpes.vvelox.net> <20110819175115.GA11383@dan.emsphone.com> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Robert Bonomi Subject: Re: wpa_cli issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2011 19:11:33 -0000 On Fri, 19 Aug 2011 12:51:16 -0500 Dan Nelson wrote: > In the last episode (Aug 19), Zane C. B-H. said: > > On Fri, 19 Aug 2011 09:14:54 -0500 (CDT) Robert Bonomi > > wrote: > > > From: "Zane C. B-H." > > > > Is there any way to undefine a variable once it has been set? > > > > > > *As(stated*, the answer involves the offspring of the mating of > > > a rhinoceros and an elephand. > > > > > > =GUESSING= that you mean a shell 'envionment variable', the > > > answer is 'yes'. _How_ one can do it depends on the shell > > > (*unspecified*!) being used. 'unsetenv' _may_ do the trick. > > > Alternatively a variable assignment with no value (.e.g > > > "VARIABLE=") may work. > > > > Blarg? > > > > None of these is even vaguely related to my question about > > wpa_cli, as stated in the subject. > > wpa_cli only understands a fixed list of variables to set, and it > doesn't make sense to "undefine" them. You can set them back to > their default values, but they must have a value. > > Defaults from looking at the source: > > EAPOL::heldPeriod = 60 > EAPOL::startPeriod = 30 > EAPOL::maxStart = 3 > EAPOL::authPeriod = 30 > dot11RSNAConfigPMKLifetime = 43200 > dot11RSNAConfigPMKReauthThreshold = 70 > dot11RSNAConfigSATimeout = 60 > > Running "set" from within wpa_cli should print these values, too, > according to the manpage. That is for stuff set via set, but when it comes to the individual network variables, not all of these have a default value other than not defined, AFAIK, and setting them back to the defaults as far as I can tell is impossible for some. A example of this is the bssid variable. Once this has been set, I've been unable to find any way to remove it via wpa_cli. Any suggestions would be much appreciated. Thanks. :)