From owner-freebsd-questions@FreeBSD.ORG Tue Aug 26 00:28:12 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 402A47A4 for ; Tue, 26 Aug 2014 00:28:12 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D01743E94 for ; Tue, 26 Aug 2014 00:28:11 +0000 (UTC) Received: from r56.edvax.de (port-92-195-111-1.dynamic.qsc.de [92.195.111.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id C0734276A9; Tue, 26 Aug 2014 02:28:02 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s7Q0S2wq003065; Tue, 26 Aug 2014 02:28:02 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 26 Aug 2014 02:28:02 +0200 From: Polytropon To: leeoliveshackelford@surewest.net Subject: Re: how to install wireless n.i.c. on FreeBSD 9.1 Message-Id: <20140826022802.198cd285.freebsd@edvax.de> In-Reply-To: References: <20140823025527.bd80818d.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2014 00:28:12 -0000 On Mon, 25 Aug 2014 11:22:10 -0700, leeoliveshackelford@surewest.net wrote: > The complete name of the circuit board is as follows: "TP-Link > TL-WDN4800 450 Mbps Wireless N Dual Band PCI Express Adapter." Ah, "N"... there are still N chipsets not fully supported by FreeBSD, maybe you accidentally picked one of those? But first let's check the configuration before we scream in despair for having bought the _one_ model that is _not_ supported. :-) > In my > previous message, I mis-identified the manufacturer, as you correctly > noted. To the command "pciconf -lv," I received the following response: > > none0@pci0:40:0:0 class=0x028000 card=0x3112168c chip=0x0030168c > rev=0x01 hdr=0x00 > > vendor = 'Atheros Communications Inc.' > > device = 'AR9300 Wireless LAN adaptor' > > class = network So the Atheros chipset is correctly identified, good. > Upon checking the webpage specified in your message, I read the > following line: "The ath(4) driver supports all Atheros Cardbus and PCI > cards, except those that are based on the AR5005VL chipset." Good, so this one will probably be supported, I hope. > The three modified files are /etc/wpa_supplicant.conf, and /etc/rc.conf, > and /boot/loader.conf. Copies of these files are attached. Let's see: [loader.conf text/plain (84B)] if_ath_ahb_load="YES" wlan_wep_load="YES" wlan_ccmp_load="YES" wlan_tkip_load="YES" The first line looks strange. There are /boot/kernel/if_ath.ko and /boot/kernel/ahb.ko, and "man ahb" reveals that this one is for "Adaptec EISA SCSI host adapter driver". But as if_ath_ahb.ko does not exist, the _correct_ module won't be loaded. The first line should read: if_ath_load="YES" Change the file accordingly. Next file. [rc.conf text/plain (206B)] hostname="HP7USH74200Y0" wlans_ath0="wlan0" ifconfig_wlan0="WPA" SYNCDHCP sshd_enable="YES" ntpd_enable="YES" powerd_enable="YES" dumpdev="NO" Again, there's an error which explains your initial SYNCDHCP: command not found message: The SYNCDHCP has to be _inside_ the quotes. Keep in mind that /etc/rc.conf is basically a shell script, so it follows all the rules from "man sh". What you have here is: setting a variable and calling a command (which doen't exist). The correct line: ifconfig_wlan0="WPA SYNCDHCP" This should work. The common syntax is keyword="VALUE", where the VALUE can contain spaces. Last file. [wpa_supplicant.conf text/plain (42B)] network={ ssid="WPA" psk="F70FA10C57" } While "WPA" is a strange name of a network, it's a valid one. :-) The rest of the file looks fine. But note: freebsd-questions is a _public_ mailing list, so I hope "F70FA10C57" isn't your _actual_ key. If it is, change it quickly! You don't want to tell the whole Internet your access credentials. Passwords are like underwear: change yours often, don't share with friends, the longer the better, they must remain mysterious, don't leave them lying around. :-) It's common to enter "obvious nonsense" in such cases, like network={ ssid="MYNETWORKNAME" psk="SECRETPASSWORD" } As long as the syntax is kept correct, the actual information does not matter here (except, maybe, if a password contained quote characters or other things that might cause a hickup for wpa-supplicant, but that's not the case here). After you have corrected the files, restart your system and see if it works. Chances are high that there were just those two little mistakes, and your WLAN should be up and running quickly. It's not that working WLAN is something magical... :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...