From owner-freebsd-current Wed Feb 26 12: 7:36 2003 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id EB50837B401; Wed, 26 Feb 2003 12:07:34 -0800 (PST) Subject: Re: Checksum offload support for Intel 82550/82551 In-Reply-To: from Attila Nagy at "Feb 26, 2003 08:15:20 pm" To: bra@fsn.hu (Attila Nagy) Date: Wed, 26 Feb 2003 12:07:34 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20030226200734.EB50837B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I think my problem is not that hard. This bug only occurs when you are > using CURRENT (or 5.0 RELEASE) from (I think) the point where BPF changed. Actually, there's something else than changed. The ng_fec module tries to set ifp->if_output to ng_fec_output() so that it can do some output processing on frames, however, later it would call ether_ifattach(), which would set ifp->if_output to ether_output(), which wouldn't work. I just commited a fix for this. (I verified that I can successfully send packets via fec0.) I also modified the input handling so that it no longer uses the ng_ether_input_p hook. Now that FreeBSD 5.x has an ifp->if_input vector, it's not necessary to abuse this hook anymore. This avoids a collision with the ng_ether module, which is what was supposed to be using this hook in the first place. Let me know how this works. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message