- 44net - mailman.ardc.net

Maintenance complete
by schuyler＠ardc.net 29 May '26

29 May '26

Hello all, Our maintenance of the 44Net mailing list server is complete. There's a lot more activity these days on ARDC's groups.io server, so we encourage you to check if out, if you haven't already: https://ardc.groups.io/g/main Thanks! 73 DE N0GIS

1 0

Upcoming mailing list server maintenance - Fri 29 May 2026
by Schuyler Erle N0GIS 27 May '26

27 May '26

Hello all, ARDC will be performing maintenance on the 44Net mailing list server this coming Friday 29 May starting around 0900 PT (GMT-7). The practical impact should be nil, but list messages may be a little slow to deliver that day. We will send another notification when maintenance is complete. Thank you! -- Schuyler Erle N0GIS (he/him) Director of Technology Amateur Radio Digital Communications https://ardc.net/

1 0

Two Contract Positions are Open at ARDC
by Rebecca Key 15 Apr '26

15 Apr '26

Hey Everyone, Our two part-time contract positions are still open: - Software Developer: https://www.ardc.net/ardc-is-hiring-software-developer/ - Technical Writer: https://www.ardc.net/ardc-is-hiring-technical-writer/ If you're interested in applying or just want to learn more, be sure to check out the links above. As always, please don't hesitate to reach out if you have any questions! 73, Rebecca KO4KVG -- Rebecca Key - KO4KVG Communications Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Is anyone handling tickets anymore
by Christopher Munz-Michielin 13 Feb '26

13 Feb '26

Hello all, Wondering if anyone has had success in getting a ticket resolved by ARDC recently? I support two different amateur radio organizations, both of which have had tickets open with ARDC since before Christmas with no response. Is anyone working tickets anymore? 73, Chris

3 3

APRS Web Server help
by vk1kw＠netspace.net.au 31 Jan '26

31 Jan '26

Hello All, I am having problems with the APRS WEB server port 14501 JNOS 2 Version Q as it crashes JNOS when APRS page tab is accessed. The page works fine on JNOS 2.0 Version M but something in my autoexec.bat APRS section in Q is not right. There are no APRS stations appearing in the log and I suspect there may be a problem there however I have not had any success finding any recordings. At one stage I saw the web page top section but no other ports displayed. If you have a successful 14501 APRS web page running I would love to see your APRS autoexec.bat section please? Many, many thanks in advance, Rob VK1KW http://vk1kw.dyndns.org

1 0

2FA Locked me out
by Peter Mallett 04 Jan '26

04 Jan '26

Hi All, Happy new year to one and all, hope it goes well this year. Ok, I have 2FA on my login to the portal and I can not get in, appears the cellphone side of things no longer works. A long while back, my address 44.147.210.24/29 had a /24 attached to it and I have not been able to get this fixed but as it has not caused me a problem up to now, I have not worried too much about it. I have sent a couple of emails but nothing has come back to me yet, maybe a time difference thing but I would like to get my addressing sorted back to what it used to be, that of 8 addresses to which the main one I use is 44.147.210.26 being ZL2BAU-3 for my node here, starting at 44.147.210.24 to 44.147.210.31 Anyway, I wonder if there are any suggestions for me ?????? Regards ...... Peter ZL2BAU

1 0

LetsEncrypt SSL certificates for HTTPS within the 44net
by Mark Phillips 30 Oct '25

30 Oct '25

Hi Folks, I'm having some trouble trying to get LetsEncrypt SSL certificates authorised for use on my WWW devices. The issue seems to be that I do not have control of the TLD and so I can never authorise the issuing of the certificate. I've tried *.ni2o.ampr.org (generic catch all), fqdn.ni2o.ampr.org (device specific) and many other variations but they all fail at the authorizing of the cert. What am I doing wrong? I'm using LetEncrypt (free not-for-profit) SSL certificates successfully in other areas but i do control the domain for those. Thanks for your help Mark / G7LTT

4 6

Re: [ardc] ARDC is Recruiting Volunteers for our 2026 Committees
by Charles J. Hargrove 17 Sep '25

17 Sep '25

Shouldn't a volunteer for an amateur radio related organization actually have an amateur radio license _before_ volunteering? Otherwise the group gets diluted by those who don't know what being an amateur radio license holder and active participant is all about. "An amateur radio license OR a technical degree OR experience in digital communications is required to serve in any volunteer role." On 9/16/2025 3:23 PM, Rebecca Key via groups.io wrote: > Hey Everyone, > *We’re now accepting applications for our 2026 volunteer cohort, which > includes some new roles. Check out our latest blog post for more > details: https://www.ardc.net/join-ardcs-2026-volunteer-team/ <https:// > www.ardc.net/join-ardcs-2026-volunteer-team/>.* > *As always, if you have any questions, please don't hesitate to reach out!* > *73,* > *Rebecca KO4KVG* -- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM http://www.nyc-arecs.org NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32 "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan

7 10

ARDC is Celebrating 44 Years of 44Net
by Rebecca Key 05 Sep '25

05 Sep '25

Hey Everyone, This month marks the 44th anniversary of 44Net! We're celebrating this milestone by sharing stories and facts about our history. If you have something you want to share, let us know at comms(a)ardc.net or you can drop them here in the thread. Also, be sure to follow our social media pages to keep up with our series of 44Net facts: * Twitter/X: https://x.com/ARDC_73 * Facebook: https://www.facebook.com/ardc.73/ * LinkedIn: https://www.linkedin.com/company/amateur-radio-digital-communications/ Stay tuned and 73, Rebecca KO4KVG -- Rebecca Key - KO4KVG Communications Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Ping Test
by Harold Kinchelow 05 Sep '25

05 Sep '25

Hello everyone... New thread. Just wondering if I could get a couple of ping and traceroute test to 44.63.63.193 and 194. I can reach a few address's I found, even from a host on my ampr LAN but need to know if anyone can reach me. I am using OpenWRT and do believe I have firewall rules setup properly to allow for ping. Thanks anyone and everyone Kilo (Harold) https://www.qrz.com/db/K7ILO DMR Repeater 446.275 MHz, -5 MHz Amateur Radio Digital Network Sysop for: 3104.adn.systems<http://3104.adn.systems> (Dallas, TX.) 3105.adn.systems<http://3105.adn.systems> (Los Angeles, CA.)

4 3

My Own encap info
by k7ilo＠outlook.com 01 Sep '25

01 Sep '25

Hey all. Am I supposed to see my own gateway in the latest encap.txt file that was just downloaded to my machine? I know its probably mentioned somewhere but I think I ran out of search words to try. Thanks Harold K7ILO

2 1

Re: Gateway on WAX202
by lleachii＠aol.com 30 Aug '25

30 Aug '25

With citation, of course.If it needs any updates, let me know.73,LynwoodKB3VWG -------- Original message --------From: John Burwell via 44net <44net(a)mailman.ampr.org> Date: 8/30/25 14:30 (GMT-05:00) To: k7ilo(a)outlook.com Cc: 44net(a)mailman.ampr.org Subject: [44net] Re: Gateway on WAX202 Nobody would fault you for adding those notes to the wiki, now that you’ve found them :)--John Burwell - KI5QKX44Net Program ManagerAmateur Radio Digital Communications (ARDC)ardc.net> On Aug 30, 2025, at 12:55, Harold via 44net <44net(a)mailman.ampr.org> wrote:> > Never mind everyone.> > I actually found my notes which were actually copied from Lynwood KB3VWG here.> Persistence pays LOL> > Thanks everyone> > Kilo (Harold)> K7ILO> _______________________________________________> 44net mailing list -- 44net(a)mailman.ampr.org> To unsubscribe send an email to 44net-leave@mailman.ampr.org_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org

1 0

Gateway on WAX202
by Harold Kinchelow 30 Aug '25

30 Aug '25

Hey all Does anyone know if the gateway install instructions (cant remember the call that wrote it) on a Netgear WAX202 is still available somewhere? It was located on the old wiki a few years ago and it seems a lot did not make it to its new location. It included a tad more info on getting a gateway running on this hardware with Openwrt. Thanks everyone Kilo (Harold) https://www.qrz.com/db/K7ILO DMR Repeater 446.275 MHz, -5 MHz Amateur Radio Digital Network Sysop for: 3104.adn.systems<http://3104.adn.systems> (Dallas, TX.) 3105.adn.systems<http://3105.adn.systems> (Los Angeles, CA.)

3 2

Gateway on WAX202
by Harold Kinchelow 30 Aug '25

30 Aug '25

Hey all Does anyone know if the gateway install instructions (cant remember the call that wrote it) on a Netgear WAX202 is still available somewhere? It was located on the old wiki a few years ago and it seems a lot did not make it to its new location. It included a tad more info on getting a gateway running on this hardware with Openwrt. Thanks everyone [cid:95b786a7-4623-4483-8638-f3080610b503] Kilo (Harold) https://www.qrz.com/db/K7ILO [cid:8f806e7c-7918-444a-a6ff-fa88869d3894] DMR Repeater 446.275 MHz, -5 MHz Amateur Radio Digital Network Sysop for: 3104.adn.systems<http://3104.adn.systems> (Dallas, TX.) 3105.adn.systems<http://3105.adn.systems> (Los Angeles, CA.)

1 0

Fedora 42 make JNOS2 version O problem
by vk1kw＠netspace.net.au 16 Aug '25

16 Aug '25

Help please? I am trying to compile the latest version of Langelaar JNOS2.0 version O on Fedora 42 platform however when I go to "make" I get multiple warnings "old-style function definitions"! And it does not compile. Possibly the Fedora MAKE has changed and it does not recognize the config.h although the ./configure seems to work ok. So is there a fix without loading up an old Fedora system? Is there a fix in the makefile code? Have you been able to compile it using fedora and if so, may I have a copy of your jnos.exe file please-(last resort) Many thanks Rob VK1KW

4 3

Elmer Help on final setup of my vpn
by mike＠idahoquad.com 08 Apr '25

08 Apr '25

Guys I need help setting up my vpn to UCSD. PERHAPS a local Elmer near Idaho. I have all the parts to this setup except the VPN. Help would be appreciated 73 Mike K7MDI

1 0

Elmer Help on final setup of my vpn
by mike＠idahoquad.com 08 Apr '25

08 Apr '25

Guys I need help setting up my vpn to UCSD. PERHAPS a local Elmer near Idaho. I have all the parts to this setup except the VPN. Help would be appreciated 73 Mike K7MDI

1 0

Re: [ARDC:net-44-vpn] Uncomplicated Firewall for AMPR installs
by Mark Phillips 27 Mar '25

27 Mar '25

Well, it took only 4 hours after I posted my previous message for my document to be striped and placed on hamradio.my. Clearly the op did not read my notice about hosting it on their server or felt that as he was in Malaysia my views did not count - wrong!!! That's now dealt with and has been taken down. The latest and only authorized source of my documents can be found at http://ni2o.ampr.org/documents/ If you are hosting a copy of any of my documents please remove them. Instead, you may link back to my document archive. This request applies to ALL platforms. I am sorry if this seems to be draconian but I am done with being plagiarized by those that think "it's just a ham document". Over the years my work has appeared in numerous publications including QST entirely without my permission - spelling errors and all!!! This has ultimately lead to me enforcing my copyright. Mark /NI2O On Tue, Mar 25, 2025, 23:32 Mark Phillips via groups.io <enicomms= gmail.com(a)groups.io> wrote: > I wrote another doc. This time it is on the Uncomplicated Firewall package > that comes shipped as default in all Debian based Linux distro's including > Ubuntu, Raspian and Debian itself. > > It is NOT meant to be a full "UFW Operators Guide" but simply a few > pointers to get your systems secured and keep out the great unwashed. > > I do not grant permission to anyone other than ARDC to "host" this or > any of my documents on their system, website or document archive. From time > to time this document may be updated by me and posted where relevant. My > work should NOT be considered "public domain". > > See attached. > > Mark / NI2O > _._,_._,_ > ------------------------------ > Groups.io Links: > > You receive all messages sent to this group. > > View/Reply Online (#359) <https://ardc.groups.io/g/net-44-vpn/message/359> > | Reply to Group > <net-44-vpn@ardc.groups.io?subject=Re:%20%5BARDC%3Anet-44-vpn%5D%20Uncomplicated%20Firewall%20for%20AMPR%20installs> > | Reply to Sender > <enicomms@gmail.com?subject=Private:%20Re:%20%5BARDC%3Anet-44-vpn%5D%20Uncomplicated%20Firewall%20for%20AMPR%20installs> > | Mute This Topic <https://groups.io/mt/111911375/237834> | New Topic > <https://ardc.groups.io/g/net-44-vpn/post> > Your Subscription <https://ardc.groups.io/g/net-44-vpn/editsub/237834> | Contact > Group Owner <net-44-vpn+owner(a)ardc.groups.io> | Unsubscribe > <https://ardc.groups.io/g/net-44-vpn/leave/11245824/237834/2124973700/xyzzy> > [enicomms(a)gmail.com] > _._,_._,_ >

2 1

Help in changing IP addresses from portal.ampr.org
by hf1l＠wp.pl 26 Mar '25

26 Mar '25

I have a problem, I have changed IP addresses by my internet supplier. I had the address 62.69.192.233 And now I have speech: 78.9.233.153 I wanted to change entries for my various domains e.g. www.sr1bsz.ampr.org, mail.hf1l.ampor.org or others. Can anyone help me with this, writes emails on the website.ampr.org with a request for help and I have no answer? I provide login and password to the portal.ampr.org I am asking for help. I am 77 years old after the last heart attack and implantation of the cardioverter in 2017 and 14 days in a coma, I have a lot of information from my memory. I am asking for help

2 1

Uncomplicated Firewall for AMPR installs
by Mark Phillips 26 Mar '25

26 Mar '25

I wrote another doc. This time it is on the Uncomplicated Firewall package that comes shipped as default in all Debian based Linux distro's including Ubuntu, Raspian and Debian itself. It is NOT meant to be a full "UFW Operators Guide" but simply a few pointers to get your systems secured and keep out the great unwashed. I do not grant permission to anyone other than ARDC to "host" this or any of my documents on their system, website or document archive. From time to time this document may be updated by me and posted where relevant. My work should NOT be considered "public domain". See attached. Mark / NI2O

2 1

HRWB 229 - All About 44Net and the ARDC
by Rebecca Key 13 Feb '25

13 Feb '25

Hey Everyone, If you haven't already, check out /HRWB 219 - All About 44Net and the ARDC/, where John Burwell KI5QKX, Rosy Schechter KJ7RYV, and myself were the guests: we had a great time, and 2.5h went by fast! You can give the podcast a listen here: https://www.hamradioworkbench.com/podcast/hrwb-229-all-about-44-net-and-the…. 73, Rebecca KO4KVG -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

ampr-ripd
by Jean VE2PKT 07 Feb '25

07 Feb '25

Hi, Anyone here using ampr-ripd willing to give me some advise? I have mine running and (Finally) learning router, but cannot connect to any stations. I suspect a route problem. 73 de Jean VA2OM / VE2PKT

5 6

IPIP Packet Corruption
by Eric Johnson 13 Jan '25

13 Jan '25

All, I was trying to bring up an AMPRNet IPIP tunnel in my lab network, but when I did a packet capture on the WAN side of the gateway I am setting up, I noticed that on average, about 80% of the IPIP packets I receive from the UCSD gateway have their inner headers corrupted. As far as I can tell, the first 4 bytes of the inner header are being overwritten with a garbage byte sequence (hex 00-04-00-00). I have included a packet capture showing what's going on. At packet 63, the RIP announcement starts, and continues through packet 100, so there's some known-good traffic in there. Has anyone seen anything like this before? I have another AMPRNet IPIP tunnel set up on a datacenter server, and it has no such problem, so this is an isolated issue (i.e., not an issue with the UCSD gateway). The only other thing I could suspect is that the ISP-issued modem/gateway combo unit. Of course, I have no visibility into traffic upstream of this unit, so I don't have a way to know if it is causing the corruption. Unfortunately, my ISP doesn't let me disable the gateway function of the unit, so I have to suspect the firmware of this device. Any and all help is appreciated. I am going to call my ISP tomorrow and see if they are aware of any issues with these modem/gateway units. Thanks, Eric Johnson - AE0JE

4 5

Re: [ARDC:44Net] IPIP Packet Corruption
by Eric Johnson 13 Jan '25

13 Jan '25

