Subj : Re: Packet Radio
To   : dejavu
From : Vk3jed
Date : Fri Jun 19 2020 12:07:00

-=> On 06-17-20 08:12, dejavu wrote to Vk3jed <=-

 de> Cool. I've experimented with BPQ, not sure if it's the same as LinBPQ
 de> and it worked for me, however I don't recall why I stopped using it.
 de> I'm going to circle back to it this week and check it out again and try
 de> to remember what the trouble was that I encountered.

LinBPQ and BPQ32 (the WIndows version) are descendents of BPQ.  They are
compatible and offer the same services, though LinBPQ and BPQ32 can do more,
because of the better features of their host OS (Linux/Windows), compared to
DOS.

 de> I've seen the 44.x address space, however I have no experience with it.
 de> Can you explain the purpose of the 44.x address space at a high level
 de> and share a use case or two for it?

It's a block of addresses set aside for ham radio use.  The use cases have
changed slightly since it first came about.  Initially, it was a place where
ham stations could experiment with IP, using software such as KA9Q NOS, which
was quite an advanced package that ran on top of DOS.  KA9Q could also run on
top of BPQ (which ran as a TSR on DOS), which is how my old setup worked, back
in 1991.

The 44.x address space could be used as a "virtual network" running on top of
the Internet and sites could be linked using tunnels or other technologies,
which is done to this day.

Today, 44.x address space has more used.  In addition to providing IP
connectivity to packet stations, the address space also facilitates:

IP connectivity for ham mesh and other high speed networks.  These networks
look more like wifi than traditional packet radio, and IP is a natural fit. 
These networks can also support IPv6, if desired.

Internet services for amateurs.  With the IPv4 shortage around the world,
getting a large number of IP addresses can be difficult.  But for us hams, no
problem.  If we can find a provider that will route a /24 (or larger) via BGP,
we can get a block of addresses allocated and have our provider route them to
where we want.  For example, I have a VPS that runs an IRLP reflector, D-STAR
reflector and a bunch of public Echolink proxies (like around 150).  I have a
/24 routed to it via BGP, and this was done for 2 reasons:

1.  I could only get a /28 using normal IP space, and I have to justofy that
(easy, since I was using them all and starting to run short at the time).

2.  As my provider switched uplinks, I had to renumber every few years, which
is a tedious and error prone process, complicated by needing coordination
between the admins of some of the services I carry (especially IRLP and
D-STAR).  Now using address space allocated to me, rather than my provider
minimises the risk of this happening.  And for ham services, the price is
right. :)

 de> In my experience with "Packet", "Pactor modes" or "APRS" I haven't seen
 de> an actual use case for the 44.x address space.

Packet can use it, but doesn't need it.  The other modes you presented it,
don't use IP (other than APRS-IS, which is the Internet service that carries
APRS data).
 Vk>
 Vk> Cool.  Well, here in FSX_HAM, this can be discussed across 2 networks!
 Vk> It is linked to VK_HAMNET on VKRadio. :)
 Vk>

 de> Cool!

Yeah, it is.  I have to move the gateway to a DOS based system running in a VM,
but it is working. :)



.... X-Files? No... They're downstairs. We're the Y-Files.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

.