Conversation

Notices

1. lamp (lamp@berserker.town)'s status on Tuesday, 03-Jan-2023 14:19:38 JST lamp

   #berserker.town does not support #IPv6 ☹️

   • djsumdog (djsumdog@djsumdog.com)'s status on Tuesday, 03-Jan-2023 14:19:20 JST djsumdog

     in reply to

     • Thorwegian ❄️
     • verified neko :verified::verified::verified::makemeneko:
     • :trole:
     I have Hetzner and have all my IPv4/6 dual-stack configured correctly, but I'm a big IPv6 advocate. @roboneko is right thought; it's just an additional IP address. It seems like the issue you had was that it was being used for outbound and other servers didn't know how to send things back.
     
     I would recommend getting familiar with IPv6. It's really not that difficult unless you're doing something crazy, like handling multiple IPv4 and IPv6 addresses on isolated docker networks (which I wrote a tutorial for because it's that insane):
     
     https://battlepenguin.com/tech/docker-with-ipv6-and-network-isolation/
     
     I started writing a status page application that would handle both IPv4 and v6 checks to make sure dual-stack setups are configured correctly, but it kinda got kicked to the backlog-of-life™
   • verified neko :verified::verified::verified::makemeneko: (roboneko@bae.st)'s status on Tuesday, 03-Jan-2023 14:19:21 JST verified neko :verified::verified::verified::makemeneko:

     in reply to

     • Thorwegian ❄️
     • :trole:
     @thor @lamp @thor @lamp it's literally just an additional ip address on the interface, you don't need to worry about the kernel part of the network stack
     
     you can remove the offending ip address from the interface with the usual tools. if the ip was retrieved via dhcp you can edit the config for your client. if it ended up there some other way then you'd need to figure out what did it obviously
     
     but aside from being annoying as fuck to work with and having shitty tooling they're really nothing to worry about. it's really is just an additional ip address on the interface
   • Thorwegian ❄️ (thor@berserker.town)'s status on Tuesday, 03-Jan-2023 14:19:22 JST Thorwegian ❄️

     in reply to

     • :trole:

     @lamp i can disable it on the kernel level but in my experience, this actually breaks stuff, so i can't do it.

   • Thorwegian ❄️ (thor@berserker.town)'s status on Tuesday, 03-Jan-2023 14:19:23 JST Thorwegian ❄️

     in reply to

     • :trole:

     @lamp to me, it's this subsystem that i didn't ask for and it keeps appearing everywhere and i have to keep plugging the leaks. the fact everything tries so hard to get you to use to it actually makes me want to resist it even more.

   • Thorwegian ❄️ (thor@berserker.town)'s status on Tuesday, 03-Jan-2023 14:19:24 JST Thorwegian ❄️

     in reply to

     • :trole:

     @lamp it's probably because Hetzner configures an IPv6 address that i don't think i've found a way of disabling, and i haven't bothered to manually config a netplan because doing that on a remote box can be a hassle if you accidentally bring it off the network. there's console access but still.

   • :trole: (lamp@mastodong.lol)'s status on Tuesday, 03-Jan-2023 14:19:25 JST :trole:

     in reply to

     • Thorwegian ❄️

     @thor it's using ipv6 for outbound requests.

     there's really nothing to it it's just like ipv4 but... again.

   • Thorwegian ❄️ (thor@berserker.town)'s status on Tuesday, 03-Jan-2023 14:19:26 JST Thorwegian ❄️

     in reply to

     @lamp i'm not seeing any AAAA record for berserker.town, so you must've dug that out somehow. see, i don't even know how you did that, which i probably should know if i'm going to run an extra protocol stack.

   • Thorwegian ❄️ (thor@berserker.town)'s status on Tuesday, 03-Jan-2023 14:19:27 JST Thorwegian ❄️

     in reply to

     @lamp oops, i thought i had removed all traces of IPv6 records and disabled any listening ports. i don't know enough about IPv6 to feel i can do it properly and securely. it's just one extra thing to worry about.

   • lamp (lamp@berserker.town)'s status on Tuesday, 03-Jan-2023 14:19:37 JST lamp

     in reply to

     • Thorwegian ❄️

     berserker.town's #IPv6 is 2a01:4f9:c011:b79d::1. @thor almost definitely needs to do nothing more than add `listen [::]:80; listen [::]:443 ssl;` to nginx and AAAA records to DNS. Nginx default server listens on it.

   • Thorwegian ❄️ (thor@berserker.town)'s status on Tuesday, 03-Jan-2023 14:20:09 JST Thorwegian ❄️

     in reply to

     • djsumdog
     • verified neko :verified::verified::verified::makemeneko:
     • :trole:

     @djsumdog @roboneko @lamp the only reason i have for bothering with IPv6 is external pressure to get familiar with it. altruistically adopting it? nah. it must at least offer some reward. but if i do it, the only reward will be silence, seeing as no one thanks you for using it.