Forgot the attachment. On Sun, Jan 12, 2025 at 10:57 PM Eric Johnson via groups.io <micromashor= gmail.com(a)groups.io> wrote: > All, > > I was trying to bring up an AMPRNet IPIP tunnel in my lab network, but > when I did a packet capture on the WAN side of the gateway I am setting up, > I noticed that on average, about 80% of the IPIP packets I receive from the > UCSD gateway have their inner headers corrupted. As far as I can tell, the > first 4 bytes of the inner header are being overwritten with a garbage byte > sequence (hex 00-04-00-00). I have included a packet capture showing what's > going on. At packet 63, the RIP announcement starts, and continues through > packet 100, so there's some known-good traffic in there. > > Has anyone seen anything like this before? > > I have another AMPRNet IPIP tunnel set up on a datacenter server, and it > has no such problem, so this is an isolated issue (i.e., not an issue with > the UCSD gateway). The only other thing I could suspect is that the > ISP-issued modem/gateway combo unit. Of course, I have no visibility into > traffic upstream of this unit, so I don't have a way to know if it is > causing the corruption. Unfortunately, my ISP doesn't let me disable the > gateway function of the unit, so I have to suspect the firmware of this > device. > > Any and all help is appreciated. I am going to call my ISP tomorrow and > see if they are aware of any issues with these modem/gateway units. > > Thanks, > Eric Johnson - AE0JE > _._,_._,_ > ------------------------------ > Groups.io Links: > > You receive all messages sent to this group. > > View/Reply Online (#600) <https://ardc.groups.io/g/44net/message/600> | Reply > to Group > <44net@ardc.groups.io?subject=Re:%20%5BARDC%3A44Net%5D%20IPIP%20Packet%20Corruption> > | Reply to Sender > <micromashor@gmail.com?subject=Private:%20Re:%20%5BARDC%3A44Net%5D%20IPIP%20Packet%20Corruption> > | Mute This Topic <https://groups.io/mt/110582298/5279349> | New Topic > <https://ardc.groups.io/g/44net/post> > Your Subscription <https://ardc.groups.io/g/44net/editsub/5279349> | Contact > Group Owner <44net+owner(a)ardc.groups.io> | Unsubscribe > <https://ardc.groups.io/g/44net/leave/12923996/5279349/682613783/xyzzy> [ > micromashor(a)gmail.com] > _._,_._,_ > >

1 0

44net uses
by Dave Gingrich 21 Dec '24

21 Dec '24

Every year IRLP hosts a QSO party on New Years Eve. This is an informal gathering with no net control station. This is now largely conducted over 44net. The destination reflector (conference) in Australia and a large part of the IRLP infrastructure are on 44net address space. We have five central servers performing all authentication services and software updates. Four (out of five) are on 44net addresses. We also have issued over 500 VPN clients for Linux, so many of our member repeaters are also on 44net. While use of 44net is not required, IRLP is grateful and truly appreciates the use of the address space! If you have an IRLP node in your area, anyone here is welcome to join in. Below is the announcement sent to all of our IRLP owners. > > New Year’s Eve Around the World QSO Party, Reflector 9600 (Sydney), Tuesday, December 31. > > The nineteenth annual New Years Eve Around the World QSO Party will again be held on Reflector 9600 in Sydney, Australia. The party gets under way officially at 10:30 UTC (05:30 US eastern) Tuesday, December 31. It continues (officially) until 10:30 UTC Wednesday January 1. I say “Officially” because you are welcome to connect much earlier than that (now if you want) and stay as long as you like. > > This is a casual informal party with no net control or designated operators anytime during the event. Simply stop in, greet your friends, make new ones and simply enjoy yourself as the New Year wends its way around the planet, beginning in New Zealand 11:00 UTC (Dec-31) and ending in Hawaii at 10:00 UTC (Jan-1). > > This is an IRLP only event. Please resist the temptation to bridge folks in from other networks just because it sounds like fun. Instead, invite your local friends over to your repeater or encourage them to use a local resource to join in. > > Auld lang syne! > > Dave K9DC, K9IP — Dave K9DC, K9IP

1 0

44Net Update, December 6, 2024
by John Burwell 06 Dec '24

06 Dec '24

Hello 44Net, Thanks to our ticket handlers for their help with working through the surge of tickets on Sunday. We can expect more of these bumps in ticket activity as members respond to the various notices that the portal sends out at the start of each month. Thanks also to everyone who followed up on open tickets over the past two weeks since our last update. I’m excited to see paths clear for more people to get involved in 44Net! Here are the current ticket stats at time of writing: Total new and waiting tickets: 446 - New: 0 - Waiting (“open”): 446 - Waiting on user: 406 - Waiting on admin: 40 - Total closed since April 3: 4,422 Over the past few weeks, I’ve had the opportunity to speak directly with some of our members, which has been enlightening and inspiring. It’s great to hear how the new portal and other recent developments have helped so many of us get so much more out of our subnets so quickly. I’ve heard stories, many from newly licensed hams, of 44Net connecting families from across town and friends from across continents. The projects are as diverse as the people, and it occurs to me that they all have one thing in common: people creating ways to make connections with each other. I find it compelling. Looking ahead, I have no doubt that 2025 will bring more great forward progress, thanks to the exceptional talent, experience, ambition, and engagement across all the communities that make up 44Net. There are a lot of great ideas, and there is a lot of motivation to make things happen. I’m excited to see what comes next! As a final note, this will be the last 44Net weekly update of 2024. As always, let me know if I can ever be of any assistance. Until January, thanks for everything, may you find joy, and 73! John KI5QKX

1 0

44Net Update, November 22, 2024
by john＠ardc.net 23 Nov '24

23 Nov '24

Hello 44Net, Rebecca KO4KVG has artfully passed the weekly update to me to handle from now on. Thanks to Rebecca for all her work and help on this for the past several months! We would like to officially introduce Adam Lewis KC7GDY, who recently joined as our IT and Development Manager and has quickly become a fixture in the community. Read more about Adam in our latest blog post: https://www.ardc.net/ardc-introduces-it-development-manager-adam-lewis-kc7g… Volunteers and staff have been busy helping keep tickets under control since our ticket party in October. Many thanks to everyone for their help and patience as we clear the backlog. Here are the current ticket stats at time of writing: Total new and waiting tickets: 411 - New: 0 - Waiting (“open”): 407 - - Waiting on user: 380 - - Waiting on admin: 30 - Total closed since April 3: 4,150 As we approach the end of the year, I’ve been looking back at our progress getting through verification and network request tickets, and I have teased out some more fun facts: 1. Since tracking began in July, the number of tickets awaiting response from an administrator has been between 13 and 62, for a fairly steady average of 42. 2. In that same period, the number of tickets awaiting response from a user has increased from as few as 46 to as many as 414. That suggests to me that our volunteers and staff have moved through an enormous number of tickets, which I think is amazing. It also suggests that ticket handlers might be waiting on users more than users are waiting on handlers, at least as far as the portal is concerned. There are likely many explanations for this, but two things occur to me to mention: - If you are a user with an open ticket and you haven’t heard anything in a while, take a moment to check your ticket’s status in the portal. It is likely that more information is required, and it is possible that email notifications have not made it to your inbox. So, please follow up if you haven’t lately. The sooner we can help get your ticket closed, the sooner you can get more involved in 44Net! - If your ticket is stuck for any reason — and this goes for users and ticket handlers alike — don’t spin your wheels more than you have to. Ask for escalation if needed. Reach out to me personally if you like, at john(at)ardc.net. We are all ready to do what we can to help us all get the most out of 44Net. Let us know. Now that ticket handling has reached a steady state, we can get back to looking ahead. A sincere thanks to everyone for all the patience and support as we work together to get where we want to go. Finally, a note on programming: this will be the last weekly update for November, as we here in the United States are preparing for Thanksgiving, and ARDC will be closed next Thursday and Friday, November 28 and 29. Nevertheless, don’t hesitate to reach out if there is anything we can do for you. Until December, thanks for everything, have a great weekend, and 73! John KI5QKX

1 0

Trying to reach VA7MAS
by Chris 21 Nov '24

21 Nov '24

If VA7MAS is reading this please can you email me chris(a)ardc.net If anyone knows VA7MAS please could you ask them to drop me an email. Thank you, Chris - G1FEF — ARDC Administrator Web: https://www.ardc.net

1 0

44Net Update, November 15, 2024
by Rebecca Key 20 Nov '24

20 Nov '24

** *Hey Everyone,* * Last week, we welcomed our 44Net Program Manager John Burwell KI5QKX to ARDC! If you'd like to learn more about John, check out our recent blog post published earlier this week: https://www.ardc.net/ardc-welcomes-44net-program-manager-john-burwell-ki5qk… <https://www.ardc.net/ardc-welcomes-44net-program-manager-john-burwell-ki5qk…>. As John is the point of contact for 44Net-related communications, he will be distributing these weekly updates starting next week. That said, I won’t be too far away, and please don’t hesitate to reach out if you have any questions for me! Regarding ticket stats, as of today, * About 0 new tickets are in the queue. * About 409 tickets are open and awaiting response. o 387 are awaiting a response from the user o 22 are awaiting a response from an admin Since April 3, we have closed about 4,092 tickets. If you were unable to attend the Portal Training Workshops and are interested in becoming a Ticket Handler, please sign our confidentiality agreement, send me an email (rebecca(a)ardc.net), and I will send you the link to the video, along with the password. Our confidentiality agreement can be found on our website, specifically the Volunteer Services and Confidentiality Agreement (for 44Net Portal) link under ‘44Net’: https://www.ardc.net/ardc-community-resources/ <https://www.ardc.net/ardc-community-resources/>. If there’s anything within the documentation that is not clear or intuitive, please let us know at newportal(a)ardc.net. Portal documentation can be found below: * Intro to the Portal: https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro> * Organizations in the Portal: https://wiki.ampr.org/wiki/Organizations_in_the_Portal <https://wiki.ampr.org/wiki/Organizations_in_the_Portal> * [Ticket Handlers] Call Sign Verification How-To: https://wiki.ampr.org/wiki/Portal_Call_Sign_Verification <https://wiki.ampr.org/wiki/Portal_Call_Sign_Verification> Please note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. As always, let us know if you have any questions! 73, and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

44Net Update, November 8, 2024
by Rebecca Key 08 Nov '24

08 Nov '24

** *Hey Everyone,* * As of today, * About 6 new tickets are in the queue. * About 433 tickets are open and awaiting response. Please note that 433 includes both new and open tickets. o 414 are awaiting a response from the user o 13 are awaiting a response from an admin Since April 3, we have closed about 4,013 tickets. If you were unable to attend the Portal Training Workshops and are interested in becoming a Ticket Handler, please sign our confidentiality agreement, send me an email (rebecca(a)ardc.net), and I will send you the link to the video, along with the password. Our confidentiality agreement can be found on our website, specifically the Volunteer Services and Confidentiality Agreement (for 44Net Portal) link under ‘44Net’: https://www.ardc.net/ardc-community-resources/ <https://www.ardc.net/ardc-community-resources/>. If there’s anything within the documentation that is not clear or intuitive, please let us know at newportal(a)ardc.net. Portal documentation can be found below: * Intro to the Portal: https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro> * Organizations in the Portal: https://wiki.ampr.org/wiki/Organizations_in_the_Portal <https://wiki.ampr.org/wiki/Organizations_in_the_Portal> * [Ticket Handlers] Call Sign Verification How-To: https://wiki.ampr.org/wiki/Portal_Call_Sign_Verification <https://wiki.ampr.org/wiki/Portal_Call_Sign_Verification> Please note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. Finally, please note that ARDC will be closed on Monday, November 11 in observance of Veteran’s Day in the US. As always, let us know if you have any questions! 73, and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Verifying callsigns under ACMA's class license system
by Stuart Longland VK4MSL 04 Nov '24

04 Nov '24

Hi all, I noticed this morning there was a notification that my callsign verification was due to expire in a few months time. The ACMA stopped sending paper licenses back in 2016, going digital-only with a PDF you download from the website (with no authentication). In 2024 they moved the Amateur Radio service from being an apparatus-licensed service for which we pay an annual fee and receive (as a PDF) a soft-copy of the license; to a class-licensed system wherein there is no license fee, and no license issued of any kind. Glorified CB essentially. Force-Majeure… these are circumstances beyond my control. What verification evidence does the ARDC accept? Or should we prepare for 44net to disappear from Australia's packet radio networks forever? Regards, -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.

8 12

44Net Update, November 1, 2024
by Rebecca Key 01 Nov '24

01 Nov '24

** *Hey Everyone,* * As of today, * About 174 new tickets are in the queue. * About 459 tickets are open and awaiting response. Please note that 459 includes both new and open tickets. o 257 are awaiting a response from the user o 28 are awaiting a response from an admin Since April 3, we have closed about 3,730 tickets. A correction on closed tickets: on 10/25, the 3,828 tickets reported in the update actually corresponds to the total number of tickets in the system, not the number of closed tickets. Revisiting the stats, the actual number closed on 10/25 would’ve been closer to about 3,600. If you were unable to attend the Portal Training Workshops and are interested in becoming a Ticket Handler, please sign our confidentiality agreement, send me an email (rebecca(a)ardc.net), and I will send you the link to the video, along with the password. Our confidentiality agreement can be found on our website, specifically the Volunteer Services and Confidentiality Agreement (for 44Net Portal) link under ‘44Net’: https://www.ardc.net/ardc-community-resources/ <https://www.ardc.net/ardc-community-resources/>. If there’s anything within the documentation that is not clear or intuitive, please let us know at newportal(a)ardc.net. Portal documentation can be found below: * Intro to the Portal: https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro> * Organizations in the Portal: https://wiki.ampr.org/wiki/Organizations_in_the_Portal <https://wiki.ampr.org/wiki/Organizations_in_the_Portal> * [Ticket Handlers] Call Sign Verification How-To: https://wiki.ampr.org/wiki/Portal_Call_Sign_Verification <https://wiki.ampr.org/wiki/Portal_Call_Sign_Verification> Please note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. Finally, if you haven’t already, please be sure to check out our October Newsletter for other recent news and updates: https://www.ardc.net/?na=view&id=82 <https://www.ardc.net/?na=view&id=82>. If you’d like to subscribe to the newsletter, you can fill out the form and click ‘Subscribe’ here: https://www.ardc.net/about/newsletter/ <https://www.ardc.net/about/newsletter/>. As always, let us know if you have any questions! 73, and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

2 1

ARDC Portal Login
by Peter Mallett 31 Oct '24

31 Oct '24

Hello, Does anyone know if there are issues with the 2FA logins, has failed to work for me for about the last week and a half. Regards ..... Peter ZL2BAU

2 1

44Net Update, October 25, 2024
by Rebecca Key 24 Oct '24

24 Oct '24

** *Hey Everyone,* * As of today, * About 84 new tickets are in the queue. * About 339 tickets are open and awaiting response. Please note that 339 includes both new and open tickets. o 209 are awaiting a response from the user o 46 are awaiting a response from an admin If you were unable to attend the Portal Training Workshops and are interested in becoming a Ticket Handler, please sign our confidentiality agreement, send me an email (rebecca(a)ardc.net), and I will send you the link to the video, along with the password. Our confidentiality agreement can be found on our website, specifically the Volunteer Services and Confidentiality Agreement (for 44Net Portal) link under ‘44Net’: https://www.ardc.net/ardc-community-resources/ <https://www.ardc.net/ardc-community-resources/>. If there’s anything within the documentation that is not clear or intuitive, please let us know at newportal(a)ardc.net. Portal documentation can be found below: * Intro to the Portal: https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro> * Organizations in the Portal: https://wiki.ampr.org/wiki/Organizations_in_the_Portal <https://wiki.ampr.org/wiki/Organizations_in_the_Portal> * [Ticket Handlers] Call Sign Verification How-To: https://wiki.ampr.org/wiki/Portal_Call_Sign_Verification <https://wiki.ampr.org/wiki/Portal_Call_Sign_Verification> Please note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. As always, let us know if you have any questions! 73, and have a great rest of your week, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Results from the Portal Ticket Handling Party
by Rebecca Key 22 Oct '24

22 Oct '24

** *Hey Everyone,* * Before we trained folks in our community on ticket handling, we had about 996 tickets open and awaiting response (as of October 4)*. At our Ticket Party yesterday (10/16), in about 2.5 hours, we closed 430 tickets for call sign verification, resulting in 148 call sign verification tickets open and awaiting a response, bringing the overall number of tickets open and awaiting a response to 316. This event was a major success in reducing our ticket backlog! We want to extend a major thank you to all of our volunteers who showed up at our Ticket Party yesterday, along with folks who attended our training session last week: John Burwell KI5QKX John Davis WB4QDX Kevin Duffelmeyer KD2PDL Chip Eckardt W9OQI Dave Gingrich K9DC Rich Gopstein KD2CQ Austin Hadley KE8YGW Trevor Halsey KD8SEP George Kirn N9PNO Dave Koberstein N9DK Toshiyuki “Tom” Mabuchi JF3LGC Ronnie Montgomery W0RDM Peter Pototsky NH6FU Boudewijn “Bob” Tenty VE3TOK Jann Traschewski DG8NGN Răzvan Zeceş YO6RZV If you participated in eliminating this backlog, and your name is not on this list, please let me know, so we can acknowledge your contributions. We couldn’t have done this without all of you! 73, Rebecca KO4KVG *To summarize our previously reported ticket statistics, * 996 total (i.e., in addition to call sign verification) tickets were open and awaiting response as of October 4. * 717 total tickets were open and awaiting response as of October 11. * 316 total tickets were open and awaiting response at the conclusion of the Ticket Party on October 16. This number was achieved due to: o Volunteers closing 430 call sign verification tickets! * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

6 10

Re: If you aren't a current list member, sending this message will subscribe you.
by pete M 20 Oct '24

20 Oct '24

spammmmmmmmmmmm!!!!!!!!!!!!! Pierre VE2PF ________________________________________ De : 1mw35ake--- via 44net <44net(a)mailman.ampr.org> Envoyé : 19 octobre 2024 01:01 À : 44net(a)mailman.ampr.org Objet : [44net] If you aren't a current list member, sending this message will subscribe you. https://www.indonesiaescortspage.com/ If you aren't a current list member, sending this message will subscribe you. _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org To unsubscribe send an email to 44net-leave(a)mailman.ampr.org

1 0

44Net Update, October 18, 2024
by Rebecca Key 18 Oct '24

18 Oct '24

** *Hey Everyone,* * Again, we want to extend a major thank you to all who showed up at our Ticket Party on Wednesday. We had about 15 people show up, and we significantly reduced the number of call sign verification tickets in about 2.5 hours! With that, here are our current ticket stats: As of today, * About 62 new tickets are in the queue. * About 314 tickets are open and awaiting response. Please note that 314 includes both new and open tickets. o 218 are awaiting a response from the user o 34 are awaiting a response from an admin Since April 3, we have closed 3,828 tickets. If you were unable to attend the Portal Training Workshops and are interested in becoming a Ticket Handler, please sign our confidentiality agreement, send me an email (rebecca(a)ardc.net), and I will send you the link to the video, along with the password. Our confidentiality agreement can be found on our website, specifically the Volunteer Services and Confidentiality Agreement (for 44Net Portal) link under ‘44Net’: https://www.ardc.net/ardc-community-resources/ <https://www.ardc.net/ardc-community-resources/>. If there’s anything within the documentation that is not clear or intuitive, please let us know at newportal(a)ardc.net. Portal documentation can be found below: * Intro to the Portal: https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro> * Organizations in the Portal: https://wiki.ampr.org/wiki/Organizations_in_the_Portal <https://wiki.ampr.org/wiki/Organizations_in_the_Portal> * [Ticket Handlers] Call Sign Verification How-To: https://wiki.ampr.org/wiki/Portal_Call_Sign_Verification <https://wiki.ampr.org/wiki/Portal_Call_Sign_Verification> Please note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. As always, let us know if you have any questions! 73, and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

44Net Update, October 11, 2024
by Rebecca Key 11 Oct '24

11 Oct '24

** *Hey Everyone,* * As of today, * About 558 new tickets are in the queue. o Of these 558 tickets, 43 are new from within the last week. * About 717 tickets are open and awaiting response. Please note that 717 includes both new and open tickets. o 136 are awaiting a response from the user. o 49 are awaiting a response from an ARDC admin. Since April 3, we have closed 3,070 tickets. To minimize the backlog of tickets, we will be dedicating Wednesday, October 16 entirely to handling tickets with a Ticket Party. The party begins at 9a PT / 12p ET / 4p UTC, with a training session the hour before. If you’d like to attend the training and/or party, please RSVP to the respective event on the 44Net Subgroup calendar <https://ardc.groups.io/g/44net/calendar>(https://ardc.groups.io/g/44net/calendar) or email rebecca(a)ardc.net for the Zoom link. Please note that a signed confidentiality statement is required prior to ticket handling. For more information, check out the previous related communication here: https://ardc.groups.io/g/44net/topic/ticket_handling_party/108937069 <https://ardc.groups.io/g/44net/topic/ticket_handling_party/108937069>. If there’s anything within the documentation that is not clear or intuitive, please let us know at newportal(a)ardc.net. Portal documentation can be found below: * Intro to the Portal: https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro> * Organizations in the Portal: https://wiki.ampr.org/wiki/Organizations_in_the_Portal <https://wiki.ampr.org/wiki/Organizations_in_the_Portal> Please note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. As always, let us know if you have any questions! 73, and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Ticket Handling Party, Wednesday, October 16, 4 - 11p UTC
by Rebecca Key 10 Oct '24

10 Oct '24

** *Hey Everyone,* * Firstly, thank you for your patience while ARDC gets up to speed with our tickets. In an effort to minimize the backlog of tickets as efficiently as possible, we are holding a Ticket Party on Wednesday, October 16, from: 9a - 4p PDT 12 - 7p EDT 4 - 11p UTC 5p - 12a BST 6p - 1a CET If you’d like to attend and help us reduce the backlog, please see the inviteon the Groups.io Calendar of this subgroup (https://ardc.groups.io/g/44net/viewevent?eventid=2497221&calstart=2024-10-16) and RSVP to receive the Zoom link.You can also email me (rebecca(a)ardc.net <mailto:rebecca@ardc.net>) for the link if you prefer. If you did not attend our training workshop on Tuesday, we will hold another Portal Training Workshop immediately before the Ticket Party at: 8 - 9a PDT 11a - 12p EDT 3 - 4p UTC 4 - 5p BST 5 - 6p CET The invitefor the training can also be found on the Groups.io calendar of this subgroup where you can RSVP(https://ardc.groups.io/g/44net/viewevent?eventid=2497220&calstart=2024-10-16). You can also email rebecca(a)ardc.net <mailto:rebecca@ardc.net>for this link as well. Please note that participation in the workshop and the ticket party will require a signed volunteer agreement, which includes a confidentiality statement. This is because both the training and tickets will involve seeing Portal users’ personal information. If you would like to attend the Ticket Party and are unable to attend the live workshop, please let me know so we can provide you with a recording of Tuesday’s training session, along with a confidentiality statement to sign. If you have any other questions, please don’t hesitate to reach out. 73, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Welcome Schuyler Erle N0GIS, ARDC's new Director of Technology
by Rosy Schechter - KJ7RYV 04 Oct '24

04 Oct '24

Hi folks, As some of you may have already seen, this week we are welcoming Schuyler Erle N0GIS to our team as our new Director of Technology. You can learn a bit more about him in this blog post: https://www.ardc.net/meet-schuyler-erle-n0gis-ardcs-new-director-of-technol… Schuyler is one of two hires that we decided to make during the interview process for our tech team lead. The second one - who has been part of 44Net for a number of years – will be starting with us in just over a month. I look forward to introducing him to you as well. In the meantime, welcome Schuyler! 73, Rosy -- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net

2 1

44Net Update, October 4, 2024
by Rebecca Key 04 Oct '24

04 Oct '24

** *Hey Everyone,* * As you might have noticed, there was no weekly update last week. As I live in an area that was heavily impacted by Hurricane Helene, I was without power and cell service. As we’ve got backup power running at my house, I’m glad to get back online. All that said, below are some updates from this week regarding 44Net and our Technology Department: On Tuesday, October 1, ARDC welcomed our new Director of Technology, Schuyler Erle N0GIS. You can learn more about Schuyler by checking out our latest blog post here: https://www.ardc.net/meet-schuyler-erle-n0gis-ardcs-new-director-of-technol… <https://www.ardc.net/meet-schuyler-erle-n0gis-ardcs-new-director-of-technol…>. Regarding tickets, as of today, * About 845 new tickets are in the queue. o Of these 845 tickets, 325 are new from within the last week. * About 996 tickets are open and awaiting response. Please note that 996 includes both new and open tickets. o 134 are awaiting a response from the user. o 42 are awaiting a response from an ARDC admin. Since April 3, we have closed 2,718 tickets. To minimize the backlog of tickets, we will be dedicating Wednesday, October 16 entirely to handling tickets. If you’d like to take part in reducing the backlog, please reply to this email, and we will provide you information regarding next steps! Our next Regional Coordinators Meeting, which will be a Portal Training Workshop, will be on Tuesday, October 8, 2024 from 5:30 - 7a PDT / 12:30 - 2p UTC. If you are a Regional Coordinator and would like to attend, please RSVP using the Groups.io calendar of the 44Net Coordinators Subgroup <https://ardc.groups.io/g/coordinators>to receive the Zoom link or email contact(a)ardc.net <mailto:contact@ardc.net>.Please note that this is the first of many workshops, so if you’re unable to make this one, be on the lookout for other training opportunities in the future.If you’re interested in helping out on October 16 with the ticket backlog, we highly encourage you to attend this workshop! If there’s anything within the documentation that is not clear or intuitive, please let us know at newportal(a)ardc.net. Portal documentation can be found below: * Intro to the Portal: https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro> * Organizations in the Portal: https://wiki.ampr.org/wiki/Organizations_in_the_Portal <https://wiki.ampr.org/wiki/Organizations_in_the_Portal> Please note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. Finally, if you haven’t already, please be sure to check out our September Newsletter for other recent news and updates: https://www.ardc.net/?na=view&id=81 <https://www.ardc.net/?na=view&id=81>. If you’d like to subscribe to the newsletter, you can fill out the form and click ‘Subscribe!’ here: https://www.ardc.net/about/newsletter/ <https://www.ardc.net/about/newsletter/>. As always, let us know if you have any questions! 73, and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

PY3NZ
by Chris 01 Oct '24

01 Oct '24

If PY3NZ is reading this please can you email me. If anyone knows how to contact PY3NZ please could you pass my message on to them. Thank you Chris - G1FEF — ARDC Administrator Web: https://www.ardc.net

2 1

44net VPN
by Jean VE2PKT 25 Sep '24

25 Sep '24

Good day to all, I have change ISP and now the Gateway stop working, I should say it's working one way. I remember reading somewhere there was some VPN or similar for users having trouble with ISP filtering 44 network. Any info's is welcome. -- 73 de Jean, VA2OM / VE2PKT Sysop de: VE2PKT (BBS), VE2PKT-2 (BPQNode), VE2PKT-4 (XRPI) : VE2PKT-5 (Jnos), VE2PKT-9 (DXCluster) RF: 145.05 Mhz (1.2K Bps) Packet, 147.435 Mhz, VARA Internet: Telnet: ve2pkt.dyndns.org port 2323 (Xrpi Node) - VE2PKT-4 Telnet: ve2pkt.ampr.org port 9000 (DXCluster) - VE2PKT-9 E-Mail: packet: va2om(a)ve2pkt.#qbc.qc.can.noam ampr net: va2om(a)ve2pkt.ampr.org Inet: ve2pkt(a)gmail.com Hamshack Hotline: 5500000866 Membre Createur du groupe PacketQuebec(a)groups.io https://groups.io/g/PacketQuebec Carte des Station RF au Quebec https://www.google.com/maps/d/u/0/viewer?invite=CIero5gJ&mid=12uFqoa9Kw7jM-…

2 1

Unable to edit DNS records / non-intuitive record creation
by Cara Salter 24 Sep '24

24 Sep '24

Hi all, I recently made a CNAME record from @.na1cl.ampr.org to my gateway at rtr-nj1.na1cl.ampr.org, but ran into issues using it. When I looked at the DNS records that were actually created, it looks like this: na1cl.ampr.org. 86400 IN CNAME rtr-nj1.na1cl.ampr.org.ampr.org. Which does not match the portal help text of "enter a fully qualified domain name terminated with a period". In addition, it looks like there's no option to edit already-created resource records from the portal. Is there a planned feature to edit resource records and clarify the help text? Thanks and 73, Cara NA1CL

2 3

44Net Update, September 20, 2024
by Rebecca Key 20 Sep '24

20 Sep '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 558 new tickets are in the queue. * About 732 tickets are open and awaiting response. o 137 are awaiting a response from the user. o 56 are awaiting a response from an ARDC admin. Since April 3, we have closed 2,572 tickets. We are currently taking roll to identify our active regional coordinators. If you are an active regional coordinator and would like to remain in the role, please let Adam KC7GDY, our IT & Development Manager, know via email (adam(a)ardc.net) if you haven’t already! On the note of Regional Coordinators, we’re in the process of scheduling our next meeting for early/mid-October: https://ardc.groups.io/g/coordinators/topic/scheduling_the_october/108526267 <https://ardc.groups.io/g/coordinators/topic/scheduling_the_october/108526267>. If you haven’t already, please respond to the above thread and let us know if the days/times presented will work for you. Last week, Rosy sent out drafts of both the DNS policy and the EULA for review (attached). If you have any input, please feel free to ask questions in this thread or send a note to Rosy (rosy(a)ardc.net) within the next week, as we will be sending these items to the Board after that for final approval and implementation. If there’s anything within the documentation that is not clear or intuitive, please let us know at newportal(a)ardc.net. Portal documentation can be found below: * Intro to the Portal: https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro> * Organizations in the Portal: https://wiki.ampr.org/wiki/Organizations_in_the_Portal <https://wiki.ampr.org/wiki/Organizations_in_the_Portal> Please note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. As always, let us know if you have any questions! 73, and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

44Net Update, September 13, 2024
by Rebecca Key 13 Sep '24

13 Sep '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 662 new tickets are in the queue. * About 754 tickets are open and awaiting response. o 57 are awaiting a response from the user. o 53 are awaiting a response from an ARDC admin. Since April 3, we have closed 2,486 tickets. We are currently taking roll to identify our active regional coordinators. If you are an active regional coordinator and would like to remain in the role, please also let Adam KC7GDY, our IT & Development Manager, know via email (adam(a)ardc.net) if you haven’t already! Earlier this week, Rosy sent out drafts of both the DNS policy and the EULA for review (attached). If you have any input, please feel free to ask questions in this thread or send a note to Rosy (rosy(a)ardc.net) within the next couple of weeks, as we will be sending these items to the Board after that for final approval and implementation. The archives to the 44Net mailing list have been added to the website. You can find them in the following places: * Resources page (44Net section): https://www.ardc.net/ardc-community-resources/ <https://www.ardc.net/ardc-community-resources/> * 44Net page (Mailing list sub-bullet): https://www.ardc.net/44net/ <https://www.ardc.net/44net/> * Direct link to archive: https://mailman.ardc.net/mailman3/hyperkitty/list/44net@mailman.ampr.org/la… <https://mailman.ardc.net/mailman3/hyperkitty/list/44net@mailman.ampr.org/la…> Documentation that describes how organizations work in the portal is now live on the wiki: https://wiki.ampr.org/wiki/Organizations_in_the_Portal <https://wiki.ampr.org/wiki/Organizations_in_the_Portal>. For those of you that are either trustees or members of clubs/organizations that utilize 44Net, we hope you find this helpful! Also, if there is something that is not clear or intuitive (this also applies to the portal documentation, https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro>), please let us know at newportal(a)ardc.net. Finally, note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. As always, let us know if you have any questions! 73, and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Archive
by John Kristian 11 Sep '24

11 Sep '24

Is there an archive of previous messages sent to 44net(a)mailman.ampr.org ? Where can I access it? -- Best regards, John Kristian W6JMK

2 1

Subscribe
by John Kristian 11 Sep '24

11 Sep '24

Please permit me to view the archive of messages that were sent to the 44net mailing list. I have an account in portal.ampr.org, and I'm a member of https://ardc.groups.io/g/44net . -- Best regards, John Kristian W6JMK

2 1

For review: DNS policy and EULA
by Rosy Schechter - KJ7RYV 10 Sep '24

10 Sep '24

Hello 44Net, During some previous discussions with you all, we promised that we would share upcoming policies with you prior to adoption. With this in mind, I'm writing to share a couple of policies with you all to review - DNS Subdomain Policy and a new End User License Agreement (EULA) - and to open the floor for discussion and feedback. Both of these documents have been through some rounds of discussion and feedback with some of the regional coordinators, as well as staff, TAC, and board. It feels like, overall, we've landed in a place that works for all parties, and my hope is that you'll agree. Each of the policies are attached for review, and some summary information is below. Thanks for any thoughts / comments. We'll collect and discuss over the next couple of weeks before taking to the Board for final approval and implementation. 73, Rosy // Summary: DNS Subdomain policy Purpose: this policy outlines a standard for DNS subdomains that will help us to clean up our unwieldy database of DNS entries and assigning ownership to the ones still in use. Important notes: * preferred format is callsign.ampr.org; second-level subdomains permitted * if you were managing a top level subdomain that didn't fit that format prior to the launch of the new Portal, you can claim it and keep using it for now. Caveat: ARDC may revoke access to subdomains like hr.ampr.or, policy.ampr.org, or others that may seem to represent ARDC official hr or policy business. There are some other exceptions like this listed in the policy doc. // Summary: EULA Purpose: replacement of our existing Terms of Service (TOS) - https://www.ardc.net/about/legal/terms-of-service/ Important notes: * Though a bit more legalese in the EULA, there are very few substantive changes from the existing TOS * The main note is: for regional coordinators, gateway operators, or other users who may be assigning IP addresses to a subnet user, and they do not wish to have that user register on the Portal, then they take responsibility for the activities of that user. The goal of this is to give folks a pathway for managing their users as they have been, and accepting that with this responsibility comes some accountability. // Again, questions welcome. Thank you for taking the time to review. -- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net

1 0

44Net Update, September 6, 2024
by Rebecca Key 06 Sep '24

06 Sep '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 592 new tickets are in the queue. * About 710 tickets are open and awaiting response. o 56 are awaiting response from the user. o 62 are awaiting response from an ARDC admin. Since April 3, we have closed 2,429 tickets. To provide clarity on the number of tickets we’ve closed: we’ve recently updated our statistics system, where we can now track our previously deleted tickets that included PII. Therefore, since August 30, the number we report includes these previously deleted tickets. Please also note that only the headers of these tickets are stored; there is no PII stored. We are looking for folks that would be interested in conducting a code review (Laravel experience required) and pen testing of the portal. If you’re interested, please let Adam KC7GDY know via email (adam(a)ardc.net). We are currently taking roll to identify our active regional coordinators. If you are an active regional coordinator and would like to remain in the role, please also let Adam KC7GDY know via email if you haven’t already! If you weren’t able to make it to our Regional Coordinators meeting yesterday, here is the link to the recording of the meeting: https://vimeo.com/1007040170 <https://vimeo.com/1007040170>, which can also be found on the Regional Coordinators page: https://www.ardc.net/44net/regional-coordinators/ <https://www.ardc.net/44net/regional-coordinators/>. We will distribute the meeting notes and related documents as soon as we have them available. As many of you have asked about ways to help with the portal: if you come across something in the portal documentation - https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro>- that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net. Also note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

44Net Update, August 30, 2024
by Rebecca Key 30 Aug '24

30 Aug '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 45 new tickets are in the queue. * About 152 tickets are open and awaiting response. o 47 are awaiting response from the user. o 60 are awaiting response from an ARDC admin. Since April 3, we have closed 2,378 tickets. We are looking for folks that would be interested in conducting a code review (Laravel experience required) and pen testing of the portal. If you’re interested, please let Adam KC7GDY know via email (adam(a)ardc.net). We are currently taking roll to identify our active regional coordinators. If you are an active regional coordinator and would like to remain in the role, please also let Adam KC7GDY know via email. Our next Regional Coordinators Meeting will be on Thursday, September 5, 2024from 3 - 4:30p PDT / 10 - 11:30p UTC. If you are a Regional Coordinator and would like to attend, please RSVP using the Groups.io calendar of the 44Net Coordinators Subgroup (https://ardc.groups.io/g/coordinators)to receive the Zoom link or email contact(a)ardc.net. We are hiring for the roles of Administrative & Marketing Associate and Grants Associate. If you’re interested in applying for either of these roles, send a resume and cover letter to hr(a)ardc.net and be sure to send all files (including a cover letter) as separate PDF attachments without spaces in the name (e.g., jane-doe-cover-letter.pdf). Please note that Grants Associate applicants selected for interviews will be asked to provide a writing sample. To learn more about these roles, check out the below blog posts: * Administrative & Marketing Associate: https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/ <https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/> * Grants Associate: https://www.ardc.net/ardc-is-hiring-a-grants-associate/ <https://www.ardc.net/ardc-is-hiring-a-grants-associate/> As many of you have asked about ways to help with the portal: if you come across something in the portal documentation - https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro>- that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net. Also note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. Finally, be sure to check out our August Newsletter for our most recent news and updates: https://www.ardc.net/?na=view&id=80 <https://www.ardc.net/?na=view&id=80>. If you’d like to subscribe to the newsletter, you can fill out the form and click ‘Subscribe!’ here: https://www.ardc.net/about/newsletter/ <https://www.ardc.net/about/newsletter/>. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Subject: 44Net Update, August 23, 2024
by Rebecca Key 23 Aug '24

23 Aug '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 40 new tickets are in the queue. * About 168 tickets are open and awaiting response. o 84 are awaiting response from the user. o 44 are awaiting response from an ARDC admin. Since April 3, we have closed 1,428 tickets. We’ve recently had more requests to share statistics that provide more information on the rate at which tickets are opened and closed: work on developing code to provide these stats is still in progress, and we will be sharing these metrics once we have them. We are looking for folks that would be interested in a code review (Laravel experience required) and pen testing of the portal. If you’re interested, please let Adam KC7GDY know via email (adam(a)ardc.net). We are currently taking roll to identify our active regional coordinators. If you are an active regional coordinator and would like to remain in the role, please also let Adam KC7GDY know via email. On the note of Regional Coordinators, our next Regional Coordinators Meeting will be on Thursday, September 5, 2024from 3 - 4:30p PDT / 10 - 11:30p UTC. If you are a Regional Coordinator and would like to attend, please RSVP using the Groups.io calendar of the44Net Coordinators Subgroup <https://ardc.groups.io/g/coordinators>to receive the Zoom link or email contact(a)ardc.net <mailto:contact@ardc.net>. We are hiring for the roles of Administrative & Marketing Associate and Grants Associate. If you’re interested in applying for either of these roles, send a resume and cover letter to hr(a)ardc.net and be sure to send all files (including a cover letter) as separate PDF attachments without spaces in the name (e.g., jane-doe-cover-letter.pdf). Please note that Grants Associate applicants selected for interviews will be asked to provide a writing sample. To learn more about these roles, check out the below blog posts: * Administrative & Marketing Associate: https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/ <https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/> * Grants Associate: https://www.ardc.net/ardc-is-hiring-a-grants-associate/ <https://www.ardc.net/ardc-is-hiring-a-grants-associate/> As many of you have asked about ways to help with the portal: if you come across something in the portal documentation - https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro>- that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net. Also note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Re: F6CNB Contact
by Chris 16 Aug '24

16 Aug '24

Thanks Ludovic, I do have Remi's email, and I have been emailing but receiving no replies. Remi, if you're reading this, I received your email and replied - please check your spam folder Thanks, Chris - G1FEF — ARDC Administrator Web: https://www.ardc.net > On 16 Aug 2024, at 20:40, f5pbg(a)free.fr wrote: > > Hello Chris, > > his email is f6cnb(a)hutin.org > > Best regards, > Ludovic - F5PBG > > > Le 16/08/2024 à 15:35, Chris via 44net a écrit : >> If F6CNB is reading this please can you email me direct. >> >> If anyone is able to contact F6CNB please could you ask them to email me. >> >> Thank you! >> >> Chris - G1FEF >> — >> ARDC Administrator >> >> Web: https://www.ardc.net >> >> >> _______________________________________________ >> 44net mailing list -- 44net(a)mailman.ampr.org >> To unsubscribe send an email to 44net-leave(a)mailman.ampr.org >

1 0

44Net Update, August 16, 2024
by Rebecca Key 16 Aug '24

16 Aug '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 66 new tickets are in the queue. * About 157 tickets are open and awaiting response. o 51 are awaiting response from the user. o 40 are awaiting response from an ARDC admin. Since April 3, we have closed 958 tickets. We’ve recently had more requests to share statistics that provide more information on the rate at which tickets are opened and closed: we are currently working on developing code to provide these stats, and we will be sharing these metrics once we have them. We are looking for folks that would be interested in a code review (Laravel experience required) and pen testing of the portal. If you’re interested, please let Adam KC7GDY know via email (adam(a)ardc.net). We are currently taking roll to identify our active regional coordinators. If you are an active regional coordinator and would like to remain in the role, please also let Adam KC7GDY know via email. We are hiring for the roles of Administrative & Marketing Associate and Grants Associate. If you’re interested in applying for either of these roles, send a resume and cover letter to hr(a)ardc.net and be sure to send all files (including a cover letter) as separate PDF attachments without spaces in the name (e.g., jane-doe-cover-letter.pdf). Please note that Grants Associate applicants selected for interviews will be asked to provide a writing sample. To learn more about these roles, check out the below blog posts: * Administrative & Marketing Associate: https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/ <https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/> * Grants Associate: https://www.ardc.net/ardc-is-hiring-a-grants-associate/ <https://www.ardc.net/ardc-is-hiring-a-grants-associate/> As many of you have asked about ways to help with the portal: if you come across something in the portal documentation - https://wiki.ampr.org/wiki/Portal_intro <https://wiki.ampr.org/wiki/Portal_intro>- that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net. Also note that wiki updates can be made directly if you have an account on wiki.ampr.org. If you don’t have a wiki account and would like one, you can request an account setup by emailing wiki(a)ampr.org. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

F6CNB Contact
by Chris 16 Aug '24

16 Aug '24

If F6CNB is reading this please can you email me direct. If anyone is able to contact F6CNB please could you ask them to email me. Thank you! Chris - G1FEF — ARDC Administrator Web: https://www.ardc.net

1 0

44Net Update, August 9, 2024
by Rebecca Key 09 Aug '24

09 Aug '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 62 new tickets are in the queue. * About 172 tickets are open and awaiting response. o 47 are awaiting response from the user. o 63 are awaiting response from an ARDC admin. Since April 3, we have closed 944 tickets. We are looking for folks that would be interested in a code review (Laravel experience required) and pen testing of the portal. If you’re interested, please let us know. We are currently taking roll to identify our active coordinators. If you are an active coordinator and would like to remain in the role, please let Adam KC7GDY know via email (adam(a)ardc.net). We are hiring for the roles of Administrative & Marketing Associate and Grants Associate. If you’re interested in applying for either of these roles, send a resume and cover letter to hr(a)ardc.net and be sure to send all files (including a cover letter) as separate PDF attachments without spaces in the name (e.g., jane-doe-cover-letter.pdf). Please note that Grants Associate applicants selected for interviews will be asked to provide a writing sample. To learn more about these roles, check out the below blog posts: * Administrative & Marketing Associate: https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/ <https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/> * Grants Associate: https://www.ardc.net/ardc-is-hiring-a-grants-associate/ <https://www.ardc.net/ardc-is-hiring-a-grants-associate/> As many of you have asked about ways to help with the portal: if you come across something in the portal documentation - https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-… <https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…>- that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Radio Club & SDR
by dave.g4ugm＠gmail.com 05 Aug '24

05 Aug '24

Folks, I am just setting up some networking for our local radio club. We intend to have some SDR receivers and remote access to our HF Station. The issue is we do not have an externally visible IP address. Our router, and old(ish) Draytek, does support a variety of VPN services. Could we use a VPN through 44.net to obtain an externally routable IP address? Is this a legitimate use of 44net? Dave G4UGM

2 1

44Net Update, August 2, 2024
by Rebecca Key 02 Aug '24

02 Aug '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 37 new tickets are in the queue. * About 152 tickets are open and awaiting response. o 57 are awaiting response from the user. o 58 are awaiting response from an ARDC admin. Since April 3, we have closed 937 tickets. If you weren’t able to make it to our Regional Coordinators meeting last week, the recording of the meeting is now available: https://vimeo.com/manage/videos/992384749 <https://vimeo.com/manage/videos/992384749>, as well as the meeting notes: https://www.ardc.net/wp-content/uploads/2024-07-27-regional-coordinator-mee… <https://www.ardc.net/wp-content/uploads/2024-07-27-regional-coordinator-mee…>. To see videos and notes from previous meetings, be sure to check out our Regional Coordinators page on the website: https://www.ardc.net/44net/regional-coordinators/ <https://www.ardc.net/44net/regional-coordinators/>. On the note of Regional Coordinators, we are currently taking roll to identify our active coordinators. If you are an active coordinator and would like to remain a coordinator, please let Adam KC7GDY know via email (adam(a)ardc.net <mailto:adam@ardc.net>). We are hiring for the role of Grants Associate. If you’re interested in applying, send a resume and cover letter to hr(a)ardc.net <mailto:hr@ardc.net>and be sure to send all files (including a cover letter) as separate PDF attachments without spaces in the name (e.g., jane-doe-cover-letter.pdf). Please note that applicants selected for interviews will be asked to provide a writing sample. To learn more about the role, check out our latest blog post: https://www.ardc.net/ardc-is-hiring-a-grants-associate/ <https://www.ardc.net/ardc-is-hiring-a-grants-associate/>. As many of you have asked about ways to help with the portal: if you come across something in the portal documentation - https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-… <https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…>- that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net <mailto:newportal@ardc.net>. Finally, be sure to check out our July Newsletter for our most recent news and updates:https://www.ardc.net/about/newsletter/ <https://www.ardc.net/about/newsletter/>. If you’d like to subscribe to the newsletter, you can fill out the form at the top of the page and click ‘Subscribe’. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

44Net Update, July 26, 2024
by Rebecca Key 26 Jul '24

26 Jul '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 54 new tickets are in the queue. * About 153 tickets are open and awaiting response. o 50 are awaiting response from the user. o 49 are awaiting response from an ARDC admin. Since April 3, we have closed 926 tickets. The next Regional Coordinators meeting is tomorrow, Saturday, July 27, 2024 at 10am PDT / 5pm UTC. If you’re a Regional Coordinator and would like to attend, please RSVP using the Groups.io calendar of the subgroup or email contact(a)ardc.net <mailto:contact@ardc.net>to receive the Zoom link. You will also be able to find the agenda and other documents we’ll be discussing at the meeting on the pinned message in the Coordinators subgroup, ardc.groups.io/g/coordinators/topics <http://ardc.groups.io/g/coordinators/topics>. In response to a request to share our lessons learned from the portal launch, Rosy sent an email out yesterday titled “Portal rollout lessons learned,” which includes a cleaned-up summary from our internal retrospective. Here’s the link on Groups.io if you’d like to take a look: https://ardc.groups.io/g/44net/topic/portal_rollout_lessons/107550598 <https://ardc.groups.io/g/44net/topic/portal_rollout_lessons/107550598>. As many of you have asked about ways to help with the portal: if you come across something in the portal documentation (https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-… <https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…>) that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net <mailto:newportal@ardc.net>. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Portal rollout lessons learned
by Rosy Schechter - KJ7RYV 25 Jul '24

25 Jul '24

Hello all, A few weeks ago, someone requested that ARDC share our lessons learned from the recent Portal launch. In the spirit of transparency, please find those notes below. They comprise a cleaned-up summary from an internal retrospective that occurred just over a month ago. Our retrospectives follow the following format: * What worked well? * What didn’t work as well? * What can we do better next time? (These become action items / updates to internal standard operating procedures) The “lessons learned” notes are summarized in a similar format below. As you can see, there’s a lot of room to improve, but the good news is that we are learning a lot and actively working to improve it. Feedback and questions welcome; as always, please be kind. 73, Rosy // What worked well? * Our pre-testing identified numerous bugs and UI problems, and we fixed them pre-deployment * We fixed bugs quickly, pre- and post- deployment * We provided user-facing how-to documentation * UI of new portal was vastly improved from old portal, including the implementation of a new ticketing system * ARDC internal team worked well together, ensuring team cohesion even during the most challenging portions of deployment What didn't work as well? * The code was not developed in an open-sourced fashion, eliminating opportunities for feedback and improvement pre-launch * We were not sufficiently prepared for the initial call sign verification volume (we expected 30-50 in the first 24 hours; we received over 1000 in that time frame), and thus were not able to handle it * Our DNS/Subdomain and Level of Trust policies were incomplete prior to launch, resulting in confusion with our staff and volunteers, as well as 44Net members * The initial / pre-launch communications to the mailing list did not fully prepare users for the shift in procedure. As an example, we did not specify major changes in workflow or policy from the user’s perspective. What can we do better next time? * Engage all stakeholders (in this case, regional coordinators and general 44Net users) in the design process * Provide any new or updated policies well in advance of launch, providing opportunities for feedback and discussion. * Develop code in an open-source fashion, or at least share v1 code well in advance of production-level deployment. * Ensure that we have trained multiple administrators, so that we can handle a potential overload of usage. * In our communications, make sure that we are clear about what’s changing and what’s staying the same, and speak to it from the user's perspective. Also provide notice farther in advance (e.g. 2-3 months, with reminders, rather than just 2-4 weeks) -- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Hamcloud VPN
by Apostolos Kefalas 25 Jul '24

25 Jul '24

Hello Everyone, I do not know if this is the appropriate list to ask this question but I can not find any other contact. So please ignore if this is irrelevant! I am trying to connect to HamCloud VPN service. So far I have imported my LOTW certificate to Mozilla Firefox 115.12.0esr and try to authenticate as a radio amateur against https://vpn.hc.r1.ampr.org by clicking on "Login ARRL LoTW" in order to get my credentials but the links do not seem to work! Any help would be greatly appreciated! Thanks Apostolos, SV1LJJ

2 1

44Net Update, July 19, 2024
by Rebecca Key 21 Jul '24

21 Jul '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 48 new tickets are in the queue. * About 139 tickets are open and awaiting response. o 46 are awaiting response from the user. o 45 are awaiting response from an ARDC admin. Since April 3, we have closed 921 tickets. The next Regional Coordinators meeting is next Saturday, July 27, 2024 at 10am PDT / 5pm UTC. If you’re a Regional Coordinator and would like to attend, please RSVP using the Groups.io calendar of the subgroup or email contact(a)ardc.net <mailto:contact@ardc.net>to receive the Zoom link. ARDC is Hiring for an Administrative & Marketing Associate. If you’re interested in applying, send a resume and cover letter to hr(a)ardc.net <mailto:hr@ardc.net>and be sure to send all files (including a cover letter) as a PDF attachment without spaces in the name (e.g., jane-doe-cover-letter.pdf). To learn more about the role, check out our latest blog post: https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/ <https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/>. As many of you have asked about ways to help with the portal: if you come across something in the portal documentation (https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-… <https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…>) that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net <mailto:newportal@ardc.net>. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

5 5

44Net Update, July 12, 2024
by Rebecca Key 18 Jul '24

18 Jul '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 19 new tickets are in the queue. * About 117 tickets are open and awaiting response. o 70 are awaiting response from the user. o 28 are awaiting response from an ARDC admin. Since April 3, we have closed 918 tickets. ARDC is Hiring for an Administrative & Marketing Associate. If you’re interested in applying, send a resume and cover letter to hr(a)ardc.net <mailto:hr@ardc.net>and be sure to send all files (including a cover letter) as a PDF attachment without spaces in the name (e.g., jane-doe-cover-letter.pdf). To learn more about the role, check out our latest blog post: https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/ <https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/>. As many of you have asked about ways to help with the portal: if you come across something in the portal documentation (https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-… <https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…>) that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net <mailto:newportal@ardc.net>. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

4 5

a communication about communications
by Rosy Schechter - KJ7RYV 10 Jul '24

10 Jul '24

Dear 44Net community, I think it’s safe to say that the past few months on this mailing list have been, well, a lot. ARDC launched a new portal, which, we learned post-launch, definitely had some major issues. Much of the frustration around this rollout is more than reasonable. Unfortunately, communications from a very vocal minority crossed a threshold from expressing warranted and reasonable frustration and shifted to hostility, flaming, and trolling. Harassment of some of our employees occurred off-list. It was at this point that ARDC’s Code of Conduct committee was brought into the discussion. The Committee’s purpose is to confirm whether, in fact, a dispute is simply a disagreement, or whether it is harassment, trolling, or similar. Necessarily, the Committee must not include people directly impacted by the dispute, so that they can, to the best of their ability, respond impartially. At an even higher level, their job is to uphold ARDC’s values – notably of respect, accountability, and fairness. https://www.ardc.net/about/values/ In the case of this dispute – as a previous mail forwarded to these lists described – the committee’s decision was to temporarily suspend the accounts of one or more mailing list members. Some mailing list members may not like this decision. Other mailing list members have applauded it. Some mailing list members are so frustrated by the entire situation that they are unsubscribing and/or relinquishing their posts (which, to me, is disheartening but understandable). In our decisions, we are not going to make everyone happy. It is the nature of making decisions in an environment with a variety of opinions. To maintain room for diversity of thought, our commitment must be, first and foremost, to keeping healthy, supportive spaces for dialogue, discussion, and learning. This means, at times, (ideally temporary) removal of people whose behaviors significantly detract from those goals. In the breathing room that has been created from the temporary suspension, I hope that we may all get back to solving technical and policy problems, and to engaging in open and respectful dialogue. Thank you for your attention. 73, Rosy -- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net

10 19

44Net Update, July 3, 2024
by Rebecca Key 03 Jul '24

03 Jul '24

** *Hey Everyone,* * It’s a short week here at ARDC, as we will be closed on Thursday, July 4 and Friday, July 5 in observance of Independence Day in the US. We will return to the office on Monday, July 8. Below are some updates from this week regarding 44Net: As of today, * 17 tickets have been received since June 29, bringing our total of new tickets to 37. * About 288 tickets are open and awaiting response. o 214 are awaiting response from the user. o 37 are awaiting response from an ARDC admin. Since April 3, we have closed 746 tickets. As many of you have asked about ways to help with the portal: if you come across something in the portal documentation (https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-… <https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…>) that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net <mailto:newportal@ardc.net>. As always, let us know if you have any questions! 73 and have a great weekend, ** Rebecca ** KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

HTTP 500 error in portal when trying to link my subnet to my gateway
by KUN LIN 01 Jul '24

01 Jul '24

When I am in the Update Gateway page and trying to link gateway, I get http 500 error after click on “add new network”. [cid:image003.png@01DACA57.43FF47E0] Could anyone take a look at the portal? Thanks Kun

5 7

44Net Update, June 28, 2024
by Rebecca Key 28 Jun '24

28 Jun '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, * About 34 new portal tickets remain (21% decrease from last week), and * About 288 tickets are open and awaiting response (1% increase from last week). Since April 3, we have closed 735 tickets (1% increase from last week). On the note of metrics, we recently had some great questions regarding key performance indicators (KPIs). We’re working on developing additional metrics to expose these once we have a production quality process in place. If any of you have any other questions regarding metrics, please let us know: any constructive feedback is welcome! Regarding DNS claims: if you have any that you would like deleted, please email a list to newportal(a)ardc.net <mailto:newportal@ardc.net>, and we’ll take care of deleting them for you. The following new features have been added to the portal: * Clubs and organizations are now able to add up to 10 of their own call signs by default. This number can be adjusted on a per club / organization basis. * The individual limit of 5 call signs is also now adjustable on a per user basis. * Individuals can now belong to multiple clubs / organizations on a single account, eliminating the need to create multiple logins if you are involved with several clubs / organizations. * A ‘Maps’ menu has been added: this allows users to generate a map from a Maidenhead locator, as well as perform distance and bearing calculations, and can convert from DMS to lat/long and back. If anyone has suggestions for useful tools to add to the portal, please let us know at newportal(a)ardc.net <mailto:newportal@ardc.net>. ARDC is Hiring: if you’re interested in applying for the role of Technology Department Manager, send a resume and cover letter to hr(a)ardc.net <mailto:hr@ardc.net>. Ensure that your documents include your call sign, and be sure to send all files (including a cover letter) as a PDF attachment without spaces in the name (e.g., jane-doe-cover-letter.pdf). You can learn more about the role by checking out our latest blog post here: https://www.ardc.net/technology-department-manager/ <https://www.ardc.net/technology-department-manager/> As many of you have asked about ways to help with the portal: if you come across something in the portal documentation (https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-… <https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…>) that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net <mailto:newportal@ardc.net>. Finally, be sure to check out our June Newsletter for our most recent news and updates: https://www.ardc.net/?na=view&id=77 <https://www.ardc.net/?na=view&id=77>. If you’d like to subscribe to the newsletter, you can fill out the form and click ‘Subscribe!’ here: https://www.ardc.net/about/newsletter/ <https://www.ardc.net/about/newsletter/>. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Fwd: Code of Conduct report
by Charles J. Hargrove 27 Jun '24

27 Jun '24

Wow! Comment on something wrong and some people get their underwear in a bunch (you thought I was going to use another word). Those who feel like they are "threatened" when we point out their downfalls needs to grow up. We are adults here and we need to take as much as we give it. How about revealing who is make these supposed complaints? I have no problem being in the public eye, why not them? -------- Forwarded Message -------- Subject: Code of Conduct report Date: Wed, 26 Jun 2024 16:00:11 -0700 From: conduct(a)ardc.net To: n2nov(a)n2nov.net Hello Charles, The ARDC Conduct Review Committee has received additional reports regarding the recent content you have posted to the 44Net mailing list. The Committee will be meeting soon to review the reports in full. In the meanwhile, please review the Code of Conduct at https://www.ardc.net/about/legal/code-of-conduct/. Repeated posts with overall negative or 'trolling' messaging are not acceptable under this policy. We ask that you refrain from such in all further communications. Regards, The ARDC Conduct Review Committee This message is intended only for the addressed recipient. Please do not forward this email without permission. -- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM http://www.nyc-arecs.org NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32 "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan

3 4

Update re: subdomains
by Rosy Schechter - KJ7RYV 26 Jun '24

26 Jun '24

Dear 44Net community, It’s been just over two months since we launched the new Portal. It came with, as you have seen, some major bumps. Today, ARDC is resolving, at least temporarily, one of those hurdles: administrative access to subdomains. As of today, anyone who had a subdomain with ampr.org before the launch of the new Portal on April 3, 2024, will, for now, have full access to their DNS records. This includes subdomains that fall outside of our preferred format of callsign.ampr.org. This administrative access still depends on call sign verification, which requires confirming given name, family name, email, and valid amateur radio license. This step helps us ensure that the network is being used by valid amateur radio operators. During our recent work, we’ve found several bad actors, which is both unfair to the community and a security risk. We’ve also made a functional change to the portal: once a call sign is verified, you are now automatically able to create a subdomain with the format of callsign.ampr.org. All other new requests for subdomains that fall outside of that format (e.g., foo.ampr.org, which I’ll refer to as nonstandard subdomains for brevity) will require review and approval. Please note that we will be limiting the number of nonstandard subdomains going forward. Thus, if you have one (or, in some cases, many more), please consider it temporary. You can currently create as many second-level subdomains as you want—e.g., foo.callsign.ampr.org, bar.callsign.ampr.org, etc. We are working on a more official policy around subdomains using ampr.org. As promised at the recent regional coordinators' meeting, we will ensure you can see this policy before officially implementing it. We will also provide a transition period, likely many months, for users to edit their entries before official deprecation. This is, ultimately, what we should have done initially, and we take responsibility for not following a better process and, instead, rolling out this change without taking proper preparatory steps. Some of you may be wondering why we are making this change in the first place. It is because, without doing so, we end up in our current and very unwieldy situation: a database of over 51,000 DNS entries, most without knowledge of who they belong to, accumulated over at least a decade, with very few entries currently in use. If we aim to increase the usage of 44Net, then we need a system where we understand ownership and are able to provide an efficient service where we can address problems as they arise. For now, we hope that this helps to unblock anyone that currently feels blocked, while also providing an ample notice for changes that are coming down the pipeline at a later, though likely not-so-distant date. If you have questions, please ask. Many thanks, Rosy -- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net

9 13

Re: How to admin 44.151 ?!
by Main 26 Jun '24

26 Jun '24

> On Jun 26, 2024, at 12:46 PM, Main <adam(a)ardc.net> wrote: > > > If anyone is looking for it, Here is a link to the Portal Guide. > > > https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-… > https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-… > > Some of the setup info, like DNS, is in there. > > For allowing others to request IP’s from your prefix, > you will need to change its “Mode” from “private” to “open” > > I’ll make a quick how-to for making that mode change and upload. > > Here are a couple of other DNS how-tos > > > > > Adam kc7gdy > > > >> On Jun 26, 2024, at 11:53 AM, f5pbg--- via 44net <44net(a)mailman.ampr.org> wrote: >> >> Hello, >> >> here are my practical questions: >> . How can a French radio amateur request for an IP 44.151 /32 for example ? >> . Until now, as administrator, I managed the numbering, but I don't know how to do it now. >> . I used to create DNS in this sub-domain with direct-to-server commands, but now I don't know how. >> >> It's still a big mystery. >> >> Thank's. >> >> Ludovic - F5PBG - Subnet 44.151 in distress... 😉 >> _______________________________________________ >> 44net mailing list -- 44net(a)mailman.ampr.org >> To unsubscribe send an email to 44net-leave(a)mailman.ampr.org >

1 0

Re: [ARDC:Coordinators] Welcome to coordinators@ardc.groups.io
by Charles J. Hargrove 26 Jun '24

26 Jun '24

Reviewing some of the messages on the ARDC coordinators list from last September, and then comparing it to our experiences since April 3rd, will make you wonder what has really "improved" over the old way of doing things. There has been a notification for another coordinators' Zoom meeting about a month away. Will we be getting the same "we goofed, but everything is fine" responses from those in ARDC paid positions? I really hope that they have learned the painful lesson of the failed cut-over, but it is hard to see anything through the fog. BTW, Jon had left his paid ARDC position soon before the April 3rd mess. On 9/8/2023 10:51 AM, Jon Kemper wrote: > Hello All, > > Some of the information floating around is not accurate, so let me try > to clear the air a bit. > > At this time, there are no changes to the regional coordinator role. The > TAC community volunteers are only discussing how to improve our address > allocation policies and to assure that they are applied equally within > all regions. The goal is to increase the usage of the 44Net address > space and to provide additional community services for hams beyond IP-IP > mesh. This includes new designated subnets for things like the VPN based > PoPs. > > The current process in place made sense when it was first established > but in actuality it is not working well for many users and can be a > burden on volunteer coordinators. On the backed, it all funnels onto > Chris. One of the things that we are looking into is how to better > automate the back-end processes. Part of this will be building new and > more powerful administrative features into the portal for the regional > coordinators to use. > > The TAC has its hands full working on several projects and has only > begun to dive into address space policies. As technical and > administrative changes develop, these are being documented and will be > published and made available to all. And, when we are ready to work on > how the coordination workflow could be improved, this is not going to > happen in a vacuum. We will be calling upon the regional coordinator > group and working with extended communities like Hamnet and others to be > involved with helping us figure out how to best improve the process for > membership. > > There is a lot of work ahead and I thank you all for participating. > Together, we can make 44Net an even better community resource! > > 73, Jon -- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM http://www.nyc-arecs.org NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32 "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan

1 0

AMPR WHOIS
by Razvan YO6RZV 22 Jun '24

22 Jun '24

Hello all, Quick question, I tried to find informations about the AMPR WHOIS, but I did not find something relevant. I'm trying to see how my BGP announced allocation is showing up in the AMPR WHOIS. I tried first from my home ISP, but I was prompted with a 403 Forbidden Apache webpage on the whois.ampr.org. I also tried to access the same via the 44Net VPN (Wireguard) and I've received the same. Tried to access it via one of my BGP announced IP's, the same. If somebody has a KB or some informations about the restrictions (e.g. who can interogate the WHOIS) from what IP Addresses, etc. I would really appreciate gaining some informations about this side. -- 73's Thanks, Razvan - YO6RZV

2 3

44Net Update, June 21, 2024
by Rebecca Key 21 Jun '24

21 Jun '24

** *Hey Everyone,* * Below are some updates from this week regarding 44Net: As of today, about 43 new portal tickets remain (19% increase from last week), and about 285 tickets are open and awaiting response (3% increase from last week). Despite an increase in tickets from last week, the number of new tickets and the number of tickets open/awaiting response have decreased within the last three weeks or have remained constant (14% decrease and no significant change, respectively). Since April 3, we have closed 729 tickets (8% increase from last week). Regarding DNS claims: if you have any that you would like deleted, please email a list to newportal(a)ardc.net <mailto:newportal@ardc.net>, and we’ll take care of deleting them for you. ARDC is Hiring: if you’re interested in applying for the role of Technology Department Manager, send a resume and cover letter to hr(a)ardc.net <mailto:hr@ardc.net>. Ensure that your documents include your call sign, and be sure to send all files (including a cover letter) as a PDF attachment without spaces in the name (e.g., jane-doe-cover-letter.pdf). You can learn more about the role by checking out our latest blog post here: https://www.ardc.net/technology-department-manager/ <https://www.ardc.net/technology-department-manager/> Finally, as many of you have asked about ways to help with the portal: if you come across something in the docs (https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…) that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net <mailto:newportal@ardc.net>. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

2 1

Fwd: [ardc] ARDC is Hiring: Technology Department Manager
by Charles J. Hargrove 21 Jun '24

21 Jun '24

"Experience working with nonprofits and/or open-source technology projects is required." In other words, if you come from a corporate background then don't bother. The last few months have shown us that they absolutely need corporate experience! On 6/20/2024 5:13 PM, Rebecca Key via groups.io wrote: > Hey Everyone, > > We are currently hiring for the role of Technology Department Manager. > If you're interested in applying, send a resume and cover letter to > hr(a)ardc.net <mailto:hr@ardc.net>. Please ensure that your documentation > includes your amateur radio call sign, and be sure to send all files > (including a cover letter) as a PDF attachment without spaces in the > file name (e.g., jane-doe-cover-letter.pdf). > > To learn more about the role, check out our latest blog post: > https://www.ardc.net/technology-department-manager/ > <https://www.ardc.net/technology-department-manager/>. > > 73, > Rebecca > KO4KVG -- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM http://www.nyc-arecs.org NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32 "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan

2 2

Re: [ARDC:44Net] [ardc] ARDC is Hiring: Technology Department Manager
by Charles J. Hargrove 21 Jun '24

21 Jun '24

But purposely block the for-profit corporations? Not cool and shortsighted. On 6/20/2024 9:36 PM, Brian Wall wrote: > Non-profit can still be corporate experience. There are many large corporate non-profits; healthcare being one. Many skilled IT directors in healthcare networks. >> On Jun 20, 2024, at 9:32 PM, Charles J. Hargrove <n2nov(a)n2nov.net> wrote: >> >> "Experience working with nonprofits and/or open-source technology projects is required." >> In other words, if you come from a corporate background then don't bother. >> The last few months have shown us that they absolutely need corporate experience! >> >>> On 6/20/2024 5:13 PM, Rebecca Key via groups.io wrote: >>> Hey Everyone, >>> We are currently hiring for the role of Technology Department Manager. If you're interested in applying, send a resume and cover letter to hr(a)ardc.net <mailto:hr@ardc.net>. Please ensure that your documentation includes your amateur radio call sign, and be sure to send all files (including a cover letter) as a PDF attachment without spaces in the file name (e.g., jane-doe-cover-letter.pdf). >>> To learn more about the role, check out our latest blog post: https://www.ardc.net/technology-department-manager/ <https://www.ardc.net/technology-department-manager/>. >>> 73, >>> Rebecca >>> KO4KVG -- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM http://www.nyc-arecs.org NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32 "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan

1 0

Re: IPIP tunnel for Mikrotik
by KUN LIN 19 Jun '24

19 Jun '24

Oh, I am on ROS7/CHR. Is there a way to get it work on ROS7? Kun ________________________________ From: Marius Petrescu via 44net <44net(a)mailman.ampr.org> Sent: Monday, September 18, 2023 9:18 To: 44net(a)mailman.ampr.org <44net(a)mailman.ampr.org> Subject: [44net] Re: IPIP tunnel for Mikrotik The v3.1 scripts are for ROS up to 6.40, and the v3.2 scripts from ROS 6.41 up to the latest v6 releases. The scripts do NOT work on ROS 7 due to the fact that the RIP handling changed and the RIP timers do not work correctly. Marius, YO2LOJ On 18/09/2023 18:01, KUN LIN via 44net wrote: Hi Has anyone setup the IPIP tunnel successfully in Mikrotik? I think the instruction in Wiki is written for ROS 2.0. Things has changed a lot and I have trouble following. I created the IPIP tunnel in the interface and not sure what to do next. I added my IP subnet to the IP tab. The RIP configuration menu is very different now. Kun _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org> To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>

5 11

Re: Organization Callsigns (was: Re: Update re: subdomains)
by Dan Cross 15 Jun '24

15 Jun '24

On Fri, Jun 14, 2024 at 3:30 AM Chris via 44net <44net(a)mailman.ampr.org> wrote: > [snip] > 2. In relation to point 1. How do we vet the person requesting access to use an organisation’s call sign? This is really only an issue for US based clubs as the call sign has a trustee listed on the ULS database, but it would seem, that person is not always able/willing/interested in creating an account on the portal to have the call sign verified. This certainly needs more thought. > > The ideal situation would be for the trustee to create an account on the portal, verify the call sign, then hand it off to another member in the organisation, i.e. once setup they do not have to be the POC for the call sign - is this really asking too much of someone who has already agreed to be the trustee, which arguably comes with such responsibilities? This will, of course, be case dependent. In some cases, yes, it really is asking too much. In other cases, no. Should the trustee be involved at all? I would say that yes, they should. Some sort of proactive means for them to acknowledge delegation seems reasonable. But there ought to be a minimally invasive way for them to be, probably one that doesn't involve the portal. Taking a step back and trying to examine it from a holistic standpoint, it's about striking a balance between validating the authority of using the call to prevent abuse, and the bureaucratic hassle involved for the users/trustees. Merely being a trustee requires very little administrative burden. As I understand it, in the US, it can all be handled via mail through the US postal service; occasionally one sends the equivalent of a postcard to the FCC. That's it. This can obviously be done by nearly anyone, including by folks who are not technical, don't use computers, etc. As has been mentioned, e.g. by AE0JE, such people certainly exist. And even where folks have the technical expertise to do this, they may have neither the time nor the desire. As I mentioned earlier, I'm pretty much the only one in my club pushing to make use of AMPRNet. No one else particularly cares---I hope they will once they see how some of the cool stuff one can do with it, but we're not there yet. Forcing our callsign trustee to create an account on the portal, presumably going through his own verification process (requiring tickets and so on) all just for him to say, "yes, Dan can use the club's callsign to request an allocation" sounds like a good way to make the project stall indefinitely. Being the trustee for a callsign does not really confer any additional status on the person; among many clubs it's a minor chore taken on by whatever member who agrees to do it, but the responsibility can be passed around between different people over time. For instance, consider what happens if the trustee moves and leaves the club, or loses interest in radio, or (sadly) becomes an SK? The club doesn't necessarily cease to exist, and the callsign is still perfectly valid, but the trustee responsibility necessarily moves to someone else. This must be accounted for in some way in whatever policy emerges around this. - Dan C.

5 7

Re: Club Callsign Verification
by Eric Johnson 15 Jun '24

15 Jun '24

Ok, makes sense. It sounds like there is a ham responsible for maintaining the node. Why couldn't you use that ham's callsign for DNS services? Eric AE0JE On Sat, Jun 15, 2024, 1:55 PM Terence Theijn <terence(a)theijn.nl> wrote: > Ibm isn’t the user/maintainer they just host the site. They don’t have > access to or are allowed to use the network in any way. They just host the > pop in my example. > > So just providing roof access and power. > > 73 > > On 15 Jun 2024, at 19:46, Eric Johnson via 44net <44net(a)mailman.ampr.org> > wrote: > > > I understand it's not a repeater, that's just the best analogy I have. We > have a similar system here, but it's not as well-known or widespread as > hamnet. > > Usually, any DNS name that resolves to an IP is equivalent. Can you > elaborate on why you couldn't use a subdomain on a callsign? > > Furthermore, could you address the questions regarding non-ham (IBM) use > of this system? > > Eric AE0JE > > On Sat, Jun 15, 2024, 1:38 PM Terence Theijn <terence(a)theijn.nl> wrote: > >> Hamnet pop isn’t a radio repeater. It’s a pop for hamnet. We call the 44 >> net hamnet here and it runs on wireless links. >> >> It’s a complete wireless mesh network with many p2p links providing >> network connectivity to other hams/repeaters etc. >> >> So just adding a subdomain before a callsign isn’t going to cut the needs. >> >> 73 >> >> PD3T >> >> On 15 Jun 2024, at 14:27, Eric Johnson <micromashor(a)gmail.com> wrote: >> >> >> Chris: Sounds good, thank you. >> >> Terence, >> >> I am not the most familiar with hamnet, although at some point, there has >> to be a ham involved, right? The way repeaters typically work here is that >> a ham or group of hams speaks to a building owner and asks for an agreement >> to host a repeater and a little bit of rooftop space. That repeater is then >> usually referred to by the callsign of the ham(s) who maintain it and have >> the agreement with the building owner. >> >> Forgive me if I'm misunderstanding, but does hamnet usually work in a >> similar way? If so, couldn't the site be named pi90ibm.pd3t.ampr.org, >> assuming you are the maintainer of that site? >> >> If there isn't a ham involved at any step: >> - How is it legal use of the amateur bands? >> - Is it really a ham radio network at that point? >> >> Eric AE0JE >> >> On Sat, Jun 15, 2024, 6:01 AM Terence Theijn <terence(a)theijn.nl> wrote: >> >>> I see a lot of issues with hamnet pops without clubcallsings and are >>> just commercial building owners willing to host the housing for a hamnet >>> pop to extend the amprnet wireless network range. >>> >>> You do want those site to be recognizable some of those sites can even >>> host services like remote sdrs. >>> >>> For example ibm is willing to host a pop for network coverage. To make >>> it recognizable you can name it pi90ibm. This aint an official callsign. >>> How is one going to verify that? >>> Did you think about those? >>> >>> Regards >>> >>> PD3T >>> >>> >>> On 15 Jun 2024, at 09:12, Chris via 44net <44net(a)mailman.ampr.org> >>> wrote: >>> >>> A copy of the official PDF download from the ULS site of the club’s call >>> sign; >>> >>> _______________________________________________ > 44net mailing list -- 44net(a)mailman.ampr.org > To unsubscribe send an email to 44net-leave(a)mailman.ampr.org > >

3 3

Re: Club Callsign Verification
by Eric Johnson 15 Jun '24

15 Jun '24

I understand it's not a repeater, that's just the best analogy I have. We have a similar system here, but it's not as well-known or widespread as hamnet. Usually, any DNS name that resolves to an IP is equivalent. Can you elaborate on why you couldn't use a subdomain on a callsign? Furthermore, could you address the questions regarding non-ham (IBM) use of this system? Eric AE0JE On Sat, Jun 15, 2024, 1:38 PM Terence Theijn <terence(a)theijn.nl> wrote: > Hamnet pop isn’t a radio repeater. It’s a pop for hamnet. We call the 44 > net hamnet here and it runs on wireless links. > > It’s a complete wireless mesh network with many p2p links providing > network connectivity to other hams/repeaters etc. > > So just adding a subdomain before a callsign isn’t going to cut the needs. > > 73 > > PD3T > > On 15 Jun 2024, at 14:27, Eric Johnson <micromashor(a)gmail.com> wrote: > > > Chris: Sounds good, thank you. > > Terence, > > I am not the most familiar with hamnet, although at some point, there has > to be a ham involved, right? The way repeaters typically work here is that > a ham or group of hams speaks to a building owner and asks for an agreement > to host a repeater and a little bit of rooftop space. That repeater is then > usually referred to by the callsign of the ham(s) who maintain it and have > the agreement with the building owner. > > Forgive me if I'm misunderstanding, but does hamnet usually work in a > similar way? If so, couldn't the site be named pi90ibm.pd3t.ampr.org, > assuming you are the maintainer of that site? > > If there isn't a ham involved at any step: > - How is it legal use of the amateur bands? > - Is it really a ham radio network at that point? > > Eric AE0JE > > On Sat, Jun 15, 2024, 6:01 AM Terence Theijn <terence(a)theijn.nl> wrote: > >> I see a lot of issues with hamnet pops without clubcallsings and are just >> commercial building owners willing to host the housing for a hamnet pop to >> extend the amprnet wireless network range. >> >> You do want those site to be recognizable some of those sites can even >> host services like remote sdrs. >> >> For example ibm is willing to host a pop for network coverage. To make it >> recognizable you can name it pi90ibm. This aint an official callsign. How >> is one going to verify that? >> Did you think about those? >> >> Regards >> >> PD3T >> >> >> On 15 Jun 2024, at 09:12, Chris via 44net <44net(a)mailman.ampr.org> wrote: >> >> A copy of the official PDF download from the ULS site of the club’s call >> sign; >> >>

4 3

Re: Club Callsign Verification
by Chris 15 Jun '24

15 Jun '24

Hi Terence, As I said previously in relation to subdomains - other formats will be considered on a case by case basis, if someone requests a subdomain that isn’t a call sign there are other ways of verifying the identify of the person should ARDC decide that the request is appropriate. 73, Chris - G1FEF — ARDC Administrator Web: https://www.ardc.net > On 15 Jun 2024, at 11:01, Terence Theijn <terence(a)theijn.nl> wrote: > > I see a lot of issues with hamnet pops without clubcallsings and are just commercial building owners willing to host the housing for a hamnet pop to extend the amprnet wireless network range. > > You do want those site to be recognizable some of those sites can even host services like remote sdrs. > > For example ibm is willing to host a pop for network coverage. To make it recognizable you can name it pi90ibm. This aint an official callsign. How is one going to verify that? > Did you think about those? > > Regards > > PD3T > > >> On 15 Jun 2024, at 09:12, Chris via 44net <44net(a)mailman.ampr.org> wrote: >> >> A copy of the official PDF download from the ULS site of the club’s call sign;

1 0

Re: Club Callsign Verification
by Eric Johnson 15 Jun '24

15 Jun '24

Chris: Sounds good, thank you. Terence, I am not the most familiar with hamnet, although at some point, there has to be a ham involved, right? The way repeaters typically work here is that a ham or group of hams speaks to a building owner and asks for an agreement to host a repeater and a little bit of rooftop space. That repeater is then usually referred to by the callsign of the ham(s) who maintain it and have the agreement with the building owner. Forgive me if I'm misunderstanding, but does hamnet usually work in a similar way? If so, couldn't the site be named pi90ibm.pd3t.ampr.org, assuming you are the maintainer of that site? If there isn't a ham involved at any step: - How is it legal use of the amateur bands? - Is it really a ham radio network at that point? Eric AE0JE On Sat, Jun 15, 2024, 6:01 AM Terence Theijn <terence(a)theijn.nl> wrote: > I see a lot of issues with hamnet pops without clubcallsings and are just > commercial building owners willing to host the housing for a hamnet pop to > extend the amprnet wireless network range. > > You do want those site to be recognizable some of those sites can even > host services like remote sdrs. > > For example ibm is willing to host a pop for network coverage. To make it > recognizable you can name it pi90ibm. This aint an official callsign. How > is one going to verify that? > Did you think about those? > > Regards > > PD3T > > > On 15 Jun 2024, at 09:12, Chris via 44net <44net(a)mailman.ampr.org> wrote: > > A copy of the official PDF download from the ULS site of the club’s call > sign; > >

2 1

Re: Club Callsign Verification
by Eric Johnson 15 Jun '24

15 Jun '24

Chris and the group, I don't yet see a thread for this one, please forgive me if I missed it. --<snip>-- 2. In relation to point 1. How do we vet the person requesting access to use an organisation’s call sign? This is really only an issue for US based clubs as the call sign has a trustee listed on the ULS database, but it would seem, that person is not always able/willing/interested in creating an account on the portal to have the call sign verified. This certainly needs more thought. The ideal situation would be for the trustee to create an account on the portal, verify the call sign, then hand it off to another member in the organisation, i.e. once setup they do not have to be the POC for the call sign - is this really asking too much of someone who has already agreed to be the trustee, which arguably comes with such responsibilities? --</snip>-- I agree with everything you say insofar as this would be the solution in the ideal world. However, unfortunately, in cases like mine, this is not always the case. I'll spare you the details, but the gist is that the trustee has agreed to "hang on" to the callsign until we can get some issues sorted (which is turning out to take over a year due to bureaucratic processes). Our trustee is generally very busy, and to actively pursue the process of getting portal-verified would be a big ask, and would likely require a lot of nagging from me for it to ever get done. Likewise, many of the administrative tasks of the club have been delegated to me, as I am familiar with the processes and have the time to navigate them. In the US, only the trustee has access to download the Official copy of the club license through the ULS. Therefore, if someone presents an Official copy of the license as verification material, one could be reasonably confident that the trustee has entrusted them to act on the club's behalf. While I don't believe that simply having the Official copy should grant someone the "keys to the kingdom", a simple verification email to the club and/or the trustee would be sufficient to ensure the delegate is acting in good faith. It's important to note that getting verified in the portal and a quick "Yep, permission granted!" reply to a verification email differ significantly in magnitude. Is anyone else in a similar situation, or had similar experiences that could weigh in? Eric AE0JE

2 1

44Net Update, June 14, 2024
by Rebecca Key 14 Jun '24

14 Jun '24

Hey Everyone, Below are some updates from this week regarding the 44Net Portal: ** ** As of today, about 36 new portal tickets remain (20% increase from last week), and about 276 tickets are open and awaiting response (4% increase from last week). Despite an increase in tickets from last week, the number of new tickets and the number of tickets open/awaiting response have either decreased within the last two weeks or have remained constant (28% decrease and no significant change, respectively). Since April 3, we have closed 675 tickets (6% increase from last week). ** ** Earlier this week, Rosy KJ7RYV sent out an email about subdomain updates. In an effort to unblock our current users, our temporary steps forward are as follows: * Anyone with an ampr.org subdomain prior to 4/3/2024 will, for now, have full access to their DNS records, pending the required call sign verification * Once a call sign is verified, you can automatically create a subdomain with the callsign.ampr.org format. Other requests that fall outside of this format will require review and approval. * Please note that, moving forward, we will be limiting the number of subdomains outside of callsign.ampr.org and these current exceptions are temporary. ** ** Finally, as many of you have asked about ways to help with the portal:if you come across something in the docs that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net <mailto:newportal@ardc.net>. The link to the portal docs can be found here: https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…. ** ** As always, let us know if you have any questions! ** ** 73 and have a great weekend, ** ** Rebecca KO4KVG -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Point 3 - The subdomain policy that is in progress
by lleachii＠aol.com 14 Jun '24

14 Jun '24

Chris, Thanks for steering things back on topic. I trust if I maintain civil discussions, all is well.Since we now understand privately Rosy in judgment of you position deferres to you technically, which I respect - I hope you now consider my simple 2 inquiries that began (what I understood) to be why I responded about one or two of my examle records that I'm having issues claiming (as the tickets are on hold for different reasons, one assuming I just accepted a categorical name change in lieu of my claim ticketS), where you mentioned a ticket - as follows:I have logged in and understand that the portal system says "with user".What I do not understand is this -Is there a policy in place?Will you then proceed to delete these "non callsign" entries once one it is implemented?I have some other things to discuss, like the server in the UK that till has high latency for users on other continents, etc. - I'll message you.- KB3VWG

3 2

Point 1
by lleachii＠aol.com 14 Jun '24

14 Jun '24

Keep in mind at least in FCC land.- We have a time frame to file for callsign of related SK, etc.- "Memorial Clubs" that assume names, etc.Also, some resources were always to be assigned to the RACES or ARES callsigns after this infrastructure was completed (passed architect approval before this, but BGP/whatever tunneling will keep us compatible with all) may slow us.Likewise, e.g. they work in unison and just wanted you consider that when programming the backends of how callsigns work for users.I believe both in a programmatic workflow would refer to those like myself (e.g. aware of what your referencing) as neither trustee/president/Radio officer would directly answer. I thought of mentioning Point 2 here, but 1 seems more relevant. 73,- KB3VWG

1 0

Re: Point 3 - The subdomain policy that is in progress
by lleachii＠aol.com 14 Jun '24

14 Jun '24

Chris at al,I want to remind everyone of this. As far as I'm aware the portal policy has Sai that if you don't login with 6 months (or something as such) your "resources" can be removed.I don't understand why we all can proceed with and you delete all the state records.So next question technically- Why the resistance if any one of us agreed already to return our resources for e.g. if as we as in the US IT industry "get hit by a bus" and become an SK. In 6 months or so...viola.- KB3VWG -------- Original message --------From: lleachii--- via 44net <44net(a)mailman.ampr.org> Date: 6/14/24 04:21 (GMT-05:00) To: lleachii--- via 44net <44net(a)mailman.ampr.org> Subject: [44net] Point 3 - The subdomain policy that is in progress Chris, Thanks for steering things back on topic. I trust if I maintain civil discussions, all is well.Since we now understand privately Rosy in judgment of you position deferres to you technically, which I respect - I hope you now consider my simple 2 inquiries that began (what I understood) to be why I responded about one or two of my examle records that I'm having issues claiming (as the tickets are on hold for different reasons, one assuming I just accepted a categorical name change in lieu of my claim ticketS), where you mentioned a ticket - as follows:I have logged in and understand that the portal system says "with user".What I do not understand is this -Is there a policy in place?Will you then proceed to delete these "non callsign" entries once one it is implemented?I have some other things to discuss, like the server in the UK that till has high latency for users on other continents, etc. - I'll message you.- KB3VWG

2 1

Re: Point 3 - The subdomain policy that is in progress
by lleachii＠aol.com 14 Jun '24

14 Jun '24

Chris, Thanks, I think point one has been addressed mutiple times. I understand that.I don't understand if or when they will be deleted. I was given an apology for what I understood to be the reason this line of discussion was opened with the Executive Staff, my Regional Coordinator and myself.I know the discussion got clouded by others, but that seems to be why I can't do anything with my records since...April 4 as I recall? I understand nobody seem to understand altering a Global DNS record that someone in "West Jiblip" may use - and when it shall change, my apologies.At minimum the apology explained I'd understand that. We can chat about unrelated records, etc. later. Since I also want to make note the discussion went into an example of how I CNAME. I am willing to edit my records if the portal allows (not dns-mdc) as a gesture, if any.- KB3VWG -------- Original message --------From: Chris <chris(a)ardc.net> Date: 6/14/24 04:48 (GMT-05:00) To: lleachii(a)aol.com Cc: lleachii--- via 44net <44net(a)mailman.ampr.org> Subject: Re: [44net] Point 3 - The subdomain policy that is in progress Hi Lynwood,On 14 Jun 2024, at 09:20, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote:Chris, Thanks for steering things back on topic. I trust if I maintain civil discussions, all is well.Always.Since we now understand privately Rosy in judgment of you position deferres to you technically, which I respect - I hope you now consider my simple 2 inquiries that began (what I understood) to be why I responded about one or two of my examle records that I'm having issues claiming (as the tickets are on hold for different reasons, one assuming I just accepted a categorical name change in lieu of my claim ticketS), where you mentioned a ticket - as follows:I have logged in and understand that the portal system says "with user".Yes, “with user” means the ticket is with you and waiting for your response.What I do not understand is this -Is there a policy in place?Relating to subdomains? No, not yet. As Rosy said we are developing this policy right now. My hope is that it will be ready soon (days or weeks, hopefully not months).Will you then proceed to delete these "non callsign" entries once one it is implemented?As the policy is not in force yet, I cannot answer this question as it will depend on what the policy ends up stating.Right now we have an SOP in place that that we are working to: - We would prefer everyone to use the callsign.ampr.org format, if you request a subdomain in this format it will be automatically approved provided: - The call sign is yours, - The call sign has been verified. - If you request a subdomain based on one of your call signs that has not been verified you will see a popup advising you to get it verified first, then come back and request the subdomain. - If you request a subdomain that is not based on one of your call signs it will popup a warning advising what our preferred format is. - In both the above two cases you have the option to ignore the warning and continue, in which case a ticket will be created for manual processing. - If we receive a ticket for a subdomain that does not exist in DNS yet (i.e. a new request) the request will be considered on a case by case basis, you may be asked to justify your request, so we can understand if your use case is a good fit, often these requests will be discussed amongst the ARDC staff to gain consensus on the final decision. - If we receive a ticket for a subdomain that already exists in DNS we will first of all attempt to ascertain if you have a legitimate right to request it, e.g. do the existing DNS records match one of your network assignments, or if you are a coordinator one of the network allocations you look after, failing that we will ask you to justify your request. If we are satisfied that your request is legitimate, i.e. you’re not trying to steal someone else’s subdomain! then your request will be approved with the following proviso / warning:—8< snip >8---Important notice about this subdomain approvalOver the past decade, ARDC has accumulated a database of over 51,000 DNS entries, the vast majority of which are unused and “ownership” is unknown. The rollout of the new Portal allows us to clean this up.Thus, in the coming months, ARDC will update our policy around top-level subdomain requests using ampr.org. Subdomains using the format of callsign.ampr.org will be automatically approved; all others will be reviewed by our team. Once approved, you may create lower-level subdomains (e.g., foo.callsign.ampr.org) without further approval.Administrative access to this non-callsign subdomain is being temporarily approved while this policy is being developed. Thus, please consider access to this subdomain as temporary.Once an official policy is in place, we will have a transition period before the official deprecation of subdomains such as this one. Please direct any questions to newportal(a)ampr.org. —8< snip >8—I hope this clears things up.73,ChrisI have some other things to discuss, like the server in the UK that till has high latency for users on other continents, etc. - I'll message you.- KB3VWG_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org

1 0

Re: Update re: subdomains
by pete M 14 Jun '24

14 Jun '24

Dont worry I read manuals, laws and many more things. What you dont seem to understand is the fact that you are not entitled to anything beside what ARDC board/staff decide. What ever the RFC or whatever else you think might mean something. ARDC have the right to decide to change any information they think should apply to all of the IP space they own. The only rights you have is to ask politely if they are ok with letting you use a part of it. They have no other obligation to you than to answer yes or no. And even when they say yes, they have no obligation to give you the control over rDNS, or BGP , geolocalisation, or anything else. Pierre VE2PF ________________________________________ De : lleachii(a)aol.com <lleachii(a)aol.com> Envoyé : 13 juin 2024 12:24 À : pete M Objet : Re: [44net] Re: Update re: subdomains This is where we (and others, i.e. those who can read manuals) disagree. No fact of the matter or the infrastructure of the Internet dictates the point of view you've seem to have blindly espoised about ARDC. Read the RFCs. Further, please don't add specifics of IP space to an already convoluted subject. Given these discussions seem to go off topic as you have attempted purposely twice - I'll simply refrain from engaging in chat with you. If this was genuine, Thanks. If not, I'm confused why you would do it. -------- Original message -------- From: pete M <petem001(a)hotmail.com> Date: 6/13/24 11:08 (GMT-05:00) To: lleachii(a)aol.com Subject: Re: [44net] Re: Update re: subdomains You are responsible of YOUR station, ARDC grants you the right to TEMPORARY USE some IP address to use for hamradio, those are NOT YOURS same for the setting linked to them. If you have no clue of the contract you have entered when asking for those IP address, better read them and understand, than thinking you own something and clame what you have no rights to. Pierre VE2PF ________________________________________ De : lleachii--- via 44net <44net(a)mailman.ampr.org> Envoyé : 13 juin 2024 10:31 À : pete M via 44net Objet : [44net] Re: Update re: subdomains There is no such thing. Maybe you misunderstand what I'm referring to. We are responsible for our own stations during an emergency in the US (hence why ARDC shouldn't mess with MY settings since I may be disconnected from them when discovering it). I assumed this was international at any given moment. If you have no clue or understanding, you should remain silent in that case. It's easier to be quiet and learn tan to be loud and wrong. -------- Original message -------- From: pete M via 44net <44net(a)mailman.ampr.org> Date: 6/13/24 09:53 (GMT-05:00) To: Amprnet 44 Net <44net(a)mailman.ampr.org> Subject: [44net] Re: Update re: subdomains Since when is it OK to use 44net for any other use than ham experimentation on that IP address space? If you use a network for experimentation as a primary link for emergency you miss understood the use of the 44net. Yes it is appealing to do so. But be aware that this network can and will change over the time. Some stuff will break. Some will cease to exist. And new stuff will appear. ARDC is not a ISP nor a commercial entity that provide professional services for commercial grade networking. If the network infrastructure you use is primary for life safety, better go the commercial route. If you are a BACKUP in case everything else is gone. That is not the same thing, and the authority dealing with ham should better know about it. This is my opinion of the situation and note ARDC view. I am not talking for them. Pierre VE2PF ________________________________________ De : Chris via 44net <44net(a)mailman.ampr.org> Envoyé : 13 juin 2024 06:47 À : lleachii(a)aol.com Cc : Amprnet 44 Net Objet : [44net] Re: Update re: subdomains Hello Lynwood, For the record, I have never made any derogatory remarks to you publicly or in private, you completely misconstrued an offer of help I made for reasons I still do not understand. If you wish to discuss this then I am more than happy to, as I would like to clear up any misunderstandings. Please feel free to contact me off-list as this is not the appropriate place for such discussions. With regards to the rest of your email, I refer you to Rosy’s email to this list which explains the current situation. I am sure she would be more than happy to answer any questions you may have. Kind Regards, Chris - G1FEF — ARDC Administrator Web: https://www.ardc.net/ On 13 Jun 2024, at 11:10, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote: Chris, I have logged in and understand that the portal system says "with user". What I do not understand is this - * Is there a policy in place? * Will you then proceed to delete these "non callsign" entries once one it is implemented? You all may not have noticed, but I'm being very particular NOT to agree to new DNS terms, IP record changes, etc. (i.e. stuff that preexisted your control of this domain and space). Before I post the text (since it's quite similar to what I read posted by an ARDC employee), I will not quote it at this time. Please offer clarity (publicly, because you have said some derogatory things to me before in private which you seem uncourageous to say publicly - so I'm uncomfortable) before I proceed. I also need ARDC to understand that there will be concerns if you then proceed to delete entries I've made very clear I wish to continue use of (as well as my GOVERNMENTAL RACES SPONSOR). I've explained the nature of your inheritance, but somehow - I need to clarify this seemingly contrary policy before I agree. Please note, my records also show and indicate this "policy" is not because of the numerous amount of DNS records - I will not discuss this further here. Anyone seeing the updates on portal ticket clearing statistics can see that. And if your answer is YES to the latter question above - common sense also provides that you can just as well identify and handle them, as you would need to do so to accomplish that task. Yet, a hassle for records I'm in fact attempting to claim (over and over - obviously I'm making records that I'm clamming them)? Since I pray common scene now prevails - I simply ask you not hold my records "hostage" in this commercialization game. Thanks and 73, Lynwood KB3VWG (reviewed by a Sensitivity Expert, please be courageous and secretly report the entire text as a Code of Conduct violation if you desire, including this disclaimer to show your ignorance - yes this portion was reviewed as well) On Wednesday, June 12, 2024 at 03:17:04 PM EDT, Chris via 44net <44net(a)mailman.ampr.org> wrote: Lynwood, Please check your tickets, I replied 2 day ago, just waiting on your reply. 73, Chris - G1FEF On 12 Jun 2024, at 18:43, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote: I have not been allowed to make those edits. On Wednesday, June 12, 2024 at 01:36:45 PM EDT, Steve L via 44net <44net(a)mailman.ampr.org> wrote: In my opinion for the purposes of tracking ownership, nonstandard subdomains should only exist via a cname record. Example of Lynwood (doing it correctly in my opinion) speedtest.ampr.org<http://speedtest.ampr.org/>. 300 IN CNAME kb3vwg-010.ampr.org<http://kb3vwg-010.ampr.org/>. kb3vwg-010.ampr.org<http://kb3vwg-010.ampr.org/>. 300 IN A 44.60.44.10 In theory speedtest.ampr.org<http://speedtest.ampr.org/> could have a direct A record.. such as speedtest.ampr.org<http://speedtest.ampr.org/>. 300 IN A 44.60.44.10 But that is problematic. Just my 2 cents. On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net <44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>> wrote: Dear 44Net community, It’s been just over two months since we launched the new Portal. It came with, as you have seen, some major bumps. Today, ARDC is resolving, at least temporarily, one of those hurdles: administrative access to subdomains. As of today, anyone who had a subdomain with ampr.org<http://ampr.org/> before the launch of the new Portal on April 3, 2024, will, for now, have full access to their DNS records. This includes subdomains that fall outside of our preferred format of callsign.ampr.org<http://callsign.ampr.org/>. This administrative access still depends on call sign verification, which requires confirming given name, family name, email, and valid amateur radio license. This step helps us ensure that the network is being used by valid amateur radio operators. During our recent work, we’ve found several bad actors, which is both unfair to the community and a security risk. We’ve also made a functional change to the portal: once a call sign is verified, you are now automatically able to create a subdomain with the format of callsign.ampr.org<http://callsign.ampr.org/>. All other new requests for subdomains that fall outside of that format (e.g., foo.ampr.org<http://foo.ampr.org/>, which I’ll refer to as nonstandard subdomains for brevity) will require review and approval. Please note that we will be limiting the number of nonstandard subdomains going forward. Thus, if you have one (or, in some cases, many more), please consider it temporary. You can currently create as many second-level subdomains as you want—e.g., foo.callsign.ampr.org<http://foo.callsign.ampr.org/>, bar.callsign.ampr.org<http://bar.callsign.ampr.org/>, etc. We are working on a more official policy around subdomains using ampr.org<http://ampr.org/>. As promised at the recent regional coordinators' meeting, we will ensure you can see this policy before officially implementing it. We will also provide a transition period, likely many months, for users to edit their entries before official deprecation. This is, ultimately, what we should have done initially, and we take responsibility for not following a better process and, instead, rolling out this change without taking proper preparatory steps. Some of you may be wondering why we are making this change in the first place. It is because, without doing so, we end up in our current and very unwieldy situation: a database of over 51,000 DNS entries, most without knowledge of who they belong to, accumulated over at least a decade, with very few entries currently in use. If we aim to increase the usage of 44Net, then we need a system where we understand ownership and are able to provide an efficient service where we can address problems as they arise. For now, we hope that this helps to unblock anyone that currently feels blocked, while also providing an ample notice for changes that are coming down the pipeline at a later, though likely not-so-distant date. If you have questions, please ask. Many thanks, Rosy -- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net<http://ardc.net/> _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org> To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org> _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org> To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org> _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org To unsubscribe send an email to 44net-leave(a)mailman.ampr.org _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org> To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org> _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org To unsubscribe send an email to 44net-leave(a)mailman.ampr.org _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org To unsubscribe send an email to 44net-leave(a)mailman.ampr.org

14 25

Request- on air WG testers
by lleachii＠aol.com 13 Jun '24

13 Jun '24

If anyone is performing an on-air Wireguard tests on a band, wattage, etc. requiring a licence and the test key is not the all-zeros in the white-paper document. Please provide information where the key may be found/is published. Thanks, KB3VWG

1 0

Re: Update re: subdomains
by lleachii＠aol.com 13 Jun '24

13 Jun '24

Lastly, Nobody's referring to an ISP. I'm confused why you tried to confuse and distract this by mentioning pure nonsense.None of us have ARDC as an ISP to my knowledge and they offer no such services.The next time you or someone else simply won't addresses my point or refer me to someone who answers, I'll report you for violation of Code of Conduct . -------- Original message --------From: lleachii(a)aol.com Date: 6/13/24 10:31 (GMT-05:00) To: pete M via 44net <44net(a)mailman.ampr.org> Subject: RE: [44net] Re: Update re: subdomains There is no such thing. Maybe you misunderstand what I'm referring to. We are responsible for our own stations during an emergency in the US (hence why ARDC shouldn't mess with MY settings since I may be disconnected from them when discovering it). I assumed this was international at any given moment. If you have no clue or understanding, you should remain silent in that case. It's easier to be quiet and learn tan to be loud and wrong.-------- Original message --------From: pete M via 44net <44net(a)mailman.ampr.org> Date: 6/13/24 09:53 (GMT-05:00) To: Amprnet 44 Net <44net(a)mailman.ampr.org> Subject: [44net] Re: Update re: subdomains Since when is it OK to use 44net for any other use than ham experimentation on that IP address space?If you use a network for experimentation as a primary link for emergency you miss understood the use of the 44net.Yes it is appealing to do so. But be aware that this network can and will change over the time. Some stuff will break. Some will cease to exist. And new stuff will appear.ARDC is not a ISP nor a commercial entity that provide professional services for commercial grade networking. If the network infrastructure you use is primary for life safety, better go the commercial route. If you are a BACKUP in case everything else is gone. That is not the same thing, and the authority dealing with ham should better know about it.This is my opinion of the situation and note ARDC view. I am not talking for them.PierreVE2PF________________________________________De : Chris via 44net <44net(a)mailman.ampr.org>Envoyé : 13 juin 2024 06:47À : lleachii(a)aol.comCc : Amprnet 44 NetObjet : [44net] Re: Update re: subdomainsHello Lynwood,For the record, I have never made any derogatory remarks to you publicly or in private, you completely misconstrued an offer of help I made for reasons I still do not understand. If you wish to discuss this then I am more than happy to, as I would like to clear up any misunderstandings. Please feel free to contact me off-list as this is not the appropriate place for such discussions.With regards to the rest of your email, I refer you to Rosy’s email to this list which explains the current situation. I am sure she would be more than happy to answer any questions you may have.Kind Regards,Chris - G1FEF—ARDC AdministratorWeb: https://www.ardc.net/On 13 Jun 2024, at 11:10, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote:Chris,I have logged in and understand that the portal system says "with user".What I do not understand is this - * Is there a policy in place? * Will you then proceed to delete these "non callsign" entries once one it is implemented?You all may not have noticed, but I'm being very particular NOT to agree to new DNS terms, IP record changes, etc. (i.e. stuff that preexisted your control of this domain and space). Before I post the text (since it's quite similar to what I read posted by an ARDC employee), I will not quote it at this time. Please offer clarity (publicly, because you have said some derogatory things to me before in private which you seem uncourageous to say publicly - so I'm uncomfortable) before I proceed.I also need ARDC to understand that there will be concerns if you then proceed to delete entries I've made very clear I wish to continue use of (as well as my GOVERNMENTAL RACES SPONSOR). I've explained the nature of your inheritance, but somehow - I need to clarify this seemingly contrary policy before I agree.Please note, my records also show and indicate this "policy" is not because of the numerous amount of DNS records - I will not discuss this further here. Anyone seeing the updates on portal ticket clearing statistics can see that. And if your answer is YES to the latter question above - common sense also provides that you can just as well identify and handle them, as you would need to do so to accomplish that task. Yet, a hassle for records I'm in fact attempting to claim (over and over - obviously I'm making records that I'm clamming them)?Since I pray common scene now prevails - I simply ask you not hold my records "hostage" in this commercialization game.Thanks and 73,LynwoodKB3VWG(reviewed by a Sensitivity Expert, please be courageous and secretly report the entire text as a Code of Conduct violation if you desire, including this disclaimer to show your ignorance - yes this portion was reviewed as well)On Wednesday, June 12, 2024 at 03:17:04 PM EDT, Chris via 44net <44net(a)mailman.ampr.org> wrote:Lynwood,Please check your tickets, I replied 2 day ago, just waiting on your reply.73,Chris - G1FEFOn 12 Jun 2024, at 18:43, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote:I have not been allowed to make those edits.On Wednesday, June 12, 2024 at 01:36:45 PM EDT, Steve L via 44net <44net(a)mailman.ampr.org> wrote:In my opinion for the purposes of tracking ownership, nonstandard subdomains should only exist via a cname record.Example of Lynwood (doing it correctly in my opinion)speedtest.ampr.org<http://speedtest.ampr.org/>. 300 IN CNAME kb3vwg-010.ampr.org<http://kb3vwg-010.ampr.org/>.kb3vwg-010.ampr.org<http://kb3vwg-010.ampr.org/>. 300 IN A 44.60.44.10In theory speedtest.ampr.org<http://speedtest.ampr.org/> could have a direct A record.. such asspeedtest.ampr.org<http://speedtest.ampr.org/>. 300 IN A 44.60.44.10But that is problematic.Just my 2 cents.On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net <44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>> wrote:Dear 44Net community,It’s been just over two months since we launched the new Portal. It camewith, as you have seen, some major bumps. Today, ARDC is resolving, atleast temporarily, one of those hurdles: administrative access tosubdomains.As of today, anyone who had a subdomain with ampr.org<http://ampr.org/> before the launchof the new Portal on April 3, 2024, will, for now, have full access totheir DNS records. This includes subdomains that fall outside of ourpreferred format of callsign.ampr.org<http://callsign.ampr.org/>.This administrative access still depends on call sign verification,which requires confirming given name, family name, email, and validamateur radio license. This step helps us ensure that the network isbeing used by valid amateur radio operators. During our recent work,we’ve found several bad actors, which is both unfair to the communityand a security risk.We’ve also made a functional change to the portal: once a call sign isverified, you are now automatically able to create a subdomain with theformat of callsign.ampr.org<http://callsign.ampr.org/>. All other new requests for subdomains thatfall outside of that format (e.g., foo.ampr.org<http://foo.ampr.org/>, which I’ll refer to asnonstandard subdomains for brevity) will require review and approval.Please note that we will be limiting the number of nonstandardsubdomains going forward. Thus, if you have one (or, in some cases, manymore), please consider it temporary. You can currently create as manysecond-level subdomains as you want—e.g., foo.callsign.ampr.org<http://foo.callsign.ampr.org/>,bar.callsign.ampr.org<http://bar.callsign.ampr.org/>, etc.We are working on a more official policy around subdomains usingampr.org<http://ampr.org/>. As promised at the recent regional coordinators' meeting, wewill ensure you can see this policy before officially implementing it.We will also provide a transition period, likely many months, for usersto edit their entries before official deprecation. This is, ultimately,what we should have done initially, and we take responsibility for notfollowing a better process and, instead, rolling out this change withouttaking proper preparatory steps.Some of you may be wondering why we are making this change in the firstplace. It is because, without doing so, we end up in our current andvery unwieldy situation: a database of over 51,000 DNS entries, mostwithout knowledge of who they belong to, accumulated over at least adecade, with very few entries currently in use. If we aim to increasethe usage of 44Net, then we need a system where we understand ownershipand are able to provide an efficient service where we can addressproblems as they arise.For now, we hope that this helps to unblock anyone that currently feelsblocked, while also providing an ample notice for changes that arecoming down the pipeline at a later, though likely not-so-distant date.If you have questions, please ask.Many thanks,Rosy--Rosy Schechter - KJ7RYVExecutive DirectorAmateur Radio Digital Communications (ARDC)ardc.net<http://ardc.net/>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave@mailman.ampr.org_______________________________________________44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave@mailman.ampr.org_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org

