From owner-freebsd-questions@FreeBSD.ORG Thu Dec 23 09:49:44 2004 Return-Path: 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 3FCB916A4CE for ; Thu, 23 Dec 2004 09:49:44 +0000 (GMT) Received: from mp.cs.niu.edu (mp.cs.niu.edu [131.156.145.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA70143D2F for ; Thu, 23 Dec 2004 09:49:43 +0000 (GMT) (envelope-from bennett@cs.niu.edu) Received: from mp.cs.niu.edu (bennett@localhost [127.0.0.1]) by mp.cs.niu.edu (8.13.2/8.13.2/d) with ESMTP id iBN9ngtV026976; Thu, 23 Dec 2004 03:49:42 -0600 (CST) Date: Thu, 23 Dec 2004 03:49:42 -0600 (CST) From: Scott Bennett Message-Id: <200412230949.iBN9ngPt026975@mp.cs.niu.edu> To: freebsd-questions@freebsd.org cc: pauls@utdallas.edu Subject: Re: ifconfig for WLAN using WEP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 09:49:44 -0000 Paul Schmehl wrote: >--On Monday, December 20, 2004 11:21:01 AM -0600 Scott Bennett > wrote: >> >> I wasn't combining them. Here's some background information: the >> only "connected" interface at the time of the ifconfig shown above is the >> loopback. The ethernet interface is "UP" but not physically connected to >> anything. The wireless interface is not "UP" and not previously >> configured for anything. >> As I wrote before, the problem is that *any* WEP-related terms given >> to the ifconfig command result in the error message being returned. >> >You'll get that error message if you try to use wep commands on a >non-wireless interface. I wonder if your system is detecting the wireless >NIC and has the correct drivers for it? fwe0 should be a ethernet over As it turns out, this was the right question to ask, for which I thank Paul. >firewire interface. What type of wireless NIC are you using? Your >wireless interface should be something like an0 or wi0, etc. > Apparently, FreeBSD is detecting the infrared port (and assigning it network interface characteristics), which is disabled in the BIOS, but FreeBSD bypasses the BIOS at a very early stage. Windows XP Home Edition sees three interfaces displayed as: Network Connections Broadband [check] Broadband Connection Disconnected WAN Minport (PPPOE) LAN or High-Speed Internet [x] Local Area Connection Network Cable Unplugged Broadcom 570x Gigabit Integrated Contr 1394 Connection Disabled 1394 Net Adaptor Wireless Network Connection Connected Dell Wireless WLAN 1450 Dual Band W I interpret the above as meaning that the "Broadband" interface is the dial-up interface, the "Local Area" interface is the real Ethernet interface (not connected physically), the 1394 interface is the infrared port as Ethernet- over-FireWire (fwe0), and the Dell 1450 card is indeed the wireless interface. Looking through the boot messages from FreeBSD 5.2.1, I don't see anything that looks like the Dell wireless card being detected. I've looked through all the man pages for the various interface types and haven't seen anything that looks appropriate. If anyone reading this can suggest what to do next, please do. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at cs.niu.edu * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************