832

submitted 1 day ago by qaz@lemmy.world to c/programmer_humor@programming.dev

159 comments fedilink hide all child comments

top 50 comments

sorted by: hot top controversial new old

[-] blackstrat@lemmy.fwgx.uk 17 points 9 hours ago

Ipv6 is broken for those that want control over their home networks thanks to Google and terribly written RFCs.

All that was needed was an extra byte or two of address space, but no, some high and mighty evangelicals in their ivory towers built something that few people understand 30 years later. Their die hard fans are sure that this will be the year of ipv6. The Year of Linux on the Desktop will come 10 years before the year of ipv6.

[-] electricyarn@lemmy.world 4 points 7 hours ago

And 10 years before fusion power?

[-] into_highest_invite@lemmygrad.ml 1 points 7 hours ago

is a /56 not enough address space for your home network

[-] silasmariner@programming.dev 2 points 6 hours ago

My home network is millions of ants with tiny little backpacks

[-] into_highest_invite@lemmygrad.ml 2 points 6 hours ago

you'll never believe this

[-] silasmariner@programming.dev 2 points 6 hours ago

The backpacks themselves? I'm glad you asked. So, they each function on an actor model, where each potential state for each actor has its own address...

[-] into_highest_invite@lemmygrad.ml 2 points 5 hours ago

are there quintillions of states

[-] DarkSideOfTheMoon@lemmy.world 10 points 12 hours ago

Also for home network I don’t won’t my IOT to have a real IP to the Internet. Using IPv4 NAT you can have a bit of safety by obscurity

[-] StopSpazzing@lemmy.world 2 points 11 hours ago

Its unlikely someone with guess your ipv6 of your iot.

[-] IphtashuFitz@lemmy.world 6 points 7 hours ago

No, but it’s far easier to explain how to configure your home network such that 182.168.1.* is for your regular devices like laptops, etc. and 192.168.2.* is for your IoT devices. Then block all access from 192.168.2.* to the internet so your IoT devices can’t “phone home”, can’t auto-update without your knowledge, can’t end up as part of a botnet, etc.

[-] StopSpazzing@lemmy.world 1 points 6 hours ago

That's the thing, you are still thinking in ipv4 terms, and that's ok. It's a different way to think of things using ipv6 and the proper way to configure them. No worries tho. Not like you are being forced to ipv6 for internal home networks.