Conversation

Notices

1. Embed this notice
   lamp (lamp@berserker.town)'s status on Tuesday, 03-Jan-2023 14:15:02 JST lamp

   #berserker.town does not support #IPv6 ☹️

   • arcanicanis likes this.
   • Embed this notice
     arcanicanis (arcanicanis@were.social)'s status on Tuesday, 03-Jan-2023 14:14:35 JST arcanicanis

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • lamp
     • Thorwegian ❄️
     3 out of the 4 US ISPs I've subscribed to in the past 5 years have provided service with CGNAT, and one other location that I had homeservers on fiber just switched to CGNAT less than two months ago:
     - Boingo Internet (WISP, on most military bases) in different 3 states
     - MetroNet (fiber), switched to CGNAT ~2 months ago
     - and my current local ISP (that I'll not name, because it's a smaller ISP that would narrow down my location)
     Spectrum/TWC was the exception, but wasn't available in some locations.
   • Embed this notice
     Thorwegian ❄️ (thor@berserker.town)'s status on Tuesday, 03-Jan-2023 14:14:36 JST Thorwegian ❄️

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • lamp

     @lamp @djsumdog @roboneko i'm not aware of a single ISP here that has customers share IP addresses, but i've heard of it from other countries

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

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • lamp

     @lamp @djsumdog @roboneko maybe there's more of an address shortage where you live. it makes no business sense to make IPv4 a second class citizen unless forced to. i suspect Norway might be spoiled with far more IPv4 addresses than it could ever need.

   • Embed this notice
     lamp@mastodong.lol's status on Tuesday, 03-Jan-2023 14:14:38 JST lamp

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • Thorwegian ❄️
     • かき@GNUsocialJP

     @thor @djsumdog @roboneko there was not enough choice for "ideological" decisions, it was either cable for 25 download and an AWFUL 3mbps upload, or this new wireless one which averages much better than that. Now fiber is available for the same price but I'm too satisfied to bother with it yet (they gonna have to schedule to run a fiber, dig a trench or whatever they gonna do)

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

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • lamp

     @lamp @djsumdog @roboneko picking an ISP like that sounds like an ideological decision

   • Embed this notice
     lamp@mastodong.lol's status on Tuesday, 03-Jan-2023 14:14:40 JST lamp

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • Thorwegian ❄️
     • かき@GNUsocialJP

     @thor @djsumdog @roboneko cuz my isp is ipv6-only and provides ipv4 by translating to ipv6 to a data center a ways away and then back to an ipv4 address that many customers are sharing... FOUR ipv4's now, each connection i make comes from a random one of four addresses

   • Embed this notice
     lamp@mastodong.lol's status on Tuesday, 03-Jan-2023 14:14:41 JST lamp

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • Thorwegian ❄️
     • かき@GNUsocialJP

     @thor @djsumdog @roboneko well i can get like 20-30% lower latency with it ?

     and it woulda let you federate with ipv6.social until they cow-towed and added ipv4 which defeated their whole point ?

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

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • lamp

     @lamp @djsumdog @roboneko why would changing the packet format lower latency?

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

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • lamp

     @djsumdog @roboneko @lamp there will be some amount of extra work to do, with little benefit for it, no matter what. if there was some kind of benefit, some way in which it actually helped... i mean, all i can think of is "help speed up adoption of IPv6 so we can all have more addresses to work with"

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

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • lamp

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

   • Embed this notice
     djsumdog (djsumdog@djsumdog.com)'s status on Tuesday, 03-Jan-2023 14:14:45 JST djsumdog

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • lamp
     • Thorwegian ❄️
     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™
     arcanicanis likes this.
   • Embed this notice
     Neko McCatface v2023 :verified::makemeneko: (roboneko@bae.st)'s status on Tuesday, 03-Jan-2023 14:14:46 JST Neko McCatface v2023 :verified::makemeneko:

     in reply to

     • lamp
     • Thorwegian ❄️
     @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
   • Embed this notice
     Thorwegian ❄️ (thor@berserker.town)'s status on Tuesday, 03-Jan-2023 14:14:47 JST Thorwegian ❄️

     in reply to

     • lamp

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

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

     in reply to

     • lamp

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

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

     in reply to

     • lamp

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

   • Embed this notice
     lamp@mastodong.lol's status on Tuesday, 03-Jan-2023 14:14:51 JST lamp

     in reply to

     • Thorwegian ❄️
     • かき@GNUsocialJP

     @thor it's using ipv6 for outbound requests.

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

     arcanicanis likes this.
   • Embed this notice
     Thorwegian ❄️ (thor@berserker.town)'s status on Tuesday, 03-Jan-2023 14:14:52 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.

   • Embed this notice
     Thorwegian ❄️ (thor@berserker.town)'s status on Tuesday, 03-Jan-2023 14:14:53 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.

   • Embed this notice
     lamp (lamp@berserker.town)'s status on Tuesday, 03-Jan-2023 14:15:01 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.

   • Embed this notice
     djsumdog (djsumdog@djsumdog.com)'s status on Tuesday, 03-Jan-2023 14:42:39 JST djsumdog

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • lamp
     • Thorwegian ❄️
     That just means your nation's ISPs are holding out to sell some of those blocks for billions. My fiber ISP recently switched to carrier grade NAT with zero notice (all my VPN connections to my hosted VMs just died and my tools showed I had a 100.x address). Thankfully I got on support and asked them to turn off CGN, they knew exactly what I was talking about, and I got a real IPv4 again (no cost, but I would pay for one).
     
     I think it's important to always have an IPv4 address if you can. They're going to get more expensive, and at some point the Internet will really be divided with the websites/services on IPv4 having even more reach. It's also always good to make sure you fully support IPv6 as well .. because we do really need IPv4 to die in a fire entirely at some point, and IPv6 is significantly complex enough that it takes a while to wrap your head around.
     arcanicanis likes this.
   • Embed this notice
     lamp@mastodong.lol's status on Tuesday, 03-Jan-2023 14:42:40 JST lamp

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • Thorwegian ❄️
     • かき@GNUsocialJP

     @thor @djsumdog @roboneko it's all fine when you're an old established ISP that already owns a good chunk of address space. but it's increasingly harder for new companies to get a hold of addresses... they have to buy them at auction for hundreds or millions of dollars. So of course they conserve them by sharing them amongst multiple customers at once with CGNAT.

     arcanicanis likes this.
   • Embed this notice
     Thorwegian ❄️ (thor@berserker.town)'s status on Tuesday, 03-Jan-2023 14:42:40 JST Thorwegian ❄️

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • lamp

     @lamp @djsumdog @roboneko that stuff is virtually unheard of over here. maybe because of this: Google tells me Norway has 16 million IP addresses assigned. that's >3X the entire population, so even if every child and adult in the country had 3 Internet connections, there still wouldn't be a shortage...

   • Embed this notice
     arcanicanis (arcanicanis@were.social)'s status on Tuesday, 03-Jan-2023 14:49:16 JST arcanicanis

     in reply to

     • Neko McCatface v2023 :verified::makemeneko:
     • djsumdog
     • lamp
     • Thorwegian ❄️
     I wouldn't say IPv6 is significantly complex; just that it's difficult at first with people who are so entrenched in thinking about everything in address scarcity than abundance, such as with subnetting. I've taught/trained Zoomers on networking in the military, by covering IPv4 and IPv6 simultaneously, and they didn't see IPv6 as much of a hurdle. In fact, subnetting is very often easier under IPv6, versus having to often use calculators for most allocations under IPv4. Meanwhile, when I was still in military (just a few years ago), networks were consistently being restructured from IPv4 addresses being shuffled around to skimp around scarcity and changes the size of various units.