From owner-freebsd-mobile@FreeBSD.ORG Fri Dec 19 05:29:25 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0AB116A4CE for ; Fri, 19 Dec 2003 05:29:25 -0800 (PST) Received: from web42005.mail.yahoo.com (web42005.mail.yahoo.com [66.218.93.173]) by mx1.FreeBSD.org (Postfix) with SMTP id 4C88E43D4C for ; Fri, 19 Dec 2003 05:29:23 -0800 (PST) (envelope-from darrylb_au44@yahoo.com.au) Message-ID: <20031219132923.7365.qmail@web42005.mail.yahoo.com> Received: from [210.50.98.36] by web42005.mail.yahoo.com via HTTP; Sat, 20 Dec 2003 00:29:23 EST Date: Sat, 20 Dec 2003 00:29:23 +1100 (EST) From: =?iso-8859-1?q?Darryl=20Barlow?= To: Kevin Oberman In-Reply-To: <20031217160415.BC9BB5D08@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-mobile@freebsd.org Subject: Re: Wireless Problems X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2003 13:29:25 -0000 Kevin, Thanks to you and also the others who replied. I was specifying the hexadecimal key correctly (my mistake in my post) and the key was showing up in wicontrol. I deleted it from the output posted. I know 64 bit wep is not much protection but posting the key on a newsgroup is probably not that good an idea. To test whether wep was to blame I actually disabled wep on the access point and tried to connect. The result was exactly the same. It seems that the card is failing to associate for some reason. Any ideas would be welcome. regards, Darryl Barlow --- Kevin Oberman wrote: > > Date: Wed, 17 Dec 2003 23:25:22 +1100 (EST) > > From: =?iso-8859-1?q?Darryl=20Barlow?= > > > Sender: owner-freebsd-mobile@freebsd.org > > > > Sorry to post about a problem with a desktop > machine > > but I may have more luck here given the problem is > a > > cardbus one. I have installed FreeBSD on a > Desktop > > Machine with a TI 1410 PCI Cardbus Bridge and an > Avaya > > Silver Wireless Network Card. > > > > The card connects perfectly to a D-Link Access > Point > > in Debian and even in Windows XP. However, in > FreeBSD > > there is "no carrier" no matter what I seem to > try. > > Troubleshooting help would be much appreciated. > > > > Device seems to come up with: > > > > ifconfig wi0 inet 192.168.4.8 netmask > 255.255.255.0 > > ssid HOME wepmode ON > > wepkey 1234567890 > > Exactly how are you specifying the WEP key? Is it an > ASCII string or a > hex value? If it's a hex value, it needs to be > entered as 0xnnnnnnn. If > it's an ASCII string, it is entered as a quoted > string, but there have > been many issues with interoperability of ASCII > strings and it is > better from both an operational and security > perspective to use a random > hexadecimal numeric key. (I use /dev/random to > generate my WEP keys.) > > Your wicontrol output looks OK. (Please don't > auto-wrap pasted screen > output, though!) It seems to see the AP and has > reasonable > signal strength, but it fails to associate and that > makes me suspect the > WEP key. Does the output of wicontrol REALLY have > the key field empty? > > I certainly don't like the disk errors, either, but > are not likely > related to the network problem. > -- > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory > (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > > > dmesg is as follows: > > > > Copyright (c) 1992-2003 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, > > 1991, 1992, 1993, 1994 > > The Regents of the University of > California. > > All rights reserved. > > FreeBSD 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT > 2003 > > > > > > > root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC > > Preloaded elf kernel "/boot/kernel/kernel" at > > 0xc06d4000. > > Preloaded elf module "/boot/kernel/acpi.ko" at > > 0xc06d421c. > > Timecounter "i8254" frequency 1193182 Hz > > Timecounter "TSC" frequency 1199664705 Hz > > CPU: AMD Athlon(tm) Processor (1199.66-MHz > 686-class > > CPU) > > Origin = "AuthenticAMD" Id = 0x642 Stepping = > 2 > > > > > > > Features=0x183f9ff > > AMD Features=0xc0440000 > > real memory = 134135808 (127 MB) > > avail memory = 122912768 (117 MB) > > Pentium Pro MTRR support enabled > > npx0: on motherboard > > npx0: INT 16 interface > > acpi0: on motherboard > > pcibios: BIOS version 2.10 > > Using $PIR table, 9 entries at 0xc00f1720 > > acpi0: power button is handled as a fixed feature > > programming model. > > Timecounter "ACPI-fast" frequency 3579545 Hz > > acpi_timer0: <24-bit timer at 3.579545MHz> port > > 0xe408-0xe40b on acpi0 > > acpi_cpu0: on acpi0 > > acpi_button0: on acpi0 > > pcib0: port 0xcf8-0xcff on > > acpi0 > > pci0: on pcib0 > > agp0: > bridge> > > mem > > 0xe6000000-0xe7ffffff at device 0.0 on pci0 > > pcib1: at device 1.0 on pci0 > > pci1: on pcib1 > > pci1: at device 0.0 (no driver > > attached) > > isab0: at device 4.0 on pci0 > > isa0: on isab0 > > atapci0: port > > 0xd800-0xd80f at device 4.1 on > > pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > uhci0: port > > 0xd400-0xd41f > > irq 9 at device 4.2 on > > pci0 > > usb0: on uhci0 > > usb0: USB revision 1.0 > > uhub0: VIA UHCI root hub, class 9/0, rev > 1.00/1.00, > > addr 1 > > uhub0: 2 ports with 2 removable, self powered > > uhci1: port > > 0xd000-0xd01f > > irq 9 at device 4.3 on > > pci0 > > usb1: on uhci1 > > usb1: USB revision 1.0 > > uhub1: VIA UHCI root hub, class 9/0, rev > 1.00/1.00, > > addr 1 > > uhub1: 2 ports with 2 removable, self powered > > pci0: at device 9.0 (no driver > > attached) > > cbb0: at device 10.0 > on > > pci0 > > cardbus0: on cbb0 > > pccard0: <16-bit PCCard bus> on cbb0 > > pcib0: slot 10 INTA is routed to irq 5 > > rl0: port > 0xa400-0xa4ff > > mem 0xd5000000-0xd50000ff > > at device 11.0 on pci0 > > rl0: Realtek 8139B detected. Warning, this may be > > unstable in autoselect mode > > pcib0: slot 11 INTA is routed to irq 10 > > rl0: Ethernet address: 00:50:bf:27:7b:64 > > miibus0: on rl0 > > rlphy0: on > > miibus0 > > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, > > 100baseTX-FDX, auto > > pci0: at device 12.0 (no > driver > > attached) > > sym0: <810a> port 0x9800-0x98ff mem > > 0xd4800000-0xd48000ff irq 9 at device 13.0 > > on pci0 > > sym0: Symbios NVRAM, ID 7, Fast-10, SE, parity > > checking > > sym0: open drain IRQ line driver > > sym0: using LOAD/STORE-based firmware. > > atapci1: > port > > > > > 0x8000-0x803f,0x8400-0x8403,0x8800-0x8807,0x9000-0x9003,0x9400-0x9407 > > mem > > 0xd4000000-0xd401ffff irq 10 at device 17.0 on > pci0 > > ata2: at 0x9400 on atapci1 > > ata3: at 0x8800 on atapci1 > > fdc0: NE72065 > > or > > clone)> port > > 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 > > fdc0: FIFO enabled, 8 bytes threshold > > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > > ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on > > acpi0 > > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in > > COMPATIBLE mode > > ppc0: FIFO with 16/16/8 bytes threshold > > ppbus0: on ppc0 > > plip0: on ppbus0 > > lpt0: on ppbus0 > === message truncated === http://personals.yahoo.com.au - Yahoo! Personals New people, new possibilities. FREE for a limited time.