[44net] Re: Reaching BGP subnets through AmprGW

Hi to the group. One of the project of the TAC this year was to work on a way to links all of the 44net network legs in a better and more effective way. It is a project to add point of presence around the globe to help route between each of them with better route. And at the same time, helping people to connect to the 44net than using the ipip network. ( we are not talking about removing the ipip mesh, just adding way's to connect to the 44 net ip realm ) I cant wait to see the result of that work done by a real good group of people. I was in good health most of the year and was not able to follow the progress of the project. (Still I dont have more than a few good days a week.) So I did not do much in the whole story. So the the TAC keep going strong. Also Chris also worked on another project. When it will come online people will like it a lot! Pierre VE2PF ________________________________________ De : Mike Quin via 44net &lt;44net(a)mailman.ampr.org&gt; Envoyé : 20 décembre 2023 03:55 À : 44net(a)mailman.ampr.org Objet : [44net] Re: Reaching BGP subnets through AmprGW Thank you Bob and Lynwood I’m running ampr-ripd 2.4-1 on a Raspberry Pi (Raspbian 11). I understand the suggestion to just route traffic to these systems via the internet, but that feels like it contradicts how the FAQ describes AmprGW’s features: "It forwards traffic between Internet hosts (including those AMPRNet that are directly connected to the Internet [BGP-routed]) and IPIP tunneled AMPRNet hosts” (https://wiki.ampr.org/wiki/FAQ<https://na01.safelinks.protection.outlook…)mp;reserved=0>). I’m aware that connections between IPIP hosts and the general Internet need to be authorized (by having an DNS A record) does that restriction also apply to BGP-routed parts of 44net? Mike 2M0MQN