44net

44net@mailman.ampr.org

3191 discussions

by Rosy Schechter - KJ7RYV

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

1 year, 8 months

44Net Update, July 3, 2024

by Rebecca Key

** *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 year, 8 months

HTTP 500 error in portal when trying to link my subnet to my gateway

by KUN LIN

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

1 year, 8 months

44Net Update, June 28, 2024

by Rebecca Key

** *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 year, 8 months

Fwd: Code of Conduct report

by Charles J. Hargrove

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

1 year, 8 months

Update re: subdomains

by Rosy Schechter - KJ7RYV

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

1 year, 8 months

Re: How to admin 44.151 ?!

by Main

> 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 year, 8 months

Re: [ARDC:Coordinators] Welcome to coordinators@ardc.groups.io

by Charles J. Hargrove

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 year, 8 months

AMPR WHOIS

by Razvan YO6RZV

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

1 year, 8 months

44Net Update, June 21, 2024

by Rebecca Key

** *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

1 year, 8 months

← Newer
1
...
4
5
6
7
8
9
10
...
320
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net