From owner-freebsd-current Tue May 19 18:33:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08788 for freebsd-current-outgoing; Tue, 19 May 1998 18:33:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08758 for ; Tue, 19 May 1998 18:32:50 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id VAA22737; Tue, 19 May 1998 21:32:39 -0400 (EDT) (envelope-from wollman) Date: Tue, 19 May 1998 21:32:39 -0400 (EDT) From: Garrett Wollman Message-Id: <199805200132.VAA22737@khavrinen.lcs.mit.edu> To: Bill Trost Cc: current@FreeBSD.ORG Subject: Re: fast forwarding patches In-Reply-To: <15774.895617911@cloud.rain.com> References: <199805191600.SAA09893@labinfo.iet.unipi.it> <15774.895617911@cloud.rain.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > AFAIK, the only link layer that does not performing checksumming packets > in their entirety is SLIP. Don't run both SLIP and fast forwarding and > everything should be fine. The purpose of the IP header checksum (and also the transport checksum) is principally NOT to guard against link errors -- indeed, it is entirely insufficient for that. Rather, it is intended to guard against logical errors which cause packets to be corrupted while in host memory. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message