From owner-freebsd-questions@FreeBSD.ORG Thu Jan 26 05:19:46 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 196D816A420 for ; Thu, 26 Jan 2006 05:19:46 +0000 (GMT) (envelope-from illoai@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id A47F643D48 for ; Thu, 26 Jan 2006 05:19:45 +0000 (GMT) (envelope-from illoai@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so176215wxc for ; Wed, 25 Jan 2006 21:19:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=iRQrzvS75y3j1VuSBa7omICmVnToqLrqPcECF0Yx+x3uR8sI8xBmM2WbmY/ViUThHWMSL2R9vP3f/yWxke5hRdAsyvMJSvN5/B0gG8zo+NdflsPZzNsDeiH6Np1FGwMfEkYQ1GkqxEGRpogz1Cf38RulJ0PWTNknNpg1zhdyMlo= Received: by 10.70.26.17 with SMTP id 17mr1787092wxz; Wed, 25 Jan 2006 21:19:44 -0800 (PST) Received: by 10.70.57.17 with HTTP; Wed, 25 Jan 2006 21:19:44 -0800 (PST) Message-ID: Date: Wed, 25 Jan 2006 23:19:44 -0600 From: "illoai@gmail.com" To: Jonathan Herriott MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: freebsd-questions@freebsd.org Subject: wlan_wep (was: Touchpad Mouse and Battery Monitoring) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2006 05:19:46 -0000 On 1/25/06, Jonathan Herriott wrote: > My last issue is the wireless. I have an intel PRO/Wireless 2100 > card, and I can't use it with encryption. If I turn encryption off on > my router, it works. Obviously this is bad. I saw somewhere that all > I have to do is type: > > kldload wan_wep > > but it can't find wan_wep. Any ideas on that? > You're missing the "l" in wlan_wep, for starters. Also, counterintuitive at first maybe, but split unrelated questions into seperate mail with different subjects. -- --