You are here

Internet speed on Tunnel Client LAN

6 posts / 0 new
Last post
AC0WN
AC0WN's picture
Internet speed on Tunnel Client LAN

Quick question please:
Recently setup a couple of Trevor's Internet Mesh Nodes and sure appreciate the work he did to present this system.  I noticed that the internet speed on the tunnel's LAN is greatly reduced from the speed offered by my home wireless network.  My 2.4G home network runs at about 50 mbps while the speed on the internet when connected to the tunnel's AP is under 5 mpbs.  Any ideas on what causes this and possible ways to correct same?
Many thanks for any input.  :)
73,
julie
ac0wn

KG6JEI
Well not knowing your network

Well not knowing your network layout my first question would be is your internet on your mesh node being routed out another remote mesh node? Or if this is over a cellular link that would be a slow down. A traceroute might help to verify that.

I don’t think anyone has ever profiled tunnel performance speed as is not intended to be a primary path so I am not sure what our max tunnel speeds are (any sort of VPN Connection like tunnels is usually less than wire speed performance)

AC0WN
AC0WN's picture
Traceroute info and clarification

Thank you very much for the quick response!  Please allow me to apologize for the inaccurate description of my network.  I'm a real newbie at AREDN and TCP/IP in general.  My Internet Mesh Node is an exact copy of Trevor's and is currently obtaining internet access via it's AirGateway which is connected wirelessly to my home network on 2.4g.  When I connect directly to my home wireless network on 2.4g I get about 50 mbps speeds.  When I connect to the AP of the Internet Mesh Node and perform the same speed test I get approximately 5 mbps speeds.  Here are traceroutes to www.aredn.org performed in these two configurations:

VIA:  Macbook Pro connected wireless directly to home wireless 2.4g AP.
Traceroute has started…

traceroute to fe4.edge.pantheon.io (23.185.0.4), 64 hops max, 72 byte packets
 1  jm (192.168.1.1)  1.163 ms  0.592 ms  0.567 ms
 2  10.102.64.1 (10.102.64.1)  7.667 ms  7.722 ms  17.701 ms
 3  dtr01flrnor-tge-0-0-0-10.flrn.or.charter.com (96.34.111.152)  12.709 ms  7.931 ms  8.001 ms
 4  96-34-105-74.static.unas.or.charter.com (96.34.105.74)  10.935 ms  27.196 ms  12.195 ms
 5  96-34-111-220.static.unas.or.charter.com (96.34.111.220)  11.591 ms  11.851 ms  12.580 ms
 6  96-34-108-175.static.unas.or.charter.com (96.34.108.175)  16.705 ms  19.226 ms  18.024 ms
 7  96-34-108-160.static.unas.or.charter.com (96.34.108.160)  25.343 ms  22.326 ms  24.378 ms
 8  bbr01snjsca-bue-1.snjs.ca.charter.com (96.34.2.252)  29.722 ms  31.141 ms  31.839 ms
 9  bbr02snloca-bue-6.snlo.ca.charter.com (96.34.0.1)  42.396 ms  39.143 ms  39.834 ms
10  bbr01snloca-bue-4.snlo.ca.charter.com (96.34.0.28)  40.771 ms  37.821 ms  42.998 ms
11  bbr01mtpkca-bue-5.mtpk.ca.charter.com (96.34.0.26)  48.046 ms  47.042 ms  47.727 ms
12  bbr01ashbva-tge-0-1-0-1.ashb.va.charter.com (96.34.3.139)  41.287 ms  102.639 ms  84.890 ms
13  199.27.73.26 (199.27.73.26)  84.809 ms  213.318 ms  91.868 ms
14  23.185.0.4 (23.185.0.4)  35.980 ms  37.729 ms  129.054 ms


VIA:  Macbook Pro connected wireless to Internet Mesh Node's AP.
Traceroute has started…

traceroute to fe4.edge.pantheon.io (23.185.0.4), 64 hops max, 72 byte packets
 1  localnode (10.68.19.113)  3.950 ms  0.936 ms  0.739 ms
 2  192.168.1.1 (192.168.1.1)  12.190 ms *  10.764 ms
 3  10.102.64.1 (10.102.64.1)  90.700 ms  82.213 ms  14.622 ms
 4  dtr01flrnor-tge-0-0-0-10.flrn.or.charter.com (96.34.111.152)  15.214 ms  30.876 ms  182.865 ms
 5  96-34-105-74.static.unas.or.charter.com (96.34.105.74)  49.870 ms  14.830 ms  47.686 ms
 6  96-34-111-220.static.unas.or.charter.com (96.34.111.220)  254.348 ms  39.212 ms  71.540 ms
 7  96-34-108-175.static.unas.or.charter.com (96.34.108.175)  181.333 ms  202.999 ms  48.054 ms
 8  96-34-108-160.static.unas.or.charter.com (96.34.108.160)  53.451 ms  257.818 ms  22.840 ms
 9  bbr01snjsca-bue-1.snjs.ca.charter.com (96.34.2.252)  34.144 ms  98.639 ms  89.334 ms
10  bbr02snloca-bue-6.snlo.ca.charter.com (96.34.0.1)  51.624 ms  160.863 ms  41.943 ms
11  bbr01snloca-bue-4.snlo.ca.charter.com (96.34.0.28)  279.276 ms  101.881 ms  110.570 ms
12  bbr01mtpkca-bue-5.mtpk.ca.charter.com (96.34.0.26)  45.036 ms  63.394 ms  56.851 ms
13  bbr01ashbva-tge-0-1-0-1.ashb.va.charter.com (96.34.3.139)  107.670 ms  118.603 ms  102.607 ms
14  199.27.73.26 (199.27.73.26)  48.025 ms  134.106 ms  190.613 ms
15  23.185.0.4 (23.185.0.4)  443.799 ms  78.317 ms  81.141 ms

KG6JEI
 > 1  localnode (10.68.19.113

 > 1  localnode (10.68.19.113)  3.950 ms  0.936 ms  0.739 ms
Looks good
 > 2  192.168.1.1 (192.168.1.1)  12.190 ms *  10.764 ms
This is not so good, we’re seeing some packet loss from localnode to 192.168.1.1. This isn’t a good sign. Since the mesh node is responding ok in the previous hop I would question the cables and switches and devices between the mesh node and 192.168.1.1, also it’s a question if this wireless client/bridge is having trouble connecting to the Access  Point due to its position or how it’s mounted in your kit. Your going to want to look at the RF link quality at this stage as well. In theory it could also be the mesh node itself is having trouble routing from its LAN to WAN port but I usually expect that to show up on hop 1.

 > 3  10.102.64.1 (10.102.64.1)  90.700 ms  82.213 ms  14.622 ms
By this point everything is so slow with such high latency and variability in the packet latency I would expect slow downs to be occurring.

Considering I haven’t built a Trevor setup that is about all I can offer on what I’m seeing but that should provide a starting point to review what is going on.

N8JJ
slow tunnel

I am having similar speed issues.
Running traceroute from within the node to the tunnel server internet IP yields 74ms direct and 1350ms (avg numbers) through the tunnel over the same path.
I am going to try different hardware for the client to see if it makes a difference.

N8JJ
Tunnel performance through AT&T

After some troubleshooting and research, I have concluded that the AT&T 5268AC modem slows down the tunnel by a factor of 10!
There may be some setting on it that I can change, but I haven't found it.
Does anyone else have AT&T service and good tunnel performance?
I can ping the non-tunnel internet IP at 70ms, But when I go through the tunnel, it's 1500ms.
Testing with other hams who have Time-warner cable modem, show no speed drop.

 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer