Conversation

Notices

1.  (mint@eientei.org)'s status on Tuesday, 13-Jun-2023 02:03:03 JST 

   • pomstan
   • 

   @pomstan @pomstan@xn–p1abe3d.xn–80asehdb @mint Classic Scaleway.

   $ ping срёт.онлайн PING срёт.онлайн(2001:bc8:1828:50d::1 (2001:bc8:1828:50d::1)) 56 data bytes ^C --- срёт.онлайн ping statistics --- 6 packets transmitted, 0 received, 100% packet loss, time 5111ms $ ping срёт.онлайн -4 PING (51.15.34.68) 56(84) bytes of data. 64 bytes from срёт.онлайн (51.15.34.68): icmp_seq=1 ttl=52 time=78.2 ms 64 bytes from срёт.онлайн (51.15.34.68): icmp_seq=2 ttl=52 time=77.9 ms 64 bytes from срёт.онлайн (51.15.34.68): icmp_seq=3 ttl=52 time=80.7 ms 64 bytes from срёт.онлайн (51.15.34.68): icmp_seq=4 ttl=52 time=77.8 ms 64 bytes from срёт.онлайн (51.15.34.68): icmp_seq=5 ttl=52 time=77.8 ms 64 bytes from срёт.онлайн (51.15.34.68): icmp_seq=6 ttl=52 time=78.2 ms ^C --- ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5006ms rtt min/avg/max/mdev = 77.797/78.425/80.650/1.005 ms

   I’ll make the local resolver ignore IPv6 records for your instance.

   •  (mint@ryona.agency)'s status on Tuesday, 13-Jun-2023 02:03:02 JST 

     in reply to

     • pomstan
     @mint @pomstan ping again
   •  (mint@ryona.agency)'s status on Tuesday, 13-Jun-2023 02:03:28 JST 

     in reply to

     • pomstan
     • 
     @mint @pomstan Now it seems to federate instantly.
   • pomstan (pomstan@xn--p1abe3d.xn--80asehdb)'s status on Tuesday, 13-Jun-2023 20:32:27 JST pomstan

     in reply to

     • pomstan
     • 

     @mint @mint kill yourself niggers

     live migration is what, 15 years old?

      likes this.
   • pomstan (pomstan@xn--p1abe3d.xn--80asehdb)'s status on Tuesday, 13-Jun-2023 20:32:28 JST pomstan

     in reply to

     • 

     @mint @mint god fucking dammit

   • pomstan (pomstan@xn--p1abe3d.xn--80asehdb)'s status on Tuesday, 13-Jun-2023 20:32:51 JST pomstan

     in reply to

     • 

     @mint @mint looks like cloud-init generates some bogus ipv6 configuration, they probably cached old instance metadata or something

     why the fuck would you assign ip addresses statically if they are really dynamic, that is the question

      likes this.
     Machismo repeated this.
   •  (mint@ryona.agency)'s status on Tuesday, 13-Jun-2023 20:35:40 JST 

     in reply to

     • pomstan
     @pomstan @mint That's been the case since at least 2018, IPv6 has been randomly stopping working on one of their ARM dedics. Eventually I just moved all my shit elsewhere after dealing with tunnel brokers for a while.