From owner-freebsd-net@FreeBSD.ORG Thu Feb 19 10:51:03 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7588F10656CA for ; Thu, 19 Feb 2009 10:51:03 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id 203218FC1C for ; Thu, 19 Feb 2009 10:51:02 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id 339851F450A; Thu, 19 Feb 2009 05:45:44 -0500 (EST) Received: from memory.visualtech.com (h-67-103-204-242.phlapafg.covad.net [67.103.204.242]) by mailstore.visualtech.com (Postfix) with ESMTP id 86E26ADC25E; Thu, 19 Feb 2009 06:00:46 -0500 (EST) Date: Thu, 19 Feb 2009 05:50:35 -0500 From: Adam K Kirchhoff To: "Paul B. Mahol" Message-ID: <20090219055035.1ff55f19@memory.visualtech.com> In-Reply-To: <20090218194810.075e0c7c@sorrow.ashke.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> <20090218080420.681788d2@memory.visualtech.com> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> <20090218111223.4483b923@memory.visualtech.com> <3a142e750902181027q25863f39ycc342d6506949eb9@mail.gmail.com> <20090218134935.14f0a8c2@memory.visualtech.com> <20090218142659.135a73bc@memory.visualtech.com> <3a142e750902181610h65f23d13vfeb20cc19ea0944a@mail.gmail.com> <20090218194810.075e0c7c@sorrow.ashke.com> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-visualtech-MailScanner: Found to be clean Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2009 10:51:04 -0000 On Wed, 18 Feb 2009 19:48:10 -0500 Adam K Kirchhoff wrote: > On Thu, 19 Feb 2009 01:10:08 +0100 > "Paul B. Mahol" wrote: > > > On 2/18/09, Adam K Kirchhoff wrote: > > > --- if_ndis.c 2009-01-31 00:22:11.000000000 -0500 > > > +++ if_ndis.c.orig 2009-02-18 14:03:30.000000000 -0500 > > > @@ -2459,6 +2459,11 @@ > > > bzero((char *)&config, len); > > > config.nc_length = len; > > > config.nc_fhconfig.ncf_length = sizeof(ndis_80211_config_fh); > > > + > > > + device_printf(sc->ndis_dev, "couldn't change " > > > + "Testing config.nc_dsconfig: %u \n", > > > + config.nc_dsconfig); > > > + > > > rval = ndis_get_info(sc, OID_802_11_CONFIGURATION, &config, &len); > > > > printf should be bellow ndis_get_info() and above ndis_set_info(). > > Alright, I've moved the printf down a few lines and recompiled. > > > Does same problem happens when not using WPA eg. wpa_supplicant? > > It's actually been running just fine since I got home. I'm still using > wpa_supplicant, but with WEP instead of WPA. This has been about four > hours. Not much network traffic, but certainly more than what causes > the problem at work. > > I'm going to let it continue to run through the night. I have a cron > job setup to transfer several 800 meg files to this laptop via scp, so > it'll be interesting to see if that works over this driver. > > Tomorrow morning, when I get into work, I'll grab the debug output > again, this time with the printf (hopefully) in the correct place. Looks like config.nc_dsconfig is 2462000 The wireless connection stayed up all night, even while transferring over 2 gigs of data via scp. The problem appears to be specific to this AP using WPA. I can try WPA on my home network in about 10 hours to see if the same happens there. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.