1 0

Re: Update re: subdomains
by lleachii＠aol.com 13 Jun '24

13 Jun '24

There is no such thing. Maybe you misunderstand what I'm referring to. We are responsible for our own stations during an emergency in the US (hence why ARDC shouldn't mess with MY settings since I may be disconnected from them when discovering it). I assumed this was international at any given moment. If you have no clue or understanding, you should remain silent in that case. It's easier to be quiet and learn tan to be loud and wrong. -------- Original message --------From: pete M via 44net <44net(a)mailman.ampr.org> Date: 6/13/24 09:53 (GMT-05:00) To: Amprnet 44 Net <44net(a)mailman.ampr.org> Subject: [44net] Re: Update re: subdomains Since when is it OK to use 44net for any other use than ham experimentation on that IP address space?If you use a network for experimentation as a primary link for emergency you miss understood the use of the 44net.Yes it is appealing to do so. But be aware that this network can and will change over the time. Some stuff will break. Some will cease to exist. And new stuff will appear.ARDC is not a ISP nor a commercial entity that provide professional services for commercial grade networking. If the network infrastructure you use is primary for life safety, better go the commercial route. If you are a BACKUP in case everything else is gone. That is not the same thing, and the authority dealing with ham should better know about it.This is my opinion of the situation and note ARDC view. I am not talking for them.PierreVE2PF________________________________________De : Chris via 44net <44net(a)mailman.ampr.org>Envoyé : 13 juin 2024 06:47À : lleachii(a)aol.comCc : Amprnet 44 NetObjet : [44net] Re: Update re: subdomainsHello Lynwood,For the record, I have never made any derogatory remarks to you publicly or in private, you completely misconstrued an offer of help I made for reasons I still do not understand. If you wish to discuss this then I am more than happy to, as I would like to clear up any misunderstandings. Please feel free to contact me off-list as this is not the appropriate place for such discussions.With regards to the rest of your email, I refer you to Rosy’s email to this list which explains the current situation. I am sure she would be more than happy to answer any questions you may have.Kind Regards,Chris - G1FEF—ARDC AdministratorWeb: https://www.ardc.net/On 13 Jun 2024, at 11:10, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote:Chris,I have logged in and understand that the portal system says "with user".What I do not understand is this - * Is there a policy in place? * Will you then proceed to delete these "non callsign" entries once one it is implemented?You all may not have noticed, but I'm being very particular NOT to agree to new DNS terms, IP record changes, etc. (i.e. stuff that preexisted your control of this domain and space). Before I post the text (since it's quite similar to what I read posted by an ARDC employee), I will not quote it at this time. Please offer clarity (publicly, because you have said some derogatory things to me before in private which you seem uncourageous to say publicly - so I'm uncomfortable) before I proceed.I also need ARDC to understand that there will be concerns if you then proceed to delete entries I've made very clear I wish to continue use of (as well as my GOVERNMENTAL RACES SPONSOR). I've explained the nature of your inheritance, but somehow - I need to clarify this seemingly contrary policy before I agree.Please note, my records also show and indicate this "policy" is not because of the numerous amount of DNS records - I will not discuss this further here. Anyone seeing the updates on portal ticket clearing statistics can see that. And if your answer is YES to the latter question above - common sense also provides that you can just as well identify and handle them, as you would need to do so to accomplish that task. Yet, a hassle for records I'm in fact attempting to claim (over and over - obviously I'm making records that I'm clamming them)?Since I pray common scene now prevails - I simply ask you not hold my records "hostage" in this commercialization game.Thanks and 73,LynwoodKB3VWG(reviewed by a Sensitivity Expert, please be courageous and secretly report the entire text as a Code of Conduct violation if you desire, including this disclaimer to show your ignorance - yes this portion was reviewed as well)On Wednesday, June 12, 2024 at 03:17:04 PM EDT, Chris via 44net <44net(a)mailman.ampr.org> wrote:Lynwood,Please check your tickets, I replied 2 day ago, just waiting on your reply.73,Chris - G1FEFOn 12 Jun 2024, at 18:43, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote:I have not been allowed to make those edits.On Wednesday, June 12, 2024 at 01:36:45 PM EDT, Steve L via 44net <44net(a)mailman.ampr.org> wrote:In my opinion for the purposes of tracking ownership, nonstandard subdomains should only exist via a cname record.Example of Lynwood (doing it correctly in my opinion)speedtest.ampr.org<http://speedtest.ampr.org/>. 300 IN CNAME kb3vwg-010.ampr.org<http://kb3vwg-010.ampr.org/>.kb3vwg-010.ampr.org<http://kb3vwg-010.ampr.org/>. 300 IN A 44.60.44.10In theory speedtest.ampr.org<http://speedtest.ampr.org/> could have a direct A record.. such asspeedtest.ampr.org<http://speedtest.ampr.org/>. 300 IN A 44.60.44.10But that is problematic.Just my 2 cents.On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net <44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>> wrote:Dear 44Net community,It’s been just over two months since we launched the new Portal. It camewith, as you have seen, some major bumps. Today, ARDC is resolving, atleast temporarily, one of those hurdles: administrative access tosubdomains.As of today, anyone who had a subdomain with ampr.org<http://ampr.org/> before the launchof the new Portal on April 3, 2024, will, for now, have full access totheir DNS records. This includes subdomains that fall outside of ourpreferred format of callsign.ampr.org<http://callsign.ampr.org/>.This administrative access still depends on call sign verification,which requires confirming given name, family name, email, and validamateur radio license. This step helps us ensure that the network isbeing used by valid amateur radio operators. During our recent work,we’ve found several bad actors, which is both unfair to the communityand a security risk.We’ve also made a functional change to the portal: once a call sign isverified, you are now automatically able to create a subdomain with theformat of callsign.ampr.org<http://callsign.ampr.org/>. All other new requests for subdomains thatfall outside of that format (e.g., foo.ampr.org<http://foo.ampr.org/>, which I’ll refer to asnonstandard subdomains for brevity) will require review and approval.Please note that we will be limiting the number of nonstandardsubdomains going forward. Thus, if you have one (or, in some cases, manymore), please consider it temporary. You can currently create as manysecond-level subdomains as you want—e.g., foo.callsign.ampr.org<http://foo.callsign.ampr.org/>,bar.callsign.ampr.org<http://bar.callsign.ampr.org/>, etc.We are working on a more official policy around subdomains usingampr.org<http://ampr.org/>. As promised at the recent regional coordinators' meeting, wewill ensure you can see this policy before officially implementing it.We will also provide a transition period, likely many months, for usersto edit their entries before official deprecation. This is, ultimately,what we should have done initially, and we take responsibility for notfollowing a better process and, instead, rolling out this change withouttaking proper preparatory steps.Some of you may be wondering why we are making this change in the firstplace. It is because, without doing so, we end up in our current andvery unwieldy situation: a database of over 51,000 DNS entries, mostwithout knowledge of who they belong to, accumulated over at least adecade, with very few entries currently in use. If we aim to increasethe usage of 44Net, then we need a system where we understand ownershipand are able to provide an efficient service where we can addressproblems as they arise.For now, we hope that this helps to unblock anyone that currently feelsblocked, while also providing an ample notice for changes that arecoming down the pipeline at a later, though likely not-so-distant date.If you have questions, please ask.Many thanks,Rosy--Rosy Schechter - KJ7RYVExecutive DirectorAmateur Radio Digital Communications (ARDC)ardc.net<http://ardc.net/>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave@mailman.ampr.org_______________________________________________44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave@mailman.ampr.org_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org

