From owner-freebsd-hackers Fri Jan 20 09:38:09 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA15740 for hackers-outgoing; Fri, 20 Jan 1995 09:38:09 -0800 Received: from inet-gw-3.pa.dec.com (inet-gw-3.pa.dec.com [16.1.0.33]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id JAA15734 for ; Fri, 20 Jan 1995 09:38:04 -0800 Received: from muggsy.lkg.dec.com by inet-gw-3.pa.dec.com (5.65/10Aug94) id AA26197; Fri, 20 Jan 95 09:34:41 -0800 Received: from whydos.lkg.dec.com by muggsy.lkg.dec.com (5.65/DEC-Ultrix/4.3) with SMTP id AA24719; Fri, 20 Jan 1995 12:30:19 -0500 Received: from localhost (localhost [127.0.0.1]) by whydos.lkg.dec.com (8.6.9/8.6.9) with SMTP id NAA04311; Fri, 20 Jan 1995 13:35:39 GMT Message-Id: <199501201335.NAA04311@whydos.lkg.dec.com> X-Authentication-Warning: whydos.lkg.dec.com: Host localhost didn't use HELO protocol To: Garrett Wollman Cc: hackers@FreeBSD.org Subject: Re: NETBEUI for FreeBSD? Any docs? In-Reply-To: Your message of "Thu, 19 Jan 1995 20:35:35 EST." <9501200135.AA00248@halloran-eldar.lcs.mit.edu> X-Mailer: exmh version 1.5omega 10/6/94 Date: Fri, 20 Jan 1995 13:35:37 +0000 From: Matt Thomas Sender: hackers-owner@FreeBSD.org Precedence: bulk > < said: > > > As does NETBEUI in Workgroup for Windows. Most of the support for NETBEUI > > already exists in FreeBSD in the netccitt directory. NETBEUI is little more > > than LLC2 (ISO 8802.2 Class 2) with SMB running over it. LLC2 is really LAPB > > slightly hacked to works over LANs. netccitt already has the LAPB > > engine, someone needs to add in the LAN support (as well as getting the > > right hooks in ethersubr). > > You mean like: > > wollman@khavrinen(753)$ pwd > /usr/src/sys/netccitt > wollman@khavrinen(754)$ ls llc* > llc_input.c llc_output.c llc_subr.c~ llc_var.h > llc_input.c~ llc_subr.c llc_timer.c > > ? Or is there something more? (I suspect so, since the existing LLC2 > code only talks to the X.25 code.) The llc code looks like it should work for doing the LLC2 work. There are a few datagrams that need to dealt with for name discovery but those should not be hard to add. Adding a socket interface to the llc routines (look at the X.25 interface to see what needs to added on the bottom) should suffice. If I were doing it, I'd make the interface a generic LLC2 interface with bind/listen/accept /connect etc suppport. (The UI packets would be delivered to the listener to deal with -- the listener would also transmit). The reason for that is so other LLC2 protocols could be added (such as RPL) without additional kernel hacking. Matt Thomas Internet: matt@lkg.dec.com U*X Networking WWW URL: http://ftp.dec.com/%7Ethomas/ Digital Equipment Corporation Disclaimer: This message reflects my Littleton, MA own warped views, etc.