Slashdot Mirror


No IPv6 Doomsday In 2012

itwbennett writes "Yes, IPv4 addresses are running out, but a Y2K-style disaster/frenzy won't be coming in 2012. Instead, businesses are likely to spend the coming year preparing to upgrade to IPv6, experts say. Of course there's a chance that panic will ensue when Europe's RIPE hands out its last IPv4 addresses this summer, but 'most [businesses] understand that they can live without having to make any major investments immediately,' said IDC analyst Nav Chander. Plus, it won't be until 2013 that North America will run out of IPv4 addresses and there's no sense getting worked up before then."

39 of 233 comments (clear)

  1. Business as usual by InterestingFella · · Score: 4, Insightful

    ISP's and hosting companies will not run out of IPs. This only means that the price per IP will start to slowly grow. Hell, every time I order server the companies still happily hand me over 5 IPs without me even asking for them. With a simple request I can also buy 256 ips for the price of $300 a year.

    1. Re:Business as usual by Anonymous Coward · · Score: 5, Insightful

      a Y2K-style disaster/frenzy won't be coming in 2012. Instead, businesses are likely to spend the coming year preparing to upgrade to IPv6

      Sounds just like a Y2K-style disaster/frenzy.

    2. Re:Business as usual by pak9rabid · · Score: 2

      You can...it's called Time Warner Business Class. And besides, with stuff like DynDNS, why do you even need a static IP for your home?

    3. Re:Business as usual by Shakrai · · Score: 3, Informative

      why do you even need a static IP for your home?

      The question I'd like to ask is why don't they just hand out a static IP by default? The vast majority of broadband connections are always on; they aren't saving IPs by handing out dynamic assignments.

      Of course I already know the answer to my question. It can be located above the '4' key on most keyboards...

      --
      I want peace on earth and goodwill toward man.
      We are the United States Government! We don't do that sort of thing.
    4. Re:Business as usual by Eevee · · Score: 2

      t can be located above the '4' key on most keyboards...

      Well, on my Dell keyboards it's the F4 key (slightly offset), but on my HP and Sun keyboards it's F3.

    5. Re:Business as usual by pak9rabid · · Score: 2

      Don't use a stupid VPN solution. Last I checked, OpenVPN works just fine over a dynamic IP.

    6. Re:Business as usual by pak9rabid · · Score: 4, Informative

      The question I'd like to ask is why don't they just hand out a static IP by default?

      There's a few good reasons off the top of my head that I can think of:

      • - Dynamic IPs cut a lot of bullshit out of support calls
      • - DHCP servers hand out more information that just IPs (default gateway, DNS servers, domain, etc)
      • - ISPs like to have the option of re-allocating blocks of IPs without having to call hundreds/thousands of customers to have them renumber their equipment
    7. Re:Business as usual by XanC · · Score: 4, Informative

      DHCP can be used to hand out a static IP.

    8. Re:Business as usual by bbn · · Score: 2

      If you are using Debuan/Ubuntu/etc just do this simple command:

      sudo apt-get install gogoc

      Tada! You got IPv6. Test it at http://test-ipv6.com/

    9. Re:Business as usual by Columcille · · Score: 4, Insightful

      And the good news about this is "normal people" don't have a clue what you're talking about when mentioning ipv4 or ipv6. Tell them, "We're about to run out of IP addresses!" and they'll blink at you. Tell them, "No! PANIC! IPV4 IS ALL FILLT UP!" and they will call for some friendly people to take you to a padded room. Tell them, "Oh, and we have a problem with programs that use a two digit year instead of a four digit year" and they will build disaster shelters.

      --
      I love my sig.
    10. Re:Business as usual by DocSavage64109 · · Score: 2

      On my keyboard, it's a 7 key.

    11. Re:Business as usual by u17 · · Score: 2

      Because all sorts of services won't talk to you if you are on a spam blacklist. And pretty much all dynamic address pools are on such blacklists.

    12. Re:Business as usual by noh8rz2 · · Score: 2, Funny

      always when I'm in the flow.

      How odd that the ip change is in sync with your monthly hormonal cycle. Could it be pheromones?

    13. Re:Business as usual by hairyfeet · · Score: 3, Insightful

      The problem is it WILL be a disaster but not for the reasons people think of, it'll be the flyover states that cause the disaster. Frankly the pay for IT in right to work states is so damned bad nobody bothers learning more than the bare minimum and the corps sure as fuck aren't gonna pay for courses on their dime, so you have poorly trained worker with zero incentive to learn this new tech. Add to this the shitty pay and even shittier hours have caused most of the older guys like myself to run to the hills and get away from the bullshit equals a perfect storm where the old guys that could have picked it up easily are gone and the new guys hate their jobs and are doing the bare minimum until they can find another line of work.

      So my prediction is while the coasts will work everything in between will rapidly fall apart. problems that would have taken an hour or two under IPV4 and which will take the same time under IPV6 on the coasts will take days or weeks simply because the skilled manpower isn't there and frankly won't be forthcoming because corps have screwed IT so badly here nobody is taking the courses anymore. My local college is thinking about dropping the IT related courses simply because everyone is in medical or law, nobody is bothering with IT as its seen as a dead end. Basically the corps made the bed but we're all gonna get to lie in it when everything that has to cross the flyover states goes to shit. Hell I called my local ISPs the other day and even their tech guys didn't know jack shit about IPV6 nor could they give me a timetable, NOT a good sign folks and talking to friends in neighboring states they are hearing the same thing.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    14. Re:Business as usual by neokushan · · Score: 2

      And there was me wondering what F3 did that was so special...

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    15. Re:Business as usual by neokushan · · Score: 2

      In the UK, Virgin Media (about the only Cable/DOCSIS ISP here) managed to do both incorrectly.
      They don't give out static IPs, but they also don't like it when customers plug in different equipment. In "the old days" it was particularly bad, if a customer plugged in a device with a different MAC (e.g. they went from being directly connected to using a router) the DHCP lease refused to issue an IP until the host table on the UBR was flushed.
      These days it isn't too bad, but there's still a 4-device limit and sometimes the DHCP lease can last for weeks.
      To make matters worse, the only OFFICIAL way the host table can be flushed is via second-line support - first line don't have any tools to do this, so if you do get stuck in that position and don't have a way of spoofing your MAC, you're in trouble - and that's if you know what you're doing.

      If you're lucky, the agent you speak to will recognise the problem (self-assigned IP) and not immediately blame the equipment, get second line to flush the UBR and away you go. If you're REALLY lucky, you'll get an agent that knows a trick to flush the UBR manually (Remove Coax from Modem, power on and let it assign a 192.x.x.x IP, then plug the Coax back it - it flushes the internal host table to remove the 192 IP and at the same time flushes the UBR's host table for that modem - simples).

      Still, I did always wonder why the bothered doing this and not at least have the graciousness to offer a static IP, especially as their IP leases get longer and longer with each renew (mine is currently at something like 3 months).

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    16. Re:Business as usual by jcurran · · Score: 2

      For the last 10 years I have read: "Yes, IPv4 addresses are running out.. blaa FUD blaa blaa FUD" So far nothing has happened. Most computers out there are NAT'ed so, please stop spreading FUD.

      And indeed, they have been running out for the past ten years - look at slide 5 from this presentation: https://www.arin.net/knowledge/v4_deplete_v6_adopt.pdf The fact is that ISPs and hosting companies are having to now undergo major changes in order to continue to grow. The fact that we've known this was coming and developed IPv6, gotten into every major OS and the gear of every major network equipment manufacturer is simply good preparation for what's to come.

  2. Business opportunity by ccguy · · Score: 4, Insightful

    Well, anyone looking to make some big bucks in the next 1-3 year should start learning IPv6. Nothing major needed, just setup a IPv6 network at home, if you can rent an external server with IPv6 in any of the many data centers that already offer it, and play with it.

    It's not a lot of effort and there will be many highly paid job offers soon.

    1. Re:Business opportunity by rubycodez · · Score: 2, Insightful

      I doubt much "highly paid jobs", it'll just get thrown onto the backs of IT droids with the rest of the crap they have to do (speaking as one myself)

    2. Re:Business opportunity by SJHillman · · Score: 3, Insightful

      I think he means you can hire yourself out as an "IPv6 Changeover Consultant", spend ten minutes coming up with an IPv6 addressing scheme and then passing it on the the IT droids while taking the credit and the money.

    3. Re:Business opportunity by pak9rabid · · Score: 2

      Lots of SMB's don't have "IT droids". This actually would be a good opportunity for people such as yourself to break away from the shackles of corporate IT and write your own ticket as a consultant/contractor.

    4. Re:Business opportunity by EdIII · · Score: 5, Interesting

      The problem is not learning IPv6. That's easy. At least to anyone with more than a little experience doing this. I was working before the Internet even came around and before Ethernet, so I don't see it as a big obstacle.

      Where is all the fucking Enterprise hardware and firmware updates to support it?.

      That's what needs to be solved. I could support IPv6 tomorrow if it was a simple firmware change. IPv6 will not be rolled out into Enterprise environments for at least 10-15 years completely. Reason why is simple. Not every network device supports it. I got clients that still have 5 years or more to go on lease contracts for huge printer and document systems. No IPv6 firmware updates in the pipeline that I know about.

      Operating systems will be faster of course, but you need to cover all of the devices first.

      My biggest issue is the routers themselves. If you are running a business or have branch offices, you are not, or should not, be doing that on any hardware you can pick up at BestBuy. Prosumer or higher routers that can set up multiple WAN ports don't have IPv6 yet. Perhaps the absolute newest ones might, but that could represent 20-30k in new equipment costs for a medium sized business with branch offices. For what? Just IPv6?

      Unless the manufactures get off their asses, stop being greedy, and push out a firmware update for existing hardware to support IPv6 there will be a lot of people like me that have two choices:

      1) Stay with IPv4
      2) Spend tens of thousands of dollars on new hardware.

      Tough situation.

      P.S - Why do any of that until at least 1/3rd of all customers are using IPv6?

    5. Re:Business opportunity by interval1066 · · Score: 2

      The last few times I installed an os (which were Windows and Linux machines) they came with ipv6 stacks, and it seemed like very little configuration was nessessary. In fact, if I recall, the configuration instructions were how to turn the ipv6 stack off if you wanted to do that. It seemed to be on by default.

      --
      Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
    6. Re:Business opportunity by klapaucjusz · · Score: 3, Informative

      Where is all the fucking Enterprise hardware and firmware updates to support it?.

      Most large companies have been requiring IPv6-capable gear for the last 4 years or so, while the DoD mandages IPv6 support since 2005.

      Because of that, most recent hardware and software is IPv6-capable. Cisco IOS, for example, has been doing IPv6 since 2001. Microsoft servers have been able to work over IPv6 since Server 2003. Mac OS X since 10.4, Linux since the 2.4 series.

      If you're still stuck with IPv4-only hardware or software, it's your fault.

      --jch

    7. Re:Business opportunity by bbn · · Score: 3, Informative

      HP did a quick one. We got a ton of IPv6 enabled HP 2910al HP layer 3 gigabit switches. Did I say layer 3? What I meant was layer 3 IPv4 and managed layer 2 IPv6 switches.

      Yes, HP apparently figured the switch would qualify for all those government deals that mandates IPv6 support. I bet they were right. But the switches are just some very expensive managed switches for any IPv6 work. No support for routing IPv6 nor any other useful IPv6 support. But you _can_ telnet, ssh, SNMP etc to them using IPv6. The switch can be assigned an IPv6 address. So this qualifies for an IPv6 gold logo. They just do not advertise very loud that it is a logo for a "client"-device.

      So does HP suck? Not especially so. It is the whole industry pulling this stunt.

  3. Silly by HBI · · Score: 4, Insightful

    Only the regional NICs have run out of blocks to distribute. No one has actually run out of IPv4 addresses. Moreover, there is a lot that still can be done to reclaim addresses. Lastly, the huge swathes of multicast and class E addresses haven't even been tapped.

    This is just more attempts for the shill media to try to herd people into replacing their gear. It'll fail like the rest.

    The USG was scheduled to go to IPv6 in 2006. It hasn't even begun yet.

    --
    HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
    1. Re:Silly by jesseck · · Score: 2

      Well, I don't want no stupid NAT - anywhere. I can ssh to my home machine and my work machine from anywhere in the world. No NAT at work, and portforwarding at home. I'd like to ssh to every machine at home though - without paying for more addresses. I'd like to ssh into my smartphone too (so I can turn on the gps and find out where I put it.) But that isn't even offered today. IPv6 will make all of this easy. Enough addresses, nothing to pay extra for. Except the transition.

      I, too, would like to ssh into your machines at home and your smartphone.

    2. Re:Silly by jandrese · · Score: 3, Interesting

      In my experience the difficulty with IPv6 translation isn't at the socket layer--all of that stuff was figured out ages ago and only requires a few tweaks here and there to support both easily--the difficulty is with parsing configuration files, creating dialog boxes, etc... Lots of UI elements were spaced assuming that an IP address would only need 15 digits to be fully displayed, and IPv6 breaks that.

      The upshot is that converting an application over to IPv6 is rarely as easy as it should be.

      --

      I read the internet for the articles.
  4. Re:Cleanup the IP Space by SJHillman · · Score: 3, Interesting

    You assume everyone with an IP is using it to host a website. And what about people that have a redundant data link that only comes up when their main link goes down? "Well, we haven't had any downtime in the past year, guess we don't need any backups! Go ahead, take my IP!"

  5. Re:Cleanup the IP Space by ae1294 · · Score: 2

    There are so much junk IP addresses out there going nowhere

    Couple of A blocks won't give you 10 years with the way things are expanding in Asia and Africa.

    I have an idea, why don't we separate the African Internet from our Internet. We could have two Internet's! They would be separate but equal..

  6. Re:I'll be getting ready now, thanks by Todd+Knarr · · Score: 3, Funny

    No, I'm not a drama queen. I'm a paranoid bastard who makes Mad-Eye Moody look positively naively trusting. Which is another way of saying I've been through major infrastructure deployments before. I don't believe in Murphy, I'm on a first-name basis with the little toerag.

    Making an IPv6 tunnel work, that's easy. The hard part's making it not work in the spots that need to not work without breaking what's supposed to work. If everything goes smoothly it'll be a piece of cake, and if I do it now it'll probably go smoothly. But if I wait until the last minute, 99 times out of a hundred it won't go smoothly. So I'll be paranoid and get it done now and be pleasantly surprised at the lack of problems, then kick back and relax with a bowl of popcorn while Murphy visits all the people who waited and zany hijinks ensue.

  7. Way harder than a firmware update. by Sycraft-fu · · Score: 3, Interesting

    For cheap consumer devices that do everything in software, sure a firmware update is all it would take, at least in theory (IPv6 can take more memory and CPU so on limited devices there might not be enough). However enterprise networking devices? They usually have to have parts replaced.

    Reason is that to get the kind of speeds and latencies we want, you need ASICs, Application Specific Integrated Circuits. Those are just what they sound like: Devices designed to do a specific thing. That also means they aren't programmable. ASICs allow us to do stuff cheaper and faster than we could do in software.

    A simple example is a gigabit switch. Crack one open and you see a very small little chip that handles all the switching. Now try it with a PC, stick in 8 gigabit cards and have it bridge between them. It'll overwhelm it, despite having a powerful CPU. Reason the switch can handle it is that little chip does nothing but switch packets. It is designed for only one task and does it well.

    So enterprise stuff has this too, but some more complex ones. You get ASICs to speed up routing. Problem is if the ASIC was made for IPv4, it cannot be expanded to IPv6. You need a new one.

    On the campus where I work they upgraded all the big routers to do IPv6 and it was pricey, seven figures even with our discounts. All the supervisor modules had to be replaced. Now yes, before that they could have technically turned it on, there was IPv6 for IOS on the older stuff. However it was all done in CPU, which is pretty limited on those routers. So if a couple people used it, it'd be fine. However if lots of people did, it'd crash the routers. The only way to give them the capacity to support it for everyone was to get new IPv6 hardware.

    It isn't a matter of being greedy. As I said, Cisco would let you turn IPv6 on for many devices, like the 6500/7600s we use. It just couldn't accelerate it because it lacked the hardware. No magic fix for that.

    Remember high end networking equipment isn't replaced often. You can leave it in place for over a decade. They aren't going to replace it all just for fun.

    1. Re:Way harder than a firmware update. by Anonymous Coward · · Score: 3, Insightful

      A PC will handle layer 2 bridging just fine /w 8 ports. There really isn't a whole lot of effort involved in shoving packets around like that. Did you base your statement on actual observation or did you pull it out of your ass?

      Those desktop 5 and 8 port switches from Linksys or whatever have "switch on a chip" type IC's because they're cheap, not because they're wonderfully efficient (though obviously lower power and better latency than a PCI bus)

      Obviously in a datacenter, you want a real switch.. They're more efficient, lower latency, easier to manage, and have a full array of enterprise management and configuration capabilities.

  8. Re:why arent the nerds excited? by Jeremi · · Score: 2

    what scares me is the lack of a "real" private address range (with nat) like we do now with ipv4.

    Dunno what your threshold for "real" is, but Wikipedia mentions this... perhaps that would do.

    --


    I don't care if it's 90,000 hectares. That lake was not my doing.
  9. It's not YOUR addresses ... by garry_g · · Score: 3, Insightful

    ... what you don't seem to get is that the problem is not when ARIN runs out, but when your business partners get IPv6 addresses you can't reach because you didn't do your f@ckin' homework and upgrade to dual-stacked ... So go ahead, stick to IPv4, and once your boss comes in and asks why you can't exchange data with your possibly largest customer, tell him: "why would we want IPv4? Arin hasn't run out yet" ... good luck on finding a new job afterwards ...
    And if you believe "Hey, no problem, it's just the Chinese and Japanese and Australians, who needs them" - think again, Europe's RIPE will run out of IPv4 addresses next ...

  10. Re:ask the us fbi for some by jcurran · · Score: 2

    they have 65 + million ipv4 addresses....

    Registrations are publicly visible in the WHOIS database, so please elaborate which address blocks you refer to?

  11. Re:Cleanup the IP Space by ae1294 · · Score: 2

    Took the words right out of my mouth.. 'The people' in those countries have been shown time and time again that they can't be trusted. We've been letting them get away with raping and stealing from our servers for long enough. My oldest server got raped just last month and I'm still worried that some root-kit or other may still be inside of her. They deserve to be segregated from the rest of us upstanding types...

  12. Re:Can't help but wonder... by ae1294 · · Score: 2

    No it is the Evangelical Christians who are believing a Pagan calendar designed to help worship many gods. Sometimes I don't think most of these people actually read the bible.

    Maybe they know their own religion is full of shit.

    You can mod me down but you can't mod down the coming Mayan Apocalypse. Ah Pukuh shall call fourth Ah Muzencab to smite thee all.

  13. Re:Bologna by evilviper · · Score: 4, Insightful

    All the articles I've read seem to come down to "it's more convenient" for applications not to have to deal with NAT... Of course it is also more convenient for people who mean to do you harm, too, since we're back to connections to outside resources coming from the machine's actual IP address, a public NATing of the private one.

    NAT doesn't provide any security. Never has, never will. No, I'm not wrong. No, I'm still not wrong.

    If you have a firewall between your private network and the public Internet, then you'll have all the security you want, whether using IPv4 or IPv6, with or without NAT. If you don't, then it's trivial for bad guys to reach services you don't want them to get to. If there's NAT in-between, it'll take a couple extra specially-crafted packets, but it's pretty trivial to get around.

    IPv6 addresses with a firewall? Bad guys can know the IPv6 address of your valuable systems all they want, but if your firewall is blocking incoming connections by default, they can't get a single bit through to the destination.

    I don't understand why people's brains turn to jello when talking about IPv6.

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant