Hacker News new | ask | show | jobs
by zinekeller 1636 days ago
Not this discussion again.

Okay, you can indeed do that... but how do you get an address is the another question. You might answer "Just go to the RIR", sure, but ASNs aren't given willy-nilly, they need to prove that they'll need different routing needs for external peering, and some RIRs do insist on this. The most loose RIR in terns of regulations is RIPE, but what about other companies in other parts of the world?
2 comments
eqvinox 1636 days ago
You get your private prefix by appending 10 random hex nibbles to "fd". For example, fdb9:3667:a8da::/48. (Please make your own random prefix.)

You also missed the point of this sub-thread since the question was about private space. IPv6 fd00::/8 is IPv4 10.0/8. The only difference is an added bit of semantics to make merging networks easier.

link
iso1210 1636 days ago
The problem is that ipv6 advocates say "just have your network auto-renumber itself every time you change upstream provider", "run multiple IP addresses on every host" etc

I don't think I've ever seen anyone suggesting using a /48 in fd00:: and NAT66 at the edge, and NAT64 is discouraged rather than maintaining a dual stack solution (and if you need to maintain a working ipv4 solution, why even bother with ipv6)

link
throw0101a 1636 days ago
> You might answer "Just go to the RIR", sure, but ASNs aren't given willy-nilly

You get an PI address block and ask your ISP to advertise it on your behalf in their public ASN, e.g.:

> If multi-homing to more than one provider, the customer must obtain an Autonomous System (AS) number, available at http://www.arin.net. If multi-homing only to us, we will provide a private AS number.

* https://support.allstream.com/knowledge-base/bgp-request-inf...

link
zinekeller 1636 days ago
> You get an PI address block and ask your ISP to advertise it on your behalf

And? Get nothing in some regions because all of their ISPs aren't willing to provide this service even with money?

I know provider-independent addresses, but don't pretend it'll solve the problem of IPv6. The fact that you need to do some service wrangling rather than "take this IP for private use, just don't ask us when IP conflicts happen" (and ULA implementation is inconsistent even in enterprise routers) means headaches abound that didn't exist for IPv4.

link