From owner-freebsd-net@freebsd.org Thu Feb 1 20:40:37 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 495B8EC7B91 for ; Thu, 1 Feb 2018 20:40:37 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 9F00684C04; Thu, 1 Feb 2018 20:40:36 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Thu, 01 Feb 2018 21:39:23 +0100 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 0082D8CA-2318-4034-9024-A112AD1E8698.1 envelope-from (authenticated bits=0); Thu, 01 Feb 2018 21:39:22 +0100 From: Rainer Duffner Message-Id: <8D9EE21E-687F-4F33-B971-D093CFB404ED@ultra-secure.de> Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Issues with bxe NIC Date: Thu, 1 Feb 2018 21:39:18 +0100 In-Reply-To: Cc: Marius Halden , FreeBSD Net To: Matt Joras References: <1517494674.4068747.1255940744.6E4465CF@webmail.messagingengine.com> <1517497005.912910.1255997344.7F24E8FC@webmail.messagingengine.com> X-Mailer: Apple Mail (2.3445.5.20) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=15 total_conn=10 shared_ip=Y X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 4820, bad: 1, connections: 5294, history: 4819, asn_score: 535, asn_connections: 564, asn_good: 535, asn_bad: 0, pass:asn, asn_all_good, relaying Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 20:40:37 -0000 > Am 01.02.2018 um 21:21 schrieb Matt Joras : >=20 > This is one of many issues we have seen with the NetXtreme II device. After I had problems with lagg(4) (well, it just didn=E2=80=99t work at = all), I opened a PR (or I found an existing one) and added to it. I didn=E2=80=99t even really realize it was bxe(4) at first. After a while, I switched to ix(4) and there was no further issue with = the server.