Skip to main content

ip address - Why is ARIN (etc.) allocating such large blocks of IPv6 addresses?



The whole issue of IPv4 depletion and waste seems to be finally getting behind us with the (somewhat) increased deployment of IPv6.



The sole purpose of IPv6 was to solve the issue of IPv4 address space running out. If that is the case then why are governing organisations allocating such large blocks of v6 addresses that are purely and utterly overkill and an obvious waste?



Is there logical reasoning behind the allocations or is it more of a case of a "I'm rich, Lets share them all around!" sort of thing?




For example, I was recently allocated a /48 block of v6 addresses with a single server. That's a staggering 1,208,925,819,614,629,174,706,176 addresses for my single server. I doubt the kernel would let me allocate that many addresses to an interface and I doubt any available NIC would support even a 10000th of them. Why are IPv6 addresses being handed out in such large blocks?


Answer



The main reason is that stateless address autoconfiguration as per RFC4862 requires a /64 network to work properly. Add to that the assumption that one will want more than a single subnet at one's installation and the difficulty of routing arbitrary multiples of a /64, and the automatic tendency seems to be to assign a /56, or if lazy, a /48.



Oddly, I'm already seeing the first signs of parsimony in the UK. I've had v6 in my home office for a couple of years, now, but recently changed provider. The old one gave me a /56 automatically; the new one gave me a /64, but when I mentioned that I was subnetting happily upgraded me to a /56 without charge.



My guess is that the base allocation will stabilise at a /64 once v6 becomes common, with anyone who has a half-decent reason for it getting a /56.


Comments

Popular posts from this blog

iLO 3 Firmware Update (HP Proliant DL380 G7)

The iLO web interface allows me to upload a .bin file ( Obtain the firmware image (.bin) file from the Online ROM Flash Component for HP Integrated Lights-Out. ) The iLO web interface redirects me to a page in the HP support website ( http://www.hp.com/go/iLO ) where I am supposed to find this .bin firmware, but no luck for me. The support website is a mess and very slow, badly categorized and generally unusable. Where can I find this .bin file? The only related link I am able to find asks me about my server operating system (what does this have to do with the iLO?!) and lets me download an .iso with no .bin file And also a related question: what is the latest iLO 3 version? (for Proliant DL380 G7, not sure if the iLO is tied to the server model)

linux - Awstats - outputting stats for merged Access_logs only producing stats for one server's log

I've been attempting this for two weeks and I've accessed countless number of sites on this issue and it seems there is something I'm not getting here and I'm at a lost. I manged to figure out how to merge logs from two servers together. (Taking care to only merge the matching domains together) The logs from the first server span from 15 Dec 2012 to 8 April 2014 The logs from the second server span from 2 Mar 2014 to 9 April 2014 I was able to successfully merge them using the logresolvemerge.pl script simply enermerating each log and > out_putting_it_to_file Looking at the two logs from each server the format seems exactly the same. The problem I'm having is producing the stats page for the logs. The command I've boiled it down to is /usr/share/awstats/tools/awstats_buildstaticpages.pl -configdir=/home/User/Documents/conf/ -config=example.com awstatsprog=/usr/share/awstats/wwwroot/cgi-bin/awstats.pl dir=/home/User/Documents/parced -month=all -year=all...

linux - How can I get my mediawiki to stop thinking I have cookies disabled?

I've searched half a day for how to resolve this issue, and can't figure it out. Shortly after I made my wiki a simple private wiki according to the instructions at Mediawiki's website, it started giving me this weird login error message: Wiki uses cookies to log in users. You have cookies disabled. Please enable them and try again. If I remove those private wiki settings, the error disappears, even if I try logging in. But I need it to be a private wiki for only my team. So what do I do? Here's what I've done so far. Just to be safe, after ever change, I try rebooting Apache using: sudo /etc/init.d/apache2 restart In my php.ini file, I have the following set: session.save_path = "/var/lib/php5" session.cookie_secure = secure session.cookie_path = /tmp session.cookie_domain = my server's internal URL (should I even set this? this field was blank before, but not commented out) session.referer_check = Off I ran the following to ensure that the fold...