Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 05 Dec 2016 07:23:01 +0000
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.
Message-ID:  <bug-211219-2472-Y1IHwrCrpa@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/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211219

--- Comment #8 from Franco Fichtner <franco@opnsense.org> ---
Hi all,

Last time we checked this also affected 11.0.  Unfortunately, there multiple
issues at play here:

The FreeBSD em(4) driver under 10.3+ has this bug, and the Intel 7.6.2 driv=
er
fixes this on 10.3.  But the Intel driver does not fully work under 11.0 --=
 it
has issues with netmap(4) (e.g. using Suricata) there.

The link issue in particular also manifests in several VM deployments that =
we
heard of through OPNsense, where widespread emulation of e1000 is an integr=
al
part of daily operation and required to be reliable.  The only fix there wa=
s to
install the Intel driver, but obviously this doesn't fully work on 11.0
anymore.

So we were hoping to see some progress in either:

Getting the FreeBSD 10.3+ regression ironed out,

and/or

Seeing an Intel driver bump for reliable netmap(4) operation under 11.0.

Bottom line is can we help in any way to speed this up?


Thanks,
Franco

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211219-2472-Y1IHwrCrpa>