Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 2 [3]

Author Topic: New POPs?  (Read 22840 times)

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1723
Re: New POPs?
« Reply #30 on: September 20, 2009, 06:02:21 AM »

Current top 20 latency list only includes 4 POPS.  I reloaded it 15 minutes later just in case I caught the list being regenerated - and still only 4 pops.  OOPS?

Yeah working on it right now, hopefully all happy in a while.

Edit: Scripts are happy once more, running a big batch to get everything updated again, probably take all day.
« Last Edit: September 20, 2009, 09:38:56 AM by broquea »
Logged

snarked

  • Hero Member
  • *****
  • Posts: 766
Re: New POPs?
« Reply #31 on: September 20, 2009, 12:44:22 PM »

Better.  However, not all tunnels are showing.  Los Angeles, Tokyo, and Zurich definently missing.  By tunnel #:  6, 15 (LA), 19, 20, 22, and 23 (the latter two being Tokyo and Zurich not necessarily respectively).  Let's see how it does 24 hours from now....
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1723
Re: New POPs?
« Reply #32 on: September 20, 2009, 01:27:55 PM »

Because I'm not running all the polls at once. I'd like the machine to be a little sane ;) I'm going to sleep now, with the remaining scripts just firing off.

Also, why are you using Zurich? Geo-location thinks your IPv4 endpoint is The States. Seems strange is all........
« Last Edit: September 20, 2009, 01:35:49 PM by broquea »
Logged

jimb

  • Hero Member
  • *****
  • Posts: 805
  • ^^^ Warped picture
Re: New POPs?
« Reply #33 on: September 20, 2009, 01:54:28 PM »

Yikes.  Going to sleep at 1:30PM?  I thought I was bad. 

I'm wondering if I'll show up in the top 20 now, since my avg. is about 8-9ms (only five hops away since you guys peer with DSLExtreme).    :)
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1723
Re: New POPs?
« Reply #34 on: September 20, 2009, 03:05:53 PM »

Yikes.  Going to sleep at 1:30PM?  I thought I was bad. 

I'm wondering if I'll show up in the top 20 now, since my avg. is about 8-9ms (only five hops away since you guys peer with DSLExtreme).    :)

meh so much for a nap, too awake already. also you came in around 12ms, but even the top 20 don't break 4ms. competition is tough!
Logged

jimb

  • Hero Member
  • *****
  • Posts: 805
  • ^^^ Warped picture
Re: New POPs?
« Reply #35 on: September 20, 2009, 03:35:45 PM »

Yikes.  Going to sleep at 1:30PM?  I thought I was bad. 

I'm wondering if I'll show up in the top 20 now, since my avg. is about 8-9ms (only five hops away since you guys peer with DSLExtreme).    :)

meh so much for a nap, too awake already. also you came in around 12ms, but even the top 20 don't break 4ms. competition is tough!
You guys must measure it differently (or from a different spot) than I do with MTR or ping:
{root@gtoojimb/pts/3}~# mtr -r 72.52.104.74
HOST: gtoojimb                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. fw                            0.0%    10    1.0   1.0   0.9   1.1   0.m
  2. xxx                          100.0    10    0.0   0.0   0.0   0.0   0.0
  3. SJC1.CR1.Gig7-0-10.dslextrem  0.0%    10    7.3   7.0   6.4   7.3   0.3
  4. 10gigabitethernet2-3.core1.s  0.0%    10    7.3   8.0   7.1  13.8   2.0
  5. 10gigabitethernet1-2.core1.f  0.0%    10   15.4  10.3   8.1  15.4   2.9
  6. tserv3.fmt2.ipv6.he.net       0.0%    10    8.8   8.9   7.9  10.9   0.9

