From owner-freebsd-net@freebsd.org  Fri Jan  6 14:32:18 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC1A5CA2048
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Fri,  6 Jan 2017 14:32:18 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id DB6B71BDA
 for <freebsd-net@FreeBSD.org>; Fri,  6 Jan 2017 14:32:18 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v06EWIx7022926
 for <freebsd-net@FreeBSD.org>; Fri, 6 Jan 2017 14:32:18 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 211219] NIC status does not pass into a state of "no carrier"
 after disconnecting the cable.
Date: Fri, 06 Jan 2017 14:32:19 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: IntelNetworking
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: julien@perdition.city
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-211219-2472-h3srjFcloW@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211219-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-211219-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jan 2017 14:32:19 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211219

Julien Cigar <julien@perdition.city> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |julien@perdition.city

--- Comment #13 from Julien Cigar <julien@perdition.city> ---
I *think* I experienced something similar on a Soekris 6501 (amd64) recentl=
y.
We have two of those boxes which serve as a redundant firewall, dhcp server,
local DNS server, etc..

The DHCP server is configured in "balancing mode", with something like:

load balance max seconds 3;
mclt 1800;
split 128;

Which means (more of less) that client DHCP requests are balanced between t=
he
two. Recently the BACKUP died (still powered on, but unreachable), but for =
some
unknown reason the clients which got their IPs from the BACKUP DHCP server =
just
"lost" it after the lease time passed.. and didn't get a new IP from the MA=
STER
node.. I suspect also that's because the interfaces didn't go into the "no
carrier" state.

This is on 10.2-RELEASE with 82574L cards.

--=20
You are receiving this mail because:
You are the assignee for the bug.=