Basically, in a fully configured IPIP network most VOIP scenarios
should work without issues.
1. The tunnel system is a full mesh, meaning that your
destinations are directly reachable via the mesh. Any mesh partner
is a P2P VPN, the only drawback is a slightly reduced MTU
For BGP announced destinations, if you route to them via amprgw
you will get a bottleneck at amprgw. If you use your public IP to
reach them, sacrificing your 44net source address in the process,
that bottleneck is gone.
2. If you announce your subnet via BGP, there are 2 scenarios depending on your peers configuration. It is the reverse of the situation from point 1, and outside your control.
3. VPN solutions offert no advantage over the mesh and may increase latency, but you are right, they depend on their server and networking capabilities.
So if your partners are on the mesh, the mesh is the best
solution. For others, your mileage may vary. But at least for BGP
destinations, try to NAT to your public IP instead of tunneling
via amprgw.
Marius, YO2LOJ
Hello,
Did you get any answers for VoIP traffic?I'm interested in testing VoIp.
Frédéric ZULIANF1sxo
Le mar. 21 juin 2022 à 13:52, Ken via 44net <44net@mailman.ampr.org> a écrit :
Hello all,
So I have been assigned a block of IPs and have successfully created a gateway. I am able to pass traffic trough it as expected and it works as one would expect. However...
My intended use case for amprnet includes a lot of VOIP traffic, which as we all know is heavily dependent on latency and bandwidth. I am currrently utilizing the IPIP tunnel approach to connect my gateway into the system.
My questions are,
1. If I deploy my VOIP services on 44Net with my current configuration, what are the pitfalls?
2. If I announce my gateway via BGP will my throughput then be limited to uscd gateway, or will it be based on my connection speed?
3. I know some vpn capabilities have been introduced into the system, I presume that my connection will then be rated based on the connection at the VPN server location.
Thank you so much! I appreciate the opportunity given here to learn and expand my knowledge.
73,
de KC2IDB
_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org
_______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org