Spark Fibre 100 and Huawei HG659b: High latency

Forums › Spark New Zealand (including Skinny and BigPipe) › Spark Fibre 100 and Huawei HG659b: High latency

geektahiti

24 posts

Geek

#236419 1-Jun-2018 09:20

Hi There

Spark just enabled the fibre connection.

It is working very well and speed test shows 100 Mbps and 20 Mbps upload.

However, I have got some issues when connecting to my VPN Work from home.

Latency is going very high e.g.

Without VPN Spark Fibre:

ping www.google.com: 30 ms

With VPN on Spark Fibre

ping www.google.com: 300 ms

ping worknetwork VPN: 244 ms

I have also tried with another Vodafone Guest connection VDS with VPN enabled:

ping www.google.com: 28 ms

ping worknetwork VPN: 112 ms

How do we explain the high latency on Spark with VPN?

Linux

10294 posts

Uber Geek

Trusted

Lifetime subscriber

#2026709 1-Jun-2018 09:26

@hio77 One for you :)

John

Pluralsight

Learn cloud, mobile, security, data and web technologies with Pluralsight (affiliate link).

hio77

'That VDSL Cat'
12982 posts

Uber Geek

ID Verified

Trusted

Voyager

Subscriber

#2026735 1-Jun-2018 09:34

Think i may have heard bits... On this one...
Please dm me details including traceroute to and from vpn endpoints.

No promises, routing is a complex thing and any preformance over a vpn itself is well outside of our control.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

hio77

'That VDSL Cat'
12982 posts

Uber Geek

ID Verified

Trusted

Voyager

Subscriber

#2027418 2-Jun-2018 10:54

After quite some review, unfortunately this is on the Telstra side.

I've also had mention of another AU based connection having the same issue.

unfortunately, your best be will be to speak to telstra on this one for direct engagement.

I'll see if our network guys can engage in a discussion, but it's two networks upstream.. so no promises at all..

Routing is a complex thing, in this instance the issue is the return path from telstra to NTT is going over SXC for the return path not the sending path.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.