301

Happy 30th birthday to RFC 1631 ("NAT"), the "short term solution" we all rely on (datatracker.ietf.org)

submitted 5 months ago by BodilessGaze@sh.itjust.works to c/programmer_humor@programming.dev

39 comments fedilink hide all child comments

From the conclusion:

NAT may be a good short term solution to the address depletion and scaling problems. This is because it requires very few changes and can be installed incrementally. NAT has several negative characteristics that make it inappropriate as a long term solution, and may make it inappropriate even as a short term solution. Only implementation and experimentation will determine its appropriateness.

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

[-] Hobbes_Dent@lemmy.world 45 points 5 months ago

192.168.1.1/24. Got it.

- Everyone

[-] qjkxbmwvz@startrek.website 19 points 5 months ago

I've only recently branched out from router defaults...only reason was that I wanted to VLAN off my home network, and mostly just so [Home Assistant-controlled] smart devices can't talk to the Internet at all.

[-] qprimed@lemmy.ml 31 points 5 months ago* (last edited 5 months ago)

10.0.0.0/8

172.16.0.0/12

192.168.0.0/16

🎶 a whole new wooorrrld... 🎶

[-] neidu2@feddit.nl 9 points 5 months ago

Whenever I'm given the chance at work, I let my feelings be known about using "consumer grade addressing schema" in production clusters. Sure, I use it at home, but anything beginning with "192.168" looks like my moms wifi, and has no right being part of a production network.

This comment was sponsored by the 172.16.0.0/12 gang