Date: Tue, 15 Apr 1997 00:49:40 -0500 (CDT) From: Jim Bryant <jbryant@argus> To: durham@w2xo.pgh.pa.us (Jim Durham) Cc: freebsd-hackers@freebsd.org Subject: Re: question about X.25 drivers Message-ID: <199704150549.AAA10808@argus> In-Reply-To: <3352F86E.2781E494@w2xo.pgh.pa.us> from "Jim Durham" at Apr 14, 97 11:39:26 pm
next in thread | previous in thread | raw e-mail | index | archive | help
In reply: > Jim Bryant wrote: > > > > well, x.25 is not my favorite thing in the world, but i have ulterior > > motives... to get freebsd out amongst some forward thinking hams... > > also, of course, to have a kernel level AX.25 interface to my own > > equipment, it would greatly simplify doing TCP/IP encapsulation... > > > (snip!) > > > > such a kernel driver is highly desirable... if there wasn't a market > > for it, i wouldn't be wasting my time, your time, or the -core's > > time... > > I'll volunteer to help. I'm running AX25 using a user-level program > on 2.1.7, which I'm planning to try to make into a decent port, but > I've been thinking about native AX25 stuff for a while. okay, no problem.. > My question is whether it should be part of the kernel or implemented > as a line discipline, which it really is...like SLIP. i was originally thinking along the same lines...like ppp/slip, but then the original netccitt drivers that would be an ideal starting point.. so far i have been informed of working X.25 netccitt drivers that lack AX.25, and that could be where i start... > Jim Durham, (W2XO) send me some mail sometime... kv5vdj@wv0t.#neks.ks.usa.noam wv0t just set me up with forwarding/reverse forwarding... jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" jbryant@tfs.net - KC5VDJ 2-meter, 70cm - KPC-3 Plus packet capable
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704150549.AAA10808>