Slashdot Mirror


UK's 'Unallocated' IPv4 Block Actually In Use, Not For Sale

jimboh2k writes "The UK may have 16.9 million 'unused' IPv4 addresses but according to the department that owns them, they're not for sale. The Department of Work and Pensions says it would be too expensive to reallocate those addresses and, even if it did, it would not stave off IPv4 address exhaustion by much." The addresses in question are being used for a new internal government network. Of course, why that project wasn't built using IPv6...

157 of 203 comments (clear)

  1. Let the home office keep them by Anonymous Coward · · Score: 4, Insightful

    Changing the contract will cost them at least 20% more than the current overrun.

    1. Re:Let the home office keep them by arisvega · · Score: 1, Informative

      Changing the contract will cost them at least 20% more than the current overrun.

      Perhaps. But also:

      Of course, why that project wasn't built using IPv6...

      Because the administration wants proven techniques, and not to be a testbed for new technologies. "Big deal", the Slashdot crowd may say, "IPv6 migration is simple and costs effectively nothing". Again, perhaps: but try to see this from some department's/ministry's/government's point of view- all those stamps to be pressed, reports to be filed etc. Right now this particular department is probably not using the IPv4 addresses they own, and they see it as clever to keep them in stock for the time that they will need them. From their point of view, they are good for years to come so why change that.

      --
      The three laws of thermodynamics:(1) You can't win. (2) You can't break even. (3) You can't even quit.
    2. Re:Let the home office keep them by bmo · · Score: 3, Interesting

      > and not to be a testbed for new technologies

      But IPV6 is not new technology. The RFC is 14 years old, and current computer operating systems already speak it. An 11 year old operating system, Windows XP, speaks it. http://support.microsoft.com/kb/2478747

      The "install" is merely enabling what is already there.

      > From their point of view, they are good for years to come so why change that.

      But they aren't good for years to come. Once IPV6 comes out regularly, that horde of addresses will be worthless and they will be stuck with obsolete tech. No, wait, it's already obsolete.

      --
      BMO

    3. Re:Let the home office keep them by ifrag · · Score: 5, Funny

      One does not simply "file" a report in the UK.

      ...report to be filed, signed in triplicate, sent in, sent back, queried, lost, found, subjected to public enquiry, lost again, and finally buried in soft peat for three months and recycled as firelighters.

      --
      Fear is the mind killer.
    4. Re:Let the home office keep them by Anonymous Coward · · Score: 2, Insightful

      It is much newer than IPv4. The *real* question is one that should be asked of the people asking the *dumb* question, and that is: if you have 16.9 million addresses already bought and paid for, then why would you use IPv6?

    5. Re:Let the home office keep them by bmo · · Score: 2, Interesting

      Oh look, fear mongering from an AC.

      Do you have a stack of IPV4 addresses for sale? Or perhaps you are an ISP manager wanting to continue raking in the bucks for all those static IPV4 leases?

      >Anyone taking bets on how many bugs there'll be in the latest and greatest IPv6 stuff? And how many exploitable ones?

      Did the bugs in BIND prevent people from using BIND? Did the bugs in BIND dissuade people from connecting to the net at all? No. And honestly, (here comes the analogy, but it's not a car analogy - deal with it) unless you do a sea trial, your boat sits in drydock and you don't know if it will sink or not. What is certain is that your boat is worthless in drydock.

      Your post is just FUD.

      --
      BMO

    6. Re:Let the home office keep them by PhotoJim · · Score: 1

      Because you can sell them for $1.6 billion US (1 billion pounds)?

    7. Re:Let the home office keep them by arisvega · · Score: 1

      But IPV6 is not new technology.

      Of course it is not. But I am talking about burreaucrats and government institutions, so -in a relative way as scaled by this audience- it is "new technology".

      But they aren't good for years to come. Once IPV6 comes out regularly, that horde of addresses will be worthless and they will be stuck with obsolete tech.

      Good luck telling them that: they will only listen to you when they reach a "why can't I surf the web?" situation.

      --
      The three laws of thermodynamics:(1) You can't win. (2) You can't break even. (3) You can't even quit.
    8. Re:Let the home office keep them by davester666 · · Score: 1

      But why would an 'internal govt project' require 16+ million public IP addresses? Do they really want to make sure that that many systems are secure from unauthorized access?

      --
      Sleep your way to a whiter smile...date a dentist!
    9. Re:Let the home office keep them by rs79 · · Score: 1

      "But IPV6 is not new technology. The RFC is 14 years old"

      Every few years the give up and change shit again. It's still a tiny alternative network that nobody needs to use. The idea of suggesting the UK governmet build a giant v6 only internet network is humeroud at best, criminally negligent at best. Better would be to buy things that work and for the places that need to interoperate can be set up easily and the addressing within that network is only remotely an issue if you don't know what bits really are. Or what they're for.

      --
      Need Mercedes parts ?
    10. Re:Let the home office keep them by Yoda222 · · Score: 1

      Wheel is old technology. Several thousands years. IPv6 is 14 years. That's new.

    11. Re:Let the home office keep them by bmo · · Score: 1

      You don't know about IPV6/4 gateways do you?

      --
      BMO

    12. Re:Let the home office keep them by rinka · · Score: 1

      My team had implemented the IPv6 stack in Netware back in 2004. We had been involved in extensive interoperability testing against most of the major vendors.

      The casual user may not have heard of it but those days (of IPv6 being new) are long over. None of the hardware, or software is new now. Except perhaps application software but I have seen product managers across the globe weave v6 into their product plans over the past 3-4 years as we've ran out of addresses.

      I am willing to take that bet on bugs - yes there will be a few but not as many as you expect. Exploitable - well I've seen the intersection of security (firewalls, ta-da, what have you) and v6 being discussed some 4 years ago. I don't think that will be an issue.

      Perhaps the only issue might be massive scalability. But I'm willing to bet that is not going be a major issue for quite a while.

    13. Re:Let the home office keep them by bmo · · Score: 1

      See there are these things called gateways that you can buy that will take your IPV4 internal network and connect it to the outside world with IPV6. Today.

      >WinPhone 7.5 doesn't support IPV6

      1. Cite?
      2. Even if it doesn't, that can be taken care of at the telco level

      --
      BMO

  2. Enlighten me please by zero.kalvin · · Score: 3

    What's so difficult about switching to IPv6 ? I mean where the cost really is ? It is not like I have to buy all of my hardware again, it is mostly a software issue right ?

    1. Re:Enlighten me please by h4rr4r · · Score: 3, Insightful

      You might not, but lots of enterprise hardware would have to be replaced. This stuff has long life times and as the old gear dies off, ipv6 will come with the replacements.

    2. Re:Enlighten me please by PSVMOrnot · · Score: 5, Insightful

      For a home user it is not all that much of an issue, if you are running a remotely recent OS then it is probably already IPv6 capable. At worst you may need to replace your modem/router box, and those who would have trouble with this are likely to be with an ISP that takes care of such matters for them.

      When you are dealing with large scale infrastructure and corporate networks however, things become a little more difficult. At that scale the assumption of running a recent OS doesn't always hold, so you have software updates to worry about which incurs at least a time cost (and time is money). Also the possibly replacing your router becomes replacing racks worth of managed switches, routers, dchp servers and so on. That's not even beginning to take into account all of the legacy software that expects IPv4 and requires it in order to work.

      So, yeah. Simple for home/small business users, but a major project for the IT guys who make things work behind the scenes. Fortunately said tech guys should have been working on getting ready for this for a while already; just like when they made sure that the world didn't fall over at the turn of the millenium.

    3. Re:Enlighten me please by vlm · · Score: 2

      What's so difficult about switching to IPv6 ?
      I mean where the cost really is ? It is not like I have to buy all of my hardware again, it is mostly a software issue right ?

      layer 1 and layer 2, yeah, Pretty Much software only. I say pretty much because there's a trend to F around with upper layer stuff in lower layer gear, think IP DHCP filtering in a "layer 2 smart ethernet switch"

      The real killer is the cost of hardware accelerated layer 3 routing equipment that can insta-magically-switch ipv4 but drops down to software switching of ipv6. Luckily, normal size ipv6 bandwidth loads can be easily handled by commodity PC hardware doing solely software routing. Heck normal size ipv4 bandwidth loads work fine when software switched now a days.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    4. Re:Enlighten me please by Hatta · · Score: 3, Interesting

      Is there some reason "enterprise" hardware comes with firmware that can't be upgraded?

      --
      Give me Classic Slashdot or give me death!
    5. Re:Enlighten me please by Sqr(twg) · · Score: 2

      I have a hard time imagining that upgrading an internal network to IPv6 would cost more than what selling an IPv4 /8 block on the open market would net.

    6. Re:Enlighten me please by qwertphobia · · Score: 3, Insightful

      The software on my firewall (which is up-to-date) supports IPv6 in several ways. It can route IPv6 by OSPF. It can firewall and inspect IPv6 traffic. It can provide an IPv6 address to the management interface. It can use IPv6 to download software updates and signatures from the support portal. It can perform NAT6to4 to provide IPv6 connectivity to internal IPv4 resources. However it doesn't yet support Multiprotocol BGP, which is needed to route IPv6 by BGP. This is critical to us since we have multiple ISPs. I give this example because I have found most enterprise equipment "supports" IPv6 but not in a way that enables full replacement of IPv4 addressing with IPv6 addressing. Furthermore, we know how long government projects take to implement. If this one is just completed it probably started a decade ago...

      --
      Never ask for directions from a two-headed tourist! -Big Bird
    7. Re:Enlighten me please by drsmithy · · Score: 1

      What's so difficult about switching to IPv6 ? I mean where the cost really is ? It is not like I have to buy all of my hardware again, it is mostly a software issue right ?

      If only it were that simple. Hardware is cheap.

    8. Re:Enlighten me please by firex726 · · Score: 1, Offtopic

      Someones going to have to foot the bill.

      The manufacturer does not want to since the client company has already paid for the hardware ten years ago, so they'd have to pay Devs to update the firmware and not see any new sales.
      But if they wait then those companies will have to foot the bill by buying the new model they are currently advertising.

      You got companies who still use IE6 and XP, because they paid to have some proprietary app developed for that specific version, and don't want to have it redone to a modern versions.

    9. Re:Enlighten me please by petermgreen · · Score: 4, Insightful

      A few places

      1: routers need to both understand IPv6 AND be able to forward it quickly. If the hardware forwarding engines can't handle the larger v6 addreses then a software update won't help you much.
      2: any application software that needs to communicate over IPv6 needs to use the new v6 capable APIs. Converting software can be a pain either because it requires significant changes to support IPv6* or because the vendor is being a PITA and wants to tie in v6 support to an expensive upgrade you don't want. Or worse a v6 upgrade may simply not be available at all requiring the software to be replaced completely.
      3: while windows XP has some IPv6 support it's not ready for an IPv6 only world.

      *Some examples:
      * There is no direct IPv6 equivilent to WSAAsyncGetHostByName so any app that needs to perform lookups in the background will need to be converted to use threads for name lookups.
      * In windows XP it is not possible for one socket to listen for both IPv4 and IPv6 so apps that previously only listened on a single socket may well need design changes to allow them to listen on multiple sockets.
      * Any app that stores IPv4 addresses in a binary form or a fixed-width text feild will need data format changes

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    10. Re:Enlighten me please by silas_moeckel · · Score: 3, Interesting

      Firmware sure but those asics that make networking kit fast not so much. A lot of the first gen stuff punted ipv6 stuff to the cpu fine if you just want the line item but worthless if you want to actually use it for production.

      --
      No sir I dont like it.
    11. Re:Enlighten me please by gstoddart · · Score: 5, Insightful

      What's so difficult about switching to IPv6 ? I mean where the cost really is ? It is not like I have to buy all of my hardware again, it is mostly a software issue right ?

      Because nobody has any real interest in changing to IPv6. Everybody has a working IPv4 infrastructure, and isn't interested in spending money to change over because they have no idea of how that's going to make anything better.

      IPv6 has been coming "real soon now" almost as long as I can remember. And people have mostly been saying "I don't see any good reason" for just as long.

      For large organizations, changing to this is one of those things that nobody can figure out why they'd go through the time and expense.

      I know a lot of people on Slashdot look at IPv6 as some serious awesomeness that everybody should be jumping at. But, really, if you have thousands of machines already running IPv4, that 10.0.0.0 address is just fine for now and there's simply not a compelling reason to start undertaking the transition.

      What's the benefit? What reason would a large corporation find that makes them decide to go through the pain of transitioning? By the time you invest in changing everything over and going through all of the expense and disruption ... in what way would companies be looking at getting an ROI from this?

      I just can't see why people think organizations should be undertaking this, because I don't see the pay off and the business case to be made for it.

      --
      Lost at C:>. Found at C.
    12. Re:Enlighten me please by djsmiley · · Score: 1

      How many bits for a IPv6 IP vs a IPv4 IP?

      Yes of course they should of thought about this before designing the hardware with a maximum ability to comprehend a ipv4 IP; but then again someone should of thought of the Y2K problem before 1998....

      --
      - http://www.milkme.co.uk
    13. Re:Enlighten me please by Anonymous Coward · · Score: 1

      Hardware costs are not really the issue. The problem is the devices (servers, printers, TV-cameras, etc.). Reconfiguration of those devices are a huge pain. Sure, many of them can get a new IP-address with DHCP. But some of the devices have hard coded ip-adresses (they don't even use DNS), hosts-file finfiguration and so on. Some systems may have programs where the address is compiled into the executable. And no-one knows where the source is.

      Also in many older systems, it is common that the communication flow is not documented. E.g. Imagine changing a assembly-line server to a new address and you don't reconfigure one of the many other systems it interfaces with (because you don't know the interface exists). If you are lucky it will fail with a boom, and you can fix it. If you are unlucky it will seem to work for weeks or months, until someone asks to see the log from the zyxxy-sensor data. The data are not present because the sensor was not reconfigured. Now, can you trust the procucts you manufactured over that period.

      The business risks are huge when doing IP-address conversion in a complex environment.

    14. Re:Enlighten me please by Anonymous Coward · · Score: 1

      Think of the differences a bit like the Y2K bug with legacy hardware. If the inside of a router was a simple general purpose cpu there wouldn't be an issue but this is dedicated hardware that is designed to process 4 octet addresses. Besides that there is differences in routing configuration that wouldn't fit into the same memory spaces these devices have. It would be cheaper to replace the devices than try to produce an upgrade.

    15. Re:Enlighten me please by ShanghaiBill · · Score: 2, Insightful

      I have a hard time imagining that upgrading an internal network to IPv6 would cost more than what selling an IPv4 /8 block on the open market would net.

      It doesn't matter because this is a government organization. If they sell the IPv4 block the proceeds will not go into the same account that is used to fund an IPv6 conversion. The cost of an IPv6 conversion would mostly be the salary cost of the personnel doing the conversion. Governments don't pay salaries using money from "selling stuff". If they allowed that, it would open the door to all sorts of corruption.

    16. Re:Enlighten me please by erroneus · · Score: 1

      re-training/education, software compatibilty, firmware compatibility...

      At the office we are routinely turning IPv6 in order to make things work. (I'm not saying that's the right approach but turning it off on everything keeps things running.) IPv6 is a great idea but it's also very alien. Why didn't they just make it IPv4 with an added two bytes for addresses? I guess IPv4 is just too simple and needed to be made more complicated. It always make some people feel smart to know things everyone else doesn't. Hooray for elitism.

    17. Re:Enlighten me please by jimicus · · Score: 2

      just like when they made sure that the world didn't fall over at the turn of the millenium.

      Back then there was a clear deadline that we all knew about and no practical way to stave it off.

    18. Re:Enlighten me please by gstoddart · · Score: 4, Insightful

      If only it were that simple. Hardware is cheap.

      Hardware is cheap if you're talking about a single thing, but the time to do this is pretty expensive.

      I worked on a project last year to upgrade a single enterprise-critical application -- we spent over $250K on hardware, and another million on manpower for the project.

      I've heard that rolling out Win 7 to replace XP is costing several hundred thousand per day in terms of resource costs, but that's quite removed from the source.

      Most organizations would likely spend huge amounts of money transitioning their infrastructure and applications to IPV6, probably with a lot of pain points, and at the end of the day ... what has the money bought you? Is your network faster? Is it more reliable? Are your operating costs lower? Are you more profitable?

      Or have you sunk a bunch of money into something which a bunch of networking geeks think is sexy but nobody else can figure out why they've even bother?

      In the end, it seems like a lot of work and overhead for something which seems to have some very vague short-term benefits ... and "ZOMG, you won't need to do NAT any more as everything in the world can have an IP address" is one of those reasons that usually makes me go "and then what?". People are still going to want to NAT their internal stuff behind a firewall anyway.

      I'd love to hear some compelling reasons for a company to do this. But to date, I haven't heard any. Other than the size of the address space, I don't actually know what problems IPv6 solves. The fact that companies don't seem to be flocking to it tells me I'm not the only one.

      --
      Lost at C:>. Found at C.
    19. Re:Enlighten me please by h4rr4r · · Score: 1

      You can't sell ti though. You still need to have IPv4 support for the next decade or so.

    20. Re:Enlighten me please by mwvdlee · · Score: 3, Informative

      Upgrading IPv4-only firmware to handle both IPv4 and IPv6 may require more processing power and memory space than the hardware can provide.

      Obviously the more expensive hardware would be able to cope, but those were more expensive so nobody bought them.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    21. Re:Enlighten me please by asdf7890 · · Score: 1

      I suspect you have never been exposed to civil service bureaucracy.

    22. Re:Enlighten me please by Eraesr · · Score: 1

      Call me naive. Perhaps I am because I don't know a whole lot about this subject, but couldn't companies just buy some kind of IPv6 router that can act sort of like NAT and assign IPv6 addresses to individual devices, but translate those addresses to IPv4 as data comes in? That way a company could just use IPv4 addresses internally and for the outside world, run everything through an IPv6 converter.

    23. Re:Enlighten me please by asdf7890 · · Score: 1

      That only works if the hardware can cope with the new software. Firmware updates are usually intended to support bug fixes not major feature changes, so while a lot of hardware will have room for firmware a little larger than it is provided with (to support bug fixes and small new features) you'll not find a lot that has room for a whole new network stack, either in terms of non-volatile storage to hold the code and RAM needed while it is actually running. Much of that kit was bought years ago (for such amounts of money that it surviving a decade was part of the plan) and back then and memory of most sorts was far more expensive than it is now.

    24. Re:Enlighten me please by cyber-vandal · · Score: 1

      They did. I've worked on code that said something along the lines of "if year is less than 74 then century = 20". And it's "should've" or "should have" not "should of". Should of doesn't make any sense.

    25. Re:Enlighten me please by rsclient · · Score: 3, Interesting

      Ick -- WSAAsynGetHostByName? In this day and age, you have a window handle lying around?

      I'm the Program Manager for WinSock at Microsoft. Have you looked at GetAddrInfoEx? In Windows 8/Server 2012, the DNS team added some Async features into it. Even better, it will properly handle IPv6 AND international domain names.

      And if you're doing the new "Runtime" programming for Windows 8, we done our best to make sure that most network programs never have to deal with IP addresses at all -- that means that new new RT apps should be IPv6 ready out of the box.

      (We also do the dual-stack thing with our sockets, so listener sockets just specify a port (or service) to listen on, and we automatically listen to both IPv6 and IPv4. We updates .NET 4.5 in the same way to make dual-stack be simpler.)

      Links: http://msdn.microsoft.com/en-us/library/windows/desktop/ms738518(v=vs.85).asp

      --
      Want a sig like mine? Join ACM's SigSig today!
    26. Re:Enlighten me please by unixisc · · Score: 1

      Also, the standard has been evolving for quite some time, and has still not been frozen. It's true that a lot of the equipment doesn't natively support IPv6, and it's hard to argue that they should when they risk building in features or functions that may get deprecated. Like site local addresses.

      Also, while a lot of concepts are similar, there are also a lot of brand new concepts that haven't really sunk in. Like, e.g., in IPv4, private IP addresses, such as 10.x.x.x or 192.168.x.x were used for several purposes, be it home networks, VPNs, NAT extenders, et al. But if someone is transitioning to IPv6 and has so far been having a network, say 10.1.x.x in his office, what does he use? Link-local addresses? Site-unique addresses? Admin-local? Organization-local? (Note that there are multicast addresses for the last 2, but not unicast addresses).

      I am a big supporter of IPv6 and want to see it start replaceing IPv4 in a big way, but there are several stumbling blocks towards getting there.

    27. Re:Enlighten me please by vbraga · · Score: 1
      --
      English is not my first language. Corrections and suggestions are welcome.
    28. Re:Enlighten me please by jd2112 · · Score: 1

      And you are willing to spend a butload of money on an upgrade that offers little if any increase in functionality and will most likely introduce new bugs that will have to be dealt with.

      --
      Any insufficiently advanced magic is indistinguishable from technology.
    29. Re:Enlighten me please by petermgreen · · Score: 2

      Ick -- WSAAsynGetHostByName? In this day and age, you have a window handle lying around?

      Old habbits die hard and all that but even if i'm not using it in new code there is still a need to adapt old code. So far the only way i'd found to do an IPv6 DNS lookup in the background of an event driven program using the windows DNS code is to create a thread to do it and have that thread notify the main thread when the lookup completes.

      Have you looked at GetAddrInfoEx? In Windows 8/Server 2012, the DNS team added some Async features into it.

      No I hadn't heard of it but there is no way i'm making my code dependent on win8 in the forseeable future.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    30. Re:Enlighten me please by fast+turtle · · Score: 1

      It is sort of like 802.11n. There are no less than 8 flavors of it floating around out there at different data rates and ranges. Most of the endpoint stuff you get out there is 1 antenna and 150 data rate in the crowded 2.4 range. My point not only do you have to switch out there is a huge gulf between 'crap' and 'awesome'. This is going to suck. Do not be in such a hurry to switch out..

      This is exactly why I don't even bother with 802.11n hardware. Most of it's using the crap 2.5GHz band instead of the 5GHz band that they simply drown each other out and actually go slower. In my location, I can see a grand total of 6 of those stinking 802.11n AP's and everyone of them is competing for the same bandwidth. It's why mine is set to the 802.11b speeds and you know what, I actually get close to the rated speed on the home network, even with the congestion we're seeing from the cheap "N" routers.

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    31. Re:Enlighten me please by fast+turtle · · Score: 1

      Interesting point that the IPv6 standard isn't even finalized and it explains why my ISP (TW) has stated they're not going to upgrade as yet, it's half baked.

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    32. Re:Enlighten me please by higuita · · Score: 1

      hey, if you want to stay in ipv4, go for it, use a 10.0.0.0/8 for your internal network, use NAT, etc.

      Now if you want to use a routable, public IPv4 class in your internal network, then you MUST migrate to IPv6. Not only you are laughing to all Asia countries with lack of IPv4 (and in a few months, several world locations) but in several months/few years you will to redo all that work to enable IPv6. They will spend more money doing twice. But hey, people are lazy and many thinks that "its not my money", so they dont care....

      --
      Higuita
    33. Re:Enlighten me please by Bert64 · · Score: 1

      Not really, you can do it the other way round but ipv4 has no way to address ipv6...
      What you can do is run application level proxies for eg http...

      Ofcourse there's no reason you can't dual stack your internal network, global ipv4 shortages aren't a problem if your using 10.x internally, and chances are anything you have which is old enough to not support ipv6 doesn't need to talk to the internet anyway...

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    34. Re:Enlighten me please by leighklotz · · Score: 1

      How many bits for a IPv6 IP vs a IPv4 IP?

      Yes of course they should of thought about this before designing the hardware with a maximum ability to comprehend a ipv4 IP...

      I remember having this discussion with people close to the principles about the NCP to TCP/IP transition when the 32-bit (four octet) address size was picked.
      The sound bite was that it's bigger than the biggest European phone number, so they planned ahead for a time when there would be as many computers as phones, which seemed way enough. (Remember, NCP had a hosts.txt file that listed all the hosts.)

      For DNS, they designed an hierarchical system, but events overtook the hierarchy and people got fetishistic about names, leading to most names being in ".com" and being public-facing. The original theory was that the hierarchy would be more important, with more hosts in organizations and so on.

      But on the IP side, the segmentation with subnetting (and later, classless subnetting) made things more complicated, so it became possible to run out of IP addresses even though there were still plenty available, but fragmented. Along the way with all the subnetting routing got more complicated and there were a few routing table crises that required new algorithms and lots of new designs, and that pretty much works miraculously now, but doesn't solve the walled-off inaccessible IP address problems.

      If you can figure out a way to transparently change who firewalled-off Class A subnet over to a non-routable private net and then release the class A net, you could reset the clock back to the problem IPv4 thought it was solving and become a zillionaire in the process.

    35. Re:Enlighten me please by unixisc · · Score: 1

      Depends on how long some enterprises have had certain hardware. For instance, a certain router or switch may not have enough flash memory in it to store all the extra code that adds the required IPv6 support. Normally, such gear have adequate flash in them to support upgradability, but that's not universally true, and it's one of the first places that companies cut corners while developing cost down versions of their flagship products.

    36. Re:Enlighten me please by gstoddart · · Score: 2

      They will spend more money doing twice. But hey, people are lazy and many thinks that "its not my money", so they dont care....

      Well, so far, people aren't even doing it once. So they're not paying for it twice (yet).

      The opposite of what you say is that companies don't want to spend money they don't see as providing a return. So when someone says "hey, we should spend money to go to IPv6", the company says "OK, what's in it for us" ... and if your entire answer is that there are starving children in Asia who can't afford an IPv4 address, well, I don't see why an Fortune 500 company would spend millions to make the switch just yet.

      There may be some Really Good Technical Reasons why people should ... but for the most part they get articulated as "ZOMG, we're running out of tubes for the interweb".

      As I said, IPv6 has been met with indifference for as long as I can recall, and largely because companies are asking the question "why should I do this now?" and not coming up with compelling reasons.

      There may or may not be short term thinking involved, but the amount of general apathy towards IPv6 in many circles tells me the people advocating for it need to come up with clearer and more convincing arguments than "because it's better" when all of the answers to "why" describe what seem like intangible benefits for the most part.

      And this is why geeks are often incapable of explaining something to decision makers. Because almost nobody on the "for" side of IPv6 seems to be able to string together a coherent, reasoned argument detailing why this is better. I'd love to see one.

      But mostly I see people whining about how evil NAT is, but without ever giving any supporting reasons.

      --
      Lost at C:>. Found at C.
    37. Re:Enlighten me please by unixisc · · Score: 1

      They should have made some initial products based on FPGAs so that the fast networking could be achieved, albeit @ low volumes & @ a price. Once volume picked up and price pressures increased, they could optimize those designs and replace them w/ customized ASICs.

    38. Re:Enlighten me please by unixisc · · Score: 1

      That is the solution that's called LS-NAT (Large Scale NAT), and it is a bitch to both implement & maintain. With it, one of the main reasons for going IPv6 in the first place - getting rid of NAT - is gone. A better solution is something called dual-stack lite, where the provider equipment is all IPv6 and that's what runs, but if a company is stuck on IPv4, that is tunnelled within IPv6 headers (the bundle being called softwires) and transmitted, and the IPv6 headers are removed @ the destination before it gets to the ultimate IPv4 target. But that requires the ISPs to be completely IPv6. This was incidentally the solution Comcast at one point went w/ in its field trials.

    39. Re:Enlighten me please by unixisc · · Score: 2

      Actually, the incentives for doing this is... a negative disincentive for not doing it. After a while, when public IPv4 addresses become really scarce and getting new ones will be like pulling teeth, IPv6 will be something people will have to spend an arm & a leg for just to be able to expand a network. The reason this is becoming more critical is that even NAT wouldn't cover it - one would have to go into a second level of NAT to cover it.

      So this is one of those cases where making a change is not gonna give one a new internet, or anything different, but not making the change will mean that one fine day, a company will find itself in trouble and @ a loss to expand its network.

    40. Re:Enlighten me please by unixisc · · Score: 1

      Adding even one bit would have caused the same scope of changes in everything listed above - all hardware, such as network printers, cameras, et al would have to get firmware updates to recognize this change (since it's in the header of the IPv4 protocol). Given that no matter what they did, a major change would be required, the IETF decided to bite the bullet, make the change but make it a huge change so that there may never need to be an incompatible upgrade to IPv6. If we ever have an IPv7, it would still have 128 bits, but maybe protocol rules different from IPv6.

    41. Re:Enlighten me please by Bronster · · Score: 1

      Seems to me they sold a product and made money from it - so your "should have" probably doesn't carry much weight with them.

    42. Re:Enlighten me please by Anonymous Coward · · Score: 1

      Fuck off with your useful APIs. I code linux in assembler, motherfucker. I don't use concurrency. I don't need it in my super fast linux software. I code directly to the ethernet port. DNS is my API. I got AAAAA records on my IPv7.

    43. Re:Enlighten me please by PhotoJim · · Score: 1

      The counter-analogy:

      You got a car a long time ago, and didn't really use it much. You still have it. It still works perfectly. And you now need to use it a lot, so you plan to do so. However, you find out that while it cost you only a few tens of thousands of dollars to buy it, it's now a valuable valuable car on the open market and you could get a billion dollars for it.

      Meanwhile, you can acquire the "new" car for a fraction of that cost. There's a learning curve, but you can afford to buy a lot of professional help and even build a fancy new garage for your new car with the billion dollars of cash you got selling your old car.

      Alas, you may only have a couple of years that this old car is worth so much. If you wait long, your value will plummet as everyone expects to be able to use the new roads.

      Of course it's easier to use the /8 of IPv4 IPs they have... but their huge market value today may not last. A billion pounds (not dollars, so it's more money than I was saying in my analogy) would pay for a lot of problems to be solved.

    44. Re:Enlighten me please by silas_moeckel · · Score: 1

      You do realize that fpga's were a lot more expensive and slower than a similar asic? A decade ago gigabit ports were high end layer3 switches were still a new idea and pushing the limits of what could be done. There customers wanted a check box and the companies gave it to them ipv6 works ont he devices just not line rate. If your still running stuff like cisco 6500 with sup 2's that kit is a decade old any only needs a replacement sup to enable ipv6 on the whole box or shift it to a L2 only role. Remember that at the time routing lookups of a 128 bit address was fairly hard, a lot of devices made the assumption that no network address would ever be longer than 64 bits and just dropped the lower 64 bits when making routing decisions.

      --
      No sir I dont like it.
    45. Re:Enlighten me please by petermgreen · · Score: 1

      But if someone is transitioning to IPv6 and has so far been having a network, say 10.1.x.x in his office, what does he use?

      There are really three choices. Internet addresses, unique local addreses and link local addresses. Lets consider them individually

      If it is highly unlikely you will ever change IPs (e.g. you have provider independent space or are strongly tied to your provider such that it is unlikely you will ever need to renumber) you may as well use internet addresses for everything. That way you are gauranteed uniqueness and if you decide to make something accessible on the internet later it's just a matter of changing firewall rules. If you are a small buisness and are running IPv6 It is likely most of your machines will have an internet IPv6 IP but I would advise against using it for internal stuff to reduce the pain if/when your ISP changes your prefix.

      Link local addresses are for stuff that you are pretty sure will never need to leave a single "link" (Unless it's split into VLANS an Ethernet network is a single "link" in this context regardless of how big it is).

      That leaves unique local addresses, theese are what you should use when you need private addresses that can be routed internally within your own network and to other cooperating networks but not on the general internet.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    46. Re:Enlighten me please by JeffAtl · · Score: 1

      Governments don't pay salaries using money from "selling stuff". If they allowed that, it would open the door to all sorts of corruption.

      Not directly, but law enforcement agencies do indirectly. They auction the items they've seized and use that to pay for equipment that would otherwise come out of the overall budget.

      You are right that it does open to the door to all sorts of corruption and the practice should be abolished. The agencies become dependent on the revenue.

    47. Re:Enlighten me please by erroneus · · Score: 1

      Ah yes.... IPv8 (since we skipped IPv5 to go to IPv6) will IP over subspace carrier and will handle complication such as data arriving before it was transmitted.

    48. Re:Enlighten me please by colinrichardday · · Score: 1

      But even adding two bytes to IPv4 addresses would probably requiring extensive modifications of current hardware.

    49. Re:Enlighten me please by petermgreen · · Score: 1

      Read the documentation more carefully. The function itself was introduced in vista but it's functionality was expanded in win8.

      Not that I care too much, I don't have any plans to stop supporting XP in my code in the foreseeable future.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    50. Re:Enlighten me please by marka63 · · Score: 1

      Actually it doesn't require the ISP to be completely IPv6 or even deploy the AFTR box as that can be outsourced at the cost of a little more latency.

      The AFTR box is still a LS-NAT. It just isn't a double NAT and doesn't have to be in-line nor a be a traditional router.

    51. Re:Enlighten me please by marka63 · · Score: 1

      Which isn't true. There are a whole suite of technologies designed to allow a IPv6-only host reach IPv4 only servers. Lots of mobile phones are IPv6 only devices today yet they still reach IPv4 only sites. Going from IPv6 to IPv4 is trivial. Going from a IPv4 only client to a IPv6 only server is harder only because it's hard
      to squeeze 128 bits into 32 bits and make that scale to a large number of clients.

    52. Re:Enlighten me please by marka63 · · Score: 1

      IPv6 is as finalised as IPv4 is. Whats going on now is tinkering and making IPv4 interop better. The main issue with deploying IPv6 is backend software that assumes that IP addresses are 4 octets, dotted quads or has hard coded AF_INET into the socket calls. Most of these issues are relatively straight forward to fix if you have access to the source code. There are address family agnostic techniques to address these issues that are well known.

      e.g. replace gethostbyname() with getaddrinfo(), replace "struct sockaddr_in" with "struct sockaddr_storage".

    53. Re:Enlighten me please by marka63 · · Score: 1

      But mostly I see people whining about how evil NAT is, but without ever giving any supporting reasons.

      Mainly because it is self evident to anyone who has had to code software to do anything other than the trivial connect to a server out there.

      If you want two clients to be able to talk to each other from behind a NAT you need to deploy a relay server or use STUN and PCP/UPNP and hope that the NAT is configured to support it. This all takes extra development time. Requires extra hardware for the relay server or the STUN server. It's also fragile.

      Without NAT each client knows its own address so no need for a STUN server. Depending upon the firewall it may need PCP/UPNP but there to it becomes simpler.

    54. Re:Enlighten me please by marka63 · · Score: 1

      No, we didn't skip IPv5. It just was not a main stream protocol.

    55. Re:Enlighten me please by erroneus · · Score: 1

      Its second version, known variously as ST-II or ST2, was drafted by Claudio Topolcic and others in 1987 and specified in 1990[4]. The final version of ST2, which was also known as ST2+, was drafted by the IETF ST2 Working group[5][6] and published as RFC 1819. ST2 distinguishes its own packets with an Internet Protocol version number 5, although it was never known as IPv5.
      Almost got me... taken from the page you linked us to.

    56. Re:Enlighten me please by unixisc · · Score: 1

      So unique local addresses - the fd00:/8 - are the ones to use in case of VPNs? I'm assuming that you'd not want to link 2 offices by using their link local addresses, since that would cause exactly the types of conflicts we see in IPv4. But do most people who are transitioning to IPv6 know about these 2, and the differences b/w them?

      Also, have site unique addresses - the fc00:/8 - been deprecated, or can one use them if one can come up w/ a mechanism of guaranteeing global uniqueness?

    57. Re:Enlighten me please by unixisc · · Score: 1

      I don't exactly follow. Where exactly do you have 16.4 million spare addresses? Releasing them back to either the RIRs, or selling them after splitting them would be a nightmare. Might as well just work on the IPv6 upgrade.

    58. Re:Enlighten me please by unixisc · · Score: 1

      If one needs to split it into VLANS, then what should one use - link local or unique local addresses?

    59. Re:Enlighten me please by petermgreen · · Score: 1

      Each vlan is a seperate "link" from the perspective of IP so if something needs to be routed between vlans unique-local or internet addresses should be used.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    60. Re:Enlighten me please by petermgreen · · Score: 1

      Also, have site unique addresses - the fc00:/8 - been deprecated, or can one use them if one can come up w/ a mechanism of guaranteeing global uniqueness?

      The intention with fc00::/8 was that they would be gauranteed unique (through a registration body) but not routable on the public internet. However no such registration body has yet been set up so any use of fc00::/8 at the moment would be a violation of the addressing standards.

      So for now we have to use fd00::/8 which is only "probabalisitically unique".

      So unique local addresses - the fd00:/8 - are the ones to use in case of VPNs?

      A VPN is no different from a physical connection.

      If your VPN operates on the ethernet level bridging users to a LAN then it would be no different from them physically plugging into said LAN . So you can use link local, unique local or internet addresses as appropriate.

      If your VPN operates on the IP level then you would have to use unique local addresses or internet addresses.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    61. Re:Enlighten me please by unixisc · · Score: 1

      And divided using the subnet part (the 4th word) of the address?

    62. Re:Enlighten me please by petermgreen · · Score: 1

      Right

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    63. Re:Enlighten me please by unixisc · · Score: 1

      So if somebody came up w/ a system to guarantee uniqueness of every unique address w/o registering anything beyond what already exists w/ the RIRs, should s/he use an fc00:/8 or an fd00:/8?

    64. Re:Enlighten me please by petermgreen · · Score: 1

      fc00::/8 should not be used until and unless the internet standards processes specify how it is to be used. IIRC there have been serveral proposals for allocation but none have yet been standardised.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  3. "new internal government network" by Anonymous Coward · · Score: 3, Insightful

    To me that means they should all be 10.x.x.x, and some IT workers are completely and totally incompetent.

    1. Re:"new internal government network" by Anonymous Coward · · Score: 4, Funny

      Government workers are completely and totally incompetent.

      FTFY

    2. Re:"new internal government network" by neokushan · · Score: 1

      Or by "internal" they mean "secret".

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    3. Re:"new internal government network" by Anonymous Coward · · Score: 2, Insightful

      Remember that this /8 was allocated many years before the publication of RFC1918, to which you refer.

    4. Re:"new internal government network" by backwardMechanic · · Score: 1

      It's a bit less secret now.

    5. Re:"new internal government network" by QuantumRiff · · Score: 3, Informative

      if you have connections to other networks, and/or vpn's, internal network IP's are a pain in the ass. How do you setup a VPN when both ends are using 192.168.1.x? easy, you overload NAT, so both sides see the other as a completely different subnet. Do that about 5 times, and then try to debug some firewall rules.. Many larger companies will now refuse to setup VPN's with companies that use reserved addresses, since its such a pain in the rear.

      By using a valid IP address, your assuring that they are globally unique.

      --

      What are we going to do tonight Brain?
    6. Re:"new internal government network" by firex726 · · Score: 1

      I'm curious about that too, I've heard some dumb reasons to try and justify a static IP use.

    7. Re:"new internal government network" by Ash-Fox · · Score: 1

      Many larger companies will now refuse to setup VPN's with companies that use reserved addresses, since its such a pain in the rear.

      Source?

      --
      Change is certain; progress is not obligatory.
    8. Re:"new internal government network" by Richard_at_work · · Score: 2

      Thats a bit strong, considering you know fuck all about the project they are implementing - "internal" doesn't necessarily mean "private", and there are many ways in which public addresses are beneficial.

    9. Re:"new internal government network" by QuantumRiff · · Score: 1, Informative

      We have had 4 companies we connected to with VPN's over the last two years. All 4 of them were medical industry companies with > 2,000 employees. All four required we have our own valid, routable IP range to use before they would connect with us.

      --

      What are we going to do tonight Brain?
    10. Re:"new internal government network" by Ash-Fox · · Score: 1

      That's not really enough to be considered 'many', assuming I could trust such information from further lack of published information references.

      --
      Change is certain; progress is not obligatory.
    11. Re:"new internal government network" by Chris+Mattern · · Score: 1

      They probably shouldn't have put the routers in the secret nuclear bunker.

    12. Re:"new internal government network" by vux984 · · Score: 1

      Remember that the govt said it was being used for a 'new' internal network.

      Calling an IT project "new", that predates RFC1918 is stretching "new" well past the breaking point.

    13. Re:"new internal government network" by Anonymous Coward · · Score: 1

      Could be you that's the incompetent.

      This new network is designed to interconnect with a bunch of other networks, and all the networks that are connecting to this network can be using any private network address - including 10.0/8. Therefore, inside this new network, they cannot use private address space, since that could cause routing issues with connected networks.

      They could potentially use 100.64.0.0/10.

      Also, note that the government *did not* say that this was for a new project, some editor at slashdot did. This project has been around for years, slapping some varnish on a giving it a new name does not make it new.

    14. Re:"new internal government network" by Ash-Fox · · Score: 1

      APK, couldn't or wouldn't?

      --
      Change is certain; progress is not obligatory.
  4. USternet by matt007 · · Score: 3, Informative

    Well some old dinosaur US companies or even universities own a full Class A.... do you think they need the address space more than a government ?

    IBM CSC Dupont MIT Ford Apple USPS... etc.

    see the list at : http://en.wikipedia.org/wiki/List_of_assigned_/8_IPv4_address_blocks

    1. Re:USternet by firex726 · · Score: 2

      Yea, some of those will have so many addresses that they could assign a static IP to each node and still have left overs.

      But then again it'd probably just delay things further. We're going to have to bite the bullet eventually.

    2. Re:USternet by matthew_t_west · · Score: 1

      I manage a college's network and we have a class B. Right now, we probably only use 30%, but with the growth of mobile devices, we are using more and more addresses. Each building has at least a class C for wired and a class C for wireless. It used to be, two buildings could share a class B. There's about 40 buildings, with 80 switches, 3 routers, 300+ access points, 100s of printers... Yeah, addresses get eaten up pretty quick.

      M

      --
      Browse at 1. You'll thank me later.
  5. Re:Because sixxs is a pain in the ass to get by Anonymous Coward · · Score: 1

    The biggest cost is that getting a sixxs tunnel is a royal pain in the ass as you not only need to set up a linkedin account but write a nice long essay about why you want it. How many people are going to go to that much trouble just to switch to ipv6?

  6. Re:ipv6 only, don't be stupid by sergioag · · Score: 1

    Obviously you haven't heard of 4in6, though a Dual stack approach (using 10/8) would be more convenient.

  7. why was the project not using IPv6? by Anonymous Coward · · Score: 1

    Well duh, they had a bunch of IPv4 addresses they could use, why not use 'em and save a bunch of hassle?

  8. This old tale again? by Anonymous Coward · · Score: 1, Insightful

    Company 1 says, "Well, I won't give back my unused addresses because it's not like a few /16s would make much of a difference."
    Company 2 says, "Well, I won't give back my unused addresses because it's not like a few /16s would make much of a difference."
    Company 3 says, "Well, I won't give back my unused addresses because it's not like a few /16s would make much of a difference."
    Company 4 says, "Well, I won't give back my unused addresses because it's not like a few /16s would make much of a difference."
    Company 5 says, "Well, I won't give back my unused addresses because it's not like a few /16s would make much of a difference."
    ...
    And 250 companies later
    ...
    Company 255 says "Well, I won't give back my unused addresses because it's not like a few /16s would make much of a difference."
    ...
    And there you have it. A couple /8s forever wasted because nobody looks beyond their own impact at the big picture. See also: Carbon emissions, littering, everyone else taking the bus, etc.

    1. Re:This old tale again? by Dagger2 · · Score: 1

      It's not like a couple of /8s will make much difference either. One /8 lasts for about a month or so.

      Giving back IP space is a waste of effort. Exert that effort towards your IPv6 migration instead.

    2. Re:This old tale again? by Bert64 · · Score: 1

      Well the lack of ipv6 adoption is caused by the exact problem...

      Why should i expend the cost to implement it when noone else does?

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    3. Re:This old tale again? by JSBiff · · Score: 1

      But it's all just trying to make IPv4 work, and in the end, it won't add up - there's 7 billion people on earth and 4 billion IPv4 addresses.

      They are not wrong that those /16 won't (ultimately) make much of a difference.

      Now what *would* make a difference is a 128-bit address space. . .

      Numbers are free, why should people jump through so many hoops to try to save IPv4?

  9. Re:I'm sick of these articles by firex726 · · Score: 2

    Reminds me of the switch over from Analogue to Digital TV transmission.

    Of course most home users are already setup either directly or via their ISP. It'll be businesses with these $50,000 network equipment that wont want to move over due to the cost of buying new HW when they just got through paying off the old stuff.

  10. What's in it for them by Maximum+Prophet · · Score: 1, Funny

    The UK may have 16.9 million 'unused' IPv4 addresses but according to the department that owns them, they're not for sale.

    Of course they're not for sale, no one in the department would get any benefit from selling them, and it would be more work if they did. Once the lobbyists get wind of this, someone higher up will get a campaign donation, and the block could be sold.

    --
    All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
  11. They should sell it anyway by DrXym · · Score: 4, Insightful

    Sell the block for a billion or whatever it's worth, and use the money to build an IPv6 backbone for UK government services. That in turn would free up more blocks which they could continue to sell and continue to fund the transition with. Or they could sit on them and do nothing until the world switches to IPv6 and there is a glut of IPv4 addresses that nobody is interested in buying.

    1. Re:They should sell it anyway by gramty · · Score: 3, Informative

      They can't sell them, they don't own them. the RIR (RIPE NCC) has very strict rules over the transfer of IPv4 addresses. If the currently end user no longer requires them they should are to be returned to RIPE for zero compensation, RIPE can then re-assign based on applications requirements and justification. The rules were brought in to prevent people setting up shell companies to land grab all the remaining address space once it became obvious it would be exhausted.

    2. Re:They should sell it anyway by Maquis196 · · Score: 1

      Not just that, but this /8 is probably worth more then the British gold reserve that a certain former PM sold for about 1/10th of its current price (hindsight eh?). Unless theyre really using a massive part of it, do as you say. Sell it whilst its worth something, pay some nurses and everyone is happy. (except everyone else who would want a slice of that 1B).

    3. Re:They should sell it anyway by petermgreen · · Score: 1

      Serious question: has a RIR ever tried to interfere with the sale of an OLD block (e.g. one they did not themselves allocate) and if so did they succeed?

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  12. Re:I'm sick of these articles by circletimessquare · · Score: 1

    it's the only way to solve this problem.

    Maybe the mandate can be sold to manufacturers first as an economic stimulus: think of all the new equipment that will be need to be built and all the old computers grandma still uses that will be replaced because they can't figure out how to run the windows update that force retires IPv4 and requires a trip into the control panel.

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  13. Re:Because sixxs is a pain in the ass to get by petermgreen · · Score: 3, Informative

    If you want a free v6 tunnel there are less elitist providers than sixxs. gogo6 (aka freenet6) even offer unauthenticated tunnels for individual machines* so you can just install their software and go.

    Still I consider such tunnels as a tool for those who are interested in developing/testing IPv6 and maybe as a stopgap measure for a subset of end users who really need to reach v6 servers. If you are serious about v6 then you should be using a v6 capable ISP.

    *If you want a prefix you have to create an account and authenticate to it but afaict creating an account with them is no big deal.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  14. Re:Doesn't work. by Nimey · · Score: 1

    Is sir unaware of what subnet masks and VLANs are for?

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
  15. Told you so! by Type44Q · · Score: 1

    I called that one, right here! :p

  16. Re:Doesn't work. by petermgreen · · Score: 4, Insightful

    Unless all systems attached are on the same subnet... And that plays hell with routing, causes congestion... There are reasons the 10.x is non-routed. It was aimed at large local networks - like a node cluster. Sucks when you have to go past a router. That requires routable numbers.

    BS you can route subnets of 10.x on your private networks just fine. You just can't advertise them on the public internet.

    The real problem comes when you are trying to link together a load of sites that are already using some part (or even all, it's a class A block so the default netmask is 255.0.0.0) of 10.0.0.0/8 for their local private network. It is likely that some users will need access to both the national network and existing local private networks. So if you use private IPs for your network you are stuck either trying to find a subset of 10.x that none of the sites are using (can work but there is no gaurantee there will be any such space and it's a problem if you want to add more sites later). Renumbering machines unrelated to your network at various sites so they don't clash with your network or using some horrible NAT hacks.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  17. Again with the 16.9 million instead of 16.8 by Anonymous Coward · · Score: 1

    2**24 = 16777216 so where did the extra ~130k IP addresses come from?

  18. Re:I'm sick of these articles by Soluzar · · Score: 1

    I'm still not convinced there was any benefit to the digital switchover for TV. The picture quality is worse in many cases, and the extra channels are nothing I couldn't get over satellite/cable anyway.

  19. Re:I'm sick of these articles by gstoddart · · Score: 2

    Or we can keep dragging our heels and we will be talking about horrible kludges like NAT and an inelegant, hacky Internet address space for 5-10 years. I'm really sick of these stories on Slashdot. I'm not blaming Slashdot, I am sick of the existence of these stories in a community that isn't FORCED to do the brain dead obvious. Because no authority mandates the obvious.

    Obvious? What's so obvious about it? If it was obvious, people would have switched by now.

    But since people don't perceive it as better, or worth their time and money, they don't do it. Hell, you could say it's "obvious" that companies have yet to find a good enough reason to switch to it, which is why they're staying away in droves.

    Frankly, I can't see companies doing away with NAT. Why the hell would I want my internal machines globally addressable? That always sounds like a stupid thing to me.

    You act like it's so obvious, then fine Mr. Smarty Pants ... give me ten compelling reasons I could go to management to get funding for a project to do this. All reasons which are cool from a nerdy perspective but which don't translate into a business reason will be deemed irrelevant, as they clearly have to date which is why companies aren't doing it.

    I really would love to hear your reasons. Because to date, I've always looked at it as "yeah, sounds cool, but what's in it for me?".

    And I haven't really had a satisfactory answer yet. The most I ever get is people whinging about how evil NAT is -- which is mostly just geekery as far as I can tell.

    --
    Lost at C:>. Found at C.
  20. Re:I'm sick of these articles by Richy_T · · Score: 1

    Except it's not really a problem which is why no one is particularly rushing to fix it.

    Quit wanting the government to force other to do what you think is best. It's antisocial.

  21. Re:I'm sick of these articles by circletimessquare · · Score: 1

    or: the television networks switching over to HDTV from analog.

    grow up.

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  22. Re:Because sixxs is a pain in the ass to get by higuita · · Score: 3, Informative

    sixxs dont require a linkedin account (or something changed since i created mine and several friends accounts)

    all you need is to say you want to test ipv6 on your home computer (or home network) and put your real info (name, email, etc)... that isnt much different from registering on any website.
    Requiring real info is normal, as you will access the internet with their connections, its normal they want real info to contact you or to redirect any police request if you want to use their network for illegal activities

    --
    Higuita
  23. Hold out your teacup! ;) by Medievalist · · Score: 1

    What's so difficult about switching to IPv6?

    It's not difficult any more. Nearly anything worth running has IPv6 support built in.

    I mean where the cost really is? It is not like I have to buy all of my hardware again, it is mostly a software issue right?

    Nope. It's a man-hours issue. Time is money; if you have people doing things (like reconfiguring networks that run fine on RFC1918 IPv4 address blocks) you have to pay them. Businesses that spend money on IPv6 conversions that aren't necessary are wasting money that could be better spent increasing profitability. There is no ROI on IPv6 for most businesses, only telcos and ISPs can get any return out of it. So nobody else cares.

    If you're a startup building out a new network from scratch, you might bother with IPv6. But probably not even then, since you'll have to pay more for techs who are capable of doing it as fast and reliably as IPv4.

    Large enterprises rarely permit change for change's sake. There has to be a compelling business advantage or the resources will be better used elsewhere. For example, if your ISP offered IPv6 at a discount over IPv4, then you'd light it up at your edge routers.

  24. Re:I'm sick of these articles by circletimessquare · · Score: 1

    it is obvious

    what is lacking is the existence of an authority to force the obvious change to happen. because centralized force is the only way to save us from bedlam and a hacky address space and NAT everywhere (not just within organizations, but across the internet address space, turning it into fiefdoms)

    the problem some minds have with problems like this is they see only costs on one side of the equation, and in the shorterm

    the costs of mandating the change: sudden, large, and then gone forever
    the costs of doing nothing: small, accumulative, accelerating forever to a permanent hobbling tax on the network's functions

    first lesson: no choice has zero cost. so the choice is not between cost and no cost, but between the quality and quantity of cost. some minds don't grasps this, and only balk at the idea of any sort of cost

    second lesson: looking at the problem shortterm and longterm. shortterm, the obvious answer is to do nothing. longterm, the obvious answer is to mandate the switch. there are many many examples from real life and politics, where the shortterm thinking dominates the longterm thinking and we all suffer for that. it's called kicking the can down the road. let someone else deal with the problem, even as the problem grows

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  25. Re:I'm sick of these articles by circletimessquare · · Score: 1

    if you don't understand why running out of IPv4 address space is a real and genuine problem, you shouldn't be posting on this particular website

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  26. Re:I'm sick of these articles by fustakrakich · · Score: 1

    Tell you what, to save your poor old eyes the trouble, we'll ban all further publication of IPv4 related articles. Wouldn't want you climbing the embassy walls or anything, and certainly not in New York! And we can use asset forfeiture laws to raid every home and business and remove their obsolete routers. All other non-compliance will be met with indefinite detention. How's that? Happy?

    --
    “He’s not deformed, he’s just drunk!”
  27. I'll Do It by bill_mcgonigle · · Score: 1

    I'll take care of re-addressing into a /16 and we'll spit the proceeds of the /8 50/50, OK?

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  28. Re:I'm sick of these articles by circletimessquare · · Score: 1

    no, i'm not happy, because you go to absurd thoughts. think about the switch from analog TV to HDTV. it was mandated, forced, on industry and individuals, to great expense, and led to a much better standard. and it was accomplished without concentration camps or secret police or whatever other absurd analogy you want to make, dumbass

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  29. Re:ipv6 only, don't be stupid by unixisc · · Score: 1
    This is absolutely right. This comment @ the end of the submission:

    The addresses in question are being used for a new internal government network. Of course, why that project wasn't built using IPv6...

    doesn't make sense. First of all, there is nothing indicating that IPv6 was not considered. But even if it was, it still makes sense to dual-stack them. Like I suggested in the previous thread on this story, even if they distribute it, they should do it to those already planning for IPv6. In other words, IPv4 addresses should only be sold to those willing to go IPv6 as well

  30. in the pre-NAT days.... by Larry_Dillon · · Score: 4, Informative

    For those that remember the days before NAT was prevalent, this is what way IP addresses were supposed to be used.

    --
    Competition Good, Monopoly Bad.
  31. Re:I'm sick of these articles by fustakrakich · · Score: 1

    Easy to do with TV, as all that was required was letting the license expire and not renewing it. It doesn't work that way with the internet. Fortunately, maybe not for you, a license isn't required to operate on the network. So... your absurd idea can only be met with an absurd reply. Please, don't expect me to take you seriously...

    --
    “He’s not deformed, he’s just drunk!”
  32. Re:What? by Anonymous Coward · · Score: 1

    Why are they using public IPs for an internal network. Thats kinda retarded.

    Because it's connected to other networks to which they have no control over the addressing? How do you connect two networks both using, say, 10.1.0.0/16 without a horrible NAT mess? (In reality it's often worse with companies finding ways to allocate most of 10.0.0.0/8 into a horrible mess for only a few thousand hosts). People need to stop thinking about it from an Internet-only perspective and think about private links between networks and it will become clear why many organizations need to use globally unique addressing on their networks.

    Take IBM as an example... When you outsource with IBM you often establish a tunnel with them. Using the 9.x network ensures their network doesn't overlap with any of their customers. If they were using 10.x.whatever it would be a horrible two-way NAT nightmare. At least this way the worst case is a one way NAT with a customer using RFC1918 space--but if the customer uses globally unique addresses everything can be accessed directly AND FIREWALLED APPROPRIATELY.

    When you think of GE, Ford, Du-Pont, etc they would all have had at one point large military contracts and trust me they couldn't successfully tunnel with the DoD using a mess of overlapping RFC1918 address space.

    (and stop panicking about security... firewalls (including stateful) work exactly the same way with and without NAT). GE has their whole 3/8 block advertised and they're not carrying any extra risk just because a workstation or server has the same IP both on and off the Internet.

  33. Re:I'm sick of these articles by circletimessquare · · Score: 1

    you don't appreciate or acknowledge the cost of a balkanized, NATted, hacky internet address space?

    you are so allergic to a mandated switch you don't appreciate the benefits?

    why do we have to deal with spastic hysterics like you on commonsense questions?

    we're talking about a prudent obvious solution to a real problem, and you have to start WHARGARBBBLing about raids and detention like a paranoid schizophrenic moron

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  34. Re:I'm sick of these articles by gstoddart · · Score: 2

    third lesson: sorry, but all I hear is screeching weasel, dial it back a little

    For starters, WTF is wrong with NAT? I keep seeing people say this, and it mostly amounts to apoplectic bitching about how evil it is without anything coherent behind it.

    You say it's obvious, and that there are good solid reasons why people should choose it -- and then you utterly fail to explain your case.

    As I said, if I put you in a room with management to make your case as to why, you'd fail utterly. If you can't make your case here to people who would like to hear your reasoning, then I think you've kind of proven my point that to management this is anything but obvious, and the supposed benefits are so nebulous as to be meaningless.

    Why, for instance, would NOT using NAT be better? Would my network be faster or better or more secure?

    All I hear from you is "because centralized force is the only way to make people agree with me". Which, I gotta say, isn't helping your case any.

    --
    Lost at C:>. Found at C.
  35. Re:I'm sick of these articles by fustakrakich · · Score: 1

    Pfft.. the pipe should be transparent to whatever I hook up to it. You're nuts.. trying to be the little general... I gotta laugh

    --
    “He’s not deformed, he’s just drunk!”
  36. IPV4 was designed for government use by evilandi · · Score: 5, Insightful

    I think what people have forgotten here is quite how old the internet is, for how long the British have been involved in it, and how tightly integrated into British government it has been for a long, long time.

    I'm sure Slashdotters don't need a history lesson on the origins on the internet; as a cold war military network designed to re-route traffic in the event of a nuclear strike on what would otherwise be single points of failure. What readers might need a reminder on, is the UK aspect of this early history.

    Whilst the internet began as a US-only operation, within only a handful of years this had spread to the US' closest NATO ally, the British. Given that even us Brits cheerfully admit that, from a NATO perspective, our island is essentially a 700-mile long aircraft carrier in the North Atlantic that can never be sunk, the involvement of the UK in the early days of the internet should come as no surprise. It's also well known that both American and British universities got in on the act fairly quickly, initially from the perspective of military research; most British universities were either directly addressable or a short hop through a gateway from the internet by the early 1980s. Other close NATO allies, notably the Canadians, ditto.

    What's not so well understood is that, as absolutely certain first exchange targets, the British had an extremely highly developed government continuity strategy for nuclear war. Some parts of this have come to minor public attention in the form of amusingly retro nuclear bunkers that have been re-purposed as museums, archives or modern telecoms junction points (look up the codenames Guardian, Anchor and Kingsway) with varying degrees of practicality. There are some very chilling bits like the "Protect and Survive" videos (now on Youtube) that frankly still scare me silly and we'd all rather forget. Further, there other parts such as the RSG Regional Seats of Government which remains partially, or perhaps even largely, obscured by national secrecy (and probably rightly so).

    This stuff was set-and-forget, it's original design brief was that you wouldn't be able to call the IT department if the IT department had been killed in the first strike, it had to work and remain working without significant intervention.

    Understand that concept - understand that the internet has been at the heart of the most serious British government infrastructure for around 40 years - and you begin to understand why /8 IPV4 address blocks have been, often literally, hard-wired in to the British government. This network was the network we would rely on, to survive. It was the one thing the British government could depend upon. It was the one thing which, when planning IT infrastructure, the government could be absolutely certain about.

    Having that level of certainty allowed us to build other infrastructure around it, such as the PSN Public Services Network,

    To those arguing that it's just a bunch of router reconfigurations... this is not your piddling little /24 home office network. Nor is it simply a bunch of VPNs linking regional offices over a few leased lines. This is not even one IT-savvy megacorporation like IBM. This is a nuclear-war-proof combined civilian and military network which over 40 years has been integrated into every government department and every local government office in a country of 70 million people. It's in the job centres, the benefits offices, the local tax offices, the post offices, the village doctors' offices. It's throughout public service departments which are staffed by people who, on the whole, are pretty good civil servants but who don't actually have a reason to need to know how it all hangs together, and in the vast majority weren't around when it was plumbed in.

    Would this cost more than the value of the address space to reconfigure to 10.x.x.x or IPV6? Crikey, yes, Ten times yes. Magnitudes of scale yes.

    --
    Andrew Oakley - www.aoakley.com
    1. Re:IPV4 was designed for government use by pipedwho · · Score: 1

      Would this cost more than the value of the address space to reconfigure to 10.x.x.x or IPV6? Crikey, yes, Ten times yes. Magnitudes of scale yes.

      Especially when there is no issue if the UK government just says piss off to anyone who wants their IP block, which costs them nothing.

      It is far better for everyone to let others pay for their own IPv6 infrastructure upgrades (or NAT themselves into a hole). Whereas, making the UK release or restructure their block is an expense on par with just moving over to IPv6; meanwhile, other lazy corporations avoid the cost themselves while further compounding the problem by skiving off the released address space.

      So it seems that the UK government keeping the block is a win-win for all, even if most of that "win" is not going to be a short term benefit on some random set of corporate end of year profit and loss reports.

  37. Re:I'm sick of these articles by Bert64 · · Score: 1

    On the other hand, the government could simply start putting their own sites on ipv6 only... Anyone wishing to work with the government, to pay their taxes online, to win government contracts etc, would need to use ipv6. The US already does that to a small extent in that any equipment they procure must support v6, although they don't actually use it.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  38. But if it is an internal network... by wisnoskij · · Score: 1

    ... They do not need top end internet addresses.
    And 17 million of them?

    Why does the government even have that many computers, and why does it sound like this is just one small subnetwork?

    --
    Troll is not a replacement for I disagree.
  39. Re:I'm sick of these articles by circletimessquare · · Score: 1

    the pipe won't be transparent, idiot, if it's NATted to high hell and balkanized because the name space is clogged out

    and i'm a little general because i recognize the only way forward is to mandate the change

    such fucking idiots on this site

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  40. Re:I'm sick of these articles by fustakrakich · · Score: 1

    such fucking idiots on this site

    Really man!

    --
    “He’s not deformed, he’s just drunk!”
  41. Simple economics by ternarybit · · Score: 1

    IPv6 will prevail when running v4 becomes more expensive than deploying v6.

  42. Re:I'm sick of these articles by Bronster · · Score: 1

    Long term something else may have replaced ipv6 - y'know, something actually massively better - not Blu-Ray better.

    Companies which wait longer skip over an intermediate layer of pain in that case. Lucky for them.

  43. Re:I'm sick of these articles by fustakrakich · · Score: 1

    he US already does that to a small extent in that any equipment they procure must support v6...

    That would be the way to do it.. Simply make it impossible to live without. All 'mandates' are kept within the government itself. Everybody will hop on-board as the equipment becomes more common and the old stuff wears out. Then you're gonna wake up and find your connection on IPv6.

    --
    “He’s not deformed, he’s just drunk!”
  44. Oh please.. by Gr4vyBoy · · Score: 1

    The underlying message should come across as: 'These extra ipv4 addresses are going to be used in a government project to spy on all the internet users of the UK.' Get real.

  45. Re:I'm sick of these articles by circletimessquare · · Score: 1

    i'm not here to win over someone to a point of view. IPv4 name space is running out. IPv6 has to be mandated to fix the problem. there's nothing to win over or convince someone of. you either understand the fucking obvious or you are a fucking moron

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  46. Re:Because sixxs is a pain in the ass to get by Aighearach · · Score: 3, Informative

    This is slashdot, everybody already knows to use Hurricate Electric.

  47. Re:I'm sick of these articles by fustakrakich · · Score: 1

    Stop making shit up.

    --
    “He’s not deformed, he’s just drunk!”
  48. Re:I'm sick of these articles by colinrichardday · · Score: 1

    Why, for instance, would NOT using NAT be better? Would my network be faster or better or more secure?

    http://en.wikipedia.org/wiki/Network_address_translation#Drawbacks

  49. Re:I'm sick of these articles by gstoddart · · Score: 1

    LOL, from your own link:

    "[...] it is possible that its [NAT's] widespread use will significantly delay the need to deploy IPv6. [...] It is probably safe to say that networks would be better off without NAT [...]"

    So, NAT is bad because it could delay the deployment of IPv6 because it staves off the problem of running out of address space which would drive people to IPv6. Gotcha. In this case, I'm not sure I agree with the esteemed messrs Peterson and Davie who are attributed with that quote.

    And, for most corporations, that "Services that require the initiation of TCP connections from the outside network, or stateless protocols such as those using UDP, can be disrupted" is probably a bonus.

    People don't want TCP connections initiated from outside of the firewall. That's why they have a firewall.

    So, I concede that in the opinion of some people, NAT wrecks the entire internet ... and will add that in the opinion of other people, it doesn't.

    --
    Lost at C:>. Found at C.
  50. Re:I'm sick of these articles by tqk · · Score: 1

    Imagine that: individuals (which means corporations to some people) FORCED (I said forced, yes) by government (yes, this is ok, you free market fundamentalist freaks) to sacrifice for the benefit of society.

    You should check your six. I can almost see a Brutus sneaking up on you from here. What a tyrant you'd have made. What a massive sense of entitlement you have.

    There are plenty of far bigger problems out there than ipv4 -> ipv6, but you think it's appropriate to sic the government on this?!?

    You big gov't types are all the same. You just see that gov't power can get the job done. You completely ignore the massive cost the mandated disruption is going to cost us. Left alone, plenty of small problems will be handled by those who are slow to transition, and they'll handle them when they have to in the way they can at that time.

    Mandated, it's a massive problem for everyone simultaneously. Thanks a FUCK of a lot. You just made an irritating problem a disaster.

    Say hi to Brutus for me. Sic semper tyrannis!

    --
    "Tongue tied and twisted, just an Earth bound misfit ..." -- Pink Floyd.
  51. Re:I'm sick of these articles by tqk · · Score: 1

    you either understand the fucking obvious or you are a fucking moron

    If you weren't so quick to sling insults at anyone who's disagreeing with you, we might think better of your argument.

    IPv4 name space is running out.

    So? Please list all the Earth shattering disasters looming in all of our futures every minute this isn't fixed.

    IPv6 has to be mandated to fix the problem.

    Why? Prove it, please. While you're at it, would you please describe what business you're in and what you do there? I'm just wondering what sacred cows you worship. Follow the money, you know?

    --
    "Tongue tied and twisted, just an Earth bound misfit ..." -- Pink Floyd.
  52. Re:I'm sick of these articles by colinrichardday · · Score: 1

    That wasn't the only drawback.

  53. Re:Doesn't work. by Rich0 · · Score: 1

    Yup, my employer went through a merger and no doubt getting the networks merged went as quickly as it did because one of the companies involved had a class A (yup, one of THOSE companies). Every printer, PC, and whatever in the company had a globally routable IP address - and yet they were all NATed as far as the internet was concerned. :)

  54. Re:Be Fair by marka63 · · Score: 1

    If you're going to grab networks that aren't BGP Advertised, take them all:

    7/8 (ARIN)
    9/8 (IBM)
    11/8 (US Defense)
    19/8 (Ford Motor Company)
    21/8 (US Defense)
    22/8 (US Defense)
    25/8 (UK Defense)
    26/8 (US Defense)
    28/8 (US Defense)
    29/8 (US Defense)
    30/8 (US Defense)
    31/8 (RIPE)
    45/8 (Prudential Securities)
    102/8 (AFINIC)
    104/8 (ARIN)
    179/8 (LACNIC)
    191/8 (LACNIC)

    and when are we going to do someting with 240/4? How many proposals have to be unfulfilled to use this resource when the resource is scarce? (I know, it'll take a while for some vendors to support this)

    ARIN, RIPE, AFINIC and LACNIC are all Internet Registries. They are the bodies that hand out addresses to companies and individuals. Or were you looking to generate a Perpetual Assignment Process:-)

    As for 240/4 it really can't be made usable on a global scale. To many machines can't talk to it. One could use it between consenting machines in a limited way. e.g. between the CPE and a CGN.

  55. Re:Because sixxs is a pain in the ass to get by fuzzel · · Score: 1

    sixxs dont require a linkedin account (or something changed since i created mine and several friends accounts)

    Indeed SixXS never required a LinkedIn/XING/etc account.

    Those links where only requested at the time so that one would get extra credits (ISK) donated to the person when they signed up, they got the credits because they proved a little bit more that they where real (as we, that is SixXS, could check the trust-graph in those websites) and more importantly as the people who did that actually read the signup page, which is something a lot of people clearly do not do even with colorful indicators.

    This solved a small catch-22 with people who got flashy new IPv6 enabled routers (read: AVM Fritz!Box at the time) and thus for whom a tunnel alone was not enough. As since the beginning of 2012 the new sixxsd v4 software was deployed, this was not needed anymore as one then automatically has a routed /64 next to the tunnel space.

  56. Re:Because sixxs is easy to get if you just read! by fuzzel · · Score: 1

    There are actually only few out of the 30.000+ people who signed up with a proper essay, and the ones that did always earn quite a few extra credits for when they actually do write something more than just "I need IPv6".

    If you where not able to get a SixXS account you likely just did not read the text on the signup page, most likely then proceeded by providing garbage details which is definitely not accepted and any such request simply gets rejected.

    But if you are unable or willing to read the signup page, most likely you won't get IPv6 working either as you'll be doing all kinds of things that will break the configuration, thus reading is essential.

    We (SixXS) have tried to make it as easy as possible by bringing AICCU into the world and working together with various vendors though so that they support IPv6 tunnels out of the box, but even then some problems need reading for a bit to get them resolved. Thus if you can't read at signup you likely won't pass for the rest either.

  57. Re:Be Fair by petermgreen · · Score: 1

    If you're going to grab networks that aren't BGP Advertised

    Which would be a really stupid idea. Do you think the likes of IBM would renumber their whole internal network. Or do you think it's more likely that people who got allocated addesses from 9/8 would simply be inaccessible to anyone at IBM.

    and when are we going to do someting with 240/4? How many proposals have to be unfulfilled to use this resource when the resource is scarce? (I know, it'll take a while for some vendors to support this)

    The compability issues prevent them being meaningfully used to expand global v4 space. Use on large private intranets has been proposed but frankly there are only a handful of such networks in the world and making sure everything supports class E addresses sounds only marginally less painful than making sure everything supports IPv6.

    More generally I can't help but feel that trying to add a few percent to the public v4 address space is fiddling round the edges that won't really change anything other than perhaps adding a few more months before people have to accept that v4 space is no longer going to be nearly free and easy to get.

    Due to the upfront costs and lack of any immediate benefit it has become clear that the orderly transition from v4 only with a public IP per customer to dual stack with a public v4 IP and public v6 block per customer to v6 only is not going to happen and marginally enlarging the address space is not going to change that. The only option left is for growing ISPs to deploy some mechanism* so that their least valuable customers can access resources on the v4 internet while using less than one v4 address per customer. Hopefully most of them will also offer users public v6 IPs but i'm not holding my breath.

    * Be it conventional v4 NAT, DS-LITE, NAT64, port range based IP sharing, proxies or whatever.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register