From owner-freebsd-net@FreeBSD.ORG Tue Jul 18 10:26:36 2006 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D26916A4DD for ; Tue, 18 Jul 2006 10:26:36 +0000 (UTC) (envelope-from nike_d@cytexbg.com) Received: from mail.interbgc.com (mx02.interbgc.com [217.9.224.227]) by mx1.FreeBSD.org (Postfix) with SMTP id BAFEC43D7B for ; Tue, 18 Jul 2006 10:26:27 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: (qmail 12928 invoked from network); 18 Jul 2006 10:26:25 -0000 Received: from nike_d@cytexbg.com by keeper.interbgc.com by uid 1002 with qmail-scanner-1.14 (uvscan: v4.2.40/v4374. spamassassin: 2.63. Clear:SA:0(0.1/8.0):. Processed in 1.478931 secs); 18 Jul 2006 10:26:25 -0000 X-Spam-Status: No, hits=0.1 required=8.0 Received: from niked.ddns.cablebg.net (HELO tormentor.totalterror.net) (85.130.14.211) by mx02.interbgc.com with SMTP; 18 Jul 2006 10:26:23 -0000 Received: (qmail 5136 invoked from network); 18 Jul 2006 10:26:23 -0000 Received: from unknown (HELO ?10.0.0.3?) (10.0.0.3) by tormentor.totalterror.net with SMTP; 18 Jul 2006 10:26:23 -0000 Message-ID: <44BCB74E.5020307@cytexbg.com> Date: Tue, 18 Jul 2006 13:26:22 +0300 From: Niki Denev User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: stable@freebsd.org References: <44BCB58E.8010707@cytexbg.com> In-Reply-To: <44BCB58E.8010707@cytexbg.com> X-Enigmail-Version: 0.94.0.0 OpenPGP: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: ural(4) deassociates if no activity (possible wpa_supplicant problem) 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: Tue, 18 Jul 2006 10:26:36 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Niki Denev wrote: > Hello, > > I've noticed something very interesing while using a ural(4) usb wifi device. > > When i plug the usb device, and there is absolutely no network activity, exactly > after five minutes the device deassociates from the access point. > > I've put some debug printf's in ural_newstate and when i plug the device, > i get several IEEE80211_S_SCAN state changes, > then i gets from IEEE80211_S_AUTH to ASSOC and then RUN. > Nothing wrong here, but exactly after five minutes of no activity (measured > with stopwatch) i get a state transition from IEEE80211_S_RUN to IEEE80211_S_AUTH > and it stays that way, until i remove/insert the device again or send HUP to > wpa_supplicant and restart dhclient. > > This looks maybe like wpa_supplicant problem, and i think i've had similar problems with > ath(4) mini-pci card and card bus ral(3), but as far as i remember the period of > inactivity was much greater with them (i'll try to test this on these cards too when > i have access to them again) > > > Regards, > --niki Well, after a few more moments investigating the problem it seems that dhclient is to blame. If i don't start it i don't get disconnected, and also i noticed that the five minute interval matches the dhclient renewal period of 300 seconds. So the logical question is, why dhclient makes my ural(4) adapter deassociate, and what i can do to prevent this :) Thanks! - --niki -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEvLdOHNAJ/fLbfrkRAnt+AKCnpfDdSucSccRTm4Qmg4ONVWQqzwCgygJp EE+HPPMAbzIhMOsHO6Q+f6o= =NXMO -----END PGP SIGNATURE-----