Hosthatch Stockholm IPv6 down

bjo

And IPv6 is down again with the new address.

dosai

@bjo said:
And IPv6 is down again with the new address.

Same.

Mumbly

Same, down.

bjo

The support said now:

We had an issue with the IPv6 in STO as were forced to cut out our old upstream (the old addresses) earlier than expected and >as a result outgoing traffic stopped working due to an human error/misconfiguration. We're now fully switched over to the >new IPv6 network and it will be a smoother ride from now on. I am very sorry for the inconvenience caused.

I filled up your account credit to cover your next invoice. Please do let us know if there's anything else we can do for you.

bjo

Besides that: fe80::1 still down.

Mumbly

Yeah 8 - 10 hours later, still down.

Mumbly

It works now!

bjo

They told me that a few dangling network filters had to be removed.

bjo

The routing to NC is really, erm, interesting:

HOST: store                       Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 2a0e:dc0:2::1              0.0%    10   26.2  17.8   9.4  26.2   5.7
  2.|-- 2a02:6ea0:8:1070:5033::1   0.0%    10    0.4   0.6   0.3   1.7   0.4
  3.|-- 2a03:4000:x:y::1        0.0%    10   26.0  26.4  25.9  30.1   1.3

Mumbly

@bjo said:
They told me that a few dangling network filters had to be removed.

What package do you have with hh, to get all those answers so quickly unlike the rest of us, plebs?

bjo

It's a common 1TB storage box, no special LET offer.

rcy026

@Mumbly said:

@bjo said:
They told me that a few dangling network filters had to be removed.

What package do you have with hh, to get all those answers so quickly unlike the rest of us, plebs?

I have a black friday special and a storage vps and the few tickets I've opened have been answered within an hour.
I was actually a bit surprised by this after seeing lots of threads about hh being slow on tickets, but so far they have really impressed me.

bjo

No reply regarding the IPv6 issue since the storage outage since 2 days.

bjo

Got a reply now (wow!) requesting to reconfigure the IPv6 address. Well, if fe80::1 is not pingable, that won't change anything...

dosai

My ipv6 at Stockholm storage vps works now.

DP

@bjo said: if fe80::1 is not pingable, that won't change anything

root@panopticon:~# ping fe80::1 -c 10
PING fe80::1(fe80::1) 56 data bytes

--- fe80::1 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9222ms

ICMP blocked maybe?

root@panopticon:~# ping -c 5 google.com
PING google.com(arn09s22-in-x0e.1e100.net (2a00:1450:400f:801::200e)) 56 data bytes
64 bytes from arn09s22-in-x0e.1e100.net (2a00:1450:400f:801::200e): icmp_seq=1 ttl=59 time=22.6 ms
64 bytes from arn09s22-in-x0e.1e100.net (2a00:1450:400f:801::200e): icmp_seq=2 ttl=59 time=22.1 ms
64 bytes from arn09s22-in-x0e.1e100.net (2a00:1450:400f:801::200e): icmp_seq=3 ttl=59 time=22.3 ms
64 bytes from arn09s22-in-x0e.1e100.net (2a00:1450:400f:801::200e): icmp_seq=4 ttl=59 time=22.1 ms
64 bytes from arn09s22-in-x0e.1e100.net (2a00:1450:400f:801::200e): icmp_seq=5 ttl=59 time=22.0 ms

--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 22.041/22.244/22.626/0.213 ms

But I guess these IPv6 issues are mostly (or only) impacting the storage VPSes.

bjo

Seems like ICMP block. The last time fe80::1 did not reply was an indication that IPv6 connectivy was broken. But it works now.

Shot²

Confirmed, IPv6 is functional again