From owner-freebsd-i386@freebsd.org  Wed Sep 28 20:13:30 2016
Return-Path: <owner-freebsd-i386@freebsd.org>
Delivered-To: freebsd-i386@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 DB6D5C01798
 for <freebsd-i386@mailman.ysv.freebsd.org>;
 Wed, 28 Sep 2016 20:13:30 +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 CACB97C5
 for <freebsd-i386@FreeBSD.org>; Wed, 28 Sep 2016 20:13:30 +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 u8SKDRfP049471
 for <freebsd-i386@FreeBSD.org>; Wed, 28 Sep 2016 20:13:30 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-i386@FreeBSD.org
Subject: [Bug 211219] NIC status does not pass into a state of "no carrier"
 after disconnecting the cable.
Date: Wed, 28 Sep 2016 20:13:28 +0000
X-Bugzilla-Reason: CC
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: chaodis852654@gmail.com
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-10-xluPGbo2L6@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211219-10@https.bugs.freebsd.org/bugzilla/>
References: <bug-211219-10@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-i386@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: I386-specific issues for FreeBSD <freebsd-i386.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-i386>,
 <mailto:freebsd-i386-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-i386/>
List-Post: <mailto:freebsd-i386@freebsd.org>
List-Help: <mailto:freebsd-i386-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
 <mailto:freebsd-i386-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2016 20:13:30 -0000

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

CS <chaodis852654@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chaodis852654@gmail.com

--- Comment #6 from CS <chaodis852654@gmail.com> ---
I think I experience the same using pfsense 2.3.2-RELEASE FreeBSD
10.3-RELEASE-p5 on a Soekris 6501 board (i386). In addition to that, after
connecting the cable back after a few hours or in general when the link sta=
te
changes to UP the device connected to that port has no network connectivity
until I reboot pfSense. More details can be found here:
hxxps://redmine.pfsense.org/issues/6823

--=20
You are receiving this mail because:
You are on the CC list for the bug.=