From owner-freebsd-current@FreeBSD.ORG Wed Jan 17 06:50:59 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6438116A40F for ; Wed, 17 Jan 2007 06:50:59 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id E705F13C448 for ; Wed, 17 Jan 2007 06:50:58 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp211-97.lns1.adl2.internode.on.net [203.122.211.97]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id l0H6odA1051519 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jan 2007 17:20:53 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Kip Macy" Date: Wed, 17 Jan 2007 17:20:04 +1030 User-Agent: KMail/1.9.5 References: <200701171608.49339.doconnor@gsoft.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1490697.69p0qNRZdv"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200701171720.14983.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.57 on 203.31.81.10 Cc: freebsd-current@freebsd.org Subject: Re: WPA-EAP problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2007 06:50:59 -0000 --nextPart1490697.69p0qNRZdv Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 17 January 2007 16:17, Kip Macy wrote: > > I note that it takes Windows a long time to get a lease - it spends a > > while saying "waiting for network to become ready". > > How long is "a long time"? If it is greater than 60 seconds you can > set the timeout to greater than 60s in dhclient.conf. Alternatively, > you can set the retry to a short interval. 60 seconds wouldn't be far off the mark.. Good point about dhclient.conf I hadn't though about checking it for knobs.. I am wondering if there is something peculiar with my (AP) setup that cause= s=20 it to take so long to auth.. Although I am loathe to fiddle with it because= =20 it was a bit of a PITA to debug in the first place :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1490697.69p0qNRZdv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFrccm5ZPcIHs/zowRAlwIAKCD9ol8N/8KUJ/M65Lga8Src/eUaQCeK6Ac WryjjZDl0bzV/3nm4YxSWN0= =EchP -----END PGP SIGNATURE----- --nextPart1490697.69p0qNRZdv--