Hosthatch Stockholm IPv6 down

2

Comments

  • dosaidosai OG

    @Mumbly said:

    @dosai said:
    I didn't configure network, it auto switched to the new ipv6.

    Can you post "ip -6 route" output please (blank out part of your subnet).

    ::1 dev lo proto kernel metric 256 pref medium
2a00:1a28:xxxx:xxxx::/64 dev ens3 proto kernel metric 256 pref medium
fddd:2c4:2c4:2c4::/64 dev wg0 proto kernel metric 256 pref medium
fe80::/64 dev ens3 proto kernel metric 256 pref medium
default via fe80::1 dev ens3 metric 1024 onlink pref medium
    Thanked by (1)Mumbly
  • MumblyMumbly

    Damn, I am out of ideas then. I reinstalled it also from ISO - with the same result. At this point, there's no other way than wait for support ... cough ... HostHatch support. :s

    root@stockholm:~# ifconfig
ens3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 31.220.xxx.xxx  netmask 255.255.255.0  broadcast 31.220.15.255
        inet6 2a00:1a28:1157:xxxx::1  prefixlen 64  scopeid 0x0<global>
        inet6 2a0e:dc0:2:xxxx::1  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::220:56ff:fe09:c87f  prefixlen 64  scopeid 0x20<link>
        inet6 2a0e:dc0:2:xxxx::2  prefixlen 64  scopeid 0x0<global>
        inet6 2a00:1a28:1157:xxxx:3:3:3:3  prefixlen 64  scopeid 0x0<global>
        inet6 2a00:1a28:1157:xxxx:2:2:2:2  prefixlen 64  scopeid 0x0<global>
        inet6 2a00:1a28:1157:xxxx:1:1:1:1  prefixlen 64  scopeid 0x0<global>
        ether 00:20:56:09:c8:7f  txqueuelen 1000  (Ethernet)
        RX packets 3878  bytes 262128 (255.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2546  bytes 195957 (191.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 6  bytes 832 (832.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6  bytes 832 (832.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


root@stockholm:~# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2a00:1a28:1157:xxxx::/64 dev ens3 proto kernel metric 256 pref medium
2a0e:dc0:2:xxxx::/64 dev ens3 proto kernel metric 256 pref medium
fe80::/64 dev ens3 proto kernel metric 256 pref medium
default via fe80::1 dev ens3 metric 1024 onlink pref medium


root@stockholm:~# cat /etc/resolv.conf
nameserver 1.1.1.1
nameserver 8.8.8.8
nameserver 2001:4860:4860::8844


root@stockholm:~# curl ipv6.google.com
curl: (7) Failed to connect to ipv6.google.com port 80: No route to host
  • rcy026rcy026

    I had issues with ipv6 yesterday so I opened a ticket. Within an hour they replied and asked me to try again and everything worked fine.
    My first experience ever with HostHatch's support, maybe I just got lucky but I have no complaints. :smile:

  • bjobjo OG

    @rcy026 said:
    I had issues with ipv6 yesterday so I opened a ticket. Within an hour they replied and asked me to try again and everything worked fine.
    My first experience ever with HostHatch's support, maybe I just got lucky but I have no complaints. :smile:

    Do you have 2 IPv6 prefixes or only one?

  • MumblyMumbly
    edited August 2023

    @rcy026 said:
    I had issues with ipv6 yesterday so I opened a ticket. Within an hour they replied and asked me to try again and everything worked fine.
    My first experience ever with HostHatch's support, maybe I just got lucky but I have no complaints. :smile:

    Yeah. It seems random :)

    Ticket
    IPv6 outage report - Stockholm node
    AWAITING RESPONSE 3 days ago

  • bjobjo OG

    Yesterday they asked if they could access the VM as they thought I have still issues. Some explanation what happened on 21.08. would be better.

  • rcy026rcy026

    @bjo said:

    @rcy026 said:
    I had issues with ipv6 yesterday so I opened a ticket. Within an hour they replied and asked me to try again and everything worked fine.
    My first experience ever with HostHatch's support, maybe I just got lucky but I have no complaints. :smile:

    Do you have 2 IPv6 prefixes or only one?

    2 in the panel, but only use the original one.

  • bjobjo OG

    Last reply from HH:

    I am sorry for the inconvenience caused with the IPv6 issues. We will send out an email tomorrow with instructions and information regarding improving the IPv6 reliability in Stockholm.

  • MumblyMumbly

    Eagerly waiting some sign of life from them :)

  • bjobjo OG

    Don't know which tomorrow they ment. Maybe it's @cociu 's monday.

  • dosaidosai OG
    edited August 2023

    Received this email from HH. But after configuring ipv6, network broke :p

    Dear Customer,

    You are receiving this email because your server(s) in Stockholm with an assigned IPv6 block starting with 2a00:1a28:1157. This is changing and your action is required. If you do not use IPv6, you may ignore this email.

    This is our older IPv6 network space isolated to one of our upstream providers. In order to increase the reliability and performance of our IPv6 network in Stockholm, we need to replace this IP space. We have assigned a new /64 block to your server(s), starting with 2a0e:dc0:2.

    Both the old and the new block are currently active and you may see the assigned blocks by going to the "Network" tab for a server via the control panel at cloud.hosthatch.com.

    Please change your configurations to use the new IPv6 addresses. We recommend that you do this as soon as possible, but no later than September 8th. We will then automatically unassign the old block from your server, there is no need to contact us to have it removed.

    Please see our docs https://docs.hosthatch.com/networking/#ipv6-configuration for IPv6 configuration information.

    Thank you for your understanding and apologize for the inconvenience caused.

    Best Regards,
    HostHatch Support Team

  • dosaidosai OG

    Did a reboot and the network is back running with old ipv6.

  • MumblyMumbly
    edited August 2023

    They responded to my ticket finally and IPv6 work now. There wasn't a lot of explanation apart from "I can see that 2a00:1a28:... is now responding to ping". It seems like they needed to do something at their end manually.

    I removed old subnet and the new one also work.

  • bjobjo OG

    Regarding their mail: some explanation would have been nice. Maybe I should move my borg backups to their ams location or to a storage box @mxmla

  • coldcold OG

    oh great they are more and more like VirTrash ipv6 is changing AGAIN...

  • bjobjo OG

    Did they change it before?

  • hosthatchhosthatch Hosting Provider

    @cold said:
    oh great they are more and more like VirTrash ipv6 is changing AGAIN...

    When was the last time to be exact?

    We're phasing out a ~9 year old range and moving customers to our own RIPE space instead. But still interested in finding out the answer to when the last time was? :)

  • coldcold OG

    @hosthatch said:

    @cold said:
    oh great they are more and more like VirTrash ipv6 is changing AGAIN...

    When was the last time to be exact?

    We're phasing out a ~9 year old range and moving customers to our own RIPE space instead. But still interested in finding out the answer to when the last time was? :)

    I need to check my tickets with you but I think something about a year maybe sooner

    Thanked by (1)hosthatch
  • MumblyMumbly

    To be fair to Hosthatch, their stuff can run solid for years. Consistency and stability is not their weak side.
    The only thing that can be frustrating sometimes is their "support" and I am not talking about support per se (yes, I know that we're on budget plans), but when technical issues are explicitly on their side out of the customer's power. It can be a bit challenging to keep calm when one can't do a sh... and no one responds for days.

  • bjobjo OG
    edited August 2023

    Seems IPv4 and IPv6 switched to AS60068 / Datacamp/CDN77 as upstream.

    Edit: Ipv6 seems to switch between CDN77 and Portlane. Sometimes the firsthop is 2a00:1a28:1157::1, sometimes 2605:4840:ffff::1

  • bjobjo OG

    And IPv6 is down again with the new address.

  • dosaidosai OG

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

    Same.

  • MumblyMumbly

    Same, down.

  • bjobjo OG
    edited September 2023

    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.

  • bjobjo OG

    Besides that: fe80::1 still down.

  • MumblyMumbly

    Yeah 8 - 10 hours later, still down.

  • MumblyMumbly

    It works now!

  • bjobjo OG

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

  • bjobjo OG

    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
  • MumblyMumbly

    @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? :)

Sign In or Register to comment.

© LowEndSpirit 2024

ipv6 ready