| |
PA2AGA > TCPDIG 24.02.97 22:05l 229 Lines 7701 Bytes #-10709 (0) @ EU
BID : TCP_97_23B
Read: DB7YI DG7DAH GUEST
Subj: TCP-Group Digest 97/23B
Path: DB0AAB<DB0KCP<DB0ULM<DB0LX<DB0RBS<DB0SEL<DB0ZDF<DB0AIS<DB0NDK<DB0ACH<
DB0ACC<DB0SM<PI8DAZ<PI8GCB<PI8HGL<PI8VNW
Sent: 970224/1625Z @:PI8VNW.#ZH2.NLD.EU #:47521 [Hoek v Holland] FBB5.15c
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA29775 ; Mon, 24 Feb 97 16:07:13 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.62/7.1) with SMTP
id AA00001712 ; Mon, 24 Feb 97 16:54:54 MET
Received: from pa2aga-1 by pa2aga with SMTP
id AA00001706 ; Mon, 24 Feb 97 16:49:23 MET
Received: from pa2aga-1 by pa2aga-1 (NET/Mac 2.3.62/7.6) with SMTP
id AA00009189 ; Mon, 24 Feb 97 16:49:17 MET
Date: Mon, 24 Feb 97 16:46:14 MET
Message-Id: <tcp_97_23B>
From: pa2aga
To: tcp_broadcast@pa2aga-1
Subject: TCP-Group Digest 97/23B
X-BBS-Msg-Type: B
We have complete AX.25 there, search/routing etc based on AX.25,
HW drivers... So, no routing is needed, no telnet because we maintain
nodes using AX.25.
I browsed RFC 823 and RFC 1009, as well as some other DOCs. We do not
need most of the functions (they are not needed, or are already
implemented in AX.25 part of the code).
Real question is: Is there some similar work done ? Any DOCs that
cover what actually has to be done ? Any experience on how to do
the job ? PCs can not be used on our mountain-tops, they should do
the job below. What is minimum functionality needed ? (oh yes,
just IP number based frame in - frame out ...). Good pointers ?
Best 73, gl Iztok S52D
====================================================================
For description of S5 packet projects check:
http://www.hamradio.si/hamradio/packet.html
SV sources are available for FTP at ljutcp.hamradio.si,
directory /pub/s5_intro
====================================================================
S52D : s52d@ljutcp.hamradio.si , iztok@mobitel.si, s52d@S50BOX.SVN.EU
------------------------------
Date: Sun, 23 Feb 1997 18:58:30 GMT
From: brian@nothing.ucsd.edu (Brian Kantor)
Subject: Is there a specification for RFC822<->pbbs?
There have been discussions of this in the past: the main question boils
down to "what to do with the routing info?"
If you're willing to gateway everything bidirectionally, you just take
the address and store the routing hints locally, and truncate the address.
E.g.,
wb6cyt @ wb6kdt.#soca.ca.noam
goes into RFC822 as
wb6cyt.wb6kdt@wb6xyz.ampr.org
and you add an entry of
wb6kdt #soca.ca.noam
to your BBS gateway routing table if it wasn't already there.
I happen to like this scheme; it seems more transparent than any others
I've seen suggested.
An alternative that also appeals to me is to transform the BBS into an
MX for the station, e.g.,
wb6cyt @ wb6kdt.#soca.ca.noam
goes into RFC822 as
wb6cyt@wb6kdt.ampr.org
and you add an entry of
wb6kdt #soca.ca.noam
to your BBS gateway routing table if it wasn't already there.
AND you add
wb6kdt IN MX 10 wb6xyz
to the AMPR.ORG nameserver, if there isn't one already there.
This has update delay problems, but is otherwise cleaner.
Perhaps some combination can be used, where you look for the MX record
in the nameserver, and if it isn't there, you do it the first way, and
send off the update to the nameserver. If it is there, you do it the
second way.
- Brian
------------------------------
Date: Mon, 24 Feb 1997 11:39:54 +1100 (EST)
From: Carl Makin <cmakin@nla.gov.au>
Subject: Is there a specification for RFC822<->pbbs?
On Sun, 23 Feb 1997, Brian Kantor wrote:
> There have been discussions of this in the past: the main question boils
> down to "what to do with the routing info?"
> If you're willing to gateway everything bidirectionally, you just take
> the address and store the routing hints locally, and truncate the address.
This would require preloading the routing hints with addresses that will
be sent mail outbound before any mail is sent inbound. I suppose you
could take the white pages database and use that to preload the hints
file.
I was thinking of using;
vk1kcm@vk1kcm.act.aus.oc translates to;
"vk1kcm%vk1kcm.act.aus.oc"@pbbs.vk1kcm.ampr.org
where pbbs.vk1kcm.ampr.org is a virtual domain defined to sendmail with
it's own mailer that does the address conversions and passes them to FBB
(or whatever).
You would point an MX record at your mail host for that domain.
Another possibility (which is very ugly but probably workable) would be to
assume that PBBS addresses are a subdomain of ampr.org. Something like;
vk1kcm@vk1kcm.act.aus.oc.vk1kcm.ampr.org and use that evil wildcard MX
record.
Both are a hack but hey, both are better than translating X.400 addresses!
Carl.
--
Carl Makin (VK1KCM) <http://email.nla.gov.au/~cmakin/>
C.Makin@nla.gov.au 'Work +61 6 262 1576' "Speaking for myself only!"
'If you want to make your spouse pay attention to what you say...
Talk in your sleep!'
------------------------------
Date: Sun, 23 Feb 1997 23:53:13 -0500
From: Jim Durham <durham@w2xo.pgh.pa.us>
Subject: Is there a specification for RFC822<->pbbs?
Carl Makin wrote:
>
> Has anyone worked out a spec yet for converting packet BBS messages into
> RFC822 (or whatever the current spec is)?
>
I've been laboring under the assumption that the
BID is X-bid: and that MID's are X-mid:
This is from the spec developed by a working group consisting of
W0RLI, AA4RE, N0ARY, myself and others to write a spec for PBBS's.
I think it was largely ignored, but I probably have a copy here
somewhere.
I was considering rewriting my bbs code for FreeBSD so that
it would use the RFC-822 format internally, allowing use of
various mail readers to read the bbs mail.
I'm interested in what you turn up..
73
Jim Durham, W2XO
------------------------------
Date: Mon, 24 Feb 1997 00:13:37 -0500
From: Jim Durham <durham@w2xo.pgh.pa.us>
Subject: Is there a specification for RFC822<->pbbs?
Brian Kantor wrote:
>
> There have been discussions of this in the past: the main question boils
> down to "what to do with the routing info?"
>
> If you're willing to gateway everything bidirectionally, you just take
> the address and store the routing hints locally, and truncate the address.
> E.g.,
> wb6cyt @ wb6kdt.#soca.ca.noam
> goes into RFC822 as
> wb6cyt.wb6kdt@wb6xyz.ampr.org
> and you add an entry of
> wb6kdt #soca.ca.noam
> to your BBS gateway routing table if it wasn't already there.
>
What I've been doing here is considering the bbs@routing-hints to be
a domain address. I put calls to my bbs as a sendmail mailer in
the sendmail config file for the ham "domains" of NOAM, SOAM, EU and
so forth. These go in ruleset 0 and override any other useage of these
names as real domain names. The downside is the loss of Namibia, but
that's a non-problem on my local system.
The address is then encapsulated in the usual manner by putting
a "%" in place of the "@" and sending it to my host as a gateway.
This is pretty much SOP for sendmail stuff and no tweeking is necessary
for get it to drop my host name and replace the "%" with "@", then
recognize it as a packet address and dump it off to the bbs.
ie; W1ABC@W1XYZ.CT.USA.NOAM becomes
W1ABC%W1XYZ.CT.USA.NOAM@w2xo.pgh.pa.us .
This is quite transparent in both directions , allowing use of the
"reply" command in most internet mailers. I also alias the call sign
of gateway users to their e-mail addresses, so that the six-character
restriction of PBBS "to" header space can route to an internet address.
------------------------------
End of TCP-Group Digest V97 #23
******************************
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
| |
