What about it is fiddly?
The insane addresses. The reliance on DNS, the unpredictability of addresses, that each device can have so many addresses and you need to know what each does and is used for and how that impacts inter-network routing and firewall rules. Privacy IPs, what the hell? Its a solution to something that’s fixed by tried and understood IPv4 NAT.
If you just want a flat simple network where everything on your lan is equal, everything has a globally unique and trackable IP I’m sure it’s fine. But if you have something more sophisticated it becomes much more complicated. And I genuinely can’t see how IPv6 advocates can’t see the problems it introduces.
What we need is a larger address space and fast adoption, that’s it. If after 30 years of awful adoption rates and only when people have a gun to their head they begrudgingly might adopt it, then you have a bad protocol.
But at that point there’s no difference other than it’s less familiar and more fiddly with v6. Why even bother.
Here’s my story of trying to use IPV6 for the past 3 days, and I know I’m not a typical user.
I use Opnsense as a router firewall. Using IPv4, 5/6 VLANs, almost all devices statically addressed with alias’s configured for each. This lets me have firewall rules like “block youtube on the kids devices”, or “use a different DNS server for the wife”, only allow the fire stick to access the internet after 7am. That sort of thing.
First problem is working out how to even get IPv6 on the WAN and what it even means that my ISP has given me a /48 and a /64. Loads of reading and some cobbling together later I have it. But no clients are getting addresses. Eventually fix that and now they have an address. But I don’t want to use SLAAC as that’s a nightmware to keep track of, DHCPv6 doesn’t work for android devices so they’ll be on IPv4 anyway. I don’t want each client to have a globally unique address as that just allows insane tracking. I don’t know if my IPv6 address will ever change, but it seems likley it will and that would be a nightmare to fix. I manage to get private fd00/8 addresses allocated to clients, but I don’t know how to configure IPv6 NAT so devices have an IPv6 IP, but can’t access through the WAN using it. And by that point I just don’t see the point any more. I’d just be duplicating all my rules that would be far too time consuming, confusing and I don’t see the point.
I want local private IP addresses. I don’t want clients to have unique IPs. I want the addresses to be known and static. I want my firewall rules to be tied to specific addresses for 90%+ of devices.
RAID IS NOT BACKUP RAID IS NOT BACKUP RAID IS NOT BACKUP
Don’t use Red drives for a NAS!! You need the Red Plus (or is it red pro) disks as they’re CMR.
I’d go for Ultrastar drives personally. There’s a few really good videos online analyzing the backblaze stats for different drives that are well worth watching.
EndeavourOS on my desktop and laptop. Works like a charm. By far the happiest I’ve been with a desktop distro.
On my server VMs I’m running Ubuntu Pro because it’s absolutely impeccably stable, Pro is free and I like the idea of having the option of not upgrading them for 10 years.
All running on Proxmox. I have a few appliance type VMs like opnsense and 3CX and they’re nice and stable too.
Or save yourself a character and just yay
I received so much spam and abuse of my network from .xyz domains that they are fully blocked in every conceivable way from being accessed or accessing my network.
A few people need to get off their horses and come up with and agree to IPv4². It’s exactly the same as IPv4 except there’s 2 more octets of address space - 48bits for addresses*. Job done. You’d see wide spread adoption in under 2 years and then we can forget about it all and move on with our lives safe from the clutches of IPv6.
I don’t give a crap that doesn’t neatly fit into 32 or 64 bit architectures. It’s more than doable at plenty fast speed and it keeps everything manageable.
Pretty sure my Seagate usb disks I use for backup are SMR and sustained writes are awfully slow. Luckily I’ve discovered restic for backing up which lowered a 1.5tb weekly incremental backup from 9hrs to 1 min.
Same as any OS, yes
It doesn’t tell you up front that it’s going to break
I highly recommend watching this guys videos on his analysis of the backblaze data https://www.youtube.com/watch?v=IgJ6YolLxYE&t=1
And a comparison of the difference WD drive colours, which might not be what you expect https://www.youtube.com/watch?v=QDyqNry_mDo&t=2
What utter BS. Stop spreading FUD from others. A simple search would find the source code https://github.com/snapcore/
Snaps are open source, including the store.
And why I no longer run NC. Every time it would fuck itself to death and I’d have to start from scratch again.
Ahh yes, the first time it is defined is in the conclusion after being used 25 times previously in the article.
Thank you! I hate unexplained acronyms
I skimmed through it and have no idea what BBR stands for.
I don’t understand it either. On one hand people say don’t remember addresses, use DNS and on the other DNS relies on static addresses but then every device is “supposed” to have random addresses via SLAAC or privacy addresses. It just doesn’t seem to tie together very well, but if you use them like IPv4 addresses you’re apparently doing it wrong.