• 0 Posts
  • 15 Comments
Joined 11 months ago
cake
Cake day: August 6th, 2023

help-circle
  • Sorry, but your reply suggests otherwise.

    I’m at work, I’m not going to go into a thesis on ip allocation.

    The RIRs (currently) never allocate a /64 nor a /58. /48 is their (currently) smallest allocation. For example, of the ~800,000 /32’s ARIN has, only ~47k are “fragmented” (smaller than /32) and <4,000 are /48s. If /32s were the average, we’d be fine, but in our infinite wisdom, we assign larger subnets (like Comcast’s 2601::/20 and 2603:2000::/20).

    Correct all noted here https://www.iana.org/numbers/allocations/arin/asn/

    Taking into account the RIPE allocations, noted above, the closer equivalent to /8 is the 1.048M /20s available. Yes, it’s more than the 8-bit class-A blocks, but does 1 million really sound like the scale you were talking about? “enough addresses in ipv6 to address every known atom on earth”

    If you’re going to go through and conflate 2^128 as being larger than the amount of atoms on earth to a prefixing assignment scheme I’m just going to assume this is a bad faith argument.

    Have a good one I’m not wasting more time on this. The best projections for “exhausting” our ipv6 allocations is around 10 million years from now. I think by then we can change the default cidr allocations.

    https://samsclass.info/ipv6/exhaustion-2016.htm

    Its old sure but not worth arguing further.



  • I’m fully aware how rirs allocate ipv6. The smallest allocation is a /64, that’s 65535 /64’s. There are 2^32 /32’s available, and a /20 is the minimum allocatable now. These aren’t /8’s from IPv4, let’s look at it from a /56, there are 10^16 /56 networks, roughly 17 million times more network ranges than IPv4 addresses.

    /48s are basically pop level allocations, few end users will be getting them. In fact comcast which used to give me /48s is down to /60 now.

    I’ll repeat, we aren’t running out any time soon, even with default allocations in the /3 currently existing for ipv6.







  • Accepting ssh key fingerprints on first ssh is a bad practice. Ssh ca’s and or sshfp are around and have been for decades. Accepting random host keys is like trusting random self signed ssl certificates.

    Use ssh ca’s for user and host keys so you can revoke and rekey hosts without having to update authorized keys. And then you can revoke access to hosts for users as well and much more.


  • It’s more likely an admission they have to trampoline every gpl function in the kernel which isn’t really easy to do and would let that kernel module run on any other kernel. Otherwise they would have to do a shim like nvidia which would mean a whole other level of issues like saying we support Linux but only Ubuntu which as a non Ubuntu user would mean to me they do not in fact support Linux. I’d vote with walle here but I already don’t own this game as my friends said the user base is terrible years ago but this just means there is no reason to buy any of their games.