From owner-freebsd-net@FreeBSD.ORG Sun Mar 19 23:31:37 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 233AC16A400 for ; Sun, 19 Mar 2006 23:31:37 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE1B543D45 for ; Sun, 19 Mar 2006 23:31:36 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 521C819F2C; Sun, 19 Mar 2006 15:31:35 -0800 (PST) Message-ID: <441DE9D5.3060900@bitfreak.org> Date: Sun, 19 Mar 2006 15:31:33 -0800 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Sam Leffler References: <200603191738.19442.max@love2party.net> <441DE5B2.1060202@bitfreak.org> <441DE754.6020004@errno.com> In-Reply-To: <441DE754.6020004@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Max Laier , freebsd-net@freebsd.org Subject: Re: New version of iwi(4) - Call for testers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Mar 2006 23:31:37 -0000 Sam Leffler wrote: > Darren Pilgrim wrote: >> >> Are you referring to the problem in cvsup tests where it will suddenly >> stop with a "Network write failure" error? > > Yes. The issue was that when crypto was done in the host it was > sometimes being done in-place on mbufs still owned by the socket > (exactly when depended on a lot of things but turning down the mtu > increased the likelihood). If this happened and tcp retransmitted the > previously encrypted data then it would send garbage. > > As Max said this was in the net80211 layer and affected all drivers > depending on the host to do crypto. It'll get mfc'd this week (re > permitting). I'm glad to hear I finally have a driver for my wireless NIC that's as stable it (currently) gets, since the above is the only problem I've been able to coax out of my machine. So Max... great job!