From owner-freebsd-current@FreeBSD.ORG Tue Oct 25 23:24:24 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AC2316A420 for ; Tue, 25 Oct 2005 23:24:24 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DC6B43D48 for ; Tue, 25 Oct 2005 23:24:24 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465 for ; Tue, 25 Oct 2005 16:24:20 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id E00155D04 for ; Tue, 25 Oct 2005 16:24:19 -0700 (PDT) To: current@freebsd.org Date: Tue, 25 Oct 2005 16:24:19 -0700 From: "Kevin Oberman" Message-Id: <20051025232419.E00155D04@ptavv.es.net> Cc: Subject: On-going problems with new dhclient 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: Tue, 25 Oct 2005 23:24:24 -0000 Brooks et. al., I have just spent a miserable time fighting with the new dhclient. I am currently working in Seattle getting a very large network ready for a bit computer show next month. I have excellent signal strength and don't ever see the association drop. But I keep loosing my address and long before the lease expires. For a while I was seeing the address vanish more than once a minute. Ack! I assumed that dhclient was exiting, but then I did "ps -ax | grep dhclient" and I discovered that I had a whole bunch of processes, half [priv] and half not, all on the same interface. This looked rather broken to me. I had "restarted" dhclient several times, so I suspect it was not really exiting when the network died and the address went away. I know that if_wi does not play nice with the 802.11 modem but I really don't think this should be happening. It's rally annoying! I don't see this on my home wireless, but I have seen it several times while traveling. I see it occasionally at work. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634