From owner-freebsd-current@FreeBSD.ORG Fri Dec 28 02:33:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E72516A417 for ; Fri, 28 Dec 2007 02:33:56 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id 544A813C457 for ; Fri, 28 Dec 2007 02:33:56 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1J852o-0006KP-OC; Fri, 28 Dec 2007 11:33:54 +0900 Message-ID: <47746091.6050302@fusiongol.com> Date: Fri, 28 Dec 2007 11:33:53 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Scot Hetzel References: <20071226120007.EE47716A494@hub.freebsd.org> <47730975.2060209@fusiongol.com> <790a9fff0712270122s58d3c497u1690b7ad80fd32da@mail.gmail.com> In-Reply-To: <790a9fff0712270122s58d3c497u1690b7ad80fd32da@mail.gmail.com> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Abuse-Complaints: abuse@gol.com Cc: freebsd-current@freebsd.org Subject: Re: DHCPclient issues with wireless 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, 28 Dec 2007 02:33:56 -0000 > What does 'ifconfig ural0' show before you issue 'dhcpclient ural0'? > > Does it show that ural0 is associated with your access point? > > If it doesn't show that you are associated, does a 'ifconfig ural0 > ssid ' before the dhcpclient allow you to get an IP > address? Actually, on closer inspection, I realised that my ural0 device was not being brought up upon booting the system. Strange because it always had been in the past. A simple "ifconfig ural0 up" brought it up, after which dhcpclient worked as it always had. Sorry for the noise.