this post was submitted on 04 Nov 2026
680 points (99.1% liked)

linuxmemes

33329 readers
442 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 3 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] signalsayge@infosec.pub 19 points 21 hours ago (3 children)

    I love that people forget about 127.0.0.0/8 being the loopback network. Everyone just uses .1 when there are so many to choose from.

    According ding the the law of minimal keystrokes, there's actually only 9 to choose from.

    After applying the law of minimal motion, you're down to even fewer.

    Then you go a step further to just using 127.1 (or your preferred last digit)

    [–] Aceticon@lemmy.dbzer0.com 3 points 14 hours ago (1 children)

    People also commonly do not know that the reserved for intranet ip address range of 192.168.0.0 is actually /16 so you can pick any number between 0 and 255 for that 3rd byte and have their whole network in a range other that 192.168.0.0/8 like pretty much everybody else.

    [–] jj4211@lemmy.world 2 points 7 hours ago

    I have had to deal with a lot of companies where they did the opposite, acted like 192 was a /8 and did stuff way out of the private range.

    [–] lawks@aussie.zone 5 points 20 hours ago* (last edited 6 hours ago) (1 children)

    IPv6: Fuck you, you're only allowed one, now. Yeah, yeah, I know there are about 340 undecillion addresses in the space, but I know better than you, no one in history has ever needed to bind different services to the same port on the loopback interface, and if they did they were doing it wrong. Oh you made an RFC draft? Well I let the one from ~~2015~~ 2012 expire, so good luck with your current proposal, pleb.

    [–] Equinox1289@sh.itjust.works 2 points 18 hours ago (1 children)

    Can't you just use a ULA address for that?

    [–] lawks@aussie.zone 3 points 15 hours ago* (last edited 15 hours ago) (1 children)

    So the onus is on every individual user, to pick a random ULA prefix, bind specific addresses from it to the loopback interface, which is a different procedure for different OSes, probably requires root or elevated privileges, can have hard limits on, document it, etc. Greeeeaaaaaaat design. IPv6 gives out /64 like they're about to turn bad, but can't spare a /104? Gimme a break.

    I can dig a hole with a spoon, too, but if someone made it so that no one was allowed to dig holes with shovels unless they build their own (and have permission to build the shovel), when previously everyone was allowed to dig with shovels, I would not think highly of that person's wisdom.

    Maybe you think G. Huston of APNIC and W. Kumari of Google don't really know what they're talking about?

    [–] chronicledmonocle@lemmy.world 2 points 10 hours ago (1 children)

    I don't bother with ULA addresses on my home network and just use the public /56 I have broken into various /64s for each VLAN I have. In a corporate environment, I might use ULA addresses, but since IPv6 is "everything is public by design" and an Enterprise will have a static IPv6 block, if they did it right, it's not like it'll change. And for anything that doesn't need internet, link-local is a thing.

    IPv6 isn't perfect, but I find myself liking it more and more as time goes on. Some of it is habits. Some of it is that I tire of dealing with things like CGNAT and SIP.

    [–] Blaster_M@lemmy.world 1 points 7 hours ago (1 children)

    Link-local was made for same segment networking made easy

    IPv6 link-local: For when you just can't be bothered to address a damn thing πŸ˜‚