I am with David on the side of the other digital network that need support like allstarlink and the other. Allstarlink are using 44 net space and are giving a great service to link repeaters. I already give to them from time to time. The Brandmeister server team could also be supported. (As an admin of the canadian server I do have some personal interest. ) Pierre VE2PF ________________________________________ De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de Rosy Wolfe via 44Net <44net(a)mailman.ampr.org> Envoyé : 29 septembre 2020 12:13 À : David Ranch; AMPRNet working group Cc : Rosy Wolfe Objet : Re: [44net] Inviting you to ARDC Grantmaking Survey + Community Jitsi Call Hi David, Happy to do it. The aim here is to open up communication, and I'm glad to see it's already working! Copy this. One of the questions in the survey is something like, "What are the questions we should have asked and what are your answers?" I appreciate you offering your answer regarding the supporting the 44net address space here. working through their ISP These are all excellent ideas and speak to some that I've also heard come up internally. Thank you again, David! Looking forward to hearing from others on 44net as well. Warmly, Rosy Rosy Wolfe Executive Director Amateur Radio Digital Communications (ARDC) ampr.org On 9/29/20 8:42 AM, David Ranch wrote: _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

For the IRLP network, in the last roughly 18 months, we have issued VPN connections for over 230 repeaters, plus roughly 60% of our backend infrastructure is using BGP routed 44-net addresses. Basically from service providers in Chicago, Sydney and Indianapolis. Those cities were chosen because the lion's share of the IRLP network is in North America and Australia. There are a number of IRLP nodes in .UK, but we found that performance through Chicago is more than adequate. We could light up service from additional locations in the future, but we try to use our existing infrastructure locations, to keep the costs down. We started using 44-net for IRLP back in 2015. A few folks have been using 44 for far longer. -k9dc

I would have interest in using some of this space with AREDN. Keith - AI6BX On 10/3/20, 9:55 AM, "44Net on behalf of Corey Dean via 44Net" &lt;44net-bounces+ai6bx=arrl.net(a)mailman.ampr.org on behalf of 44net(a)mailman.ampr.org&gt; wrote: Part of the BrandMeister network is using some of the 44 range. The main bm webpage is using it. I also use a /24 from the East Coast of the USA for digital voice dmr services. That is also broken out to smaller dinners so that different users and developers who only wanted to be in the 44 range for testing. Corey n3fe On Sat, Oct 3, 2020 at 12:48 PM Dave Gingrich via 44Net < 44net(a)mailman.ampr.org&gt; wrote: _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

I am 100% with you. I don't count myself as top sys admin. But I am far from being a noob. And I have been struggling to have Ipip or other ways of connecting to the net. I have multiple site connected by VPN to my vps . I run multiple wireless link with fallback to lte modem. In case of a trouble with the link and yet, the only way I think I will achieve a stable way to have a connection and 44 net IP will be by bgp. That bring that I need a /24 at a minimum. Do I need a /24? Not at first and I hope I will be able to have other hams in my region to take some of my /24 ( will give them with the VPN server) but frankly this also mean the I will be responsible for there action on the 44 net. And that is putting some pressure on me. Téléchargez Outlook pour Android<https://aka.ms/ghei36> ________________________________ From: 44Net &lt;44net-bounces+petem001=hotmail.com(a)mailman.ampr.org&gt; on behalf of Toussaint OTTAVI via 44Net &lt;44net(a)mailman.ampr.org&gt; Sent: Wednesday, October 7, 2020 9:27:49 AM To: 44net(a)mailman.ampr.org &lt;44net(a)mailman.ampr.org&gt; Cc: Toussaint OTTAVI &lt;t.ottavi(a)bc-109.com&gt; Subject: Re: [44net] Inviting you to ARDC Grantmaking Survey + Community Jitsi Call Le 03/10/2020 à 18:55, Corey Dean via 44Net a écrit : Here are some quick and dirty stats : XLX is an open-source digital gateway used all over the world to interconnect D-Star and DMR repeaters (and many other protocols) XLX API provides a "hosts" file of all registered XLX nodes with their IP This file has approx. 1700 lines. Due to triple REF, DCS, XRF naming, we can assume there are roughly 560 independent nodes. The file contains only 36 entries using AMPR 44.x IP addressing, and among them, only 12 are unique *-> Only 2% of the XLX-connected reflectors are using AMPR addresses !!!* And this is only for reflectors (=servers), who are managed by people with more than average skills. I didn't find how to obtain stats for all the repeaters connected to all the reflectors, but adoption rate will be even lower ! COMMENTS : - AMPR addressing is used on country-wide servers, and by isolated teams around the world (including myself, HI) mostly because people who maintain servers have the skills and equipment to do that. - We still have some work until mass adoption by the local reflectors and repeaters SysOps - And even more work for mass adoption by any HAM in the world... CONCLUSION : As I already said, IMHO, our #1 goal should be : make AMPR addressing easier to use, both for local SysOps/teams, and for end users. 73 de TK1BI _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