PING 72.52.104.74 (72.52.104.74) 56(84) bytes of data.
64 bytes from 72.52.104.74: icmp_seq=1 ttl=59 time=9.05 ms
64 bytes from 72.52.104.74: icmp_seq=2 ttl=59 time=8.90 ms
64 bytes from 72.52.104.74: icmp_seq=3 ttl=59 time=9.40 ms
64 bytes from 72.52.104.74: icmp_seq=4 ttl=59 time=8.72 ms
64 bytes from 72.52.104.74: icmp_seq=5 ttl=59 time=9.21 ms
64 bytes from 72.52.104.74: icmp_seq=6 ttl=59 time=10.0 ms
64 bytes from 72.52.104.74: icmp_seq=7 ttl=59 time=9.12 ms
64 bytes from 72.52.104.74: icmp_seq=8 ttl=59 time=9.15 ms
64 bytes from 72.52.104.74: icmp_seq=9 ttl=59 time=8.94 ms
64 bytes from 72.52.104.74: icmp_seq=10 ttl=59 time=9.36 ms

--- 72.52.104.74 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 4533ms
rtt min/avg/max/mdev = 8.723/9.196/10.081/0.359 ms


But yeah, if the top 20 are 4ms, I don't think I can even get close.  Maybe once I get around to replacing my P133 FW.  :)  But then 4ms seems like LAN users or something ... cheating!  :P
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1723
Re: New POPs?
« Reply #36 on: September 20, 2009, 03:51:47 PM »

It is an IPv6 ping sourced from the tunnel server to your side of the tunnel.
Logged

jimb

  • Hero Member
  • *****
  • Posts: 805
  • ^^^ Warped picture
Re: New POPs?
« Reply #37 on: September 20, 2009, 04:09:55 PM »

Oh duh.  I should have figured as much.   :-[

HOST: gtoojimb                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. hegw                          0.0%    10   10.1  10.7   9.8  13.0   1.1

{root@gtoojimb/pts/3}~# ping6 -i.5 -c10 hegw
PING hegw(hegw) 56 data bytes
64 bytes from hegw: icmp_seq=1 ttl=64 time=10.9 ms
64 bytes from hegw: icmp_seq=2 ttl=64 time=10.7 ms
64 bytes from hegw: icmp_seq=3 ttl=64 time=11.6 ms
64 bytes from hegw: icmp_seq=4 ttl=64 time=10.2 ms
64 bytes from hegw: icmp_seq=5 ttl=64 time=14.2 ms
64 bytes from hegw: icmp_seq=6 ttl=64 time=9.99 ms
64 bytes from hegw: icmp_seq=7 ttl=64 time=11.3 ms
64 bytes from hegw: icmp_seq=8 ttl=64 time=10.9 ms
64 bytes from hegw: icmp_seq=9 ttl=64 time=10.9 ms
64 bytes from hegw: icmp_seq=10 ttl=64 time=9.48 ms

--- hegw ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 4533ms
rtt min/avg/max/mdev = 9.486/11.044/14.203/1.214 ms


Naturally, even slower.   :D
Logged

snarked

  • Hero Member
  • *****
  • Posts: 766
Re: New POPs?
« Reply #38 on: September 20, 2009, 11:42:58 PM »

RE - Reply #32: It now appears that all tunnels are showing up on the latency list.

As far as me running a tunnel out of Zürich:  Two of my domains have close connections to Switzerland, so I'm about to make them appear as if they're there, ... even if hosted in the U.S.  ;-)

I get quite alot of traffic from ISP bluewin.com/.ch, so having a tunnel near them makes some sense.  After I have revised my firewall, I'll be adding the additional addresses to the DNS to activate them.
Logged

sttun

  • Jr. Member
  • **
  • Posts: 53
Re: New POPs?
« Reply #39 on: October 05, 2009, 02:06:34 PM »

We peer with AS3292 in other locations, so I'll fire off an email to them and see if they want to turn up in Stockholm.
Thank you so mouch, HE relay takes care of us users even those of us only using youre free services   :).
Hmm are TDC slow? Has anything append?  I don't mean to nag, but how long does it take these people to answer your mail. I realise that you have a lot to do and these things don't happen over night (if at all) but can jou please just pop in an update??

