21 Jun
2022
21 Jun
'22
6:51 p.m.
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
22 Jun
22 Jun
10:24 a.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
1:26 p.m.
Dave K9DC, K9IP - below
My questions are,
1. If I deploy my VOIP services on 44Net with my current configuration, what are the
pitfalls?
The main pitfall with the IPIP mesh is performance. You will be dependent on unknown
links, depending upon what each linker is capable of providing, most of which you will
have no knowledge of, nor any ability to fix anything should you want to.
VoIP does not require a ton of bandwidth. IRLP is probably the biggest consumer of raw
bandwidth (highest quality). But that is only roughly 80 kbps per connection. But it does
require decent jitter performance (changes in latency).
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?
No, If you announce your own prefix using BGP, your prefix is not dependent on UCSD at
all. It will depend on your provider’s backbone and their bandwidth. UCSD is completely
out of the loop. It is just another public IP address.
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.
VPN clients are how the 44-net connections are delivered to member clients. IRLP has
chosen to use TCP based tunnels to a nearby VPN server location. Try a ping or traceeoute
to stn4733.ip.irlp.net. That is a repeater in Indiana connected via AT&T Wireless
cellular connection, through our Chicago hub. We also provide service through our VPN hub
in Sydney, Australia.
Dave K9DC, K9IP
> On Jun 21, 2022, at 07:51, Ken via 44net <44net(a)mailman.ampr.org> 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.
>
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
11 Jul
11 Jul
4:50 a.m.
Hello,
Did you get any answers for VoIP traffic?
I'm interested in testing VoIp.
Frédéric ZULIAN
F1sxo
Le mar. 21 juin 2022 à 13:52, Ken via 44net <44net(a)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(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
7:24 a.m.
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
On 11/07/2022 00:50, Frederic Zulian via 44net wrote:
Hello,
Did you get any answers for VoIP traffic?
I'm interested in testing VoIp.
Frédéric ZULIAN
F1sxo
Le mar. 21 juin 2022 à 13:52, Ken via 44net <44net(a)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(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
_______________________________________________
44net mailing list --44net(a)mailman.ampr.org
To unsubscribe send an email to44net-leave(a)mailman.ampr.org
897
days inactive
917
days old
4 comments
5 participants
participants (5)
-
Dave Gingrich -
Frederic Zulian -
ken＠kc2idb.net -
Marius Petrescu -
Tony Langdon