Hosthatch Stockholm IPv6 down

13»

Comments

  • bjobjo OG

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

    Thanked by (1)Mumbly
  • rcy026rcy026

    @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. :smile:

    Thanked by (2)Mumbly skorous
  • bjobjo OG

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

  • bjobjo OG

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

  • dosaidosai OG

    My ipv6 at Stockholm storage vps works now.

  • TheDPTheDP OG

    @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.

  • bjobjo OG

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

    Thanked by (1)Shot²
  • Shot²Shot²

    Confirmed, IPv6 is functional again

Sign In or Register to comment.

© LowEndSpirit 2024

ipv6 ready