Date: Tue, 26 Aug 2014 14:38:16 -0700 From: leeoliveshackelford@surewest.net To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: how to install wireless n.i.c. on FreeBSD 9.1 Message-ID: <3f1e44ea23fb755ae9f8e2390ab2a3d6@surewest.net> In-Reply-To: <20140826022802.198cd285.freebsd@edvax.de> References: <c0493cf1a6cb62e193163d781348b8ad@surewest.net> <20140823025527.bd80818d.freebsd@edvax.de> <df00e520b70e5b6fc5c379195956d6b7@surewest.net> <20140826022802.198cd285.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Good afternoon, dear Polytropon. May this message find you in good
spirits. Thank you for your detailed response yesterday. I made the
corrections that you indicated in two configuration files. Upon
re-starting the computer, the error message "SYNCDHCP: Command not
found" was absent. The response to the command, "pciconf -lv" was
exactly the same as before. The response to the ifconfig command did not
indicate the presence of the wireless n.i.c. Thank you for advising me
about a possible error in security concerning one of my attached files.
I have alerted the system administrator. Have you, or has anyone any
comment about what it is that I am doing wrong here? On a different
topic, can or do you recommend a character mode programer's editor, that
is, an editor that prints a line number to the left of each line? Thank
you for any and all comments. Yours truly, Lee
On 08/25/2014 05:28 PM, Polytropon wrote:
> On Mon, 25 Aug 2014 11:22:10 -0700, leeoliveshackelford@surewest.netwrote:
>
>> 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... :-)
From owner-freebsd-questions@FreeBSD.ORG Wed Aug 27 00:15:51 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id C0EF1C05;
Wed, 27 Aug 2014 00:15:51 +0000 (UTC)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com
[IPv6:2607:f8b0:4001:c03::231])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 8906B3565;
Wed, 27 Aug 2014 00:15:51 +0000 (UTC)
Received: by mail-ie0-f177.google.com with SMTP id at20so11929873iec.8
for <multiple recipients>; Tue, 26 Aug 2014 17:15:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:sender:date:message-id:subject:from:to:content-type;
bh=52h2/nhu2s1BrOSWK0BDCyozTNIaZNx6vb11LVBZmrY=;
b=TAGQckeT4f8UuLZxBSKdXCUhw1M+fZg8+mbWcGuUmYHSWf540DMnVAIOdh/gPHqSYE
Y1KD2/b1xlgs2rPCKRLxHS23h0OAA9BAotj9dg8QdkymPhnP8qQOO9Sg748Cy/kcHKFJ
qIs5Knmq3whqh0GOeRaZi8SEz+AJj9urjKrE8xEa7fCFa33Xy1Fh/Rd+TLZNe5ee55db
7C6SGlf8eXqDtdqdkXtUnjO1AivFjgbD8PNFXUhak35cw/dc0C2mQYT1PDP+Lf+GNiz4
Lj0RJwnwcJ/APUhI3dixQdz5pTkw0I9IwSCFQQuKWRtVwoQYUWuJ/Jq6Af7f9N2/tPPF
/EZQ==
MIME-Version: 1.0
X-Received: by 10.42.83.131 with SMTP id h3mr4235008icl.77.1409098550954; Tue,
26 Aug 2014 17:15:50 -0700 (PDT)
Sender: jdavidlists@gmail.com
Received: by 10.43.43.136 with HTTP; Tue, 26 Aug 2014 17:15:50 -0700 (PDT)
Date: Tue, 26 Aug 2014 20:15:50 -0400
X-Google-Sender-Auth: bjxD1KBLo4PMf58pjUVb7hyfDqs
Message-ID: <CABXB=RRuPqSoc6CBYLf3MBr68n-w9-0cUaOCrVvhrzvRpNnE3w@mail.gmail.com>
Subject: Quarterly ports trees not getting security updates?
From: J David <j.david.lists@gmail.com>
To: freebsd-ports@freebsd.org, freebsd-questions@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>,
<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Aug 2014 00:15:51 -0000
Hello,
When the quarterly ports trees were introduced, they were described as
including security, build, and runtime fixes for 3 months.
This is a great idea, and with 2014Q2 it seemed to work pretty well.
However, it doesn't seem like 2014Q3 is getting security fixes.
For example, the openssl port has never been updated since branch;
it's still on 1.0.1_13, which has 9 open CVE's against it. Other
ports have similar issues (e.g. serf and subversion).
What could a non-expert such as myself do to help with this? Is it
just a matter of trying to identify the relevant commits from the head
of the ports tree, or is there more to it?
Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3f1e44ea23fb755ae9f8e2390ab2a3d6>