Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.

MCD



15 posts

Geek
+1 received by user: 11


Topic # 242254 17-Oct-2018 22:25
Send private message quote this post

Hi all,

 

Reading some of the threads to do with Bigpipe's move to the Spark network, I understood that traffic would no longer be routed via Auckland. With that in mind, when I check my IP location on the various web-sites that do this, ie:

 

https://www.iplocation.net/

 

...they always report my geo-location as Auckland, though I live in Wellington. I notice the speedtest websites also think I'm in Auckland as well. Is this to be expected (or did I misunderstand the other threads)?

 

I'm on gigabit UFB, with gigabit ethernet to the router. I also have a static IP.

 

Thanks!

 

 


Filter this topic showing only the reply marked as answer Create new topic
defiant
673 posts

Ultimate Geek
+1 received by user: 310

Lifetime subscriber

  Reply # 2110122 17-Oct-2018 22:57
One person supports this post
Send private message quote this post

The geoip location doesn't have any correlation to where your traffic originates from, in terms of routing, whatsoever

 

The best way to tell is to traceroute to something and usually the 2nd hop after your router is the BNG you're connected to, if its single digit latency then it's local to you in Wellington


BDFL - Memuneh
61509 posts

Uber Geek
+1 received by user: 12234

Administrator
Trusted
Geekzone
Lifetime subscriber

  Reply # 2110124 17-Oct-2018 22:58
2 people support this post
Send private message quote this post

Most of the times IP location refers to the IP block owner office address... Not many ISP have the IP blocks correctly linked to a city or region. At best IP location can tell you the country - anything below this level may or may not be correct.





MCD



15 posts

Geek
+1 received by user: 11


  Reply # 2110129 17-Oct-2018 23:14
Send private message quote this post

dfnt:

 

The geoip location doesn't have any correlation to where your traffic originates from, in terms of routing, whatsoever

 

The best way to tell is to traceroute to something and usually the 2nd hop after your router is the BNG you're connected to, if its single digit latency then it's local to you in Wellington

 

 

Thanks for the suggestion. I did a tracert to google.com here:

 

 

 

Tracing route to google.com [216.58.196.142]
over a maximum of 30 hops:

 

1 <1 ms <1 ms <1 ms testwifi.here [192.168.86.1]
2 1 ms <1 ms 1 ms 125-236-192-9.adsl.xtra.co.nz [125.236.192.9]
3 * * * Request timed out.
4 12 ms 10 ms 10 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 10 ms 10 ms 10 ms ae7-2.akbr7.global-gateway.net.nz [122.56.119.53]
6 34 ms 35 ms 34 ms xe0-0-4.sgbr3.global-gateway.net.nz [122.56.127.94]
7 34 ms 33 ms 33 ms ae2-10.sgbr4.global-gateway.net.nz [202.50.232.246]
8 35 ms 34 ms 34 ms 72.14.217.100
9 35 ms 35 ms 36 ms 108.170.247.49
10 35 ms 35 ms 35 ms 108.170.232.11
11 35 ms 36 ms 35 ms syd15s04-in-f14.1e100.net [216.58.196.142]

 

Trace complete.

 

 

 

Would that look normal for a Bigpipe connection in Wellington?

 

Cheers.

 

 

 

 


Meow
8021 posts

Uber Geek
+1 received by user: 4008

Moderator
Trusted
Lifetime subscriber

  Reply # 2110136 17-Oct-2018 23:41
2 people support this post
Send private message quote this post

MCD:

 

Would that look normal for a Bigpipe connection in Wellington?

 

Yep totally normal. Tested via a BigPipe connection:

 

traceroute to google.com (172.217.25.46), 30 hops max, 60 byte packets
1 UniFiPro (192.168.3.1) 0.457 ms 0.360 ms 0.446 ms
2 125-236-192-9.adsl.xtra.co.nz (125.236.192.9) 1.842 ms 1.755 ms 1.903 ms
3 * * *
4 ae8-10.akbr6.global-gateway.net.nz (122.56.116.5) 10.458 ms 10.379 ms 13.532 ms
5 ae7-2.akbr7.global-gateway.net.nz (122.56.119.53) 13.462 ms 13.373 ms 13.203 ms
6 xe5-0-2.sgbr3.global-gateway.net.nz (122.56.127.178) 38.298 ms xe7-0-9.sgbr3.global-gateway.net.nz (202.50.232.182) 35.535 ms xe5-0-2.sgbr3.global-gateway.net.nz (122.56.127.178) 36.776 ms
7 ae2-10.sgbr4.global-gateway.net.nz (202.50.232.246) 35.333 ms 35.332 ms 35.230 ms
8 72.14.217.100 (72.14.217.100) 35.488 ms 35.102 ms 34.223 ms
9 108.170.247.81 (108.170.247.81) 34.538 ms 34.760 ms 34.712 ms
10 108.170.233.195 (108.170.233.195) 34.920 ms 34.832 ms 108.170.233.193 (108.170.233.193) 35.529 ms
11 syd15s02-in-f46.1e100.net (172.217.25.46) 34.596 ms 34.544 ms 36.176 ms

 

Compared to 2degrees:

 

traceroute to google.com (172.217.25.46), 30 hops max, 60 byte packets
1 router (192.168.2.1) 0.394 ms 0.276 ms 0.312 ms
2 69.7.69.111.static.snap.net.nz (111.69.7.69) 1.222 ms 1.398 ms 1.352 ms
3 72.14.215.151 (72.14.215.151) 34.742 ms 34.532 ms 34.625 ms
4 72.14.215.150 (72.14.215.150) 34.705 ms 34.785 ms 34.648 ms
5 108.170.247.81 (108.170.247.81) 35.396 ms 35.388 ms 35.256 ms
6 108.170.233.193 (108.170.233.193) 34.983 ms 108.170.233.195 (108.170.233.195) 35.019 ms 34.931 ms
7 syd15s02-in-f46.1e100.net (172.217.25.46) 34.819 ms 35.114 ms 35.056 ms

 

