44net

44net@mailman.ampr.org

3196 discussions

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

← Newer
1
...
6
7
8
9
10
11
12
...
320
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net