Actually, any subnet NOT in the RIP broadcasts should be routed to the public internet. If you want to preserve your original 44 address, this should be done via amprgw (but it will be slower), otherwise NAT it via your ISP's public IP if you don't use a BGP announced 44 subnet.
Marius, YO2LOJ
On 10/09/2021 12:04, Toussaint OTTAVI via 44Net wrote:
Le 10/09/2021 à 10:09, Chris Smith via 44Net a écrit :
No, the TAC proposal has not been approved yet. There are many prefixes being announced via BGP (over 400 last time I checked) so routing only 44.190/16 to the internet is probably not a good idea as you will be unable to reach a lot of 44 hosts.
Mailman has been on 44.76.7.7 for several years this is not new.
I never noticed any problem with mailman, because my email address is hosted on a public cloud, and only my provider's mail server sent SMTP messages to mailman. I never tried to access mailman in http before.
Our TKNet network is a "work in progress", and is mostly a "closed" network for now. We announce 44.190.11.0/24 network on Internet. And we route 44.190.0.0/16 to Internet (via our 44.190.11 gateway address). About the rest of the 44 net, we currently do not route it anywhere, because I don't know exactly where and how to route it (IP-IP mesh ? eBGP HamNet ? Via tunnel ? to Internet ?). It seems the right way would be to implement eBGP for HamNet, IP-IP for the rest of the world, and set a default route to public Internet. But I never took time to implement this.
I look forward to the decision of the TAC. We need to simplify and clarify things, HI :-)
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net