From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 03:45:01 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40FB41065675 for ; Fri, 2 Sep 2011 03:45:01 +0000 (UTC) (envelope-from mailinglistmember@mgwigglesworth.net) Received: from mail.mgwigglesworth.net (mail.mgwigglesworth.com [75.146.26.81]) by mx1.freebsd.org (Postfix) with ESMTP id BC2A68FC14 for ; Fri, 2 Sep 2011 03:45:00 +0000 (UTC) To: freebsd-net@freebsd.org, freebsd-wireless@freebsd.org Date: Thu, 01 Sep 2011 23:43:44 -0400 Envelope-To: freebsd-net@freebsd.org,freebsd-wireless@freebsd.org References: <4E5D5422.9040609@mgwigglesworth.net> <4E5EE805.5010905@mgwigglesworth.net> Message-ID: <4E6050F0.2040203@mgwigglesworth.net> From: "Martes G Wigglesworth" Received: from devsecure.mgwigglesworth.net (192.168.5.21 [192.168.5.21]) by mail.mgwigglesworth.net; Thu, 01 Sep 2011 23:44:59 -0400 Organization: M. G. Wigglesworth Holdings, LLC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.20) Gecko/20110817 Fedora/3.1.12-1.fc14 Lightning/1.0b2 Thunderbird/3.1.12 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: [Solved] Re:Commands for AR5212 cause system to hang using 8.2-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mailinglistmember@mgwigglesworth.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 03:45:01 -0000 On 08/31/2011 10:08 PM, Adrian Chadd wrote: > I didn't think wlan_xauth was deprecated; it should be installed in > /boot/kernel/ . > > > Adrian From the freenode #freebsd channel, I discovered just what you have indicated, and was in the process of correcting a bad kernel install. After installing the kernel again, all required dependencies for hostapd have been restored, and it will start, and run. However, the new issue is that my wlan0 device will be setup with all the device settings of hostap AP mode, except for the ip address. The device becomes active, and registers as an access point having the desired ssid, however, no IP address is ever issues during the rc.conf setup process. Example: (with hostapd activated on boot) wlan0: flags=8843 metric 0 mtu 1500 ether 00:1b:2f:37:02:46 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid wireless2 channel 1 (2412 MHz 11g) bssid 00:1b:2f:37:02:46 country US ecm authmode WPA privacy MIXED deftxkey 2 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 23 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs (without hostapd activated on boot) wlan0: flags=8843 metric 0 mtu 1500 ether 00:1b:2f:37:02:46 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid wrouter0 channel 1 (2412 MHz 11g) bssid 00:1b:2f:37:02:46 country US ecm authmode OPEN privacy OFF txpower 23 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs rc.conf section for this device is as follows: wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap" ifconfig_wlan0="inet 192.168.200.1 netmask 255.255.0.0 ssid "wrouter0" mode 54g channel 1" However, all works perfectly, if I simply assign the intended ip address to the wlan0 device. Any input on this? -- Respectfully, Martes G Wigglesworth M. G. Wigglesworth Holdings, LLC www.mgwigglesworth.net