From owner-freebsd-hackers Thu Oct 24 14:17:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA22280 for hackers-outgoing; Thu, 24 Oct 1996 14:17:21 -0700 (PDT) Received: from gatekeeper.ray.com (gatekeeper.ray.com [138.125.162.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA22270 for ; Thu, 24 Oct 1996 14:17:13 -0700 (PDT) From: Gregory_D_Moncreaff@ccmail.ed.ray.com Received: (mailer@localhost) by gatekeeper.ray.com (8.7.5/8.7.3) id RAA06213 for ; Thu, 24 Oct 1996 17:11:39 -0400 Received: from zeus.ed.ray.com by gatekeeper.ray.com; Thu Oct 24 17:10:57 1996 Received: from ccmail.ed.ray.com by ZEUS.ED.RAY.COM (PMDF V4.2-10 #4335) id <01IB11QMCQRK0017IX@ZEUS.ED.RAY.COM>; Thu, 24 Oct 1996 17:12:53 EDT Date: Thu, 24 Oct 1996 16:53 -0400 (EDT) Subject: 2.1 netccitt [x.25/hd/pk/llc] fubar'd Cc: hackers@FreeBSD.org Message-id: <01IB11QN0BJA0017IX@ZEUS.ED.RAY.COM> MIME-version: 1.0 Content-transfer-encoding: 7BIT Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk hi, I'm trying to work with the netccitt code, specifically x.25 over hdlc/labp, that was on the freeBSD 2.1 distribution. As far as I can tell, whomever was working with the llc code in 92-93 completely fubar'd the interaction between pk and hd, and left netccitt in a non working state [lots of mismatched protocol lookup function pointers, arguments, return values, etc] Is there any earlier archived netccitt code, vintage '91 or so, that might be in better shape to be had?? I know that bsdi and freeBSD are near identical with respect to netccitt in their 2.1 versions (excepting the extra rtalloc param that bsdi has) but what about the other bsd's (net,open,386,etc)? If anyone is working with 2.1 freeBSD or bsdi, the problem I am currently stuck on is trying to figure out how an hcp can be allocated to handle incoming packets so that hdintr doesn't complain about not finding a hcp on the hdcbhead list that matches the receive ifp in the packet header. The only allocation routine is called when issuing a connect, which is for outgoing. Trying to issue connects in both directions crashes one of the nodes in some vm routine and doesn't produce a core file... btw: I am running this over a SDL Riscom 8/SA board whose driver was hacked from the Cronyx-Sigma driver that came with 2.1 freeBSD [both drivers use the same cl-cd2401 chips], would it be a good thing to fold this into the freebsd distribution (or at least get device numbers assigned)? Is any one else using this board? thanks, G