On Tue, 18 Jan 2000, James S. Kaplan KG7FU wrote:
> Perhaps I wasn't clear.... Does there exist a "how-to", examples or
> explicit instructions on how to use sendmail for radio amprnet, radio pbbs,
> local delivery and internet delivery ALL on the same box?
Rulesets for radio pbbs do exist, or at least I've seen some people try to
develop them. The radio pbbs addressing scheme never has mapped well
with what the rest of the world uses. I think most of those handling radio
pbbs mail do so using dedicated bbs software that understands the
addressing. Many of us just simply don't bother handling anything but standard
SMTP mail.
...
>
> > I personally think you'd be better off fixing the actual problem though
> > (the DNS problem or whatever it actually is) than naiively working
> > around it with manual name->address mappings.
>
> Ok, I'll bite. How do I fix it? One problem is my isp's DNS has an entry:
>
> Server: ns1.rio.com
> Address: 206.96.130.10
>
> Non-authoritative answer:
> 0.1.26.44.in-addr.arpa name = crv.lan.ampr.org
>
> Authoritative answers can be found from:
> 44.IN-ADDR.ARPA nameserver = hamradio.ucsd.edu
This is correct. The amprnet DNS at hamradio.ucsd.edu has 44.26.1.0
assigned to crv.lan.ampr.org.
>
> etc.....
>
> But a traceroute from rio.com reveals no route to host, thusly:
> traceroute to 44.26.1.0 (44.26.1.0), 30 hops max, 40 byte packets
> 1 gatekeeper (206.96.130.254) 1 ms 1 ms 1 ms
> <snip>
> 10 sdsc-gw.san-bb1.cerf.net (134.24.12.26) 406 ms 380 ms 439 ms
> 11 192.12.207.5 (192.12.207.5) 406 ms 471 ms 439 ms
> 12 muir-rs-backbone.ucsd.edu (132.239.254.11) 469 ms 386 ms 386 ms
> 13 ampr.org (44.0.0.1) 381 ms * 465 ms
> 14 * * *
Yup, that's correct also.
> Correct me if I'm wrong, but aren't address groups such as 192.168 and 44.0
> considered "private" nets and technically aren't supposed to be routed via
No, net 44 is assigned to amateur radio and if we provide an internet connected
router the rest of the internet quite happily routes all 44.x.x.x traffic to it.
We have such a router, it's called 'mirrorshades' aka 'ampr.org' and it
accepts all net 44 traffic from the rest of the internet. It in turn will use
IPIP encapsulation to forward IP packets to the various ampr.org
gateways scattered around the world.
There is no current gateway handling 44.26.1.x so all packets from the
internet deadend at mirrorshades. Exactly what your traceroute shows.
> internet? Even if they were, the ampr.org docs clearly state that 44.26.1.0 is
> for "testing" and is not to be assigned. AND, why does the rest of the world
Where does it say this, I find 44.26.1.0 assigned to crv.lan.ampr.org according
to the DNS files at hamradio.ampr.org.
> know to route 44.26.1.0 to ucsd.edu/ampr.org, yet ampr.org doesn't have it?
As I said above, Everything for 44.x.x.x goes to ampr.org at ucsd, but since
there is no gateway handling traffic for 44.26.1.x it has no place to go after
that.
> My local net just happens to be 44.26.1....see what the problem is now?
Exactly what addresses do you have? I don't find your callsign in the list of
assigned addresses at hamradio.ucsd.edu. There are a number of reasons
why that might be, but knowing your addresses will help figure things out.
> > Like I've been saying, I'm neither a programmer nor a seasoned net
> professional. As such, I need a bit more "1-2-3..." guidance than some
> of you. I'm sure by the posts I see here that there are many more "Linux
> Newbies", new hams, hams new to packet and just plain old dumb hams like myself
> that would be more inclined to get heavily into ax.25 networking, instead of
> turned off, if it weren't for the lack of simplistic docs and negative
> responses from a few vocal, but harsh, hams-in-the-know.
>
I admit the docs could be better, but, the issues are complex and it isn't easy
coming up with cookbook type answers that cover all the permutations.
It's much easier coming up with answers to specific circumstances.
As far as negative and harsh responses go, not all of us are that way so it's
best to just ignore them and wait for the good responses to pop out of the
woodwork.
Now, what else can I help you with.
Ken, N7IPB
--
Motorola Email: [EMAIL PROTECTED]
Seattle Cellular Design Center Office: (425) 487-8854
24000 35th Ave SE, Suite 100 Cell : (206) 499-4872
Bothell, WA 98021 Fax : (425) 483-3400
