• 1 Post
  • 246 Comments
Joined 3 years ago
cake
Cake day: June 29th, 2023

help-circle
  • No, you still need a gateway, maybe what you’re referring to is the lack of NAT? But that honestly makes it less confusing, there’s still a default gateway though. It’s funny you say the subnetting thing because for me it’s the opposite. In v4 subnets are variable sized, sure /24 is the most common but I’ve found everything from /8 all the way to /29 in the wild. In v6…every subnet in a sane network is a /64, it’s practically enforced by the standard. You basically can’t go smaller and going bigger is pointless. That means the first 4 hex groups are your subnet, the last 4 are the device, basically always. Now VPNs are one of the few environments where /64 isn’t super heavily enforced and you can go smaller but it’s still good practice to use it anyway. Memorizing addresses is…you’re not wrong, but also I personally don’t find it that bad and here’s why. The first half of the address isn’t THAT much longer than a v4 address. It is a bit, and yes it’s hex so letters. Thing is, the first half is the bit you can’t control, kinda equivalent to your public v4, so once you memorize that, the second half can be whatever you want and as short as you want. Worst case you can always use DNS to avoid memorizing addresses but that does require extra configuration.



  • 🤔, I’m not sure what would cause it to break other than a misconfiguration, my setup isn’t stock though, my most recent endeavor was migrating to a VTless system, so I do a lot of “different” and non-conventional things. Sure I’ve had configs break but it’s because I made a mistake, that’s not the init’s fault.




  • Having run both systemd and sysv, they both never really break in my experience unless it’s self inflicted. I don’t think I’ve ever just had one break randomly, the systemd recovery environment is much better when there is a breakage, and I’m not sure the boot times are really any different in my setup. Maybe if I tried something a little more parallel than sysv they’d be faster but eh.






  • Small ones are actually often better than big ones. I have a love hate relationship with cloudflare, they contribute to internet centralization but it IPv6 enables so many sites transparently and they only let you turn it off if you’re an enterprise customer. So some guy using free cloudflare has IPv6 but not discord, ironic. That being said I have NAT64+DNS64 which lets me access the remaining legacy v4 services without having v4 on my network or devices. Although according to my firewall stats over 90% of my traffic is v6 native, the remainder is NAT64. Honestly the only services I use on a regular basis which don’t work if I disable NAT64, discord, steam, and my bank. Everything else I use is v6 native, YT, Crunchyroll, lemmy (this instance), even steam downloads (just not login ironically).



  • It’s normal for the loopback con path to end in 1, each con path is unique for each interface. My guess is that if your pihole sometimes works, the IPv4 server is your pihole and the IPv6 servers are ISP provided (especially if there are 2), so they work for the internet but not your internal network. Ideally you would set your pihole’s IPv6 address as your IPv6 DNS as well. Failing that, setting the IPv6 mode in your network manager UI to “Automatic, addresses only” will make it not used for DNS






  • Might be possible? It’s not only possible but rather easy to do, in fact I often have multiple installs side by side in different subvolumes and I can switch between them, reinstall as needed, snapshot them. The only partition I have separate is /boot because it has to be vfat for the esp. Tbh accidentally blowing up a subvolume isn’t all that much more or less difficult to do than accidentally blowing up a partition. IMO if you’re paranoid about wrecking something the only safe separation is multiple drives and disconnecting the one you want to avoid touching. I keep home in a separate subvolume specifically for the separation you mention, it can persist across different installs because it’s separate. Subvolumes are fully isolated from most failures with the exception of filesystem corruption.