Note the bold - it isn't possible to get up to Auckland in 1.8ms from Wellington. If we compare this with Voyager (who pass traffic via Auckland - at-least on this connection) you'll see the 2nd hop is a little more:

 

traceroute to google.com (172.217.25.46), 30 hops max, 60 byte packets
1 192.168.4.1 (192.168.4.1) 0.782 ms 0.511 ms 0.631 ms
2 114.23.3.255 (114.23.3.255) 24.569 ms 24.444 ms 24.546 ms
3 114.23.3.230 (114.23.3.230) 24.198 ms 24.310 ms 24.192 ms
4 ae9-143.akbr6.global-gateway.net.nz (122.56.118.157) 24.464 ms 24.344 ms 24.238 ms
5 ae7-2.akbr7.global-gateway.net.nz (122.56.119.53) 24.263 ms 24.596 ms 24.735 ms
6 xe5-0-4.sgbr3.global-gateway.net.nz (122.56.127.186) 49.219 ms xe7-0-4.sgbr3.global-gateway.net.nz (122.56.127.2) 49.826 ms xe5-0-5.sgbr3.global-gateway.net.nz (122.56.127.190) 49.037 ms
7 ae2-10.sgbr4.global-gateway.net.nz (202.50.232.246) 48.831 ms 48.965 ms 48.842 ms
8 72.14.217.100 (72.14.217.100) 50.212 ms 51.444 ms 48.804 ms
9 108.170.247.81 (108.170.247.81) 48.195 ms 49.367 ms 108.170.247.49 (108.170.247.49) 49.708 ms
10 108.170.233.195 (108.170.233.195) 48.835 ms 48.443 ms 108.170.233.193 (108.170.233.193) 49.338 ms
11 syd15s02-in-f14.1e100.net (172.217.25.46) 49.038 ms 49.295 ms 49.884 ms

 

The BigPipe connection tested above also shows its IP Location in Auckland. This is just how it is configured. The 2degrees IP shows as Christchurch (or Nelson - depending on what location provider I use) for me and the Voyager connection shows as Auckland where the connection is in Nelson. IP Geolocation is wildly inaccurate.





defiant
673 posts

Ultimate Geek
+1 received by user: 310

Lifetime subscriber

  Reply # 2110139 18-Oct-2018 00:35
One person supports this post
Send private message quote this post

MCD:

 

Thanks for the suggestion. I did a tracert to google.com here:

 

 

 

Tracing route to google.com [216.58.196.142]
over a maximum of 30 hops:

 

1 <1 ms <1 ms <1 ms testwifi.here [192.168.86.1]
2 1 ms <1 ms 1 ms 125-236-192-9.adsl.xtra.co.nz [125.236.192.9]
3 * * * Request timed out.
4 12 ms 10 ms 10 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 10 ms 10 ms 10 ms ae7-2.akbr7.global-gateway.net.nz [122.56.119.53]
6 34 ms 35 ms 34 ms xe0-0-4.sgbr3.global-gateway.net.nz [122.56.127.94]
7 34 ms 33 ms 33 ms ae2-10.sgbr4.global-gateway.net.nz [202.50.232.246]
8 35 ms 34 ms 34 ms 72.14.217.100
9 35 ms 35 ms 36 ms 108.170.247.49
10 35 ms 35 ms 35 ms 108.170.232.11
11 35 ms 36 ms 35 ms syd15s04-in-f14.1e100.net [216.58.196.142]

 

Trace complete.

 

 

 

Would that look normal for a Bigpipe connection in Wellington?

 

Cheers.

 

Yep, your gateway is located in Wellington.

 

As @michaelmurfy alluded to, if your gateway was in Auckland it'd be ~12-15 ms (on fibre) for the 2nd hop.

 

It's safe to ignore the geoip information, according to various geoip databases I'm either in Nelson, Christchurch, Hawkes Bay and Wellington.. I'm in Wellington.


560 posts

Ultimate Geek
+1 received by user: 108


  Reply # 2110145 18-Oct-2018 01:03
Send private message quote this post

Tor can let you be everywhere.





No backup, no pity. Anyway, RAID isn't one.


Webhead
2125 posts

Uber Geek
+1 received by user: 691

Moderator
Trusted
Lifetime subscriber

  Reply # 2110147 18-Oct-2018 01:55
Send private message quote this post

Not sure where Maxmind get their data, but they knew more or less exactly where I live by my ip-address.

 

 





3621 posts

Uber Geek
+1 received by user: 1343

Subscriber

  Reply # 2110164 18-Oct-2018 07:19
Send private message quote this post

jarledb:

Not sure where Maxmind get their data, but they knew more or less exactly where I live by my ip-address.


 



I think that was a fluke. Tried a handful of Vocus and a couple Devoli IP''s... all come back as Auckland.

MCD



15 posts

Geek
+1 received by user: 11


  Reply # 2110322 18-Oct-2018 10:29
Send private message quote this post

Thanks all for the advice, glad to know it's working as expected.

 

I do see a few odd things happen with speedtest.net; Tests to Spark's Wellington server report a ping of 1ms, Spark Auckland around 10ms. Some other servers in Wellington report ~20ms, so I'm guessing in that case it's being routed up to Auckland, then back to Wellington (presumably due to peering agreements)?

 

 


7775 posts

Uber Geek
+1 received by user: 2565

Subscriber

  Reply # 2110394 18-Oct-2018 11:30
One person supports this post
Send private message quote this post

yep, that will likely be it

Filter this topic showing only the reply marked as answer Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.