From owner-freebsd-questions Mon Feb 9 18:53:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25276 for questions-outgoing; Mon, 9 Feb 1998 18:53:59 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25262 for ; Mon, 9 Feb 1998 18:53:37 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-65.HiWAAY.net [208.147.148.65]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id UAA30114; Mon, 9 Feb 1998 20:53:35 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id UAA01043; Mon, 9 Feb 1998 20:07:30 -0600 (CST) Message-Id: <199802100207.UAA01043@nospam.hiwaay.net> X-Mailer: exmh version 2.0.1 12/23/97 To: george cc: questions@FreeBSD.ORG From: David Kelly Subject: Re: JNOS In-reply-to: Message from george of "Mon, 09 Feb 1998 05:00:43 CST." <34DEE1DA.2C0148EF@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Feb 1998 20:07:30 -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am wondering if anyone has ever tried running JNOS packet bbs on > FreeBSD.? > > I see it running on a Linux machine... For those who don't know, JNOS and TNOS are derivatives of the original KA9Q NET and NOS code which implemented its own IP world in a single DOS executable. While used for many other things, it became the basis for experimenting with IP over amateur radio. TNOS 2.22 (or was it 2.23?) (http://www.lantz.com) was the last version I submitted FreeBSD patches direct to the author. Mostly they were retained in TNOS 2.30 but its a couple of unresolved references away from a clean FreeBSD compile. I started back on TNOS 2.30 this weekend and got distracted discovering the inner workings of the FreeBSD ports system. Maybe we'll have a FreeBSD port of TNOS soon. Also got distracted working on the One Biggest Problem of connecting the TNOS IP world to the FreeBSD kernel's IP world. Linux systems use SL/IP thru a pty pair, slattach from the kernel side, and let TNOS attach to one (which one? slave or master? I forget) of the pty's. FreeBSD's pty's don't support all the ioctl's FreeBSD's slattach issues. So that doesn't work. Was playing with /dev/tun0. "hd /dev/tun0" and then using ifconfig on tun0, and pinging thru the interface was a kick. It worked! But there are 2 problems, TNOS knows SL/IP not tun, but worst of all FreeBSD refuses to allow any but root to read/write /dev/tun0. Permissions on the device don't matter, the kernel double checks and refuses to operate if the process connected to /dev/tun0 is not root. IMHO a program such as TNOS has no business running as root so a minimal setuid-root buffer process is needed. Maybe same process should fake SL/IP? But then how to connect it to TNOS? Thru pty's! And we're back to the original SL/IP problem. Probably would be best/easiest to write a new slattach. /dev/tun0 offers some real attractive prospects for IP over amateur radio. Simply reframe the output of /dev/tun0 into KISS format and dump it on the TNC. Same for TNC output, strip the KISS framing and dump it on /dev/tun0. Then start wondering how to adjust the IP timers thru the /dev/tun interface... more time spend reading ppp code. And not writting code. And that's what I did this weekend. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe questions" in the body of the message