1 0

Re: Update re: subdomains
by lleachii＠aol.com 13 Jun '24

13 Jun '24

Lastly, I guess it was forgotten we all can access the DNS records. I want to highlight something of major concern.I'm begging Rosy to stop doing this misquote of the original count or records to make it seem as if there's today an issue under a new portal system that now handles DNS records. I have no clue why this falsehood keeps being perpetuated to the 44net family. Again if they can be handled post-policy, they take utlization the same resources/CPU/skill to identify and handle now.- KB3VWG -------- Original message --------From: lleachii--- via 44net <44net(a)mailman.ampr.org> Date: 6/13/24 06:33 (GMT-05:00) To: Chris <chris(a)ardc.net> Cc: Steve L <kb9mwr(a)gmail.com>, Amprnet 44 Net <44net(a)mailman.ampr.org> Subject: [44net] Re: Update re: subdomains As I've already explained, after a 4-year process, we have been approved for governmental installation. Your so-called "policy" is causing concerns where we actually use RF for emergencies.I would need to know when I need to notify organizations that this policy affect their emergency communications plansI need to schedule thisOur sponsor's approval process may be canceled anyway (i.e. your network seems to just make arbitrary changes without even considering the infrastructure, users, usage, DOWNTIME, etc.) - for something like DNS that usually remains untouched once setYou can just imagine other logistics particular to those points. I'm not sure if you think people merely "play radio" or what infrastructure, but please keep in mind people who really have concerns when you send these emails from California (or whatever radio vacation spot foundation funds accommodate communication).Til this date, nobody has once said when changes may actually affect the users, which I find scary for folks who claim to work professionally in the IT field. Most times, we only find out after issues have occurred/discovered. Why am I the only person who finds that odd?- KB3VWG- KB3VWG On Thursday, June 13, 2024 at 06:11:09 AM EDT, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote: Chris,I have logged in and understand that the portal system says "with user".What I do not understand is this -Is there a policy in place?Will you then proceed to delete these "non callsign" entries once one it is implemented?You all may not have noticed, but I'm being very particular NOT to agree to new DNS terms, IP record changes, etc. (i.e. stuff that preexisted your control of this domain and space). Before I post the text (since it's quite similar to what I read posted by an ARDC employee), I will not quote it at this time. Please offer clarity (publicly, because you have said some derogatory things to me before in private which you seem uncourageous to say publicly - so I'm uncomfortable) before I proceed.I also need ARDC to understand that there will be concerns if you then proceed to delete entries I've made very clear I wish to continue use of (as well as my GOVERNMENTAL RACES SPONSOR). I've explained the nature of your inheritance, but somehow - I need to clarify this seemingly contrary policy before I agree.Please note, my records also show and indicate this "policy" is not because of the numerous amount of DNS records - I will not discuss this further here. Anyone seeing the updates on portal ticket clearing statistics can see that. And if your answer is YES to the latter question above - common sense also provides that you can just as well identify and handle them, as you would need to do so to accomplish that task. Yet, a hassle for records I'm in fact attempting to claim (over and over - obviously I'm making records that I'm clamming them)?Since I pray common scene now prevails - I simply ask you not hold my records "hostage" in this commercialization game.Thanks and 73,LynwoodKB3VWG(reviewed by a Sensitivity Expert, please be courageous and secretly report the entire text as a Code of Conduct violation if you desire, including this disclaimer to show your ignorance - yes this portion was reviewed as well) On Wednesday, June 12, 2024 at 03:17:04 PM EDT, Chris via 44net <44net(a)mailman.ampr.org> wrote: Lynwood,Please check your tickets, I replied 2 day ago, just waiting on your reply.73,Chris - G1FEFOn 12 Jun 2024, at 18:43, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote: I have not been allowed to make those edits. On Wednesday, June 12, 2024 at 01:36:45 PM EDT, Steve L via 44net <44net(a)mailman.ampr.org> wrote: In my opinion for the purposes of tracking ownership, nonstandard subdomains should only exist via a cname record.Example of Lynwood (doing it correctly in my opinion)speedtest.ampr.org. 300 IN CNAME kb3vwg-010.ampr.org.kb3vwg-010.ampr.org. 300 IN A 44.60.44.10In theory speedtest.ampr.org could have a direct A record.. such asspeedtest.ampr.org. 300 IN A 44.60.44.10But that is problematic.Just my 2 cents.On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net <44net(a)mailman.ampr.org> wrote:Dear 44Net community, It’s been just over two months since we launched the new Portal. It came with, as you have seen, some major bumps. Today, ARDC is resolving, at least temporarily, one of those hurdles: administrative access to subdomains. As of today, anyone who had a subdomain with ampr.org before the launch of the new Portal on April 3, 2024, will, for now, have full access to their DNS records. This includes subdomains that fall outside of our preferred format of callsign.ampr.org. This administrative access still depends on call sign verification, which requires confirming given name, family name, email, and valid amateur radio license. This step helps us ensure that the network is being used by valid amateur radio operators. During our recent work, we’ve found several bad actors, which is both unfair to the community and a security risk. We’ve also made a functional change to the portal: once a call sign is verified, you are now automatically able to create a subdomain with the format of callsign.ampr.org. All other new requests for subdomains that fall outside of that format (e.g., foo.ampr.org, which I’ll refer to as nonstandard subdomains for brevity) will require review and approval. Please note that we will be limiting the number of nonstandard subdomains going forward. Thus, if you have one (or, in some cases, many more), please consider it temporary. You can currently create as many second-level subdomains as you want—e.g., foo.callsign.ampr.org, bar.callsign.ampr.org, etc. We are working on a more official policy around subdomains using ampr.org. As promised at the recent regional coordinators' meeting, we will ensure you can see this policy before officially implementing it. We will also provide a transition period, likely many months, for users to edit their entries before official deprecation. This is, ultimately, what we should have done initially, and we take responsibility for not following a better process and, instead, rolling out this change without taking proper preparatory steps. Some of you may be wondering why we are making this change in the first place. It is because, without doing so, we end up in our current and very unwieldy situation: a database of over 51,000 DNS entries, most without knowledge of who they belong to, accumulated over at least a decade, with very few entries currently in use. If we aim to increase the usage of 44Net, then we need a system where we understand ownership and are able to provide an efficient service where we can address problems as they arise. For now, we hope that this helps to unblock anyone that currently feels blocked, while also providing an ample notice for changes that are coming down the pipeline at a later, though likely not-so-distant date. If you have questions, please ask. Many thanks, Rosy -- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org To unsubscribe send an email to 44net-leave(a)mailman.ampr.org _______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org _______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave@mailman.ampr.org_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org _______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org