Le 07/10/2020 à 22:43, Tony Langdon via 44Net a écrit : I'm also living on an island, even if it's a bit smaller and closer from the continent than yours, HI :-) Here's the setup here : - A VPS server at Vultr for $5/month (but I think the $2.5/month instance would do the job, too). The VPS is located in Paris. It does the BGP announcement, and tunnels all our public subnets (currently, 44.190.11.0/24) to our local data center on the island. - The local TKNet data center is composed of a dozen of VMs (VPN gateway, WWW, XLX, Asterisk, Nagios, Netbox, ADSB, etc...) and physical machines (NAS, AMBE servers for XLX and Asterisk gateway). It's currently hosted in my business space in the data center of Ajaccio (on the island). I can afford hosting it for free in my business DC, but any second-hand physical server, with Open-Source virtualization distribution, and a fiber connection to Internet with just one fixed IP would do the job. - In the DC, the main virtual machine is a gateway router : it gets traffic from the tunnel from Paris, it has two local VLANs on 44.168 and 44.190 for local machines, it handles OpenVPN/Wireguard tunnels to remote sites, and does all the routing and firewalling. - As all is virtual, we can host as many VMs as we need at no additional cost. This allows for better separation of functions, and allow great experiments (just pop a new VM, then install and test whatever you want on it) Assuming quite any sysop / sysadmin team can get a second-hand server, install ProxMox virtualization on it, then host it in any location with a fiber and a single fixed IP, the only cost for that infrastructure is $5/month for the Vultr VPS, for an unlimited number of VMs and remote sites (all deserved with 44net addresses). For non-profit associations, I think this is better than all-VPS (because even if Linux is a fantastic army knife, it's difficult to put too much functions on a single machine, and adding any additional VPS costs some $$$) The main idea there is that there are two separated functions, at different layers of the network ISO model, that can (and probably must) be handled separately, in different locations and/or by different people : - Routing (eBGP announcement for public subnets, IP-IP tunelling or iBGP routing for HamNet, VPNs to remote locations, ...) - Applications / services (XLX, IRLP, Echolink, digital and analog repeaters, etc...) For the system to be really easy to deploy and use for everybody, sysops/sysadmins who deploy applications (a repeater, a reflector, a server) would not have to bother too much with complex routing. They just would have to configure a 44.x IP on their LAN interface, and connect it to a "router" (a Linux or OpenWRT system, running on a VM or a $20 appliance, with a pre-defined configuration). At home, a Raspberry Pi or equivalent, with two network adapters, would allow everybody to have 5 real fixed public IPs in 44.x range, that are independent from their current ISP. No need for a fixed ISP IP. No more "port openings" on tricky Internet boxes. And no more headaches when moving from an ISP to another. 73 de TK1BI

On Tue, Sep 29, 2020 at 9:15 AM Rosy Wolfe via 44Net &lt;44net(a)mailman.ampr.org&gt; wrote: I am wondering if you can describe the ways you have been able to utilize the ARDC Technical Advisory Committee related to these ideas that you have heard come up internally and how you plan to use the TAC going forward. Tom KD7LXL

David Ranch via 44Net &lt;44net(a)mailman.ampr.org&gt; writes: As Rosy said in her reply, thanks much for jumping in with these thoughts. I'll add comments about two specific things we've already done or are doing specifically in support of 44Net that may not be top of her mind. One of the first things we worked on after Brian passed was formalizing our relationship with Chris, G1FEF, who had taken on various 44Net admin responsibilities as a volunteer. We now pay him as a contractor to administer much of our infrastructure. That includes core 44Net assets, as well as some software we're using to run ARDC itself. Part of our statement of work with Chris relates to possible 44Net improvements, and I'm sure that we can and will allocate funds to address some number of such improvements over time. More discussion about what's actually needed and with what sense of priority would be awesome input for us to hear through the survey, upcoming "town hall" meeting, etc. Second, we're currently working through the legal issues associated with making grants to non-US entities, specifically in support of a grant request for hardware improvements to packet infrastructure in Europe. As we've previously communicated, broadening the scope of grant recipients beyond other 501(c)3 charities or equivalent tax status recipients in the US requires significant legal and financial process work. There are several "categories" of recipients, each of which will require different chunks of work on our part to set up. ARDC is determined to get to the point where we can make grants to non-incorporated groups and potentially even individuals in large part because that's what we need to be able to grant funds more broadly for things like on-air 44net assets around the world. Rosy and I are "on it", but it's neither easy nor fast... and my part of the work is being done 100% as a volunteer. Thank you all for your continued patience! 73 - Bdale, KB0G ARDC Treasurer / CFO