[–] 2 points 1 day ago

It's just a 'proper' IPv6 private address, the IPv6 equivalent of '10.'.

I say proper as a private address in ipv6 is supposed to be fd, then 40 random bits, then whatever you want. Nothing stops you from having fd::/64 as your private network though. The thinking was people who got tired of merging networks that happened to choose the same 10.x.x.x scheme and/or vpn connecting to multiple sites similarly with the same private address. So they thought it would be swell if every private network on earth would likely be unique, so they said you 'must' randomize 5 bytes of it. Then no renumbering/no conflicting vpn connections.

  • source
  • parent
  • context
  • Further the audit log that you pretty much always need to consult when something fails for mysterious reasons in case it might be SELinux isn't even readable by the user that got dinged. So I can't even code in a way to check if SELinux was the reason and guide the user, instead I have to provide a diagnostic utility they have to 'sudo' to explain to them, or be vague and say 'check if selinux is somehow involved. So I end up despite doing my damndest to not run with privilege asking users to run something with privilege to check a security mechanism.

    fedora preinstalls a tool that warns users if they have tripped up in selinux, and provides dome details

    alerts are shown to the user in desktop notifications, and there's a gui tool with some actions

  • source
  • parent
  • context
  • [–] 2 points 1 day ago

    By adding a host, or /32, route to the gateway you should then be able to use it as the default gateway on your main subnet. I was not being serious when I suggested it, as another comment says, it's a pretty stupid idea, and there really isn't any sane usecase for it, except possibly one of those 1am "if it's stupid but it works it's still stupid, but it'll do until morning" type fixes that you shudder to recall years later.

  • source
  • parent
  • context
  • [–] 2 points 1 day ago

    The real nightmare when someone puts two ip addresses on the same host through different interfaces. Now that makes for some confusing troubleshooting and explanations in various applications.

    What really gets me is in about 3/4 networks in the last couple of weeks I've been asked to help troubleshoot, the problem has been duplicate IP addresses. I don't know what is going on with people...

  • source
  • parent
  • context
  • [–] 4 points 1 day ago (1 child)

    It can be made to work, just really really stupid.

    Ultimately the 'gateway' is really a mac address, and the IP is just the thing to ARP to get the mac address. And you can do some gnarly things to pull off things like off-subnet gateway addresses.

    You should never ever do it, but you can if you hate yourself enough.

    Becomes easier in IPv6 to do these shenigans too.

  • source
  • parent
  • context
  • I recently had a ticket for a university that had a /12 of public IPs. They gave every computer, printer, etc. a public IP on their whole network. Nothing has NAT. It was insane. They could buy an entire other university building with the money they'd make selling some of that address space down to even a /24.

  • source
  • parent
  • context
  • [–] 3 points 1 day ago (1 child)

    That’s mostly because it violates established standards, but you know that already. Lol.

    Hey, for all you know he might actually be the proper owner of that subnet.....

    I know if by some crazy coincedence I had that in my subnet I'd be using it for fun.

  • source
  • parent
  • context
  • view more: next β€Ί