Another suggestion I'll make is that beyond support Dynamic DNS for
various use cases, to allow end users to manipulate thier own forward
and reverse DNS records and tie that functionality in with dynamic DNS.
--
Kris Kirby, KE4AHR
Disinformation Architect, Systems Mangler, & Network Mismanager
Hi all, I’d like the ARDC to investigate and possibly revoke the assignment for 44.144.50.0/25 due its use for commercial purposes.
I’m a long time member of the group here but I’m also heavily involved in the Helium radio-based blockchain. I’ve noticed three Helium “hotspots” or “miners” that are using this allocation. While I am personally a fan of Helium, I don’t think its use is permissible on the AMPRNet as Helium hotspots do earn monetary compensation for being connected to the Internet. As a responsible AMPR block recipient myself, I feel it’s important that we continue to honor the ARDC’s rules for the AMPR space, and this is one of them.
The hotspots in question are:
* zany-pecan-kitten at 44.144.50.71 (https://explorer.helium.com/hotspots/112en278X7KpSMfgH9JMnEfkfLSsi2osRjJ1mL…)
* petite-flint-bird at 44.144.50.73 (https://explorer.helium.com/hotspots/11bkMgWVDYSteuq1fLvowC9z4BVReQrXNGCq4F…)
* furry-pine-raccoon at 44.144.50.74 (https://explorer.helium.com/hotspots/112TRAzGUMNvEYEtHawWymZTA4cX9BWu9QFw1v…)
Sincerely,
Jeremy Cooper (KE6JJJ)
> A reply by the ARDC IT director specifically requesting that abuse reports be sent to abuse at ardc.net <https://mailman.ampr.org/mailman/listinfo/44net> <mailto:abuse at ardc.net <https://mailman.ampr.org/mailman/listinfo/44net>> and you decide to double down and list more potentially offending addresses publicly?
>
> Interesting approach.
>
> Ian VE7BST
Ian, I thought I was in a private conversation with Chris when I had replied. It wasn’t until I had already sent the message that I saw that the entire list was still CC’d. My apologies, but also a modicum of understanding is also deserved, too.
Hi, 44net!
Writing with a few updates that may interest you.
First, I’d like to introduce you to our Administrative Coordinator,
Merideth Stroh – KK7BKI. She comes from a family of hams and is helping
us with everything administrative. Please join me in welcoming her to
the team!
In advance of our upcoming board retreat in early December, Meredith and
I will be interviewing folks one-on-one about the future of amateur
radio and digital communications. If you would like to take part in one
of these interviews, you can sign up here:
https://calendly.com/ardc-rosy/30min
If you want to participate but can’t find a time listed, please reach
out and we’ll do our best to find a time that works. Note that we have
some times available in early December, but if you want your thoughts
brought to the board, please find a time by Dec. 2.
If so moved, you are also invited to apply to join either our Technical
or Grants Advisory Committees (GAC & TAC). Note that, for 2022, the role
of the TAC is going to change a little bit. In addition to focusing on
PoP development, we may also call upon TAC members to help evaluate
particularly technical in-progress grants. Learn more on our blog here:
https://www.ampr.org/now-accepting-applications-for-grants-advisory-committ…
Speaking of PoPs, we’ve been working on a plan to develop PoPs for the
address space, which incorporates a lot of the feedback and thoughts
we’ve heard on this list and through private mails from some of you.
When it’s in a better place to share (it’s so close!) I’ll do so. Thanks
for your patience on this – we’ve taken in a lot of info and are working
with volunteers to review, so it’s not a fast process, but it’s a
thorough one.
Last but not least, some of you have asked to see our 2020 tax return
(IRS Form 990-PF). You can see all our public financial documents here:
https://www.ampr.org/about/legal/
Specific links for the 2020 documents are:
* Audited financial statements:
https://www.ampr.org/wp-content/uploads/Amateur-Radio-Digital-Communication…
* 990-PF:
https://www.ampr.org/wp-content/uploads/Amateur-Radio-Digital-Communication…
Thank you for your patience here as well. As Bdale shared in an earlier
mail, with the extra time allotted for filing tax returns, many
accountants have been running behind this year, including ours. Here’s
hoping that we get this filed earlier next year.
As always, please don’t hesitate to reach out with any thoughts and
questions.
73,
Rosy
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ampr.org
Hi
Does AMPRnet have any policy around allocating /24s to individual hams for
the purpose of experimenting with BGP/etc?
My local coordinator says this used to be a "yes, but you'd have to be a
club not an individual." However I note looking through AMPR allocations
there are some in e.g. 44.31 listed as educational/tinkering BGP. Which is
what I want to do. Should I be requesting in 44.31 instead of my country's
allocation?
Regards
Donald Gordon (ZL2IP)
I have been trying to configure the AMPRtunnel for a while without success. Could someone please point me to the right direction.
I am running Debian 11 with public IP. I have configured the public IP in the AMPR portal as gateway.
I am trying to follow this document https://wiki.ampr.org/wiki/Ubuntu_Linux_Gateway_Example
When I try to run find_password.sh in ampr-ripd-2.4, I am stopped at Waiting for RIPv2 broadcasts... and never retrieve a password.
Here is what I have done so far.
in /etc/network/interfaces, I added
auto ens3:1
iface ens3:1 inet static
address 44.26.0.168
netmask 255.255.255.248
Then I created ipip tunnel using following commands
ip tunnel add ampr0 mode ipip local 209.141.42.9 ttl 255
ip link set dev ampr0 up
ifconfig ampr0 multicast
ip rule add to 44.0.0.0/8 table 44 priority 44
ip rule add from 44.26.0.168/29 table 44 priority 45
ip route add default dev ampr0 via 169.228.34.84 onlink table 44
ip route add 44.26.0.168/29 dev ens3 table 44
Then, I run ampr-ripd -d -v -i ens3 to get the password in order to plug into lat command
ampr-ripd -s -i ampr0 -a 209.141.42.9-t 44 -p <SecretPassword>
However, the find_password.sh stopped at waiting for ripv2 broadcast. Here is the logs for command
Using metric 0 for routes.
Using TCP window 840 for routes.
Using gateway 209.141.42.1 for direct 44net endpoints via interface ens3.
Waiting for RIPv2 broadcasts...
Any idea on what am I doing wrong?
Thanks
Kun
Hi,
As I have heard, it is not allowed for ARDC to create route objects in
ARIN's IRR and for that reason, RADb is used.
I am just curious why this is the case?
(It seems in general, creating IRR objects is possible via IRR-online [1])
Best,
Nick
[1] https://www.arin.net/resources/manage/irr/userguide/