Hello AMPRNet,
we like to announce a new open source HAMNET-access solution for the
70-cm-band making use of the popular ADALM Pluto SDR.
Lukas Ostendorf recently finished his master thesis "Design of a Radio
Communications Protocol for HAMNET Access in the 70cm Amateur Radio
Band" at our employer Rohde & Schwarz in Munich.
We are pleased to publish his work and further material today:
https://hnap.de/2020/09/08/master-thesis-released.html
There are still some tasks like signal amplification on the roadmap, but
the community is growing and helping to move on.
It seems the telegram group chat is currently the best place to
exchange: https://t.me/hamnet_access_protocol
Most communication is in German, however I'm pretty sure English is fine
as well. At least you will find nice pictures of current experiments in
the backlog :)
Looking forward to your contribution,
for the HNAP-Team,
Jann
DG8NGN
--
Jann Traschewski, Faber-Castell-Str. 9, D-90522 Oberasbach, Germany
Tel.: +49-911-99946898, Mobile: +49-170-1045937, E-Mail: jann(a)gmx.de
Ham: DG8NGN / DB0VOX / DB0FOX / DB0ZM / DB0DBA / DB0HZS
> Mikrotik is the only one among cheaper gear to have a PIM (only
Sparse mode) implementation. It is a bit clumsy but with a few tweaks it
is (from my experience so far) manageable.
Do you have a description somewhere how you set it up in a 44Net network?
We have a national network over here with many (mostly) MikroTik routers
linked by radio links and VPNs.
It could be an interesting experiment...
Rob
> We also have a network of PBX's tied together here in the US but using
> AREDN Mesh connectivity. Phone numbers are a flat 4-digits for local
> calling. For wide area calls, the person's (or service) 3-digit area
> code is prepended to the 4-digit local number. There are around 40 pbx's
> scattered around the world on this network. There is a White Pages
> directory to determine a person's (or service) phone number.
> It would be interesting to try to connect the two systems together.
Of course it is always tricky to interconnect two systems that have a
different and potentially conflicting numbering plan.
I actually like the numbering plan they use here.
You number is not tied to the PBX you have registered on, but it roams
with you wherever you connect. So when the local situation changes
(someone stops providing the service or some more nearby PBX appears
where you have better connectivity or better services) you can just
port your existing number without problem.
And no directory is required, I can just dial numbers on the keypad
knowing only the callsign. For you it would be 62206142
It would have been even better when they had thought of having some
unique prefix that makes it recognizable as a HAM number and not a POTS
phone number, and that avoids collisions with other numbering plans.
Rob
> Sorry about the glitches at the beginning. Jitsi was giving us problems
> (frozen or long-delayed video, etc) so I made the call to switch to
> Zoom. We regularly use zoom internally within ARDC for Board and Grant
> Advisory Committee meetings and it has performed well; it also seemed to
> work well today.
I am a bit disappointed that, as a group of radio amateurs active in IP networking,
supposedly the people who know all about how to setup a communication system
all by themselves, we have to resort to a system like zoom.us to hold a conference.
Rob
On 10/11/20 14:03, Stuart Longland wrote:
>
> I'd imagine for repeater linking, you'd be wanting sufficient bandwidth
> for RTP streams. Would DMR be capable of this or would we have to look
> to other solutions?
I hadn't even considered DMR (by which I assume you mean C4FM). Waaaay
too slow and inefficient. I was thinking either of WiFi on
point-to-point microwave a la AREDN, or some new medium speed modem on
UHF non-line-of-sight links. NPR could be a candidate, though I don't
know about its multipath tolerance.
> None of that is any use for linking internationally, which is one of the
> draw-card use cases for things like IRLP, EchoLink, AllStarLink, … etc.
> I'd imagine we'd need some sort of high-speed trunk links over HF radio
> for that. Seems like a tall order in solar minimum.
Admittedly I am biased by living in southern California, but I was
thinking about the large linked repeater networks we have here. Some
networks include dozens of mountaintop repeaters spread across several
states linked full time. Traditionally a lot of that linking was done
directly between hilltops on (hidden) analog UHF links, and I'm sure
that today much of it is done over the commercial Internet.
At least until the US gets its own QO-100, the regular Internet is
likely to remain the only practical approach for long haul links, but
it's certainly within the realm of possibility to move many of the
intrastate or adjacent-state links to an IP network on ham frequencies.
Phil
Thanks to everyone who participated in today's online meeting!
Sorry about the glitches at the beginning. Jitsi was giving us problems
(frozen or long-delayed video, etc) so I made the call to switch to
Zoom. We regularly use zoom internally within ARDC for Board and Grant
Advisory Committee meetings and it has performed well; it also seemed to
work well today.
Thanks for all the helpful comments and suggestions on our grantmaking
activities. I invite everyone interested in ARDC and its mission to
further amateur radio and related digital technologies to continue to
make your helpful thoughts and suggestions known and to consider
becoming more involved.
But I want to reiterate: you might think that giving money away is the
easiest thing in the world. It's not! (I keep thinking of the old
Badfinger song, "Come and Get It!") It's surprisingly hard work to do it
legally, effectively and efficiently, and I think those of you on the
call today got a taste of that. Some of it is WAY too much like real
work, like managing our finances and understanding and complying with
the myriad IRS and state rules for nonprofit grant-making foundations
like ours. As we explained, we do NOT want to limit our activities to
the United States, but we have to jump through a lot of extra hoops when
making grants to organizations in other countries. But we are determined
to do this, just as we are determined to eventually give grants to
individuals and groups that aren't formal charities.
The terms of our IP address sale required an NDA (Non-Disclosure
Agreement) that kept many details confidential for a time. We didn't
like it, but there would have been no sale without it. Now that our 2019
tax returns and financial audit statements are a matter of public
record, we won't have to be cagey about our finances.
Except for Rosy, our executive director, and Chris, our 44net support
guy, all of us are doing this as volunteers. Rosy has really hit the
ground running in her new position, working with prospective grantees,
politely reminding the rest of us of our action items and in general
keeping things running smoothly. We do anticipate getting additional
paid help as our work expands.
Our treasurer, Bdale Garbee, NB0G, has done a stellar job of managing
our finances, dealing with the regulatory and tax authorities, lawyers,
auditors, grantees and support organizations. Our endowment, which we
are conservatively managing ourselves, is split between low cost US and
international stock and bond index funds as well as short term reserves.
The reserves cover our expected expenses for the next few years. We hope
the rest will generate enough income to keep us going indefinitely, but
that depends on the markets. Our plan right now is to grant at least US
$5 million every year.
No other amateur radio foundation has ever operated on this scale, and
we're still just getting started. Since we don't know what will pay off,
we want to cast our nets broadly. We can afford to take risks with some
high-risk, high-reward projects knowing full well that some -- maybe
even most -- won't pan out. There's simply no other way to find out what
works.
What makes it all worthwhile is seeing the results of our work. We've
only gotten started, but the new ARISS (Amateur Radio on the
International Space Station) gear that we helped support is installed
and operational. The power supply carries a plaque memorializing our
founder, Brian Kantor WB6CYT, and his family was delighted to see the
pictures. And I've just been going through the thank-you cards and
letters (56 at last count) we've received from this year's recipients of
ARRL Foundation scholarships.
Back to where it all began -- the 44 net -- we invite suggestions on how
it should evolve and expand. We certainly have the money to support a
solid and growing infrastructure.
So...we're just getting started!
73, Phil Karn, KA9Q
ARDC President
Hi folks,
Due to some technical difficulty, we are switching to Zoom this morning:
Please use the information below, and many apologies for the last-minute
switch.
Rosy
//
ARDC is inviting you to a scheduled Zoom meeting.
Join Zoom Meeting
https://us02web.zoom.us/j/3100460055?pwd=RS9SMlFRZTBXbjZCT2c2Y2llY09KQT09
Meeting ID: 310 046 0055
Passcode: 655698
One tap mobile
+12532158782,,3100460055#,,,,,,0#,,655698# US (Tacoma)
+13462487799,,3100460055#,,,,,,0#,,655698# US (Houston)
Dial by your location
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)
+1 301 715 8592 US (Germantown)
+1 312 626 6799 US (Chicago)
+1 929 205 6099 US (New York)
Meeting ID: 310 046 0055
Passcode: 655698
Find your local number: https://us02web.zoom.us/u/ko6SfVytQ
--
Rosy Wolfe
Executive Director
Amateur Radio Digital Communications (ARDC)
ampr.org
2019 financial filings for the ARDC, Inc. have been published by
the Californian Register of Charities:
* http://rct.doj.ca.gov/Verification/Web/Download.aspx?saveas=Amateur+Radio+D…
* http://rct.doj.ca.gov/Verification/Web/Download.aspx?saveas=Amateur+Radio+D…
* https://www.ampr.org/about/legal/ (links)
TL;DR summary:
1. Sale price of $26/IP (to Amazon) minus 0.5% brokage commission [1]
2. $109 million raised, $545 thousand paid to Nationwide as broker
3. Funds now classified as Board-designated Endowment
4. Majority raised now invested in government bonds
Trustees for 2019 are listed as:
Brian Kantor - Former president
Bdale Garbee - Treasurer
Phil Karn - New president
John Gilmore - Secretary
KC Claffy is listed as a non-officer director---possibly for
CAIDA conflict-of-interest handling(?)
Erin Kenneally is no longer listed (nor referenced at all).
(Suspect that a clear answer may not be easier to find).
During Financial Year 2019, two grants were disbursed:
1. $10k - TAPR student scholarships
2. $110k - ARISS (International Space Station HAM)
Variations of the wording use in different places (paraphrased):
* "[support of] Amateur Radio Digital Communications"
* "[support of] Amateur Radio _and_ Digitial Communcations".
The latter is much wider than the former.
Hopefully the trustees can make their own announcement in due
course; but this should pre-answer the quick questions that people
may have, [2]
Before laying into the Trustees, this is pretty positive---cash was
raised, and has been sensibly invested. The way the sale was handled
was sub-optimal---picking the most dense/actively used part (HamNET)
to sell...; but hopefully lessons from that have been learnt.
Plus John Gilmore's long statement this week about the MoU with
CAIDA/UCSD, will hopefully allow Amprnet's most significant R&D/
experimentation/academic contribution over the last 20 years to be
finally be acknowleged openly,
-Paul
[1] To put things into perspective; had estimated was $24/IP, minus 1%
brokage commission---so the amount realised by the Trustees was
significantly higher; probably related to the size of the block sold,
and clean nature of the IPs.
[2] E&OE---refer to the actual documents for exact numbers + wording!
Do not rely on this TL;DR---spend your own time, and do your own
reading!
Hi 44net,
Given how many people have responded to the survey (68!), I want to make
sure that Jitsi can handle the number of people who might show up to our
call on Saturday.
In service of collecting a head count, please let us know if you're
planning to join the call by filling out your name here:
https://www.ampr.org/community-meeting/
Many thanks! If it looks like we're going to exceed the 75 person limit,
we may switch to a Zoom call. In either case, we're planning on
recording the meeting for anyone who can't make it. I'll post
information here if anything changes.
I'm looking forward to e-meeting many of you and am compiling ideas from
your emails and the survey as we speak.
All the best,
Rosy
PS here's the survey link in case you haven't taken it yet:
https://www.mysurveygizmo.com/s3/5789610/ARDC-Grantmaking-Feedback-Survey
--
Rosy Wolfe
Executive Director
Amateur Radio Digital Communications (ARDC)
ampr.org
Just to clarify.
44.168.x.y/16 IS ROUTED via BGP on Internet. But the firewall is blocking
most of the communications from outside the 44 world.
73 Remi F6CNB N5CNB
Message: 1
Date: Wed, 7 Oct 2020 14:51:12 +0200
From: Toussaint OTTAVI <t.ottavi(a)bc-109.com>
To: <44net(a)mailman.ampr.org>
Subject: Re: [44net] Education about networking (Was Re: Inviting you
to ARDC Grantmaking Survey + Community Jitsi Call)
Message-ID: <68fa5d64-3b71-2326-3ab5-1a20b0c61d0d(a)bc-109.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Le 05/10/2020 ? 10:40, Rob Janssen via 44Net a ?crit?:
>
> Please understand that in the topology I am proposing (and have
> proposed several times in the past) you don't need to do that as an
> individual, it is left to local groups or ARDC to do that.
+1
We are using a similar topology here.
Anyway, the details of our implementation differ :
- We are currently testing Wireguard as a replacement for OpenVPN (too much
odd behaviors with OpenVPN)
- Our endpoints are $20-$50 OpenWRT routers. We configure them, and send
them to the local users / sites.
- On any site, we typically route /29 (5 usable IPs) on small sites and
/28 (13 usable IPs) on more important sites
- We typically route a 44.190 subnet for things that requite public Internet
addressing (D-Star, DMR, XLX) (as defined by DG8NGN), and a
44.168 subnet for all ham-related machines.
- Any site can have a 44.190 subnet, a 44.168 subnet, or both.
- There's no more dual adressing. All machines only have a 44.168 or
44.190 IP. Except for the central gateway, no machine / no server is using
public Internet IP anymore.
- Due to the highly experimental nature of the network and the tiny size, we
do not have full internal dynamic routing yet, and we use static routing for
now. Our dynamic experiments on some sites are using OSPF.
- 44.190 subnet is routed on Internet with BGP via a Vultr VPS (which costs
$5/month, is easy to implement, and is independent of local ISP BGP
capabilities)
- 44.168 subnet is currently not routed on Internet via BGP, because this
does not have much sense. For now, it's not routed outside of our island.
But we plan to implement IP-IP routing on the central gateway (as we had in
our previous iteration)
Maybe we should try to identify all people using this kind of topology all
over the world (what I called a "Regional" or "local" gateways) ?
Then, we may try to "normalize" our implementations :
- Adoption of dual-addressing : 44.190 for things that require Internet
access, and 44.<country> for other things
- Choice of internal VPN tunneling protocol(s)
- Choice of internal routing protocol
- Choice of external routing method (tunnels and routing between gateways)
73 de TK1BI
------------------------------
Message: 2
Date: Wed, 7 Oct 2020 15:27:49 +0200
From: Toussaint OTTAVI <t.ottavi(a)bc-109.com>
To: <44net(a)mailman.ampr.org>
Subject: Re: [44net] Inviting you to ARDC Grantmaking Survey +
Community Jitsi Call
Message-ID: <6833ec63-d59d-530b-3ffa-ef2b5585a99f(a)bc-109.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Le 03/10/2020 ? 18:55, Corey Dean via 44Net a ?crit?:
> Part of the BrandMeister network is using some of the 44 range. The
> main bm webpage is using it.
Here are some quick and dirty stats :
XLX is an open-source digital gateway used all over the world to
interconnect D-Star and DMR repeaters (and many other protocols) XLX API
provides a "hosts" file of all registered XLX nodes with their IP This file
has approx. 1700 lines.
Due to triple REF, DCS, XRF naming, we can assume there are roughly 560
independent nodes.
The file contains only 36 entries using AMPR 44.x IP addressing, and among
them, only 12 are unique
*-> Only 2% of the XLX-connected reflectors are using AMPR addresses !!!*
And this is only for reflectors (=servers), who are managed by people with
more than average skills. I didn't find how to obtain stats for all the
repeaters connected to all the reflectors, but adoption rate will be even
lower !
COMMENTS :
- AMPR addressing is used on country-wide servers, and by isolated teams
around the world (including myself, HI)? mostly because people who maintain
servers have the skills and equipment to do that.
- We still have some work until mass adoption by the local reflectors and
repeaters SysOps
- And even more work for mass adoption by any HAM in the world...
CONCLUSION :
As I already said, IMHO, our #1 goal should be : make AMPR addressing easier
to use, both for local SysOps/teams, and for end users.
73 de TK1BI
------------------------------
Message: 3
Date: Wed, 7 Oct 2020 14:01:29 +0000
From: pete M <petem001(a)hotmail.com>
To: AMPRNet working group <44net(a)mailman.ampr.org>
Subject: Re: [44net] Inviting you to ARDC Grantmaking Survey +
Community Jitsi Call
Message-ID:
<MWHPR2201MB14551B41D83E8BD2DF4F56A9970A0(a)MWHPR2201MB1455.namprd22.prod.outl
ook.com>
Content-Type: text/plain; charset="iso-8859-1"
I am 100% with you.
I don't count myself as top sys admin. But I am far from being a noob. And I
have been struggling to have Ipip or other ways of connecting to the net.
I have multiple site connected by VPN to my vps . I run multiple wireless
link with fallback to lte modem. In case of a trouble with the link and
yet, the only way I think I will achieve a stable way to have a connection
and 44 net IP will be by bgp.
That bring that I need a /24 at a minimum. Do I need a /24? Not at first and
I hope I will be able to have other hams in my region to take some of my /24
( will give them with the VPN server) but frankly this also mean the I will
be responsible for there action on the 44 net. And that is putting some
pressure on me.
T?l?chargez Outlook pour Android<https://aka.ms/ghei36>
________________________________
From: 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> on behalf
of Toussaint OTTAVI via 44Net <44net(a)mailman.ampr.org>
Sent: Wednesday, October 7, 2020 9:27:49 AM
To: 44net(a)mailman.ampr.org <44net(a)mailman.ampr.org>
Cc: Toussaint OTTAVI <t.ottavi(a)bc-109.com>
Subject: Re: [44net] Inviting you to ARDC Grantmaking Survey + Community
Jitsi Call
Le 03/10/2020 ? 18:55, Corey Dean via 44Net a ?crit :
> Part of the BrandMeister network is using some of the 44 range. The
> main bm webpage is using it.
Here are some quick and dirty stats :
XLX is an open-source digital gateway used all over the world to
interconnect D-Star and DMR repeaters (and many other protocols) XLX API
provides a "hosts" file of all registered XLX nodes with their IP This file
has approx. 1700 lines.
Due to triple REF, DCS, XRF naming, we can assume there are roughly 560
independent nodes.
The file contains only 36 entries using AMPR 44.x IP addressing, and among
them, only 12 are unique
*-> Only 2% of the XLX-connected reflectors are using AMPR addresses !!!*
And this is only for reflectors (=servers), who are managed by people with
more than average skills. I didn't find how to obtain stats for all the
repeaters connected to all the reflectors, but adoption rate will be even
lower !
COMMENTS :
- AMPR addressing is used on country-wide servers, and by isolated teams
around the world (including myself, HI) mostly because people who maintain
servers have the skills and equipment to do that.
- We still have some work until mass adoption by the local reflectors and
repeaters SysOps
- And even more work for mass adoption by any HAM in the world...
CONCLUSION :
As I already said, IMHO, our #1 goal should be : make AMPR addressing easier
to use, both for local SysOps/teams, and for end users.
73 de TK1BI
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
------------------------------
Message: 4
Date: Wed, 7 Oct 2020 09:54:30 -0700
From: Rosy Wolfe <rosy(a)ampr.org>
To: Amprnet 44 Net <44net(a)mailman.ampr.org>
Subject: [44net] Please let us know if you're coming to Saturday's
call!
Message-ID: <745510ee-aeb4-0cad-7ace-8ec9abe9b0d5(a)ampr.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi 44net,
Given how many people have responded to the survey (68!), I want to make
sure that Jitsi can handle the number of people who might show up to our
call on Saturday.
In service of collecting a head count, please let us know if you're planning
to join the call by filling out your name here:
https://www.ampr.org/community-meeting/
Many thanks! If it looks like we're going to exceed the 75 person limit, we
may switch to a Zoom call. In either case, we're planning on recording the
meeting for anyone who can't make it. I'll post information here if anything
changes.
I'm looking forward to e-meeting many of you and am compiling ideas from
your emails and the survey as we speak.
All the best,
Rosy
PS here's the survey link in case you haven't taken it yet:
https://www.mysurveygizmo.com/s3/5789610/ARDC-Grantmaking-Feedback-Survey
--
Rosy Wolfe
Executive Director
Amateur Radio Digital Communications (ARDC) ampr.org
------------------------------
Message: 5
Date: Wed, 7 Oct 2020 17:01:41 +0000
From: Ruben ON3RVH <on3rvh(a)on3rvh.be>
To: AMPRNet working group <44net(a)mailman.ampr.org>
Subject: Re: [44net] Please let us know if you're coming to Saturday's
call!
Message-ID:
<AM0PR01MB3890CE45891B0A0C5286F569D30A0(a)AM0PR01MB3890.eurprd01.prod.exchange
labs.com>
Content-Type: text/plain; charset="us-ascii"
Rosy,
If I may give a suggestion: have everyone turn off their camera's and things
will go much smoother with Jitsi. Most of the issues come from everyone
sharing their camera and having a smallband internet connection, thus
filling up that pipe with everyone's camera is a bad idea ;)
73
Ruben ON3RVH
-----Original Message-----
From: 44Net <44net-bounces+on3rvh=on3rvh.be(a)mailman.ampr.org> On Behalf Of
Rosy Wolfe via 44Net
Sent: Wednesday, October 7, 2020 18:55
To: Amprnet 44 Net <44net(a)mailman.ampr.org>
Cc: Rosy Wolfe <rosy(a)ampr.org>
Subject: [44net] Please let us know if you're coming to Saturday's call!
Hi 44net,
Given how many people have responded to the survey (68!), I want to make
sure that Jitsi can handle the number of people who might show up to our
call on Saturday.
In service of collecting a head count, please let us know if you're planning
to join the call by filling out your name here:
https://www.ampr.org/community-meeting/
Many thanks! If it looks like we're going to exceed the 75 person limit, we
may switch to a Zoom call. In either case, we're planning on recording the
meeting for anyone who can't make it. I'll post information here if anything
changes.
I'm looking forward to e-meeting many of you and am compiling ideas from
your emails and the survey as we speak.
All the best,
Rosy
PS here's the survey link in case you haven't taken it yet:
https://www.mysurveygizmo.com/s3/5789610/ARDC-Grantmaking-Feedback-Survey
--
Rosy Wolfe
Executive Director
Amateur Radio Digital Communications (ARDC) ampr.org
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
------------------------------
Message: 6
Date: Wed, 7 Oct 2020 10:17:25 -0700
From: Rosy Wolfe <rosy(a)ampr.org>
To: 44net(a)mailman.ampr.org
Subject: Re: [44net] Please let us know if you're coming to Saturday's
call!
Message-ID: <aeffc385-d2ac-781f-b2c5-8bf4c656eeca(a)ampr.org>
Content-Type: text/plain; charset=utf-8; format=flowed
On 10/7/20 10:01 AM, Ruben ON3RVH via 44Net wrote:
> Rosy,
>
> If I may give a suggestion: have everyone turn off their camera's and
things will go much smoother with Jitsi. Most of the issues come from
everyone sharing their camera and having a smallband internet connection,
thus filling up that pipe with everyone's camera is a bad idea ;)
Copy! The suggestion is most welcome. Thank you, Ruben.
Rosy
Rosy Wolfe
Executive Director
Amateur Radio Digital Communications (ARDC)
ampr.org
>
> -----Original Message-----
> From: 44Net <44net-bounces+on3rvh=on3rvh.be(a)mailman.ampr.org> On Behalf Of
Rosy Wolfe via 44Net
> Sent: Wednesday, October 7, 2020 18:55
> To: Amprnet 44 Net <44net(a)mailman.ampr.org>
> Cc: Rosy Wolfe <rosy(a)ampr.org>
> Subject: [44net] Please let us know if you're coming to Saturday's call!
>
> Hi 44net,
>
> Given how many people have responded to the survey (68!), I want to make
sure that Jitsi can handle the number of people who might show up to our
call on Saturday.
>
> In service of collecting a head count, please let us know if you're
planning to join the call by filling out your name here:
>
> https://www.ampr.org/community-meeting/
>
> Many thanks! If it looks like we're going to exceed the 75 person limit,
we may switch to a Zoom call. In either case, we're planning on recording
the meeting for anyone who can't make it. I'll post information here if
anything changes.
>
> I'm looking forward to e-meeting many of you and am compiling ideas from
your emails and the survey as we speak.
>
> All the best,
> Rosy
>
> PS here's the survey link in case you haven't taken it yet:
> https://www.mysurveygizmo.com/s3/5789610/ARDC-Grantmaking-Feedback-Survey
>
> --
> Rosy Wolfe
> Executive Director
> Amateur Radio Digital Communications (ARDC) ampr.org
_________________________________________
> 44Net mailing list
> 44Net(a)mailman.ampr.org
> https://mailman.ampr.org/mailman/listinfo/44net
>
> _________________________________________
> 44Net mailing list
> 44Net(a)mailman.ampr.org
> https://mailman.ampr.org/mailman/listinfo/44net
>
------------------------------
Subject: Digest Footer
_______________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
------------------------------
End of 44Net Digest, Vol 9, Issue 97
************************************