Hi Marius,
Le 29/12/2020 à 23:54, Marius Petrescu a écrit :
I think your xlx example is not the best for the use case of 44net addresses.
It's a good example of pure HAM application not using 44net addresses because of 44net current topology.
For efficient routing and high speed and low latency as required for voip systems, it is much more efficient to do a direct connection to the server on a public interface instead of doing it the 44net way unless the server sits on a BGP announced subnet.
Our XLX is using 44.190 IP adressing. Following DG8NGN rules, it's routed directly to Internet from our data center. Reaching it via its 44.190.11.6 IP address, or via public Internet address, is currently the same latency. Some people are using dual addressing (44net and public Internet). We dropped public Internet completely, and are using only 44.190 IP addresses.
Yes, a 44 BGP network would do the trick, but I am certainly not willing to pay hundreds of USD per month for such an endeavor. BGP peering is not cheap and not readily available in the whole wide world unless it is not piggy backed on another preexisting AS for a select few working in the network business.
Several people here are using Vultr VPS. Our instance costs $5/month, but the $2.5/month instance would do the job, too. Setup is very easy. Also, as said before, we now can afford some operational costs for network infrastructure.
And even in this case, it is of no use for the client to have a 44net address, since it will again need to go the ampr-gw route to take advantage of that IP, while masquerading to the local gateway IP would yield better results.
I do not really understand. The idea of a single ampr-gw in San Diego is from the past. We are now thinking about the future. One idea would be to install several POPs (Points of Presence) in several countries or regional zones. That's what we did here, on our tiny island. We are currently experimenting dual addressing : - 44.168 : standard AMPr adressing, routed via current schemes; no output to Internet, or output via the nearest local NAT gateway - 44.190 : full Internet routing, via BGP, at the same cost as standard Internet routing. IP addresses are announced in Paris (nearest Vultr data center) then routed to our regional POP in Corsica via the most direct path.
We should look into other things, not available or not possible on the regular internet, and voip and regular services are not it.
That's an opinion ;-) But I have another one ;-)
VoIP, digital modes, SDR and other applications using computers are enjoyed by many people, particularly the young ones. The most recent commercial transceivers are SDR (ie, a computer), have Ethernet ports, and use IP. On the other hand, we own a dedicated IP range. My opinion is that every HAM application using IP should use AMPR addressing, or should be able to use it easily. If we have a good routing policy, this would allow to isolate what is pure ham radio (for ex, remote rig control) from what is general purpose Internet. AMPRNet should work as a corporate network, allowing members to communicate with each other, and with the ability to limit / control gateways to wild Internet (required by some regulations in some countries; this would help us achieve this goal)
73 de TK1BI