OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
PA2AGA > TCPDIG   10.09.96 06:10l 173 Lines 5848 Bytes #-10891 (0) @ EU
BID : TCP_96_185C
Read: DG7DAH GUEST
Subj: TCP-Group Digest 96/185C
Path: DB0AAB<DB0SL<DB0RGB<DB0ABH<DB0SRS<DB0ZDF<DB0AIS<DB0NDK<DB0ACH<DB0ACC<
      PI8DRS<PI8DAZ<PI8GCB<PI8WFL<PI8MBQ<PI8VNW
Sent: 960909/2338Z @:PI8VNW.#ZH2.NLD.EU #:64511 [Hoek v Holland] FBB5.15c
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To  : TCPDIG@EU

Received: from pa2aga by pi1hvh with SMTP
	id AA17398 ; Mon, 09 Sep 96 22:52:36 UTC
Received: from pa2aga-10 by pa2aga (NET/Mac 2.3.61/7.1) with SMTP
	id AA00004425 ; Mon, 09 Sep 96 23:44:57 MET
Received: from pa2aga-10 by pa2aga-10 (NET/Mac 2.3.61/7.1) with SMTP
	id AA00005497 ; Mon, 09 Sep 96 18:39:07 MET
Date: Mon, 09 Sep 96 08:41:17 MET
Message-Id: <tcp_96_185C>
From: pa2aga
To: tcp_broadcast@pa2aga-10
Subject: TCP-Group Digest 96/185C
X-BBS-Msg-Type: B

"import/export" format to other BBSes, or it can fire up a TELNET session
to a remote BBS and forward that way.

The whole thing has been growing over the last 7 years. It
has a lot of crummy code and just generally needs some "elegantizing",
but it works. I wish I had the time to clean it up.

I've never gone to a newer version , one of the NOSes, because it worked
pretty well, but it's getting hopelessly outdated. That's why I was
working on the wampes code. I actually got a version to compile
that had most of the duplicate funtionality stripped out, but
I never got around to adding the BBS interface for my stuff.

> 
> While external processes to hook AX.25 into the kernal as if it
> was any other network interface is nice, there is something to
> consider in the Linux AX.25 kernel stuff for establishing a
> unique address family for amateur radio connections. Am not sure
> of their internal details. Am not sure I like the AX.25 network
> functioning *differenty* than the good old standard internet.
> Am not really sure how Linux's kernel AX.25 is from ethernet.
> 

I was under the impression that they didn't support connected-mode
AX.25 at all? 

-Jim Durham
           

------------------------------

Date: Sat, 7 Sep 1996 23:15:16 -0400 (EDT)
From: Jim Durham <durham@durham.UCSD.EDU>
Subject: Anyone running FreeeBSD?

On Sat, 7 Sep 1996, Alan Cox wrote:

> If you are going to do that kind of work, do yourself and the whole BSD
> community a favour - put your AX.25 and IP over AX.25 in the kernel over
> the BSD socket API. Its not much more work that trying to patch bits
> of wampes and stuff together and it gives you a much nicer final result.
> 

I'd like to.

-Jim Durham
           

------------------------------

Date: Sun, 8 Sep 1996 17:06:36 +1000
From: "Graham Broadbridge" <grahamb@peachy.apana.org.au>
Subject: Anyone running FreeeBSD?

> One of the things
> KO4KS once listed under thoughts for future TNOS's was to split
> out each of the servers into separate executables in a more
> traditional Unix fashion.

Yep, Brian's certainly said that.  Next thing he did was build an HTTP
server
into TNOS.

That is the primary reason I went straight Linux AX25 and dropped TNOS.


Graham.

------------------------------

Date: Sun, 8 Sep 1996 00:23:59 -0500
From: Mail Delivery Subsystem <MAILER-DAEMON@mail.phoenix.net>
Subject: Returned mail: Host unknown (Name server: durham.ucsd.edu: host not
found)

This is a MIME-encapsulated message

--AAA21261.842160239/mail.phoenix.net

The original message was received at Sun, 8 Sep 1996 00:23:58 -0500
from rhorer@alpha1.phoenix.net [199.3.232.17]

   ----- The following addresses had delivery problems -----
<durham@durham.UCSD.EDU>  (unrecoverable error)

   ----- Transcript of session follows -----
550 <durham@durham.UCSD.EDU>... Host unknown (Name server: durham.ucsd.edu:
host not found)

   ----- Original message follows -----

--AAA21261.842160239/mail.phoenix.net
Content-Type: message/rfc822

Return-Path: rhorer@phoenix.net
Received: from alpha1.phoenix.net (rhorer@alpha1.phoenix.net [199.3.232.17])
by mail.phoenix.net (8.6.12/8.6.12) with SMTP id AAA21259 for
<durham@durham.UCSD.EDU>; Sun, 8 Sep 1996 00:23:58 -0500
Date: Sun, 8 Sep 1996 00:23:58 -0500 (CDT)
From: Kyle Rhorer <rhorer@phoenix.net>
To: Jim Durham <durham@durham.UCSD.EDU>
Subject: Re: Anyone running FreeeBSD?
In-Reply-To: <Pine.BSF.3.91.960907223609.6209B-100000@w2xo.pgh.pa.us>
Message-ID: <Pine.OSF.3.93.960908002101.11959D-100000@alpha1.phoenix.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 7 Sep 1996, Jim Durham wrote:

> The bbs can be called as a "mailer" from sendmail by using a
> "front-end" process in between that translates RFC-822 mail
> format to ham BBS format. My sendmail.cf file has the ham
> "domains" (NOAM, SOAM, OC, AS, AF, ME, EU) in its rule sets so
> that mail coming in to a packet address calls the bbs as a mailer.
> 
> I also have a process that looks in the var/spool/mail directory for mail
> files to the user "import" at this system, and feeds the file to the input
> of the bbs. This allows e-mailing files in the old RLI "import/export"
> format via e-mail for forwarding. On the other end, the bbs has an
> expanded forwarding file that understands forwarding by e-mail, using the
> "import/export" format to other BBSes, or it can fire up a TELNET session
> to a remote BBS and forward that way.

I'm quite interested in seeing what you have.  I co-sysop a gateway and
we've been struggling with how to interface Internet mail with packet
mail.  It sounds like what you have is almost exactly what we are looking
for.

Kyle KB5IMO
-- 
        "... but that was just a dream, just a dream, just a dream."
                                                   -- R. E. M.

                     Kyle Rhorer <rhorer@phoenix.net>
                      http://www.phoenix.net/~rhorer


--AAA21261.842160239/mail.phoenix.net--

------------------------------

End of TCP-Group Digest V96 #185
******************************

You can send your message for this bulletin
to:     tcp-group@pa2aga           on .AMPR.ORG-net
or:     tcpaga@pi8vnw.#zh2.nld.eu  on BBS-net
        ------

NOT TO: pa2aga@pa2aga  or  pa2aga@pi8vnw.#zh2.nld.eu  PLEASE!!

It will get posted automatically within a few days





Read previous mail | Read next mail


 06.07.2026 17:54:38lGo back Go up