From owner-freebsd-net Sun Apr 8 23:27:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from jason.argos.org (64-205-228-106.client.dsl.net [64.205.228.106]) by hub.freebsd.org (Postfix) with ESMTP id 4702B37B42C for ; Sun, 8 Apr 2001 23:27:50 -0700 (PDT) (envelope-from mike@jason.argos.org) Received: (from mike@localhost) by jason.argos.org (8.10.1/8.10.1) id f396Rbi31564; Mon, 9 Apr 2001 02:27:37 -0400 Date: Mon, 9 Apr 2001 02:27:37 -0400 From: Mike Nowlin To: Aleksander Rozman - Andy Cc: freebsd-net@freebsd.org Subject: Re: AX.25 or maybe X.25 support? Message-ID: <20010409022737.C31037@argos.org> References: <5.0.2.1.0.20010408223914.02248fc0@164.8.8.5> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="lCAWRPmW1mITcIfM" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.2.1.0.20010408223914.02248fc0@164.8.8.5>; from andy@kksonline.com on Sun, Apr 08, 2001 at 10:42:57PM +0200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --lCAWRPmW1mITcIfM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 0, Aleksander Rozman - Andy wrote: > I am new here, so I was just wondering if there was any talk on=20 > implementing AX.25 or X.25 protocol to FreeBSD? > AX.25 is protocol for Packet Radio (Internet through HAM devices). X.25= =20 > should be *little* similar to AX.25, but not that much. Having AX.25 done= =20 > already would be great, but if there is X.25 we could work from there and= =20 > make it AX.25. So anybody heard about anything like this on FreeBSD? I've been toying around with this for a while (about two years), but have yet to decide what the best way to handle this is. I've used the AX.25 stuff in Linux quite extensively, but I'm not really happy with the way it's designed or made use of. I suppose the first thing to figure out is what you want to DO with AX.25 drivers. Implement Net/ROM and build a 573-port backbone packet router node? IP-over-packet routing (as in NOS)? End-user BBS applications? =20 I could see FreeBSD running as an exquisite router node if the drivers were built into the kernel, ASSUMING that the configuration code and back-end drivers were written with a little more intelligence than the Linux versions are. (That could be a little difficult, but do-able.) The Net/ROM protocol sorta lends itself to this, and ROSE is a disgusting thing that should be avoided at all costs. :) If you're going to run IP over packet, the IPFW and NATD code in the kernel could add all kinds of creative stuff that's almost impossible to do with THE/NET-X1J & friends. If the main interest is running an end-user BBS, I think the appropriate method is to build in a simple KISS-to-userspace driver over serial ports, then let the userspace BBS software handle things from that point - or, you could just tweak a copy of NOS to run on FBSD and let it operate just like it does on Linux. Then I think about WAMPES. I like the idea that it integrates things betwe= en packet users & the standard UNIX services, but I absolutely hate the way it does it. With any modern system, it's completely idiotic to have a userspace program add accounts to /etc/passwd by user request. (My brain shifts gears a bit...) The WAMPES idea, implemented under FreeBSD jails, could provide the best of both worlds. Create a virtual machine that has it's own config and nothing that's security-sensitive, and you might have something worth running... I could rant on for hours. --mike N8NVW --lCAWRPmW1mITcIfM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjrRVlkACgkQJol4I8h9Gd919ACgtMyTn1qNcZOkuNeGWthv/Qa4 GyUAoIRdZvaaL/Z3rbWrSsrjZSvddqO4 =Yt3T -----END PGP SIGNATURE----- --lCAWRPmW1mITcIfM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message