3 Apr
2014
3 Apr
'14
5:31 a.m.
On Wed, Apr 2, 2014 at 1:35 PM, Paula <g8pzt(a)blueyonder.co.uk> wrote:
(Please trim inclusions from previous messages)
It was my belief that amprnet is/was synonymous with 44-net, and was
originally all about building a internet-like network over RADIO, long
before everyone had access to broadband etc. I was there, back in the
1980's, but obviously time must have fogged my memory. Or maybe the focus
of amprnet has changed over time.
I don't think it's always been about radio on 44-net. Considering KA9Q
was
installed on many DOS machines to access telnet/ftp/gopher services I think
it was more about reserving space so that hams could start that "internet
of things" before it became today's popular buzzword. When the space was
reserved, most of the networks connected were corporate, educational and
governmental entities (speaking back to post ARPAnet but pre commercial
internet - the NSFNet). It wasn't until the 90's when commercial demand
picked up for the Internet and dotcom's later here we are today.
But we still have this legacy space.
I think people should look at this space as a network first and
medium/content/errata second. What's the point of interconnection to the
larger world if you don't use it? One might as well use more radio
efficient protocols then like AX25/Node or FlDigi Multicast due to speed
limitations.
I don't care one way or the other. I have no axe
to grind; all I wanted
was clarification on how to set my system up.
First place to start is portal.ampr.org to request IP space from your
coordinator. The rest is some routing/encapsulation trickery.