21 Jun
2022
21 Jun
'22
11:24 p.m.
On 21/6/22 9:51 pm, Ken via 44net wrote:
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.
I'm curious, what sort of VoIP?
I
My questions are,
1. If I deploy my VOIP services on 44Net with my current configuration, what are the
pitfalls?
Bandwidth, jitter and latency will all be big issues, especially if you
go out to the Internet.
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?
Be careful. I separated my BGP and IPIP allocations (I have one of
each), to avoid potential routing issues.
BGP connections are routed over the Internet, like any other public IP,
bandwidth limit is whatever feeds your provider. IPIP can only reach
the Internet using the UCSD gateway, and you need DNS entries for every
host that needs Internet access.
Now for some background - about my 2 allocations. My IPIP allocation is
focused on playing over RF, with the IPIP mesh acting like a VPN between
RF connected sites. I'm not interested in Internet connectivity here,
just between other IPIP endpoints.
My BGP routed subnet is a very different beast. It is dedicated to
providing Internet facing services for hams. Among the services it
hosts are an IRLP reflector, multiple Echolink conferences, a D-STAR
reflector, over 100 Echolink proxies and 20 Echolink relays. Here, the
BGP allocation is an easy way of getting a large number of IPs to serve
the ham community.
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com