From owner-freebsd-current@FreeBSD.ORG Fri Aug 26 00:46:52 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 A1B7016A41F for ; Fri, 26 Aug 2005 00:46:52 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail1.fluidhosting.com (mail1.fluidhosting.com [204.14.90.61]) by mx1.FreeBSD.org (Postfix) with SMTP id 1456243D49 for ; Fri, 26 Aug 2005 00:46:51 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 64379 invoked by uid 399); 26 Aug 2005 00:46:51 -0000 Received: from localhost (HELO ?192.168.1.100?) (dougb@dougbarton.net@127.0.0.1) by localhost with SMTP; 26 Aug 2005 00:46:51 -0000 Message-ID: <430E667D.50508@FreeBSD.org> Date: Thu, 25 Aug 2005 17:46:53 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rudolf Cejka References: <20050825134924.GA87803@fit.vutbr.cz> In-Reply-To: <20050825134924.GA87803@fit.vutbr.cz> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Unable to connect to wireless 802.11 AP with hidden SSID 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: Fri, 26 Aug 2005 00:46:52 -0000 Rudolf Cejka wrote: > Hello, > after an upgrade from 5.x to 7.x (Aug 22), I'm unable to connect to > wireless 802.11 access point, which hides its own SSID, using dhclient > (manual settings do work, however it is not very good workaround...). I can't judge the validity of the patch, but I did want to give a "me too" on the new dhclient inexplicably blanking a valid ssid when it's started. The ssid on my APs is not hidden now, although I have seen this behavior with both hidden and visible ssids. hth, Doug