kern/131781: [ndis] ndis keeps dropping the link

[Paul B. Mahol]

On 2/19/09, Adam K Kirchhoff <adamk at voicenet.com> wrote:
> On Thu, 19 Feb 2009 05:50:35 -0500
> Adam K Kirchhoff <adamk at voicenet.com> wrote:
>
>> On Wed, 18 Feb 2009 19:48:10 -0500
>> Adam K Kirchhoff <adamk at voicenet.com> wrote:
>>
>> > On Thu, 19 Feb 2009 01:10:08 +0100
>> > "Paul B. Mahol" <onemda at gmail.com> wrote:
>> >
>> > > On 2/18/09, Adam K Kirchhoff <adamk at voicenet.com> 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.
>
> When I switched my home network to use WPA I started to have the same
> problems as with the WPA network at work.  config.nc_dsconfig still
> reads 246200.

Enable wpa_supplicant debugging and try find something interesting.
I still cant understant why enabling debug.ndis hides problem.

-- 
Paul