The "Unique Local Address" is exactly what you're looking for. fc00::/7
gives you enough bits that if you generate a random number instead of just picking one the chances of collision are small.
Does this mean I'll need extra protections so my router would not automatically start advertising these private IPv6 addresses to the world?
The RFC that covers these ULAs (RFC4193) specifically states that these numbers should not be routed on the internet, though two peers may mutually agree to pass certain prefixes. Unless Comcast decides to unilaterally route these (unlikely in the extreme) you should have no worries about route advertisement.
Assuming I will never, ever, tie that IPv6 address into the real internet (a router will NAT & firewall it), can I ignore the RFC to an extent and go with fc00::4:0/120?
Don't assume that. For instance, Comcast is currently doing IPv6 trials and they're passing out /64's to end-users (slide 5); not just the single address they're doing with IPv4. This means that their now-running IPv6 testers have the option of running with globally routeable addresses, but firewalled by their router, or do some kind of NAT with either link-local or unique-global-addresses.
However, running without any kind of address translation is not as insane as it sounds. Keep in mind a few points.
- Comcast is handing out a /64 subnet to you, so your attacker already knows what your IP space looks like.
- A /64 provides a mind bogglingly huge number of potential addresses. 2^64 worth! That's four billion IPv4 Internet's worth of IP addresses. (2^64 == 2^32 * 2^32. Four billion times four billion .) While the nature of IPv6 autoprovisioning reduces the actual number of addresses that need scanning, scanning it is still infeasible.
- Unless you set up your own domain to provide it, Comcast will not be providing forward or reverse DNS lookups to your /64-worth of IP addresses. This greatly reduces the ability of attackers to recon your network.
- Running without NAT makes certain network problems easier, and certainly makes undesirable but very popular peer-to-peer technologies (you know what I'm talking about) a lot easier to get up and running.
Running without a firewall is still just as insane as it sounds, though. Happily, you can do firewalling without having to NAT.
Second question, what's this link-local thing?
Think of it as able to reach anything in the current broadcast domain, and can not be routed. Like NetBEUI-of-old. In fact, if your home network is completely flat you can use these addresses instead of Unique Local Addresses.
Third question, what is scope id for?
It's used for two different things, which makes it annoying to describe:
Thing 1: Multicast. It defines how far the multicast packet is intended to reach.
Thing 2: (What I think you're referring to) This is used on a URI as a way of defining which interface to use. It's used primarily with link-local addresses. It should never be used in conjunction with CIDR notation, so the two syntaxes should never be combined.
Best Answer
DHCPv6 does not need to be configured to issue IPv6 addresses for a network to function. Rather, each machine assigns itself a link local address (within
[FE80::]/16
), optionally based on its MAC, but possibly random. It then listens for router advertisements, and based on the advertised prefixes, it will assign itself one or more addresses using the same logic. Typically, a host will assign itself one or more random addresses which it will use to initiate connections, thus protecting its privacy (eg. not disclosing its MAC to all hosts on the internet, and not keeping a consistent network address); it will keep a consistent one as well, for other hosts to initiate connections to. Hosts, having discovered a prefix, will then query DHCPv6 to figure out stuff like their DNS servers.That would be where the extra addresses are coming from (your use of disabling router discovery confirms this). For it to assign itself an address within
[1024::]/64
, some router on the network (running a router advertisement daemon) would have to be broadcasting that subnet; a network capture could tell you which. The packets will show up as ICMPv6 NDP router advertisements.