I just applied for a /24 out of 44.190/16, to help with this endeavor.
I’ll be announcing the prefix out of a commercial datacenter in Fremont, CA under ASN 7247.
I advise you (like is best for everyone who announces 44Net space on BGP) to make the system part of the IPIP tunnel mesh as well. I.e. make a tunl0 interface and run ampr-ripd on it, register it as a gateway using an extra IP address outside the /24 subnet. Add only the routes received over RIP, not a default route to ampr-gw. Of course you have a default route to your BGP router. This ensures that you are reachable for all AMPRnet hosts as well as normal internet systems, even when they cannot route their traffic transparently over internet themselves.
It looks like we have 3 interested parties in the US and Canada, which would certainly help out for now. It would be nice if someone in the far east or Australia could join in. We always have a large number of users from Thailand, for example.
Rob
On 20/04/18 16:57, Rob Janssen wrote:
I advise you (like is best for everyone who announces 44Net space on BGP) to make the system part of the IPIP tunnel mesh as well. I.e. make a tunl0 interface and run ampr-ripd on it, register it as a gateway using an extra IP address outside the /24 subnet. Add only the routes received over RIP, not a default route to ampr-gw. Of course you have a default route to your BGP router. This ensures that you are reachable for all AMPRnet hosts as well as normal internet systems, even when they cannot route their traffic transparently over internet themselves.
Sounds good.
It looks like we have 3 interested parties in the US and Canada, which would certainly help out for now. It would be nice if someone in the far east or Australia could join in. We always have a large number of users from Thailand, for example.
Just been talking to my VPS host, looks like I can go ahead and get a /24, and he's happy to announce it over BGP. The VPS is in Melbourne, Australia, and already hosts a considerable amount of IRLP and Echolink infrastructure.
Last night, four people requested allocations in 44.190.x.0.
As far as I can tell, one of them (VE7ALB) is in Canada, and the other three (KK6NEI, K4JH, W6KWF) are in California and plan to locate their Echolink relays in the same data center in Fremont, California. I wonder if it would be beneficial for those three to pool their resources in some way? - Brian
On Fri, Apr 20, 2018 at 08:57:34AM +0200, Rob Janssen wrote:
It looks like we have 3 interested parties in the US and Canada, which would certainly help out for now.
-
Brian Kantor -
Rob Janssen -
Tony Langdon