From owner-freebsd-net@freebsd.org  Tue May 17 21:24:44 2016
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 4D0E2B3F742
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Tue, 17 May 2016 21:24:44 +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 3D7441468
 for <freebsd-net@FreeBSD.org>; Tue, 17 May 2016 21:24:44 +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 u4HLOi5a096262
 for <freebsd-net@FreeBSD.org>; Tue, 17 May 2016 21:24:44 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 197790] Intel em driver - random outgoing traffic sent through
 wrong interface
Date: Tue, 17 May 2016 21:24:44 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: IntelNetworking
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: ddb@neosystem.org
X-Bugzilla-Status: In Progress
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-197790-2472-bF0t0DNNX6@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-197790-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-197790-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.22
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: Tue, 17 May 2016 21:24:44 -0000

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

Daniel Bilik <ddb@neosystem.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ddb@neosystem.org

--- Comment #4 from Daniel Bilik <ddb@neosystem.org> ---
Exactly the same issue here on one host. Problems started after upgrading f=
rom
9.x to 10.x, and have persisted after migrating the host to a newer hardwar=
e.
Previously, it was a machine with re(4) interfaces, while the new one uses
em(4), so I can confirm the problem is very probably not hardware related.

I had disscussed the problem on freebsd-net@ and later reported here as PR
204735. Sorry for duplicate, I've found this bugreport just now. :)

Note: I'm currently testing revisions 286028, 286037 and 286242 from HEAD,
manually applied to 10-STABLE, to see whether it changes this unpleasent
behaviour.

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