From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 04:31:36 2012 Return-Path: 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 44B13106564A for ; Thu, 23 Aug 2012 04:31:36 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0C3A58FC08 for ; Thu, 23 Aug 2012 04:31:35 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so600236pbb.13 for ; Wed, 22 Aug 2012 21:31:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=pLXos9u5R0S8zeQs3FFYJ6EVMjjSzt5wEP3GAztmWTc=; b=SKmZbyQ8NfEkCRcPUu2Y4g/41JTzjoQYe/TrPybhuVjMs2ctWbtUbS7WTmf2/R+Hkf C3hWhh5+ZMAZ8p5wAqKi4Sri/uPyHkuf/FI3Z8McrJawZQQBmsw+25mv9MnLM0uq5bgs T6bgIUUcke8/kBr4MK6vmq76ZRTv2g3qFynYw2FS9KG04FD0hljSZuFAblpR8/RJxerN FzPosdwKeWcAgiAnZri/0EYbHjrj1TKbZy4Wimz81aJXILcuVrSadzI/5Of4BCDq/5Pk ZHQiKn1Ixkmd4gRtoh8zBS7ExS6yL+hsZpioIBl7oCnp9nhul+gpPcgei9evToyYo7wD 0HaQ== Received: by 10.66.79.195 with SMTP id l3mr417123pax.33.1345696295436; Wed, 22 Aug 2012 21:31:35 -0700 (PDT) Received: from [10.0.0.63] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id ro7sm5149552pbc.8.2012.08.22.21.31.32 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Aug 2012 21:31:33 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20120823013534.GA31015@server.rulingia.com> Date: Wed, 22 Aug 2012 22:31:29 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120821095527.GA33206@hell.ukr.net> <20120822171253.GB3300@michelle.cdnetworks.com> <20120822172822.GA52909@hell.ukr.net> <201208221535.01598.jhb@freebsd.org> <20120823013534.GA31015@server.rulingia.com> To: Peter Jeremy X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQkXMGekuOMdaKCUbGwK9yhc8eg0obltsUWxy9413jzpca5FAEcFSvIPXLoXz0hqizjg+C9G Cc: YongHyeon PYUN , freebsd-current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? 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: Thu, 23 Aug 2012 04:31:36 -0000 On Aug 22, 2012, at 7:35 PM, Peter Jeremy wrote: > On 2012-Aug-22 15:35:01 -0400, John Baldwin wrote: >> Hmm. Perhaps we could use a debouncer to ignore "short" link flaps? = Kind of >> gross (and OpenBSD doesn't do this). For now this change basically = ignores >> link up events if they occur with 5 seconds of the link down event. = The 5 is >> hardcoded which is kind of yuck. >=20 > I'm also a bit concerned about this for similar reasons to adrian@. > We need to distinguish between short link outages caused by (eg) a > switch admin reconfiguring the switch (which needs the lease to be > re-checked) and those caused by broken NICs which report link status > changes when they are touched. Maybe an alternative is to just ignore > link flaps when they occur within a few seconds of a script_go(). > (And/or make the ignore timeout configurable). >=20 > Apart from fxp(4), does anyone know how many NICs are similarly > broken? >=20 > Does anyone know why this issue doesn't bite OpenBSD? Does it have > a work-around to avoid resetting the link, not report link status > changes or just no-one has noticed the issue? Speaking of fxp(4), can't it defer reporting link status changes during = the reset sequence it must perform? Wouldn't it be better to fix the = broken driver(s) to behave better than to add a twisty maze of hacks to = dhclient? Warner