Top 20 stats for tunnel latency isn't working.

[snarked]

There are no stats being reported.  Something is broken.

[broquea]

script went wonky, fixed now. data should be repopulating for a while now.

[broquea]

There ya go, back in top 5 on LAX:

#5       snarked   1.23 ms

[snarked]

Much better.

[brad]

script went wonky, fixed now. data should be repopulating for a while now.

The stats are still wrong.. at least for the Toronto POP.

[broquea]

script went wonky, fixed now. data should be repopulating for a while now.

The stats are still wrong.. at least for the Toronto POP.

Define wrong in this context. Those were the 18 tunnels that replied to ping6 queries that use that tunnel-server, out of the 84 tunnels configured. I just tested your tunnel, and it is at 23ms.
tserv19 in Hong Kong doesn't have any users yet, so it has no stats.

[brad]

Define wrong in this context. Those were the 18 tunnels that replied to ping6 queries that use that tunnel-server, out of the 84 tunnels configured. I just tested your tunnel, and it is at 23ms.
tserv19 in Hong Kong doesn't have any users yet, so it has no stats.

Meaning I wonder why my other tunnel was not on the list and it is 1ms away from the tunnelbroker server. But you mentioning pinging of the tunnel reminded me to check. I found I cannot ping the assigned IP from the PTP /64 on the tunnel but I can ping an address within the routed /64 assigned to the same interface on the server. I had found that my fw ruleset was not allowing ICMP neighbor solicitation's. I added that to the ruleset but I see that incoming solicitation's from the tunnelbroker are not responded to.