1 0

Assistance with Configuring rDNS Records for 44Net Subnets
by Razvan YO6RZV 11 Jun '24

11 Jun '24

Hello everyone, I have a question for those of you who have BGP announced subnets from 44Net, specifically regarding the configuration of rDNS (PTR) records for each IP address within the subnet. Recently, I received an allocation of a /24 subnet, which is announced via my Data Center's ASN. Everything is functioning correctly, but I need to configure rDNS for each IP address. This configuration is essential for hosting email servers to prevent potential issues. Here is a dlint output for my gateway's IP address: root@eye:~# dlint 1.77.32.44.in-addr.arpa ;; dlint version 1.4.0, Copyright (C) 1998 Paul A. Balyoz <pab(a)domtools.com> ;; Dlint comes with ABSOLUTELY NO WARRANTY. ;; This is free software, and you are welcome to redistribute it ;; under certain conditions. Type 'man dlint' for details. ;; command line: /usr/bin/dlint 1.77.32.44.in-addr.arpa ;; flags: inaddr-domain recursive. ;; using dig version 9.9.5 ;; run starting: Fri Jun 7 15:10:37 EEST 2024 ;; ============================================================ ;; Now linting 1.77.32.44.in-addr.arpa ERROR: no name servers found for domain 1.77.32.44.in-addr.arpa === ;; Now linting 32.44.in-addr.arpa ;; Checking serial numbers per nameserver ;; 2024060700 ns1.de.ardc.net. ;; 2024060700 ns.ardc.net. ;; 2024060700 a.gw4.uk. ;; 2024060700 ns2.us.ardc.net. === Based on this output, I believe that the rDNS setup needs to be handled by the ARDC staff. However, I wanted to confirm this to ensure I proceed correctly. I reached out to Chris off-list and received the following response: "You already have the subdomain yo6rzv.ampr.org setup; you can add DNS records under there. For each A record, a PTR record is automatically added in the reverse zone." From my understanding, this does not fully address my requirements, since for example, if IP Address 44.32.77.2 needs to have the rDNS set to -> something.yo44.net, this will not help. I am aware that Chris and the ARDC staff are currently handling a high volume of tickets and requests through the portal. Therefore, I am turning to the community for assistance to avoid adding more to their workload. I appreciate any guidance you can provide and apologize in advance if this question has been addressed previously. I could not find relevant information in my email archive. Thank you for your assistance. Best regards, Razvan - YO6RZV

