this post was submitted on 01 Aug 2025

857 points (96.5% liked)

Programmer Humor

25511 readers

2110 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 2 years ago

MODERATORS

anzo@programming.dev

Feyter@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

857

We don't talk about IPv5 (lemmy.world)

submitted 5 days ago by qaz@lemmy.world to c/programmer_humor@programming.dev

177 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] IphtashuFitz@lemmy.world 11 points 4 days ago (1 children)

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 6 points 4 days 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.