As always Thank you and the rest of HE for e grat service
All the best
Bjarne Nilsson
« Last Edit: October 05, 2009, 02:08:30 PM by sttun »
Logged

sttun

  • Jr. Member
  • **
  • Posts: 53
Re: New POPs?
« Reply #40 on: November 14, 2009, 07:54:50 AM »

Hello
I seems the peering in Stockholm is operational
traceroute to 216.66.80.90 (216.66.80.90), 30 hops max, 60 byte packets
 1  10.0.0.1 (10.0.0.1) [AS65534]  0.483 ms  0.580 ms  0.957 ms
 2  213.236.252.1 (213.236.252.1) [AS3292]  7.058 ms  7.151 ms  7.423 ms
 3  212.37.234.93 (212.37.234.93) [AS3292]  7.955 ms  8.510 ms  8.920 ms
 4  195.70.168.186 (195.70.168.186) [AS3292]  14.000 ms  14.133 ms  14.241 ms
 5  195.70.168.186 (195.70.168.186) [AS3292]  14.907 ms  15.405 ms  15.517 ms
 6  213.236.198.26 (213.236.198.26) [AS3292]  15.921 ms  11.813 ms  10.787 ms
 7  212.125.237.161 (212.125.237.161) [AS3292]  10.855 ms  10.940 ms  12.315 ms
 8  85.19.24.201 (85.19.24.201) [AS3292]  12.916 ms  13.068 ms  13.511 ms
 9  tge1-4.kst-peer2.sto.se.ip.tdc.net (88.131.143.64) [AS3292]  24.997 ms  26.673 ms  26.767 ms
10  netnod-ix-ge-a-sth-1500.he.net (194.68.123.187)
  •   27.663 ms  27.758 ms  28.418 ms

11  tserv24.sto1.ipv6.he.net (216.66.80.90) [AS6939]  28.675 ms  28.897 ms  28.614 ms

Great work HE thanks a lot, I'm going to move my tunnel after dinner
Logged

brad

  • Jr. Member
  • **
  • Posts: 82
Re: New POPs?
« Reply #41 on: February 14, 2010, 02:44:21 PM »

HE seems to have POPs in Zurich, Stockholm and Tokyo. Will there be tunnelbroker POPs at these loations in the future?

Does HE have plans of turning up a peering link to JPNAP Tokyo I ?
Logged

mtindle

  • Administrator
  • Newbie
  • *****
  • Posts: 25
Re: New POPs?
« Reply #42 on: February 16, 2010, 06:24:56 PM »

Does HE have plans of turning up a peering link to JPNAP Tokyo I ?

We are looking into it as we enjoy connecting to all the exchanges we reasonably can.  However, I cannot say when or even if we will for certain.  Is there a particular ASN only present on JPNAP you are interested in?
Logged

brad

  • Jr. Member
  • **
  • Posts: 82
Re: New POPs?
« Reply #43 on: February 17, 2010, 05:57:25 PM »

We are looking into it as we enjoy connecting to all the exchanges we reasonably can.  However, I cannot say when or even if we will for certain.  Is there a particular ASN only present on JPNAP you are interested in?

No, its more of a curiosity, connecting into JPNAP would (obviously) provide more opportunity for additional peering sessions. I ask as it would appear to be the largest of the exchanges in Tokyo.
Logged

mtindle

  • Administrator
  • Newbie
  • *****
  • Posts: 25
Re: New POPs?
« Reply #44 on: March 01, 2010, 04:19:44 PM »

No, its more of a curiosity, connecting into JPNAP would (obviously) provide more opportunity for additional peering sessions. I ask as it would appear to be the largest of the exchanges in Tokyo.

We aggressively go after peering with anything that has an ASN.  So I can assure you we're very interested in connecting to the JPNAP.  There are other factors however that are preventing us from doing so at this time.   Once those obstacles are cleared, we'll probably hook up to JPNAP.
Logged
Pages: 1 2 [3]