3 4

git.ampr.org admins?
by kc8qba＠wildtky.com 09 Jun '24

09 Jun '24

Does anyone know who has admin permissions on the git.ampr.org instance? I tried to create a new account but accidentally entered the wrong email address & would like to get it fixed. Best, -Steve kc8qba

3 2

44Net Update, June 7, 2024
by Rebecca Key 07 Jun '24

07 Jun '24

** *Hey Everyone,* *** Below are some updates from this week regarding the 44Net Portal: ** As of today, about 30 new portal tickets remain (40% decrease from last week), and about 266 tickets are open and awaiting response (5% decrease from last week). Since April 3, we have closed 634 tickets (12% increase from last week). For those of you interested in being a beta tester for the 44Net VPN, reach out to Adam at adam(a)ardc.net <mailto:adam@ardc.net>to get set up! Finally, as many of you have asked about ways to help with the portal (https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-… you come across something in the docs that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net <mailto:newportal@ardc.net>. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Users Complaining About Domains Failing and No Instructions
by Charles J. Hargrove 07 Jun '24

07 Jun '24

If you go through the list of domain records, you will see many that have not been claimed. Match them up to users who have yet to start or finish the LoT/Trust verification steps and it is still a headache in the making with many more unnecessary tickets that have not even hit yet. As I said many times in the past, get the coordinators on-board so that we can clear the tickets of those who are in our areas. We have acted as mentors and point of contact for many years and know these users quite well. I have one user in NY that is a trustee for two different club calls as well as his own. He finally got his verification tickets through, but now the routing to the two club calls are failing because he did not know what to do about them. Taking this whole process out of the hands of the coordinators has taken my normally less than 30 minute time out of my hands and tossed these users into a faceless mosh pit. Two phone conferences within 10 days last month and there does not seem to be any movement in including the coordinators to make this move quickly. Comments and mea culpas of the April 3rd surprise has not really corrected itself over 60 days later. -- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM http://www.nyc-arecs.org NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32 "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan

1 0

encap txt file unobtainable
by vk1kw＠netspace.net.au 07 Jun '24

07 Jun '24

Hello Kun, Sunce around May 3 I have been unable to get a copy of the full encap file. I can access the HTML portal ok. My four sources are not working. What am I missing? Mail - no encap file from the portal. Jnos2 wget ftp script I have used for several years has now failed. Unable to manually download encap from the portal as there seems to be no obvious link supplied. Ampr-rip2 is not working and there is very little configuration on the net. I have downloaded the file, installed it and run it but nothing happens. (var/lib/encap.txt file is there empty) Any info from the group on ampr-rip2 setup would be appreciated please. (it is behind a firewall and all other JNOS2 functions are working) Many thanks Rob vk1kw(a)netspace.net.au <mailto:vk1kw@netspace.net.au>

2 1

Re: DNS PTR record
by KUN LIN 03 Jun '24

03 Jun '24

I am thinking about update rDNS for an assigned IP. Kun ________________________________ From: Chris <chris(a)ardc.net> Sent: Monday, June 3, 2024 13:05 To: KUN LIN <dnwk(a)linkun.info> Subject: Re: [44net] DNS PTR record Hello Kun, Yes the PTR record option is fully functional, as are all the record types listed. What are you trying to achieve though? Kind Regards, Chris - G1FEF — ARDC Administrator Web: https://www.ardc.net On 3 Jun 2024, at 18:41, KUN LIN via 44net <44net(a)mailman.ampr.org> wrote: I saw on the portal there is an option to add PTR record in DNS. Is it functional? How do I add PTR records? I am not sure how to construct it that will be accepted by the portal. Kun _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org> To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>

2 1

DNS PTR record
by KUN LIN 03 Jun '24

03 Jun '24

I saw on the portal there is an option to add PTR record in DNS. Is it functional? How do I add PTR records? I am not sure how to construct it that will be accepted by the portal. Kun

1 0

DNS claims on the new portal
by Chris 01 Jun '24

01 Jun '24

Hello 44Net, If you have made a DNS claim on the new portal please read this email as you may need to make a change… If you are logged in and navigate to this page on the new portal: https://portal.ampr.org/domain/records/1 You are able to view all the 51,000+ DNS records that are currently in the zonefile for ampr.org If you click the “Claim” icon next to a DNS record, you are able to claim the record as belonging to you, however this may not be the best method for doing this. If you have multiple DNS records you wish to claim under a common subdomain, or you plan on adding additional records under a subdomain, then you should instead do the following: Select “My subdomains” from the “DNS” menu, then click the “Request a subdomain” button. On the next page select “ampr.org” as the domain and enter the subdomain you wish to create. When you click the “Create request” button, this will create a ticket requesting creation of the subdomain. Once approved, your subdomain will be created and (importantly) any existing DNS records under the subdomain will be automatically pulled in. Here is an example: Say the following DNS records exist, unclaimed in the database: xyz.ampr.org A 44.45.46.47 www.xyz.ampr.org CNAME xyz.ampr.org. mail.xyz.ampr.org MX 10 mail.myservers.com. a.b.c.xyz.ampr.org A 44.43.42.41 You request the subdomain “xyz.ampr.org”, when it is approved, the subdomain is created and will appear on your account under the “DNS” menu “My subdomains”. All the above records will automatically be pulled into the subdomain and if you click on the “Resource records” icon under the “Actions” column you will see them all listed, along with an “Add a resource record” button so you can add additional records under the subdomain. For those that have already created multiple DNS claim requests, please navigate to “View my tickets” from the “Tickets” menu and delete all these tickets, then follow the instructions above to create a subdomain (or subdomains if you have records under more than one subdomain). The DNS claim button is really so that individual records, not under a common subdomain, can be claimed and there is no requirement to add additional records. If any of the above is not clear, or you have any questions, please do ask, either here or by creating a support ticket on the portal. 73, Chris - G1FEF — ARDC Administrator Web: https://www.ardc.net

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net