From owner-freebsd-current@FreeBSD.ORG Thu Dec 27 02:10:00 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 98E6216A418 for ; Thu, 27 Dec 2007 02:10:00 +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 6B75513C469 for ; Thu, 27 Dec 2007 02:10:00 +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 1J7iC6-0005gr-GS for ; Thu, 27 Dec 2007 11:09:58 +0900 Message-ID: <47730975.2060209@fusiongol.com> Date: Thu, 27 Dec 2007 11:09:57 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20071226120007.EE47716A494@hub.freebsd.org> In-Reply-To: <20071226120007.EE47716A494@hub.freebsd.org> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL X-Abuse-Complaints: abuse@gol.com Subject: 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: Thu, 27 Dec 2007 02:10:00 -0000 Updated to 7.0-PRERELEASE yesterday. I have a Ralink chipset USB wireless adaptor. It gets the ural driver as expected. Typically I connect it with dhcpclient to a completely open wireless access point. dhcpclient is good enough to find the first ssid it gets and sets me up with a DHCP lease to use dhcp with it. All I needed to do was issue "dhcpclient ural0" This behaviour seems to have changed in PRERELEASE. dhcplcient simply tells me "ural0: no link...." Here's the interesting thing though. I can manually set the ipaddress, netmask, ssid, and default route of the system and "cheat" my way into network access without requiring a dhcp lease. I assume that there's been some change in dhcpclient which has upset it's normal behaviour, whereas the ural driver still works (more or less - it often "times out" randomly)