On 29/7/21 1:38 am, Antonios Chariton (daknob) via 44Net wrote:
To begin with, the TAC sees value in the Intranet and we do not consider it useless. We have a large number of users that agree with this statement and they want this private use case supported. We also believe and try to make connecting to the Internet much easier than it is today. Hopefully we will achieve it with one of the available methods, the Global Backbone / Connectivity Platform. Through this, all private networks like the HAMNET or the Belgium part will be able to connect to each other. But they can do so today, using tunnels and VPNs.
I also see value in the intranet. Here in Australia, the issue of interconnecting ham radio to the Internet is still a significant regulatory one, so my dominant use cases are either providing Internet facing services for hams (44.190.8/24 is dedicated to this), or intranet use (which is what 44.136.76.0/24 is for).
One unanticipated issue I've had is connectivity between by two IP blocks is poor by default (having to go via San Diego from VK isn't ideal!), but I locally solved that problem with a private route over a VPN between here and the host that 44.190.8/24 runs on.
It does flag a potential issue for some other IRLP reflectors though - I can't have an IRLP node with a VPN address, unless I'm careful about routing.
The existing network DOES have problems in some corner cases, and this is definitely the time to look at solutions.
Give me smooth connection between the Intranet and Internet 44net sites running BGP, and I might be inclined to renumber. ;)