From owner-freebsd-net Fri Feb 1 20:30: 8 2002 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id F079537B404 for ; Fri, 1 Feb 2002 20:30:03 -0800 (PST) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id UAA42145 for ; Fri, 1 Feb 2002 20:18:40 -0800 (PST) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.6/8.11.6) id g124Ie861881 for freebsd-net@freebsd.org; Fri, 1 Feb 2002 20:18:40 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200202020418.g124Ie861881@arch20m.dellroad.org> Subject: Delayed checksums problem? To: freebsd-net@freebsd.org Date: Fri, 1 Feb 2002 20:18:40 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm looking into this bug: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/31586 In short, using ng_bridge(4) with de(4) and xl(4) drivers, they're seeing broken TCP checksums on the wire. It sounds like there's some delayed TCP checksum hack that is breaking when doing bridging this way. Could someone quickly explain how delayed TCP checksums (or whatever they're called) is supposed to work? Thanks, -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message