Just to clarify. 44.168.x.y/16 IS ROUTED via BGP on Internet. But the firewall is blocking most of the communications from outside the 44 world. 73 Remi F6CNB N5CNB Message: 1 Date: Wed, 7 Oct 2020 14:51:12 +0200 From: Toussaint OTTAVI &lt;t.ottavi(a)bc-109.com&gt; To: &lt;44net(a)mailman.ampr.org&gt; Subject: Re: [44net] Education about networking (Was Re: Inviting you to ARDC Grantmaking Survey + Community Jitsi Call) Message-ID: &lt;68fa5d64-3b71-2326-3ab5-1a20b0c61d0d(a)bc-109.com&gt; Content-Type: text/plain; charset="utf-8"; format=flowed Le 05/10/2020 ? 10:40, Rob Janssen via 44Net a ?crit?: +1 We are using a similar topology here. Anyway, the details of our implementation differ : - We are currently testing Wireguard as a replacement for OpenVPN (too much odd behaviors with OpenVPN) - Our endpoints are $20-$50 OpenWRT routers. We configure them, and send them to the local users / sites. - On any site, we typically route /29 (5 usable IPs) on small sites and /28 (13 usable IPs) on more important sites - We typically route a 44.190 subnet for things that requite public Internet addressing (D-Star, DMR, XLX) (as defined by DG8NGN), and a 44.168 subnet for all ham-related machines. - Any site can have a 44.190 subnet, a 44.168 subnet, or both. - There's no more dual adressing. All machines only have a 44.168 or 44.190 IP. Except for the central gateway, no machine / no server is using public Internet IP anymore. - Due to the highly experimental nature of the network and the tiny size, we do not have full internal dynamic routing yet, and we use static routing for now. Our dynamic experiments on some sites are using OSPF. - 44.190 subnet is routed on Internet with BGP via a Vultr VPS (which costs $5/month, is easy to implement, and is independent of local ISP BGP capabilities) - 44.168 subnet is currently not routed on Internet via BGP, because this does not have much sense. For now, it's not routed outside of our island. But we plan to implement IP-IP routing on the central gateway (as we had in our previous iteration) Maybe we should try to identify all people using this kind of topology all over the world (what I called a "Regional" or "local" gateways) ? Then, we may try to "normalize" our implementations : - Adoption of dual-addressing : 44.190 for things that require Internet access, and 44.<country> for other things - Choice of internal VPN tunneling protocol(s) - Choice of internal routing protocol - Choice of external routing method (tunnels and routing between gateways) 73 de TK1BI ------------------------------ Message: 2 Date: Wed, 7 Oct 2020 15:27:49 +0200 From: Toussaint OTTAVI &lt;t.ottavi(a)bc-109.com&gt; To: &lt;44net(a)mailman.ampr.org&gt; Subject: Re: [44net] Inviting you to ARDC Grantmaking Survey + Community Jitsi Call Message-ID: &lt;6833ec63-d59d-530b-3ffa-ef2b5585a99f(a)bc-109.com&gt; Content-Type: text/plain; charset="utf-8"; format=flowed 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 ------------------------------ Message: 3 Date: Wed, 7 Oct 2020 14:01:29 +0000 From: pete M &lt;petem001(a)hotmail.com&gt; To: AMPRNet working group &lt;44net(a)mailman.ampr.org&gt; Subject: Re: [44net] Inviting you to ARDC Grantmaking Survey + Community Jitsi Call Message-ID: &lt;MWHPR2201MB14551B41D83E8BD2DF4F56A9970A0(a)MWHPR2201MB1455.namprd22.prod.outl ook.com> Content-Type: text/plain; charset="iso-8859-1" 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 ------------------------------ Message: 4 Date: Wed, 7 Oct 2020 09:54:30 -0700 From: Rosy Wolfe &lt;rosy(a)ampr.org&gt; To: Amprnet 44 Net &lt;44net(a)mailman.ampr.org&gt; Subject: [44net] Please let us know if you're coming to Saturday's call! Message-ID: &lt;745510ee-aeb4-0cad-7ace-8ec9abe9b0d5(a)ampr.org&gt; Content-Type: text/plain; charset=utf-8; format=flowed Hi 44net, Given how many people have responded to the survey (68!), I want to make sure that Jitsi can handle the number of people who might show up to our call on Saturday. In service of collecting a head count, please let us know if you're planning to join the call by filling out your name here: https://www.ampr.org/community-meeting/ Many thanks! If it looks like we're going to exceed the 75 person limit, we may switch to a Zoom call. In either case, we're planning on recording the meeting for anyone who can't make it. I'll post information here if anything changes. I'm looking forward to e-meeting many of you and am compiling ideas from your emails and the survey as we speak. All the best, Rosy PS here's the survey link in case you haven't taken it yet: https://www.mysurveygizmo.com/s3/5789610/ARDC-Grantmaking-Feedback-Survey -- Rosy Wolfe Executive Director Amateur Radio Digital Communications (ARDC) ampr.org ------------------------------ Message: 5 Date: Wed, 7 Oct 2020 17:01:41 +0000 From: Ruben ON3RVH &lt;on3rvh(a)on3rvh.be&gt; To: AMPRNet working group &lt;44net(a)mailman.ampr.org&gt; Subject: Re: [44net] Please let us know if you're coming to Saturday's call! Message-ID: &lt;AM0PR01MB3890CE45891B0A0C5286F569D30A0(a)AM0PR01MB3890.eurprd01.prod.exchange labs.com> Content-Type: text/plain; charset="us-ascii" Rosy, If I may give a suggestion: have everyone turn off their camera's and things will go much smoother with Jitsi. Most of the issues come from everyone sharing their camera and having a smallband internet connection, thus filling up that pipe with everyone's camera is a bad idea ;) 73 Ruben ON3RVH -----Original Message----- From: 44Net &lt;44net-bounces+on3rvh=on3rvh.be(a)mailman.ampr.org&gt; On Behalf Of Rosy Wolfe via 44Net Sent: Wednesday, October 7, 2020 18:55 To: Amprnet 44 Net &lt;44net(a)mailman.ampr.org&gt; Cc: Rosy Wolfe &lt;rosy(a)ampr.org&gt; Subject: [44net] Please let us know if you're coming to Saturday's call! Hi 44net, Given how many people have responded to the survey (68!), I want to make sure that Jitsi can handle the number of people who might show up to our call on Saturday. In service of collecting a head count, please let us know if you're planning to join the call by filling out your name here: https://www.ampr.org/community-meeting/ Many thanks! If it looks like we're going to exceed the 75 person limit, we may switch to a Zoom call. In either case, we're planning on recording the meeting for anyone who can't make it. I'll post information here if anything changes. I'm looking forward to e-meeting many of you and am compiling ideas from your emails and the survey as we speak. All the best, Rosy PS here's the survey link in case you haven't taken it yet: https://www.mysurveygizmo.com/s3/5789610/ARDC-Grantmaking-Feedback-Survey -- Rosy Wolfe Executive Director Amateur Radio Digital Communications (ARDC) ampr.org _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net ------------------------------ Message: 6 Date: Wed, 7 Oct 2020 10:17:25 -0700 From: Rosy Wolfe &lt;rosy(a)ampr.org&gt; To: 44net(a)mailman.ampr.org Subject: Re: [44net] Please let us know if you're coming to Saturday's call! Message-ID: &lt;aeffc385-d2ac-781f-b2c5-8bf4c656eeca(a)ampr.org&gt; Content-Type: text/plain; charset=utf-8; format=flowed On 10/7/20 10:01 AM, Ruben ON3RVH via 44Net wrote: things will go much smoother with Jitsi. Most of the issues come from everyone sharing their camera and having a smallband internet connection, thus filling up that pipe with everyone's camera is a bad idea ;) Copy! The suggestion is most welcome. Thank you, Ruben. Rosy Rosy Wolfe Executive Director Amateur Radio Digital Communications (ARDC) ampr.org Rosy Wolfe via 44Net sure that Jitsi can handle the number of people who might show up to our call on Saturday. planning to join the call by filling out your name here: we may switch to a Zoom call. In either case, we're planning on recording the meeting for anyone who can't make it. I'll post information here if anything changes. your emails and the survey as we speak. _________________________________________ ------------------------------ Subject: Digest Footer _______________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net ------------------------------ End of 44Net Digest, Vol 9, Issue 97 ************************************