From owner-freebsd-mobile@FreeBSD.ORG Sat Dec 3 20:50:59 2005 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 89B1B16A41F for ; Sat, 3 Dec 2005 20:50:59 +0000 (GMT) (envelope-from tp@tulsaelectronics.net) Received: from mail2.valornet.net (mail2.valornet.net [69.30.128.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87F9C43D5C for ; Sat, 3 Dec 2005 20:50:58 +0000 (GMT) (envelope-from tp@tulsaelectronics.net) Received: (qmail 31117 invoked by uid 120); 3 Dec 2005 20:50:57 -0000 Received: from 72.16.100.46 by mail2.valornet.net (envelope-from , uid 89) with qmail-scanner-1.24st (clamdscan: 0.80/791. spamassassin: 3.0.1. perlscan: 1.24st. Clear:RC:1(72.16.100.46):SA:0(0.0/5.0):. Processed in 1.258569 secs); 03 Dec 2005 20:50:57 -0000 X-Spam-Status: No, hits=0.0 required=5.0 Received: from unknown (HELO ?192.168.254.100?) (tpappano@valornet.com@72.16.100.46) by 0 with SMTP; 3 Dec 2005 20:50:56 -0000 Message-ID: <4392054D.50603@tulsaelectronics.net> Date: Sat, 03 Dec 2005 14:51:25 -0600 From: Tom Pappano User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en MIME-Version: 1.0 References: <200511222006.jAMK63oS090755@gate.bitblocks.com> <4383AA9D.2040603@tulsaelectronics.net> In-Reply-To: <4383AA9D.2040603@tulsaelectronics.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Bakul Shah , freebsd-mobile@freebsd.org Subject: Re: WEP wi0 config prob after 5.4 > 6.0 Upgrade X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tp@tulsaelectronics.net List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Dec 2005 20:50:59 -0000 Tom Pappano wrote: > Bakul Shah wrote: > >> This didn't work for me either when using WEP on iwi0. After >> a few experiments I gave up and used the following in >> /etc/rc.conf which worked fine. >> >> ifconfig_iwi0="ssid SOME_SSID nwkey 0x123456789a DHCP" >> >> > Thank you very much! > I need to test further to be sure the link will stay up indefinitely, but > for now it seems to work fine. > > Thanks again, > TP After further testing on my two notebooks (Dell CPx and Dell CPi), the CPx seems to behave OK- the connection stays up regardless of whether there is traffic. The CPi, however, will drop it's connection after a few minutes of being idle. Dhclient then must be killed and restarted. When the connection drops, ifconfig will still show the card "associated", but without an IP address. My workaround for the moment is simply keeping ssh open between CPi and another machine on my network doing a dummy job such as displaying "top". (CPi is required to be accessible 24-7) Is there somplace in the system configurations where a connection timeout period is specified, or is this just peculiar behaviour? FWIW, it is not the wireless cards, swapping them did not change anything. Reading some of the other postings to this list, I'm getting the impression that there are simply problems with the wi driver, for instance refusing to work with wpa_supplicant in wep mode, and if I want to use wpa_supplicant features, I must just get a card compatible with ath. Is this indeed the case? I suppose I could retrograde CPi back to 5.4, but that just seems wrong 8-) Thanks, TP