Subject: Re: bge(4) tcp4csum problem -- driver problem or chip problem???
To: Ignatios Souvatzis <is@NetBSD.org>
From: Brian Buhrow <firstname.lastname@example.org>
Date: 12/19/2006 09:01:31
Hello. During my tests, the only variable I changed was the tcp4csum
value with ifconfig on the bge(4) interface. Ip4csum and udp4csum were
enabled during all tests, and remain so on this production machine. I
didn't think to try disabling ip4csum while leaving tcp4csum enabled. Are
these settings not hierarchical? That is, if you enable tcp4csum, are you
not, by implication, also enableing ip4csum checking?