Slashdot Mirror


Protect Your Pre-1997 IP Address

CWmike writes "With IPv4 space running out any day now, is your legacy IP address space safe? Marc Lindsey writes that if your company obtained its IP address space before 1997, you have probably received several letters from the American Registry for Internet Numbers encouraging you to enter into a contractual agreement to protect the IP address. But should you sign it? Be careful — there are several issues you should consider before signing up for this, writes Lindsey, who offers a deeper look at the issue."

275 comments

  1. Printable by Anonymous Coward · · Score: 4, Informative

    Save some time, 4 pages is silly given the content.

    Printable Version.

    1. Re:Printable by Lord+Lode · · Score: 2

      That link times out for me. It must have lost its IP address!

  2. Seriously? by DarkKnightRadick · · Score: 3, Insightful

    There is nothing special about IPv4. Upgrade your systems to IPv6 already, folks. It's been around for what? 10 years now? Give me a break.

    --
    "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    1. Re:Seriously? by Anonymous Coward · · Score: 1

      There is nothing special about IPv4. Upgrade your systems to IPv6 already, folks.

      Well upgrading those systems costs BIG_SUM $, while using ipv4 costs almost nothing.

      Also most corporations don't see a benefit in using ipv6, so upgrading systems is a waste of money.

    2. Re:Seriously? by DarkKnightRadick · · Score: 0, Troll

      Big dollars? Are you nuts? 99% of all operating systems released since Windows ME have support for IPv6. The hardest part of the upgrade is actually switching over to it. There is no hardware to upgrade and there is no software to upgrade.

      They will once IPv4 runs out.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    3. Re:Seriously? by Anonymous Coward · · Score: 5, Insightful

      Upgrade your systems to IPv6 already, folks.

      Yeah, just like that. ISPs should replace millions of dollars worth of high end network equipment, find sensible IPv6 transit providers and re-negotiate their peering arrangements (whom may not want to peer with IPv6), then allocate and assign IPv6 addresses to every single IP endpoint on their entire network and then spend a couple of million more replacing end-user network equipment that almost certainly doesn't support IPv6, then await the massive flood of complaints from users who have additional non-IPv6 equipment behind their router which no longer works E.g. almost every consumer VoIP phone every shat out by the lowest bidder.

      That's just for a small ISP.

      The major force holding back IPv6 deployment is shitty consumer hardware that doesn't "do" IPv6, and shitty network hardware vendors who charge an arm and a leg for IPv6 capable routers etc. (coupled with the fact that people have already invested a lot of money on non-IPv6 hardware anyway). It's not like the ISPs are doing it just to piss you off.

    4. Re:Seriously? by Cwix · · Score: 1

      There are plenty of pieces of hardware that dont support IPv4. Unless you upgrade the hardware to a dual stack configuration. Routers, switches, etc arnt cheap.

      Just because the OS supports it, doesnt mean its going to be easy or cheap.

      --
      You are entitled to your own opinions, not your own facts.
    5. Re:Seriously? by kantos · · Score: 2

      I talked to the IT department at my company recently about this... all of our infrastructure supports IPv6... only one little bit that doesn't... our upstream provider... so until ViaWest gets their act together... we won't have IPv6.

      --
      Any and all content posted above may be ignored, considered irrelevant, or otherwise dismissed.
    6. Re:Seriously? by Anonymous Coward · · Score: 0

      Who marked that troll? Jeeze. /. moderation is retarded these days.

    7. Re:Seriously? by Anonymous Coward · · Score: 0

      Get the lead out of your lazy asses and upgrade already. Go ahead and mod me troll for reminding you people that you're lazy but all that's going to do is make 10 more of us remind you in the next IPv6 thread.

    8. Re:Seriously? by Pi1grim · · Score: 1

      Yeah, right, let's wait some more, untill we hit the brick wall of IPv4 space limitation, start losing money and then, when the money is lost — move over to IPv6. Never forget, that the greedy one pays twice.

    9. Re:Seriously? by TheRaven64 · · Score: 3, Insightful

      Yeah, just like that. ISPs should replace millions of dollars worth of high end network equipment

      ISPs replace millions of dollars worth of high end network equipment every year. Capacity grows fast enough that anything more than a few years old is so laughably obsolete it's not worth maintaining. Anyone who's been buying equipment for an ISP and not mandating IPv6 compatibility for the last ten years really shouldn't still have a job.

      --
      I am TheRaven on Soylent News
    10. Re:Seriously? by grumbel · · Score: 1

      The operation systems are a nice start however you still have to deal with:

      * almost no home router supports IPv6
      * almost no provider offers IPv6
      * almost no webpage runs IPv6

    11. Re:Seriously? by jellomizer · · Score: 0

      There isn't anything wrong with ipv4 either. We just need to clean up the hourders. I know my undergrad had a class B and 2 class C domains. And there are only 5000 students and like 800 faculty. Most of them doesn't need an outside address. And could be natted. I bet a lot of collages have more then they need. As well as a lot of companies. Ipv6 only offers freedom for bad network design and not knowing who is in or out.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    12. Re:Seriously? by franciscohs · · Score: 5, Informative

      I'm sorry to have to say this to you like this, but you have no idea what you're talking about. Did you think about the infrastructure where you connect all those PC's?. Take Cisco in the Datacenter for example, current status is:

      Routers and switches support IPv6 (excluding Nexus 1000V)
      Firewalls (ASA) support IPv6
      Firewall Service Modules (Cisco's Datacenter firewall solution) don't support IPv6 in transparent mode, don't support failover in IPv6, don't support IPv6 on hardware (which make them useless for real traffic)
      Load Balancers (ACE), no support
      WAN optimization, no support
      Ironport, no support

      etc.

      And even if this support comes, in most cases it's not just a simple software update, you have to update the hardware and you're talking 10's of thousands of dollars for each. So believe me, it's not that easy, even with the will and the money, in some cases there is no even offering from the vendors at this point, which is shameful.

    13. Re:Seriously? by Anonymous Coward · · Score: 0

      China moves already to IPv9

      "At the New Generation Internet Ten-Digit Network Industrialization & Development Seminar held on June 25th at Zhejiang University, it was announced that China's Internet technology, IPv9, had been formally adapted and popularized into the civil and commercial sectors. Based on a ten-digit computing method, IPv9 has its own address protocol, nameplate protocol, transitional protocol, and digital domain name regulations and standards as stated by Mr. Xie Jianping, founder of the IPv9 protocol and leader of the Ten-Digit Network Technology Standard Team. Along with being compatible with IPv4 and IPv6, IPv9 can also realize logistic separations between them and safely control them."

      Meanwhile US and Europe struggle on Ipv6!

    14. Re:Seriously? by Anonymous Coward · · Score: 0

      There may be software to upgrade - who know what custom apps business' depend upon are not able to cope with ipv6

    15. Re:Seriously? by DarkOx · · Score: 1

      Frankly most commercial targeted hardware has supported v6 for at least the past five years or so. In some situations it might need memory upgrades and the like but that is in the grand scheme of things cheap! Other things like VOIP, PC over IP, multimedia technologies have pushed the equipment much older than five years or so out of most shops that have a significant amount of investment in route/switch anyway.

      If you ask me its legacy applications as usually that probably forces most orgs to go dual stack or holds them back, kinda like it keeps IE6 and that 3270 terminal emulator on the desktop.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    16. Re:Seriously? by Splab · · Score: 5, Informative

      We do?

      Actually no we don't, because customers (that would be you) aren't willing to pay the actual cost of equipment. Upgrades are something that happens when the old stuff is dead or 5 years has passed (the time it takes to write it off), whichever comes first.

    17. Re:Seriously? by thetoadwarrior · · Score: 1

      It's going to cost when IP4 addresses run out. It cost money having to fix Y2K at the last moment. It's just laziness and stupidity to leave things to the last moment.

    18. Re:Seriously? by rabbit994 · · Score: 1

      Windows XP/2003 does not support IPv6 in any meaningful way. Yes, it has it in network config page. However, for example, it won't make DNS calls over IPv6 even when querying AAAA records. Forget getting SMB running over IPv6 properly. Finally, some products like Exchange 2003 and ISA 2004 and others have zero IPv6 support.

      Only Vista/7 and their server counterparts have full IPv6 support.

    19. Re:Seriously? by Pi1grim · · Score: 1

      Did you even read what this "IPv9" is? It's a DNS addon (works only in China) that re-routes all-number domains and resolves them a conventional IPv4 or IPv6 address. So, next time after you see an article — bother to read it before copying blindly to your comments.

    20. Re:Seriously? by h4rr4r · · Score: 1

      You mean the company won't take the hit to profit to replace that stuff.

    21. Re:Seriously? by h4rr4r · · Score: 1

      No, everyone needs a real IP not NAT. The internet is not fucking cable TV, we are all nodes not just moronic consumers.

      NAT is bad network design. Also I went to a college at a university, you seem to have attended a composite work of art.

    22. Re:Seriously? by Anonymous Coward · · Score: 0

      Your view of the world is so very cute and naive. There is tons of "obsolete" hardware running the Internet in all sorts of nooks and crannies. To claim that everyone is running 2 year old routers, switches, etc is a laughable claim.

    23. Re:Seriously? by anegg · · Score: 2

      Before you make the upgrade from IPv4 to IPv6 across your network, you will want to make sure that your network equipment can maintain its advertised speeds handling IP v6 traffic. For example, routing equipment and security devices may have had hardware optimizations that work with IPv4 protocol traffic but not IPv6. If your network equipment doesn't support IPv6 traffic at those devices rated performance levels, you will need to analyze your performance needs and equipment upgrade options prior to upgrading your network protocol from IPv4 to IPv6.

    24. Re:Seriously? by Anonymous Coward · · Score: 0

      ISPs replace millions of dollars worth of high end network equipment every year. Capacity grows fast enough that anything more than a few years old is so laughably obsolete it's not worth maintaining.

      We do? It does? It is?

      Not so much. It might be nice to live in a fantasy world where companies spend money just to keep you happy, out here in the real world, companies spend money when they damn well need too, and they spend the least amount of money they can possibly get away with. Sadly for you, capacity is not growing fast enough to make "old" kit obsolete.

      I work for a small ISP and our entire edge network capacity is no more than 3Gb/s sustained, and we commit way below that on our transits. Bandwidth at individual points on the network are far, far lower than people think. It's only a few of the bigger ISPs and the peering aggregation sites that need to worry about 10Gb Ethernet, even now. It'll be 5-10 years before you see 10Gb top-of-rack switches as the standard, and 1Gb switches will still be around long after that.

    25. Re:Seriously? by Anonymous Coward · · Score: 0

      LAN switches are on a different layer than protocol. Routers should already have IPv6 capability. The "etc" don't need to switch to enable IPv6 network to function..

    26. Re:Seriously? by the_fat_kid · · Score: 1, Insightful

      ok, I'll bite.
      A five year life cycle?
      IPv6 has been with us for 10 years?
      That mean that you have had 2 chances to upgrade your equipment to something that would support it.
      This is not some thing that has snuck up on you, your just cheap or lazy or afraid of the change.
      I think that what you meant was, "Customers are not willing to pay more for the equipment and we don't want to cut in to our profits to update our hardware."
      Except, of course for the fact that you have ignored this problem for over a decade.
      nice

      --
      -- Sig under construction...
    27. Re:Seriously? by Chemisor · · Score: 2

      IPv4 is not going anywhere, even if IPv6 is adopted by the ISPs. There is plenty of hardware around that does not support v6 addressing, like network printers and most current home broadband routers. Just like companies hoard IE6 because their stuff doesn't work without it, so will they keep intranets on IPv4 no matter how much IPv6 propaganda is flung at them. Personally, like most normal people, I have no interest in having any IPv6 on my home network. It is much easier for the ISP to provide a 6to4 gateway and let all the users keep pretending they have an IPv4 address even though it's really IPv6.

    28. Re:Seriously? by Anonymous Coward · · Score: 0

      GP:

      Anyone who's been buying equipment for an ISP and not mandating IPv6 compatibility for the last ten years really shouldn't still have a job.

      You:

      Upgrades are something that happens when the old stuff is dead or 5 years has passed (the time it takes to write it off), whichever comes first.

      I fail to see what the problem is...

    29. Re:Seriously? by Anonymous Coward · · Score: 0

      Except it really isn't a problem. People have been parroting these doom and gloom situations for a decade and yet we've done just fine with ipv4. The fact that they haven't spent all this money and yet the Internet has exploded is a good sign that it would have been a wasteful expenditure with no real ROI. You can whine all you want about them not wanting to spend their profits on this and they are being greedy, but its no different than the fact that you don't constantly replace your car, appliances, computers, etc on a yearly basis either because that's just wasteful spending and you're getting negligible benefits in return.

    30. Re:Seriously? by KingMotley · · Score: 0

      Well tesla has had all-electric vehicles for the past 4 years.
      Most people replace thier cars every 3-5 years.
      Given how you feel, you better buy one next year, or face being a hypocrite.

    31. Re:Seriously? by KiloByte · · Score: 1

      It's not like you can have anything but dual stack in the next ten years. Just run NATted IPv4 which handles DNS just fine, and use IPv6 for anything that can benefit from it. SMB is not supposed to ever leave your local network (and is abysmally slow if it does), so that's not a blocker either.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    32. Re:Seriously? by bell.colin · · Score: 3, Insightful

      It's not just Hardware you also have application software with limits, I support several at work that were purchased/developed in the last two year that require connection to a server running a background service.

      The field for the server "REQUIRES" a x.x.x.x IP format (won't even except a host-name) and won't work any other way, some of this software is required by state law so it can't be replace with another product. (we have to wait for the lazy software devs at the company to change it)

      I hate cheap-ass devs who still write software using their dusty copy of VisualBasic 4,5, or 6 and sell it to our users today for $50K.

    33. Re:Seriously? by TheCarp · · Score: 4, Interesting

      Which is fine. If I cared (I have been debating it) I could probably get my home internal network doing internal IPv6 and connected out via a tunnel this weekend (if I didn't already have some other things to do, like clean out the room that is to become the new office).

      Might be able to do it at a small business, in a few days to weeks, if things were otherwise slow.

      Try it on a large multi-site network that runs continuously. Coordinating changes between multiple groups, with varying level of skill and network clue, and varying responsibilities, all while everyone is doing their normal day job.

      Shit, its going to take you two years of meetings just to explain to mid level managers why they need to get the high level managers on board so they can make all the little fiefdoms work together on something that isn't directly of interest to any of them, but yours.

      Of course, its only two years because I figure its about that long before the high level manager hears some BS about someone else who did IpV6 and then asks the mid level managers that you have been battering for years about why they aren't doing it when these other people are.

      --
      "I opened my eyes, and everything went dark again"
    34. Re:Seriously? by leenks · · Score: 2

      Most enterprise "LAN" switches are protocol aware, however. Ever heard of a VLAN? QoS?

      More to the point, routers are protocol aware and I'd wager that most are not IPv6 capable, and if they are, they are not part of an IPv6 enabled environment (which might require considerable expense to make it IPv6 enabled, or at least a lot of planning).

    35. Re:Seriously? by WaffleMonster · · Score: 1

      Windows XP/2003 does not support IPv6 in any meaningful way. Yes, it has it in network config page. However, for example, it won't make DNS calls over IPv6 even when querying AAAA records. Forget getting SMB running over IPv6 properly. Finally, some products like Exchange 2003 and ISA 2004 and others have zero IPv6 support

      No dualstack sockets either :(

      Your right it sucks most vendors make you pay for upgrades to obtain IPv6 functionality but at least IPv6 is available in current versions of exchange and forefront (ISA).

      I have a 2003 server and IPv6 works fine. This is only because it also has IPv4 connectivity so the downsides you point out don't really apply to me.

      DNS is really the only major showstopper for going "IPv6 only" in terms of XP Internet connectivity. It can easily be resolved by installing a local proxy agent that provides IPv6 resolver functionality missing in XP.

      I think it is more realistic to project ahead in time to a point where IPv4 connectivity becomes "optional". At this point what will the XP user base look like?

      Until then all ISPs with the possible exception of some mobile carriers will be going dualstack where the XP shortcommings do not matter.

    36. Re:Seriously? by leenks · · Score: 1

      Your sig is missing a closing parenthesis.

    37. Re:Seriously? by Tony+Hoyle · · Score: 5, Informative

      The world is consuming a /8 - 16 million addresses - roughly every 3 weeks.

      Your piddling 65k addresses for a class B? 2 hours, tops.

    38. Re:Seriously? by hjf · · Score: 1

      only #2 is false. many routers provide IPv6, and more webpages than you imagine do. I was running IPv6 for several monts through a tunnel, and all google sites, even youtube, work through IPv6. Even FACEBOOK runs ipv6 too...

    39. Re:Seriously? by hjf · · Score: 2

      ooops... only #2 is TRUE! #1 and #3 are false.

    40. Re:Seriously? by Anonymous Coward · · Score: 0

      Not even remotely the same thing.

      IPv6 can do everything IPv4 can do. IPv6 network equipment has been widely available.

      Electric cars can't replace all cars. Some people drive long distances, or like to have that option, even if they could rent a gas car for the rare times they really need it. Also, there's cost and availability.

    41. Re:Seriously? by hjf · · Score: 1

      So we don't have IPv6 because vendors don't implement it, or because customers don't ask for it?

    42. Re:Seriously? by chef_raekwon · · Score: 1

      you mustn't understand how companies deal with their capital expenditures, and replacement costs of infrastructure.

      a company is going to replace network gear typically every 5 years or so. same company may replace servers every 3 years depending on need/workload.
      those replacements are typically spelled out 6 months prior to the year in which they are replaced, and the new cost is put into the capex. capex goes through approvals, and typically gets a nice little chop because IT wants to add/replace too much. capex goes back to IT Director, who plays with the numbers, removes a few upgrades, sends capex upward for approval.

      once approved, engineers are going to replace gear that will benefit the organization for the next 3 to 5 years, where the cycle will repeat itself. and because the spend is kept artificially low, only the most deserving pieces get the money.

      why would engineers think to deal with IPv6 if IPv4 is not a real pressing issue when upgrading? the pressing issue is going to be the pressure to lower latency, remove bottlenecks, and scale bandwidth. when your boss(es) are breathing down your neck because you dropped 500K on some new gear, the last thing you're thinking about is solving the internet's (someone else's) problems.

      --
      We're like rats, in some experiment! -- George Costanza
    43. Re:Seriously? by PitaBred · · Score: 1

      Doesn't matter. That just delays the problem by a few months, it doesn't solve it. There's not enough IP space for all the devices being hooked up, period. No matter how we divvy it up. NAT is not a solution.

    44. Re:Seriously? by rubi · · Score: 1

      My boss would ask (more or less what we would understand after all the manage-speak): How much will that "IPV6 Migration" project save or return?

      That is the real cause of not having already moved to IPV6, there is no clear way to convice management to spend the resources (call it money, time, personnel or whatever) in doing it.

    45. Re:Seriously? by Surt · · Score: 1

      It's been around for what? 10 years now? Give me a break.

      12 years pretty much exactly:

      IPv6 was developed by the Internet Engineering Task Force (IETF), and is described in Internet standard document RFC 2460, published in December 1998.[1]

      http://en.wikipedia.org/wiki/IPv6

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    46. Re:Seriously? by Surt · · Score: 1

      And you apparently think costs are the same for ipv4 and ipv6 equipment?

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    47. Re:Seriously? by AK+Marc · · Score: 1

      There is no hardware to upgrade and there is no software to upgrade.

      I have a router that was made in the past month, designed from scratch in the past 6 months, and it doesn't support IPv6. There are hundreds of millions of dollars of those routers out there. I'm sure there is more, but that's one that I have that I've bought. IPv6 is so far off the corporate roadmap that there are plenty of hardware makers who still don't support it and expect that the ISPs will do IPv4 to IPv6 translations or such. Sure, that can be done, but it shows that there are people making things today that are not making IPv6 compatible things.

    48. Re:Seriously? by rubi · · Score: 1

      deleted...

      If you ask me its legacy applications as usually that probably forces most orgs to go dual stack or holds them back, kinda like it keeps IE6 and that 3270 terminal emulator on the desktop.

      As I see, I'm partially with you: not that the legacy apps themselves are the ones holding back, it is the functionality provided by such apps and the cost of reproducing that funtionality in newer and (hopefully) better apps that can hold back both legacy hardware, software and protocols

      Please remember that management (the finance and accounting departments that really have control of the money and by way of that control the companies) needs a reason to change over expressed in terms of returns, being that savings in operating costs or direct benefits produced by such a project.

    49. Re:Seriously? by Surt · · Score: 1

      Very true, however IPv6 does include important routing optimizations that will (at least in theory) mean it is easier to route than IPv4.

      So there's no good reason it should route slower than ipv4, just potentially poor hardware / software implementation.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    50. Re:Seriously? by theycallmeB · · Score: 1

      Well, assuming you don't try to replace your entire network in a brief flurry of activity once every five years, then you don't have to have that much equipment in your system to end up replacing millions of dollars worth of it every year.

      Indeed, given the size and cost of some data centers these days, I don't think it would that hard to spend a couple million dollars every month upgrading the hardware in a single building. It would probably be more cost effective that trying to maintain a static configuration with the requisite supply of spare parts.

    51. Re:Seriously? by DarkKnightRadick · · Score: 1

      That just makes it worse.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    52. Re:Seriously? by grumbel · · Score: 1

      Many pages have special ip6 domain names, such ipv6.google.com or www.v6.facebook.com. Almost none have IPv6 on their main domain name, they all still experiment with it, but hesitate to actually deploy it.

      And about routers, this list is rather short and certainly doesn't qualify as "many". The really shocking part isn't even that hardly anybody has a IPv6 capable router at home, but that even routers you buy today for most part still completly lack any IPv6 capabilities.

    53. Re:Seriously? by DarkKnightRadick · · Score: 2

      How about not losing their Internet connectivity? Seems like a pretty direct benefit to me.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    54. Re:Seriously? by DarkKnightRadick · · Score: 1

      If modern routers and switches aren't IPv6 capable, that's a failure on the part of the companies making them, and those companies should refund everyone their money for being so idiotically short-sighted.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    55. Re:Seriously? by DarkKnightRadick · · Score: 1

      They just don't like my sig.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    56. Re:Seriously? by Anonymous Coward · · Score: 0

      So we don't have IPv6 because vendors don't implement it, or because customers don't ask for it?

      First one, then the other.

    57. Re:Seriously? by NJRoadfan · · Score: 2

      The Actiontec MI424WR that Verizon has been deploying for Fios service completely lacks IPv6 support. I'm sure its just a firmware update, but it is kinda silly to leave out IPv6 support. When Verizon built the fiber network, it should have been IPv6 from the start.

    58. Re:Seriously? by DarkKnightRadick · · Score: 1

      It may not be going anywhere, but it will still run out of address space very, very soon.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    59. Re:Seriously? by DarkKnightRadick · · Score: 1

      2 years of meetings that could have already have happened. IPv6 has been around for 12 years. Get a clue.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    60. Re:Seriously? by DarkKnightRadick · · Score: 1

      That's absolutely and utterly horrendous.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    61. Re:Seriously? by DarkKnightRadick · · Score: 1

      agreed

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    62. Re:Seriously? by Surt · · Score: 1

      I definitely wasn't arguing otherwise.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    63. Re:Seriously? by Anonymous Coward · · Score: 0

      What home routers support it? When I bought my last one about a year back I couldn't find any that met my needs that supported IPV6. I was looking for:

      dual radio (2.4 GHz and 5.0 GHz simultaneously so I could separate my G from N)
      IPv6 support

      I wasn't able to find one at the time. Perhaps there are some now, although a quick look through Linksys brand ones shows that they still don't support it.

    64. Re:Seriously? by Anonymous Coward · · Score: 0

      Yeah, just like that. ISPs should replace millions of dollars worth of high end network equipment, find sensible IPv6 transit providers and re-negotiate their peering arrangements (whom may not want to peer with IPv6), then allocate and assign IPv6 addresses to every single IP endpoint on their entire network and then spend a couple of million more replacing end-user network equipment that almost certainly doesn't support IPv6, then await the massive flood of complaints from users who have additional non-IPv6 equipment behind their router which no longer works E.g. almost every consumer VoIP phone every shat out by the lowest bidder.

      Yes. That's exactly what they should do. Or are you proposing they bury their head in the sand and not develop a plan for ipv6 migration? It is going to happen, so stop stalling with excuses.

      The major force holding back IPv6 deployment is shitty consumer hardware that doesn't "do" IPv6, and shitty network hardware vendors who charge an arm and a leg for IPv6 capable routers etc. (coupled with the fact that people have already invested a lot of money on non-IPv6 hardware anyway).

      It doesn't change the fact the we are running out of ipv4 addresses, and there are already consumer routers that support ipv6 (some support it without even advertizing it), so it's not like there's a lack of options. Yeah, it's going to cost a shitload of money, but if you are holding out for a low-cost solution then you are living in a dream world.

    65. Re:Seriously? by Anonymous Coward · · Score: 0

      Damn, living da vida loca is expensiva!

    66. Re:Seriously? by franciscohs · · Score: 1

      I've just switched jobs from a very big international corporation to an ISP, and in both places there is strong investment (in both, time and money) to prepare for IPv6 and the feeling is that vendors are behind expectations.

      I don't think it's customers not asking for it, maybe you wont find a lot of customers upgrading equipment just for IPv6, but if you are minimally capable on your job you will ask that any new equipment you're willing to buy from a vendor to have IPv6 support at this point. Even if you're not planning to upgrade on the short term.

    67. Re:Seriously? by zach_the_lizard · · Score: 1

      D-link has had ipv6 for at least a year or two. Their DIR-825 (or 855, whatever the model, it's 8xx) has ipv6 and dual radios, IIRC.

      --
      SSC
    68. Re:Seriously? by hjf · · Score: 1

      ipv6.google.com doesn't work anymore. Your ISP needs to partner with Google so google's DNS serves will return IPv6 addresses to hosts in those networks.

      Google or Facebook aren't hesitating. They're actually working on it. I don't know what else you want them to do. Of course they're not going to put IPv6 on their main domain, but that's only because most OSs and hosts have a broken implementation: they ask for an AAAA record first, timeout, and ask for an A record then. They don't check if IPv6 is working first and fall-back to all-IPv4.

      And about the hardware support, Jesus Christ, get over it already! I have a HP K8600 printer, which is over two years old, and it has a sticker: IPv6 ready! Even HP's JetDirect cards support IPv6.

    69. Re:Seriously? by the_fat_kid · · Score: 1

      I'm not suggesting that the IT departments are the cheap, lazy, luddites in this equation.
      I'm just saying that "the customers don't want to pay for the new equipment" is a weak excuse.
      We didn't want to pay for the old equipment. So what?
      If IPv4 doesn't give you any problems locally and you aren't worried about SomeOne Else's problems, keep it. If it aint broke why fix it?
      If you must upgrade you can pay the cost difference from your profit margin or charge more.
      I get how companies feel about lowering their profit margins, but the math is plain:
      If you must upgrade your equipment can't afford to, without charging more, then you will have to charge more.
      If the customer doesn't want to pay more they(we) can look for SomeOne Else to do it for less.
      Just don't act like there hasn't been time to deal with this.

      --
      -- Sig under construction...
    70. Re:Seriously? by Matt_R · · Score: 1

      dual radio (2.4 GHz and 5.0 GHz simultaneously so I could separate my G from N)
      IPv6 support

      http://www.fritzbox.eu/en/products/FRITZBox_Fon_WLAN_7390/index.php?tab=1

    71. Re:Seriously? by Matt_R · · Score: 1

      I have a Cisco 877 at home running native IPv6, using the Advanced IP IOS image.

      I installed a new 877 this week for a client, and was surprised that the Advanced Security IOS image lacks IPv6 support.

      You have to pay extra for IPv6 at cisco. pathetic.

    72. Re:Seriously? by Macrat · · Score: 1

      * almost no home router supports IPv6

      Linksys E3000 router

      * almost no provider offers IPv6

      http://www.comcast6.net/

      * almost no webpage runs IPv6

      You mean like Google? http://www.google.com/intl/en/ipv6/

    73. Re:Seriously? by Anonymous Coward · · Score: 0

      and I have a WRT600N flashed with DD-WRT. Dual radios and IPv6, storage, print server... OK, it doesn't support IPv6 out of the box, but it doesn't mean it doesn't support it at all.

    74. Re:Seriously? by r7 · · Score: 1

      Upgrade your systems to IPv6 already

      Is this a rhetorical question or what? Considering that no equipment currently on the market does IPv4 to IPv6 NAT any IPv6 device would only be able to contact at best 0.001% of the Internet. Give me a break is right, just not a broken Internet. IPv6 is still a long way from being usable.

    75. Re:Seriously? by Pentium100 · · Score: 1

      NAT works. Even more, it works now. Random user PC that is used to browse the web does not need a real IP, all incoming ports would be blocked by a firewall anyway. Most of the computers in a given company are client-only PCs.

      IPv6 is badly designed (not that I could have made anything better). There are a lot of devices that do not support IPv6 and will never support it (for example my printer). So, you need to either replace the devices (and get the money where? Especially if the device does its primary function well enough) or you need to use both protocols - IPv4 for communicating with the old devices and IPv6 for everything else. But then why not have some sort of NAT so you can just use IPv6 outside of your network? Oh yea, there is no way of doing that. OK, then what do I get if I spend my money (and time) and get IPv6 configured correctly (replacing some devices if needed)? All websites work on IPv4, P2P works on IPv4 too, so why should I bother?

    76. Re:Seriously? by Anonymous Coward · · Score: 0

      NAT is perfect in design because it increases efficiency something like 56525X and increases security 100X easily. If IPv6 has anything that comes close to the finesse that is NAT, then I will eat my words. However, you can not dismiss NAT as a bad thing.

    77. Re:Seriously? by kevorkian · · Score: 1

      and it is an ODD number...

      Only EVEN in production !!!!!

    78. Re:Seriously? by kasperd · · Score: 1

      Most enterprise "LAN" switches are protocol aware, however. Ever heard of a VLAN?

      VLAN is on a protocol layer just under conventional Ethernet. As such it doesn't know anything about protocols on top of it.

      QoS?

      It is possible for a switch to inspect the payload looking for headers at a much higher protocol layer than a switch should be concerning itself with, and apply different routing policy depending on what it finds.

      In the worst case such a switch would put IPv6 packets into random queues misinterpreting the headers. If you are pushing your network hard enough to need QoS at this level, then this could cause undesired behaviour. If the network is not congested, the IPv6 packets will still make it through to the proper destination.

      I think in most cases the need for QoS is on routers and not on switches. But the way the chips work nowadays, there is no longer such a clear distinction between a switch and a router. Technically if it uses MAC address to choose outgoing interface it is a switch, and if it use IP address to choose outgoing interface, it is a router. But some hardware can do either of those depending on configuration.

      Anyway, a company that actually need QoS on their local network should have network engineers with sufficient knowledge that they are also aware of the need for IPv6 and have a plan for how to get there.

      --

      Do you care about the security of your wireless mouse?
    79. Re:Seriously? by kasperd · · Score: 1

      ipv6.google.com doesn't work anymore. Your ISP needs to partner with Google so google's DNS serves will return IPv6 addresses to hosts in those networks.

      This is not correct. No matter which DNS server you use, Google will provide an AAAA record for ipv6.google.com (and no A record).

      For google.com, www.google.com, and many other google domain names there currently is a whitelist of DNS servers among ISPs that have an agreement with Google about the service level of the IPv6 connectivity. DNS servers on the whitelist gets both A and AAAA records for those domains, DNS servers not on the whitelist only gets A records.

      Of course they're not going to put IPv6 on their main domain, but that's only because most OSs and hosts have a broken implementation

      Saying most is not accurate. There has been at least one number published, and it was less than 1%. However compared to the number of people who actually have IPv6 connectivity, and compared to the reliability that Google wants, 1% is a lot.

      they ask for an AAAA record first, timeout, and ask for an A record then. They don't check if IPv6 is working first and fall-back to all-IPv4

      It's correct that most ask for AAAA first, but only if they think they have a working IPv6 connection. In some cases AAAA lookups don't work, in other cases AAAA lookup works, but there is no working IPv6 connectivity, and there is a long delay before the TCP connection times out.

      --

      Do you care about the security of your wireless mouse?
    80. Re:Seriously? by kasperd · · Score: 1

      Just run NATted IPv4 which handles DNS just fine

      Even better forget about NAT and run your recursive DNS server on an OS that properly supports a dual stack configuration. Your DNS server can do lookups over IPv4 or IPv6 as needed. Clients can contact the DNS server over IPv4 or IPv6 as needed. Since the client and DNS server are on the same network, you don't need NAT between them. The DNS server of course needs a public IPv4 addresses. At least one RIR have decided to keep a small pool of IPv4 addresses for such cases.

      --

      Do you care about the security of your wireless mouse?
    81. Re:Seriously? by sjames · · Score: 1

      Switches don't have to be upgraded, as far as they're concerned, anything above the ethernet header is just payload.

      Given that it's been 10 years now, there's a fair chance they've gone through a couple upgrade cycles since then.

    82. Re:Seriously? by sjames · · Score: 2

      Set up a 6to4 gateway somewhere and you can at least get a pilot program going to make sure everything's ready. Then pester your provider.

    83. Re:Seriously? by kasperd · · Score: 1

      How much will that "IPV6 Migration" project save or return?

      That's the wrong question. You are going to need IPv6 at some point because your business need to communicate with somebody who was not lucky enough to get an IPv4 address. Of course you may not be able to predict if this will happen in one year or in five years, but it will happen. The real questions to ask are:

      1. How much resources will you save by starting the migration now compared to later?
      2. How much will it cost if you are too late with deploying it?

      You might not even realize that you are too late. How will you measure the money you lost due to a potential customer who could not access your website because he only had IPv6 access?

      --

      Do you care about the security of your wireless mouse?
    84. Re:Seriously? by Wildclaw · · Score: 1

      NAT works.

      Nightmare address truncation works?Seriously, the only ones who say that are bastard operators from hell.

      Random user PC that is used to browse the web does not need a real IP, all incoming ports would be blocked by a firewall anyway

      I support my case.

    85. Re:Seriously? by sjames · · Score: 1

      So why weren't ISPs demanding IPv6 ready hardware for the last 2 upgrade cycles?

      The v4 exhaustion has been forecast to be right aroun now for the last 10 years. This is no surprise at all.

    86. Re:Seriously? by knorthern+knight · · Score: 1

      > There is plenty of hardware around that does not support v6 addressing,
      > like network printers and most current home broadband routers.
      [...deletia...]
      > It is much easier for the ISP to provide a 6to4 gateway and let all the
      > users keep pretending they have an IPv4 address even though it's really IPv6.

          Bingo...

      * when UHF television channels 14..83 first came out in the 1950's, you could get an adapter box with a UHF tuner that translated UHF channels to channel 3 or 4 on your old VHF-only TV set

      * when ATSC digital broadcast came out, you could get an adapter box that translated ATSC signals to channel 3 or 4 on your old NTSC analog TV set. The better ones had RCA outputs that fed directly into RCA inputs on newer NTSC TV sets.

          This is exactly what Joe Lunchbucket needs. 99% of home users are *NOT* slashdotters, and haven't got a clue about IPV6. Giving people an IPV6 connection and an IPV4 translator, and they won't care. The geeks can bypass the translator and connect directly in native IPV6 mode.

      --

      I'm not repeating myself
      I'm an X window user; I'm an ex-Windows user
    87. Re:Seriously? by rubi · · Score: 1

      I agree with you, and "how much is the return/savings" can be a (extremely) condensed form of what you postulate, but right now there isn't any compelling commercial necessity that makes clear to them how important starting early (being already somewhat late) can be. There isn't any current restriction on connectivity and odds are that any transition, even a forced one, will be more of a gradual process than a col turkey cutoff.

    88. Re:Seriously? by Pentium100 · · Score: 1

      I have a few PCs. They all share one external IP address using NAT. It works.

      In a company, here are a lot of PCs that are not supposed to receive incoming connections. Why should they have their own external IPs?

      Yes, we will run out of IPv4 addresses and we will have to start using IPv6. However, there are still IPv4 addresses left. Also, the "perfect network in theory where my printer can receive an incoming connection from outside (that is, it could if not for the firewalls and access lists) just because the theory says so" is not worth it. IPv6 will get its own modifications and then the network will be imperfect in some other way and some people will want to go to IPv8.

      One ISP I know (not my ISP though) offers three additional IPv4 addresses for its fastest "home" connection (and less or none for the slower ones, but all get at least one real IP). I honestly would not know what to do with them.

    89. Re:Seriously? by kasperd · · Score: 1

      There isn't any current restriction on connectivity and odds are that any transition, even a forced one, will be more of a gradual process than a col turkey cutoff.

      There is no doubt it will be a gradual process. And large parts of the network will be running IPv4 and IPv6 in parallel for some time. If you decide to keep your part of the network IPv4 only for a long time, then falling off the network will also be a very gradual process. It is going to start with a few people on the Internet being unable to communicate with you. As time goes on the parts of the Internet you won't be able to communicate with will keep growing. You might not notice as the number of people you can communicate with might still be growing. (A smaller and smaller percentage of a growing Internet may still be growing in absolute terms). It will be a very long time before a major part of the networks that already have IPv4 will go IPv6 only.

      --

      Do you care about the security of your wireless mouse?
    90. Re:Seriously? by Anonymous Coward · · Score: 0

      Um, no, you're wrong.

      2 of the top 5 cable broadband providers in the U.S. are still using antiquated docsis revisions and have issues with MAC cloning and MAC collision.

      Summary: stfu.

    91. Re:Seriously? by Anonymous Coward · · Score: 0

      You don't seem to understand the huge demand for IP addresses.

      Interop returned almost a complete /8 (16 million IP addresses). That didn't significantly extend the life of v4, according to ARIN
      NANOG post
      In comparison, a B and two Cs is 66,000 IPs -- a little bit less than 1/255th of what Interop returned.

    92. Re:Seriously? by petermgreen · · Score: 1

      I think it will be a long time before IPV4 addreses aren't available for important servers and also a long time before users don't have some means of reaching servers on the IPV4 internet.

      Really there are only two compelling reasons to go v6 for a company at the moment.

      1: They want a large proportion of machines to be reachable from outside thier organisation and they see that number continuing to grow.
      2: Their network is so massive that it will in the forseeable future outgrow the combination of 10.0.0.0/8 plus whatever v4 space they have aquired to date (comcast has this problem).

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

      The sad fact is that it's now too late for a smooth transition to IPV6. There will still be V4 only clients and servers past the end of net V4 allocations.

      That means the ISPs have little choice but to deploy ISP level V4 nat and use the recovered addresses for those that really need and are prepared to pay for a public V4 IP (servers etc). They will need to buy and deploy all this ISP level V4 nat gear regardless of whether they also deploy IPV6.

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

      Do you know what the profit margins are for ISPs? If they take a hit on profits, they go out of business.

      --
      Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
    95. Re:Seriously? by petermgreen · · Score: 1

      Regardless of the supposed efficiancy improvements with IPV6 prefixes the basic fact remains that routing with longer addresses requires more time to do in software and wider tables to do in hardware.

      But afaict the main issue is that older routers can route V4 in hardware but can only route V6 in software.

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

      Client machines don't care whether the DNS server they are pointed to is NATted or even in a RFC 1918 block. And no one is really going to run world-reachable DNS servers on XP -- nor Vista/7 on that matter.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    97. Re:Seriously? by KingMotley · · Score: 1

      No, even currently IPv6 can't do everything IPv4 can do. I can't connect to all the websites on the internet using IPv6, but I can with IPv4. I can't currently use IPv6 at all because my ISP doesn't support routing it.

      You will eventually be able to do everything a gas car can in an electric car. Just give it the same 10-15 years that IPv6 has been baking and the battery tech will be good enough (most likely), or you can stop off at a "gas station" and recharge just as quickly.

      As for cost and availability, how is that different between cars and network equipment? What current commercial home routers support IPv6? Linksys doesn't have any that I know of, and definately didn't 10 years ago. In fact my Linksys (610N) router I just bought less than a year ago doesn't support it, and it wasn't exactly cheap.

    98. Re:Seriously? by Anonymous Coward · · Score: 0

      Hmm, last I checked Time Warner Cable's profits were insanely up, as they seem to be every year. No matter how much these greedy bastards make they won't invest in infrastructure until they start losing money because of it. Can we ditch this pay $10 a month extra for crappy speed boost bursting for 2 minutes bullshit and get DOCSIS 3 already.

      I think the wire based broadband providers have seen the writing on the mobile broadband wall and have decided to just milk their infrastructure to the end.

    99. Re:Seriously? by Anonymous Coward · · Score: 0

      Really? Because IPv6 has been around for 10 years doesn't mean quality, reasonable priced, ipv6 capable equipment has been around for 10 years. Try to find a quality a/vdsl modem with ipv6 support for less than 100$ 10 years ago. Let me know if you find it because we are still looking for them right now.

    100. Re:Seriously? by r7 · · Score: 1

      NAT works

      Everyone knows NAT works because everyone uses NAT, most of us aren't even aware of it. The only people who have a problem with NAT are ILECs like ATT, aggregators like Google, and wirters of trojans, viruses, spambots and other P2P malware. These groups know that access to us and our data would be much easier with NAT out of the way, and they think IPv6 is a way to make this happen. Claims that NAT is harmful only exist because the ATTs and Googles of the world have a lot of money to spend on astroturf.

    101. Re:Seriously? by r7 · · Score: 1

      I'm sorry to have to say this to you like this, but you have no idea what you're talking about.

      Sorry but we do know. Whether the equipment you cited supports IPv6, well or otherwise, is irrelevant because 99.999% of the Internet is inaccessible to IPv6 nodes without NAT64 and NAT46.

      Anybody who has tried to use IPv6 knows this. IPv6 will never reach more than 0.01% of the Internet without NAT64 and NAT46 and probably NAT66 as well.

    102. Re:Seriously? by Anonymous Coward · · Score: 0

      It's easy to blame the developers, but if your users had said "We require IPv6 support", they probably would have got it.

      Developers, like everybody else, will do the easiest thing that works. If you don't ask for a feature, they're not going to go out of their way to provide it.

    103. Re:Seriously? by DarkKnightRadick · · Score: 0

      After 12 years, this should not be an issue. 12 years folks!

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    104. Re:Seriously? by alphatel · · Score: 1

      Just use "ping6 pong6.com" for testing. Forget about pinging Google's ipv6.googlesomtehinginsifd.com

      --
      When the foot seeks the place of the head, the line is crossed. Know your place. Keep your place. Be a shoe.
    105. Re:Seriously? by arth1 · · Score: 1

      Windows XP/2003 does not support IPv6 in any meaningful way. Yes, it has it in network config page. However, for example, it won't make DNS calls over IPv6 even when querying AAAA records.

      That's very strange, because my LAN's name servers listen on IPv6 and get queries from my XP box.

      Granted, you have to set up a manual route for IPv6 in XP, but it's not exactly rocket surgery.

    106. Re:Seriously? by anegg · · Score: 1

      In theory, theory and practice are the same. In practice, they aren't.

      IPv4 performance for not only routing but the application of ACLs, QoS, etc. at wire speed in many products is dependent on custom ASICs and other hardware. Its not so much a poor hardware/software implementation that makes IPv6 slower, its just that the products embedded in networks now were focused on achieving the best balance of cost and performance for the market that existed at the time the products were developed and sold. As organizations increase their demand for IPv6 routing and other features at wire speed, and are willing to pay for it, vendors will deliver (and some already have had such products available for years).

      My point was only to remind/inform folks that last year's affordable 48-port switch/router with a 96+ Gbps backplane that can do full duplex switching and routing at wirespeed including the application of ACLs and QoS isn't necessarily going to perform any where near that level with IPv6. Once the box drops out of its highly optimized custom hardware-based packet handling into software-based packet handling, the throughput goes through the floor. Converting to IPv6 is more than just checking off the boxes for IPv6 support on workstations, and may have significant hidden costs that should be identified prior to commencing the conversion.

    107. Re:Seriously? by bill_mcgonigle · · Score: 1

      So why weren't ISPs demanding IPv6 ready hardware for the last 2 upgrade cycles?

      They weren't available until a year or so ago. Sure, you could do IPv6 in software, but doing in in specialized hardware is just recently available (and what's required). So, 4 years from now should be safe to switch over.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    108. Re:Seriously? by LingNoi · · Score: 1

      All new linksys routers since last year support IPv6. There isn't support in their web UI but since the majority that the GGP is whining about never use the web ui I don't think it really matters.

    109. Re:Seriously? by tlhIngan · · Score: 1

      The major force holding back IPv6 deployment is shitty consumer hardware that doesn't "do" IPv6, and shitty network hardware vendors who charge an arm and a leg for IPv6 capable routers etc. (coupled with the fact that people have already invested a lot of money on non-IPv6 hardware anyway). It's not like the ISPs are doing it just to piss you off.

      Which is why we should just go and accept that NAT is here to stay, and design a NAT system that does v4/v6 protocol translations (you can easily design a system where a v4-only host can access v6-only hosts using clever DNS spoofs, V4 private address space DNS maps, etc). Consumers and companies swap their gateway router with this combined box, so their internal network remains unchanged (keeping their v4 investments) and not losing any bit of the 'net. ISPs can use it to keep v4-only connectivity to customers (albeit restricted since they can't port map) and equipment while they slowly acquire v6 equipment, etc. The vast majority of home users and companies, this is good enough. Thos who want real connectivity like they currently have can do it their own way.

      And let's give up with the romanticized idea that every host will be reachable once we have IPv6 going strong like the early IPv4 days that nAT "broke". Because firewalls aren't going away and they purposely break connectivity. New protocols should be translation and firewall friendly.

      The final thing? I don't know about you, but my ISP renumbers my IP every few months or so - with IPv6, all my IPv6 hosts have their IPv6 addresses change as the prefix changes. At least NAT allows me to number my hosts any way I choose independent of my real IP. Sure I can use link-local and additional private addresses to all the hosts, but it's an annoyance to deal with multiple IP addresses per host.

    110. Re:Seriously? by sjames · · Score: 1

      They weren't available because nobody was demanding it. If the sales people ask about v6 needs and the yawns become deafening they'll work on other bullet points instead.

    111. Re:Seriously? by isorox · · Score: 1

      or 5 years has passed (the time it takes to write it off)

      You don't sweat assets?

    112. Re:Seriously? by jonbryce · · Score: 1

      My desktops and laptops certainly support IPV6, and most of my servers do. However, I'm pretty sure my printer and my scanner don't. A lot of mobile devices don't - eg Android and IOS v 4, and very few routers do, certainly if you are talking about consumer grade routers.

    113. Re:Seriously? by jonbryce · · Score: 1

      If the IPv6 enabled model costs more, how do you get that past your resident bean counter, given that currently the IPv4 only model will perform exactly the same task in exactly the same way as the IPv6 model.

    114. Re:Seriously? by DarkKnightRadick · · Score: 0

      Unless your router and scanner are networked on a hub, I don't see how that is an issue.

      Okay, so I was wrong about support in devices other than computers. 12 years people. 12 years and we still have this lackluster support? Seriously? What a freaking joke.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    115. Re:Seriously? by Anonymous Coward · · Score: 0

      a lot of modems do not support ipv6 let alone routers.

      It seems the proper solution is to give the 'customer' an internal ipv4 address that routes out to an ipv6 address.

      How many websites break with ipv6 only users? I'm sure it would at least fuck up most p2p. Maybe if ISPs knew this they would push for ipv6 more.

    116. Re:Seriously? by j+h+woodyatt · · Score: 1

      That's what they all said when it was time to ditch IPX and Appletalk and get connected to this thing called the Internet. Now, the Internet is almost full, so if your business plans are predicated on the idea that the number of Internet users will continue to grow at the current rate for the next ten years, then they probably need revising.

      --
      jhw
    117. Re:Seriously? by j+h+woodyatt · · Score: 1

      On the other hand, now that the Internet is almost full, the capacity should stop growing altogether pretty soon and all that equipment they're buying this year and the next ought to suffice until the end of time.

      --
      jhw
    118. Re:Seriously? by vegiVamp · · Score: 1

      If I recall my ISP days correctly, upgrades mostly happen when the old stuff dies, period. That, or it becomes so dysfunctional it impacts baseline. Five years doesn't really enter into it, although support cost does to some measure.

      --
      What a depressingly stupid machine.
    119. Re:Seriously? by Skapare · · Score: 1

      As a network and systems administrator, I'm all ready for IPv6. It's already running on our LAN and in use. I'm just waiting for our firewall maker to get their act together and implement IPv6, and for our ISP to get their act together and deploy IPv6.

      --
      now we need to go OSS in diesel cars
    120. Re:Seriously? by h4rr4r · · Score: 1

      Check out verizon, comcast and see.

    121. Re:Seriously? by Anonymous Coward · · Score: 0

      Which is why we should just go and accept that NAT is here to stay, and design a NAT system that does v4/v6 protocol translations (you can easily design a system where a v4-only host can access v6-only hosts using clever DNS spoofs, V4 private address space DNS maps, etc).

      NAT has its limits, especially with today's (and presumably also tomorrow's) heavily AJAXified sites. There is a nice illustration of what a user behind a NAT box which limits the number of his connections might see when using Google Maps (p.10 onward). Not pretty, huh?

      However, that's probably how the things will play out: ISP sees it's out of public IPv4 addresses, can't get more, purchases a couple of big honking CGN boxes, users get a non-routable address on their end unless they're prepared to pay extra, things go back to almost normal for a while (bonus: difficulties for end users' P2P applications). Maybe they will even start seriously thinking about IPv6 rollout.

    122. Re:Seriously? by IAN · · Score: 1

      It's been around for what? 10 years now? Give me a break.

      12 years pretty much exactly:

      IPv6 was developed by the Internet Engineering Task Force (IETF), and is described in Internet standard document RFC 2460, published in December 1998.

      Make it 15 years: RFC 1883, the first IPv6 specification, was published in December 1995.

    123. Re:Seriously? by Cramer · · Score: 1

      Saying Windows XP (which a great many people and companies STILL RUN) supports IPv6 is laughable. It was and still is, EXPERIMENTAL. And does not meet any of the modern standards for IPv6. (IPv6 as an idea has been around for ~15 years. The protocol specifications (RFCs) systems follow today are only a few years old. And still changing.)

      Anyway, there's a great deal more involved than just "the OS supports it." Applications have to support it. Numerous bits of hardware have to support it -- firewalls, routers, switches, print servers, printers, access points, ntp clocks, phones, etc, etc, etc. And yes, routers need to be REPLACED to fully support IPv6; the software switching performance of even uber routers is complete crap. And most importantly... your ISP(s) have to support it. (neither of my broadband connections (TWC and Bellsouth) support IPv6. Neither do clearwire or FiOS.)

    124. Re:Seriously? by Cramer · · Score: 1

      Really? I know at least one company that's still using 20 year old *hubs*. Yes, h.u.b.s.!!! And Cisco gear so old, Cisco refunded the support contracts after having to replace one. ("oh shit, we don't have any of those.") (this company still uses IPX print servers, btw. HP never made IP firmware for them.) I'm using gear that's been EOL/EOS for 5+ years now... don't break what's working. I'll have to replace it to support IPv6 at any realistic speeds. (IPv6 is handled entirely in software.)

      Anything that has to be managed needs to support IPv6. Or your network becomes a huge f'ing mess. I've been there... appletalk, ipx, and IP on the same network.

      "upgrade the software" is a fine thing to tell yourself. However, in the real world, there are devices that will never support IPv6 because the company that made it won't upgrade it, no longer exists, or was bought out and abandoned the thing. (I have stuff in all of those categories.)

    125. Re:Seriously? by Cramer · · Score: 1

      Out of the box is what matters. If grandma cannot go to $BIG_BOX_STORE, buy something, come home and plug it in, it's useless.

      (Plus, almost no broadband ISP supports IPv6 for end users.)

    126. Re:Seriously? by Cramer · · Score: 1

      Since when does a linksys router have any other interface than the web ui? There's no serial port on them (unless you make your own.) And they don't do telnet or ssh.

      (Replacing the firmware with DD-WRT, OpenWRT, Tomato, etc. doesn't count.)

    127. Re:Seriously? by Cramer · · Score: 1

      Very few home routers support IPv6 out-of-the-box. And the millions in the field will almost certainly never see a firmware update to support IPv6. (it's more profitable to make you buy a new one.)

      I know of no broadband ISP that is openly providing IPv6 service to residential customers (in the US.) Comcast has a "trial program", and at last report, it's closed to new participants. Earthlink had a pilot program that was abandoned after laying off the one engineer running it. Getting native IPv6 connectivity from *business* connections is still spotty.

      Google is not the entire internet. While saying there are *no* websites in IPv6 is obviously wrong, most of the places people go everyday are not reachable via IPv6 only. (unless you're in china.)

    128. Re:Seriously? by Cramer · · Score: 1

      Put another way:
      Unless the hardware is very new (within a few years), it will most likely handle IPv6 purely in software, with little if any hardware support. This is the slowest of all methods.

      While the Cisco ASA lists IPv6 support on paper. Have you actually tried using it? It's a very bad joke. Maybe it's better in 8.3, but I refuse to run that brain damaged crap. Our checkpoint firewalls do not support IPv6, and would have to be completely reinstalled to do so. (the base secureOS -- running linux 2.4 -- has zero support for IPv6.)

      Load balancers... some support IPv6, for various definitions. I've not played with any of them to gauge their level of suck.

      Bottom line... the move to IPv6 will be expensive, and very messy. And will probablly take another 10 years.

    129. Re:Seriously? by Cramer · · Score: 1

      It's a good thing I'm out of Dew or it would've flown out my nose.

      Oh hell no they don't. ISPs run shit until it's completely dead. I don't want to think about all the times I've had to go to war to get $10k to upgrade a router -- even then it was someone else's used gear. While many large ISPs have the revenue to support such foolish spending, the people writing the checks aren't nearly as crazy. (besides, if they're spending millions on gear, that's millions not going in their pockets.)

    130. Re:Seriously? by sjames · · Score: 1

      Hubs don't care about IPv6. The IPX print servers don't either. If you're just concerned about management, leave that on the 10/8 net (dual stack is the only sane way to go for now anyway). I doubt you need the management interfaces on any of that hardware to be world accessible on a public IP (in fact, you probably want to be sure it isn't!).

      If necessary, you can bypass practically all of the dane brammaged hardware using 6to4 tunnels.

      If that ancient gear is capable of holding your network up, then it won't be very difficult to use old Linux boxes or even high end consumer gear to handle the v6 traffic for you.

      I'm fine with the "if it ain't broke, don't fix it" philosophy, but you should consider a lack of replacement parts and ability to interface with more recent gear to be a degree of broke.

      One thing to keep in mind, while many devices handle v6 in software, it's also less work to handle in the first place since there is never a need to recompute header checksums and NAT is unnecessary.

      If you have a room full of code talkers watching your network trafic on a vt100 handling your VPN, I can't help you. :-)

    131. Re:Seriously? by Cramer · · Score: 1

      My point was more about the age of business infrastructure. Some people seem to be under the delusion that companies rip out all their gear every few years. I've never known one that did. eg. the 20 year old 3Com dual stack hubs all over the building. (at the time, they had plenty of spares and 3com would replace the dead ones. however, as we found out with cisco, eventually, the warehouse is going to be empty.) Companies replace things when they have to, and sometimes when they *need* to.

      IPv6 in software on most router platforms is best avoided. Those packets are "process switched", which is the worst, slowest possible means of moving packets. In the Cisco world, you can make very expensive gear perform worse than junk if the packets are process switched.

      Running a bunch of parallel networks for "legacy gear" is not a great situation. Right now, IPv6 still needs IPv4 to be effective. At some point, systems will be able to function completely on IPv6, and you'll want to remove IPv4 from your network -- entirely. It's not an issue of global reachability; it's an issue of having to run and support 2 networks just for the legacy devices that cannot handle IPv6. (and right now, that's a lot of things... printers, network scanner, network fax, switches, access points, our toshiba phone switch...)

    132. Re:Seriously? by sjames · · Score: 1

      Sure, eventually you want to just drop the v4 stuff entirely, but it doesn't have to happen today.

      To be fair, MOST hubs got trashed somewhere around the time that unmanaged switches in reasonable sizes fell to under $100.

      v6 on a Cisco certainly is to be avoided, so just install a Linux box to do the v6 and let the Cisco ossify in place. If your organization is ACTUALLY still using hubs that extensively, the network performance is already in the toilet, a decent Linux box will easily keep up. (BTW, it's a miracle your ethernet cards don't freak out, so much of ethernet runs at full duplex these days, there are entire models of cards that haven't seen a collision in the real world) Keep in mind, the cpu in a Cisco supervisor card is incredibly anemic by modern standards.

      It's quite probable that at worst, a bit of creative use of vlans can allow you to keep a lot of that old gear going even with IPv6 just by adding a few linux based routers.

    133. Re:Seriously? by Cramer · · Score: 1

      Nothing ever gets "trashed", esp. functioning network gear. So until those hubs fail, they continue to be used. 20 year old pix firewalls continue to get used. Cisco routers the 20-somethings have never heard of are still pushing packets. Even today, in the software dev world, I don't get to "trash" anything that isn't broken -- or in the case of desktops/servers, something so obsolete it's hindering productivity (and even then it's an uphill battle.)

      "Just use a linux box" is not something upper management likes to hear. It's better received today, but still not the answer to everything. It's only appeal is the superior cheapness. Even a pure crap PC has a processor hundreds of times faster than Cisco's general purpose CPU (because it's not designed for heavy lifting.)

      FWIW, network performance was not the horror you may think it was. It wasn't hubs plugged into hubs, or huge multi-hub stacks. It actually ran quite well -- even after they pushed multicast video into it. (*nod* really. yes a collision is a lost packet.)

      Judging from your low UID, you should be aware of auto-negotiation. Even a modern day 1000bT card will happily link and run at 10M/half. (says the guy who looked at his laptop like it was broken when it linked to the Clearwire modem at 10/half. the asses actually built the damn thing with a 10bT port.)

      In the end, devices that only support IPv4 and can only be managed via IPv4 will require me to continue running an IPv4 network / stack in order to talk to them. Just like with the IPX printer servers... desktops don't have to run or be aware of IPX, but there's still an IPX network and at least one multi-protocol host to act as a gateway. I'd rather not have to bother.

    134. Re:Seriously? by sjames · · Score: 1

      I do know about auto-negotiate, it's part of the spec. I just also know that there is a difference between a card negotiating to 10baseT half and having it handle collisions properly.

      As for network performance, if it's not a horror there it's because it's not a very busy network. A network based on a 24 port 10baseT hub shares a glorious 10Mbps (416Kbps per host). A 24 port switch can be bought new from Fry's for $80.

      What can I say, the world is going to be forced to move on to v6 at some point. Anyone who doesn't come along for the ride will just get left behind and eventually get a nice writeup in the daily WTF.

  3. the internet a fuedal domain by kantos · · Score: 0

    ... Where IANA is the king and owns all of the IP space... granting it to its dukes (RIRs).. who in-turn grant plots to the earls (ISPs) .... who inturn grant blocks to everybody else...

    --
    Any and all content posted above may be ignored, considered irrelevant, or otherwise dismissed.
    1. Re:the internet a fuedal domain by siride · · Score: 5, Insightful

      Yes, superficially, hierarchies look like other hierarchies.

    2. Re:the internet a fuedal domain by kantos · · Score: 1

      oh I know... but it's fun to make fun of it this way... since it is very superficially identical to the feudal land-granting system

      --
      Any and all content posted above may be ignored, considered irrelevant, or otherwise dismissed.
    3. Re:the internet a fuedal domain by John+Hasler · · Score: 2

      It is superficially similar to a simplified approximation of the feudal land-granting system.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    4. Re:the internet a fuedal domain by ColdWetDog · · Score: 3, Funny

      Help! Help!

      I'm being repressed!

      --
      Faster! Faster! Faster would be better!
    5. Re:the internet a fuedal domain by Anonymous Coward · · Score: 0

      Help! Help!

      I'm being repressed!

      (muttering) ...bloody /24.

  4. Lawyer says: by Anonymous Coward · · Score: 1

    The status of IP addresses as "property" has been the subject of considerable policy debate in the industry and remains an unresolved legal question.

    Maybe, with the right argument, we could turn routing tables into property rights! That way there is a clear and legal manner for an organization to ... pay lawyers money to fight over a number.

  5. Back in the day by Anonymous Coward · · Score: 0

    In 1997 I was 6000 miles from the US. If I still lived down there and still had that IP address then the American Registry of Internet Numbers wouldn't have any jurisdiction.

  6. For crying out loud, let's just move to IPv6. by Anonymous Coward · · Score: 1

    FOR CRYING OUT LOUD, let's just move to IPv6 already.

    Yes, there will be a cost associated with it. Most things that will bring true value do cost something. It's called an investment, and moving to IPv6 would be an excellent one to make.

    America could have been a leader here. America could've used the early adoption of IPv6 to bring strategic and economic benefits. But these days, our business leaders are too short-sighted to make good investments. When all that matters is next quarter's results, solid investments will be totally ignored.

    It's likely that Europe and Asia will be making widespread use of IPv6 far before America ever will. The business cultures there encourage longer-term thinking, where it's recognized that some short-term costs can lead to huge benefits over the long term.

    1. Re:For crying out loud, let's just move to IPv6. by Anonymous Coward · · Score: 0

      Yes, that culture has indeed worked out for Europe. In fact, I think Ireland and Greece have definitely benefited the most by screwing over the short-term (haven't they screwed over the long term, as well?).

    2. Re:For crying out loud, let's just move to IPv6. by ElectroPrime · · Score: 1

      That would be great... if only all the companies hadn't realized they could now abuse the situation to steal^H^H^H^H^Hacquire increasing amounts of money from their victims^H^H^H^H^H^H^Hclients.

    3. Re:For crying out loud, let's just move to IPv6. by Anonymous Coward · · Score: 0

      Greece and Ireland are barely European. They're both on the fringes of the Continent, and in terms of commerce and governance they are far more American than they are European.

    4. Re:For crying out loud, let's just move to IPv6. by DarkOx · · Score: 1

      What has really killed IPv6 is not cost but lack of interest if not disinterest. You IT department at work does not really want the machine at your desk to be a true internet peer. They have a block of public IPs to hosts your orgs public services on and they can solve their other access problems with NAT. The need is meet and it even simplifies things in some ways depending on your perspective. At home your ISP who for most of America is probably also in the content distribution business does not care. The vast majority of their customers won't mind being NATed when the addresses run out and those ISPs would probably rather everyone be NATed anyway making certain end users were only clients. They know if they did it now their would be an out cry from a noisy few and it might bring the FCC down on them, if they wait they will have a perfect excuse to NAT everyone and nobody will really have any say in the matter because at that point it will be the only real solution.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    5. Re:For crying out loud, let's just move to IPv6. by Opportunist · · Score: 1

      Greece has squandered its income on short sighted social programs (instead of investing in school, just dump money on people so they shut up) while relying on fickle businesses like tourism for income (ya know, the kind that feel it first when the economy takes a dive).

      Ireland attracted companies with a low tax policy that ruined the finances in the long term for a short time increase in jobs.

      I doubt either can be seen as a result of "long time, planned, future investment".

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    6. Re:For crying out loud, let's just move to IPv6. by DarkOx · · Score: 1

      No actually Ireland's public finances were looking pretty good until they made a really stupid promise. They promised to fully backstop their large banks. That was a black hole that in turn cased the governments credit worth to come into question. Given how many of the largest firms their or foreign they probably could have and should have let the banks fail with little collateral damage.; More specifically guaranteed only the deposits to keep money from fleeing the country and told the bond and equity holders your on your own after all you expected to enjoy the gains from your investment privately you get to experience the loses privately.

      Had they done this their probably would have been no need for a bailout. So yea the real problem is they are governed like we are here in the USA where there is a certain protected class of old money that does not have to follow the same rules the rest of us do. Tax policy has almost nothing to do with it other than now like us their tax payers will have to chip in for the mistakes of others who are very wealthy to begin with.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    7. Re:For crying out loud, let's just move to IPv6. by Anonymous Coward · · Score: 0

      You IT department at work does not really want the machine at your desk to be a true internet peer.

      NAT is the wrong solution to that problem anyway. They should instead block incoming SYN packets, problem solved -- in a way that's more scalable (you can have multiple of these firewall boxes, with failover and load balancing), more fault tolerant (your TCP connections can persist after the firewall reboots). These qualities are quite hard to achieve with NAT.

    8. Re:For crying out loud, let's just move to IPv6. by Pi1grim · · Score: 1

      Learn the ultimate ^w combo already.

    9. Re:For crying out loud, let's just move to IPv6. by Kjella · · Score: 1

      Yes, that culture has indeed worked out for Europe. In fact, I think Ireland and Greece have definitely benefited the most by screwing over the short-term (haven't they screwed over the long term, as well?).

      You can blame the financial companies for giving countries the rope to hang themselves with, but the Greek and Irish debt crisis are almost all about public debt. To please the voters by providing lots of services and generous benefits while keeping taxes low, they've completely ignored basic economics like making your income match your expenses and just let the budget deficit run wild. Eventually the lenders go "Whoa whoa whoa, you want to borrow even MORE?" First they do it for a risk premium then they finally say no more credit for you, then people blame the lenders for "putting the thumbscrews" on the country. Of course the US crisis that lowered their tax income and increased their interest rates didn't help, but it's what happens when you push yourself to the financial limits and operate with no safety net.

      I very well understand Germany and the other countries that have been relatively conservative in spending, it's like we've saved and you've wasted, but now you expect us to come save your ass? They've been at the brink of financial collapse, and the EU brought them back from the edge with a crisis packet but they don't seem to grasp the seriousness of the situation. The public debt is still increasing and now they start talking about doing a "haircut" of their debt. But that will force everyone else to take losses, and I don't think they will. The UK used anti-terror laws against Iceland after the Icelandic bank collapse, I'm sure they'd do they same against Greece. And if you want another round of nationalism in Europe, break Germany's back trying to save the euro.

      Anyway, this got a bit off track but the point is that this is almost all a government-created crisis that was vastly accelerated by the financial crisis in the US. It's not so much an unregulated financial industry but more national leaders who act as if they got endless pockets and perhaps even in some form has counted on the EU to bail them out. And now it turns out that if everyone gets on the public debt carousel, there's nobody with money left to bail out tose that don't have money. The various European countries are now pinning each other up the way US investment banks did, which will either save them or cause an economic bust so huge the Great Depression becomes small fry. They're certainly putting more and more eggs in that basket.

      --
      Live today, because you never know what tomorrow brings
    10. Re:For crying out loud, let's just move to IPv6. by h4rr4r · · Score: 1

      As one of those IT guys at work I strongly disagree. NAT is a hack and a terrible one. Use a firewall for that.

    11. Re:For crying out loud, let's just move to IPv6. by bell.colin · · Score: 1

      What do you think most firewalls use to bridge internal addresses (10.x.x.x, 172.16.x.x, 192.168.x.x) to outside addresses?

    12. Re:For crying out loud, let's just move to IPv6. by hjf · · Score: 1

      He's probably a Linux kiddie feeling leet on Solaris who doesn't know that he should use DELETE instead of BACKSPACE.

    13. Re:For crying out loud, let's just move to IPv6. by h4rr4r · · Score: 1

      That is only for NAT, it is not actually needed at all. I have plenty of machines with real IPs in a class C just for my servers that I firewall from the rest of the world. On the ports needed you can get through just fine on the very same IPs.

      NAT is not needed for this to work.

    14. Re:For crying out loud, let's just move to IPv6. by Pentium100 · · Score: 1

      NAT is the wrong solution to that problem anyway. They should instead block incoming SYN packets, problem solved ... (your TCP connections can persist after the firewall reboots)

      So, all that would be needed to go trough the firewall would be to start the connection without the SYN flag. This would simplify NAT-T and would allow P2P software to work where it shouldn't.

      Also, instead of using a separate firewall, you can use NAT and get the same result (no incoming connections). A small company (a few users, no externally accessible servers and slow connection) can just use a cheap consumer NAT router. Is there a cheap consumer firewall? Also, there is no point giving every computer a public IP address, especially if you have a "deny SYN from all" rule in the firewall.

      Also, about the TCP connections - they would still time out while the firewall is rebooting (if there is only one firewall box), so no point there too.

    15. Re:For crying out loud, let's just move to IPv6. by kasperd · · Score: 1

      Even if you do full connection tracking you will still get a better result if you just use that tracking to filter traffic rather than modify the packets.

      --

      Do you care about the security of your wireless mouse?
    16. Re:For crying out loud, let's just move to IPv6. by Anonymous Coward · · Score: 0

      Actually, I hereby welcome the United States of Euro.

  7. IPv6 by Rehnberg · · Score: 1

    And we could just ignore this whole issue by switching over...

  8. Why? by froggymana · · Score: 2, Interesting

    Why would it matter if you have the same IP address you've had for several years? Whats wrong with switching to a different one?

    --
    "To prevent this day from getting any worse, I'll just read ERROR as GOOD THING" 1GJU8xLuDKDxEs4KLf8fAGyptoDsqvEsBT
    1. Re:Why? by isorox · · Score: 5, Insightful

      Why would it matter if you have the same IP address you've had for several years? Whats wrong with switching to a different one?

      Ask wikileaks. We're entering a world where you can't rely on DNS.

    2. Re:Why? by kthreadd · · Score: 2

      Why would it matter if you have the same phone number you've had for several years? What's wrong with switching to a different one?

    3. Re:Why? by Anonymous Coward · · Score: 0

      > Why would it matter if you have the same phone number you've had for several years? What's wrong with switching to a different one?

      Because... there's no DNS for telephone numbers...

    4. Re:Why? by TheRaven64 · · Score: 4, Informative

      Not the same. My phone number is published, my IP address isn't. I've moved IP addresses for my server four times in the last year. I set the DNS TTL to a few seconds, wait for old caches to expire, update it to the new address, and then reset the TTL to a longer value. No on notices.

      I just moved to a new mobile phone company too. My SIM ID, which is used to uniquely identify my phone on the network, changed. My phone number was moved across. The phone number is just an entry in a database that maps to a SIM ID, just as DNS maps to IP addresses (actually, DNS can map to all sorts of other things, including geospacial coordinates and telephone numbers).

      That's why we have these layers of indirection - so the low-level ones can be changed easily.

      --
      I am TheRaven on Soylent News
    5. Re:Why? by Anonymous Coward · · Score: 0

      Why would it matter if you have the same phone number you've had for several years? What's wrong with switching to a different one?

      You end up telling your friends and family your new number and your charity, political, and illegal telemarketing calls drop off to nothing for a few months.

      Loved it!

    6. Re:Why? by Anonymous Coward · · Score: 0

      Because we access servers by names, usually through DNS. Your telephone number is the lookup. If we had telephone systems that let you dial "kthreadd" we wouldn't be so attached to fixed numbers.

    7. Re:Why? by Splab · · Score: 1

      Actually it is the same. You just aren't used to have to ask the whitepages where person X is at the moment everytime you dial him up.

      In fact, it isn't until very recently you where able to move a phonenumber with you (EU, no idea how it works in US) - requiring you to update all those who might want to contact you.

    8. Re:Why? by Anonymous Coward · · Score: 0

      There most certainly is. In times past they called it a phone book, white pages, or telephone directory.

    9. Re:Why? by Anonymous Coward · · Score: 0

      No your name is looked up in exactly the same way the server name is looked up. When someone new needs to contact you they don’t magically know your number. They know your name which they look up in the appropriate system (i.e. telephone directory, address book, memory cache, etc.). You certainly don't store just numbers in your contact list. You store a name with the number so you can reference it by name. Hell, I don’t even know my wife’s mobile number by heart when I can just select her name in my mobile. If she changed her number the contact entry would just need to be updated and I could continue referencing her by name.

      I see little difference.

    10. Re:Why? by leenks · · Score: 1

      I'm not sure if you are trying to be clever or not, so I'll bite anyway...

      Before the new fangled internet came along, we had a thing called a telephone directory which provided a lookup between name and number, somewhat like DNS. Even better, you could call the operator (or a directory enquiries service) and get them to look up the number for a name if you knew their rough address.

      Of course, you could be ex-directory, and this would be like an IP address with no DNS.

    11. Re:Why? by dissy · · Score: 1

      Why would it matter if you have the same IP address you've had for several years? Whats wrong with switching to a different one?

      There isn't. The problem is you asked the wrong question.
      This is ARIN we are talking about, they don't deal with single IP addresses.

      Try a /16 block, or 65000 IP addresses.

      To reword your question into relevance: "Why would it matter if you have the same 65000 IP addresses you've had for several years? Whats wrong with switching to a different 65000 addresses?"

      Can you not imagine the undue amount of work such a change would involve to renumber that many computers, servers, routers, switches, DNS entries, DHCP MAC entries, config files for access control, and firewall rules?

    12. Re:Why? by Anonymous Coward · · Score: 0, Troll

      Yeah like what happened to them is really likely to happen to the average person. Grow up.

    13. Re:Why? by icsx · · Score: 2

      Somewhere, just now a blog stating someone's personal opinions about certain government/people/religion/whatever, running on certain domain was directed to bitspace. You still think it can't happen to average person? You grow up.

    14. Re:Why? by isorox · · Score: 2

      Yeah like what happened to them is really likely to happen to the average person. Grow up.

      In the mean time, facebook and twitter are banned from China (at least the hotel I was in last month), with the only technical means being a forged DNS entry. The BBC is currently banned because of the Peace prize coverage, I assume the same mechanism. DNS is the weakest link in the internet, and you might not even notice it.

    15. Re:Why? by TheRaven64 · · Score: 1

      I've had the same phone number for 12 years (UK), spanning four service providers, and number porting was available for longer than that - it's not a recent development. Phone numbers used to be equivalent to IP addresses - they identified physical endpoints in the network. Now they are equivalent to DNS entries - they define abstract end points that are mapped to real network addresses later.

      We can also add another layer of indirection on top of that, by having a telephone directory (which can even be implemented in DNS - some people do publish phone numbers in DNS) for mapping from people to telephone numbers, but that does not make telephone numbers equivalent to IPs. An IP is a low-level implementation detail. It exists so that two computers on the network can identify each other. You tell people your telephone number, but (unless you are wikileaks), you don't tell people your IP address directly, you tell them your domain name and get them to look up your IP.

      --
      I am TheRaven on Soylent News
    16. Re:Why? by teachknowlegy · · Score: 1

      Nobody noticed, or those who noticed can't tell you because they can't find you anymore?

    17. Re:Why? by TheRaven64 · · Score: 1

      Who wouldn't be able to find me anymore? The DNS entries still work, and I never advertised the IP address. The only people who would have known it are people who cached an old DNS entry, and those people would - by definition - know the host name(s). Same with my mobile phone. No one I communicate with knows my SIM ID or my device ID. They are looked up in the background when someone calls my number. The SIM ID corresponding to that telephone number has changed several times over the past decade or so, but the only people who are even aware of this are the telephone companies. For everyone else, the number stays the same.

      --
      I am TheRaven on Soylent News
  9. Fast? by Suki+I · · Score: 4, Funny

    There are plenty of pieces of hardware that dont support IPv4. Unless you upgrade the hardware to a dual stack configuration. Routers, switches, etc arnt cheap.

    Just because the OS supports it, doesnt mean its going to be easy or cheap.

    So, fast is not out of the question? ;)

  10. Dear owner of IP address 214.123.23.45 by Anonymous Coward · · Score: 1

    We are an Internet IP address registry in China. We have received information from a local company RANDOM PRODUCT PTY INC that they want to register the following
    IP addresses that are similar to yours:

    214.124.23.45
    214.123.32.45
    215.124.23.45

    Please contact us urgently if you do not wish us to allow this registration.

    1. Re:Dear owner of IP address 214.123.23.45 by Skapare · · Score: 1

      Ha! GLWT! These are US MIL addresses. You are probably just trying to attack them. We already know about Chinese espionage. Wikileaks told us all about it.

      --
      now we need to go OSS in diesel cars
  11. Bankrupt companies? by sunderland56 · · Score: 2

    So, where does the letter go for all of those bankrupt companies? Silicon Valley post offices must have a large pile of undeliverable ones.

    Maybe that's the final legacy of dead startups: their IPV4 address block is worth more than the company ever was.

  12. I got one by bbn · · Score: 4, Interesting

    I just checked. My 1994 class C is still allocated to me. I have no idea how to regain control over it though as every single contact detail, except my name, is outdated by 15 years.

    It was never used on the public internet. But back then they said you should get one for your local lan. This was before everyone started doing 192.168.x.y. So I applied for a class C and got it.

    Even if I did manage to get RIPE to correct the contact details, I do not know any ISP who would advertize it for me. So this class C is part of the dead IPv4 space that will probably never get used.

    1. Re:I got one by sphealey · · Score: 1

      Um, why don't you send a notarized letter via certified post to your regional IP address manager (e.g. ARIN) describing the details under which you obtained the block and giving up any interest in same? If they need that block back it would at least give them a starting point to work with.

      sPh

    2. Re:I got one by Spazmania · · Score: 5, Interesting

      IANAL, but here's some perspective from someone who has been in the thick of the ARIN policy process for the last few years:

      First, you're talking about RIPE (european IP addresses) while the article is about the registration services process at ARIN (north american IP addresses).

      Had you been talking about ARIN, this is frankly the kind of thing where you'll want to sign the LRSA and soon. ARIN will work with you to nail down the details and confirm the registration but they'll want to normalize their relationship with you via a signed contract first. I think they'll still update if you come to them with ironclad documentation, but if you had ironclad documentation you'd have been the kind of person who kept the registration up to date to begin with.

      For those who are still contactable via at least the email address published on the registration, now is not the time to sign the LRSA. ARIN claims you have more rights under the LRSA than under the regular RSA but on close examination the claim doesn't really hold up. It's a standard adhesion contract in which the powerful party has reserved the rights to themselves.

      That having been said, keep tabs on proposed ARIN policy every 6 months or so. ARIN probably won't seek the legal liability from trying to seize legacy registrations that are obviously in use, but the situation could change.

      If you are in the situation where your contact details are dead, I personally think you SHOULD sign the LRSA and normalize things with ARIN. A /24 is going to be worth at least $1000 within 12 months, and probably a lot more. IPv6 won't deploy fast enough, the IPv4 free pool will be gone by mid year and the only source of new IPv4 addresses will be folks who are willing to sell.

      On the other side, the unrouted dead registrations without valid contacts are very likely to evaporate in the next 24 months. The ARIN policies for this sort of reclamation aren't in place yet, but mark my words: they will be.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    3. Re:I got one by wmbetts · · Score: 1

      Pretty much any colo where you have a box should be able to announce it for you.

      --
      "Ubuntu" -- an African word, meaning "Slackware is too hard for me". - stolen from Dan C alt.os.linux.slackware
    4. Re:I got one by Anonymous Coward · · Score: 0

      Mod the parent up! Seriously informative, overlooked post ALERT!!!

    5. Re:I got one by phantomfive · · Score: 1

      One thing I've been trying to figure out, what exactly is going to happen in the next year or so? We know that ipv4 is going to run out of addresses, and we know that ipv6 hasn't really been rolled out yet (I myself will need to buy a new wireless router, which is ok). But what's going to happen? Will IANA stop giving out numbers and say, "sorry, nothing we can do. No more numbers." Will that pressure people to switch over to ipv6, or will it stop any new websites from coming online for a few years?

      When ipv4 addresses run out, are we really going to switch to ipv6? How, considering that no one wants to go first? As far as I can tell, y2k was relatively minor compared to this, and yet you hear nothing about it outside tech news sites.

      Maybe it will be new companies who push it first...they will have no other choice but to advertise, "if you want to visit us, come to this website, after changing this setting on your computer, etc." Kind of lame for them, but what other choice do they have?

      --
      Qxe4
    6. Re:I got one by Tony+Hoyle · · Score: 2

      "But what's going to happen? Will IANA stop giving out numbers and say, "sorry, nothing we can do. No more numbers."

      Yes. Quite possibly in less than a month.

      When we're down to 5 /8's they're distributed to the RIRs automatically and IANA shuts down its ipv4 operations forever.

      The RIRs then have until their v4 pool runs dry - they won't get any more - which may be quite quick for some (like apnic) and slower for others.

      After that it's down to what ISPs have - they'll probably ramp up their prices for v4 an instigate such horrors as carrier grade NAT, just to stretch it out, but it's just postponing the inevitable.

      And yeah, potentially this is bigger than y2k and the great unwashe don't even know it's happening - even though it *will* affect them.

    7. Re:I got one by Surt · · Score: 1

      Why don't you forward your mail from the old address to the current one, then request action by mail?

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    8. Re:I got one by Surt · · Score: 2

      With y2k, there was significant worry that existing infrastructure would cease to function. With this, it's mostly a threat of new services not being able to get started. Slowing growth is much less worrisome than an immediate reversal of 50 years of progress.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    9. Re:I got one by bbn · · Score: 1

      In my area it is only possible to forward mail for 6 months. It is certianly not possible to forward mail from an address I had 15 years ago.

      The email is to a no longer existing ISP, using their domain of course.

      The phone number is likely in use by someone else by now, and with the wrong area code in any case.

      I would probably have to find some proof that I lived at that address 15 years ago and present it to RIPE. But why would I bother? I have no use for that class C. Big companies that waste a class A can not be bothered, so why would I spent time and expense to release a class C?

      Some say I could sell it, but that is clearly against the rules for the allocatement. So not really.

      Lets just move to IPv6 and forget about it.

    10. Re:I got one by Spazmania · · Score: 1

      One thing I've been trying to figure out, what exactly is going to happen in the next year or so?

      Short answer: NAT.

      Lots and lots of perfectly good IP addresses have been deployed in use scenarios which would work perfectly well using RFC 1918 addresses aggregated behind a single public-facing IP address. When you need more IP addresses for a high-value application, you'll raid the places employing them in a low-value application.

      It's called a "zero sum game."

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    11. Re:I got one by mysidia · · Score: 1

      I just checked. My 1994 class C is still allocated to me. I have no idea how to regain control over it though as every single contact detail, except my name, is outdated by 15 years.

      If I were you, i'd start digging through my files for documents... contracts, deeds, utility bills, old ID cards, just about any document that could prove you "used to have" those contact details.

      Then contact ARIN hostmaster and request to update to your contact information or return the IPs. If you will not need the IPs then I strongly suggest you return them. Otherwise a spammer is probably going to eventually find the unannounced block and start announcing it so they can use "your /24" to send spam.

      If you want to use the IPs, then I would strongly suggest applying for the Legacy RSA and get them redeemed.

      What ARIN chooses to do with the registration if the IP space appears abandoned or no legacy RSA is signed is ultimately going to be up to the community.

      It will probably not be revoked, but there might ultimately be a reduction in "service" such as rDNS. Since the legacy swamp is well known for being targets of spammers and other unsavory people hijacking IP space, either by simply announcing space that isn't theirs, or pretending to be the bonafide registrant.

      In the end i'm sure it will partly depend on who doesn't bother to bring their space's contact info and agreements up to modern RIR standards. If major organizations such as universities had refused to sign the LRSA, then turning off RDNS or revoking probably would have not gone far... if the organizations are large enough, internet community members could stop listening to IANA/ARIN, and start their own "wild west" IP registries, bypassing ARIN for routing RDNS and registry decisions, a worst case scenario

      But the large address space holders had probably been mostly willing, from what I heard.

      If the only people who don't opt to sign the legacy RSA were a couple hundred of /24 holders; my suggestion will probably be "Give them 6 months to apply for, justify the need for, and pay the fee for the /24 they are using, otherwise, revoke it."

    12. Re:I got one by rs79 · · Score: 1

      Good thing we reserved, and never used, that multicast space: http://xkcd.com/195/

      --
      Need Mercedes parts ?
    13. Re:I got one by Surt · · Score: 1

      Ah, sorry, I assumed you were in the US where it is universally possible to forward email FOR 6 months, from any address, and is legal so long as you aren't committing fraud (you are legitimately trying to forward your own mail, and not to steal that belonging to someone else).

      Our USPS even maintains a convenient website to do it online. Mail service is really one place where the US excels!

      https://moversguide.usps.com/icoa/flow.do?_flowExecutionKey=_c11DEE43C-6C68-755E-A47C-9A6E2C257FEB_k6593D190-6E19-1AD2-3B9F-E5C75C1AAD7C

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
  13. who cares by pak9rabid · · Score: 1

    Call me crazy, but wasn't DNS invented to remove the significance of using IP addresses as a means of identification?

    1. Re:who cares by Spazmania · · Score: 1

      Call me crazy, but wasn't DNS invented to remove the significance of using IP addresses as a means of identification?

      That was before Javascript security issues mandated dns pinning.

      Not that everything (or really much of anything) actually implemented DNS TTLs before, but I like blaming Javascript for all the world's ills.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    2. Re:who cares by pak9rabid · · Score: 1

      You realize w/out javascript, the web would be a pretty boring place.

    3. Re:who cares by 93+Escort+Wagon · · Score: 1

      You realize w/out javascript, the web would be a pretty boring place.

      Without javascript, the web as we know it would not exist.

      --
      #DeleteChrome
    4. Re:who cares by Spazmania · · Score: 1

      Without javascript we'd have an html browser and a Flash browser and when I wanted a newspaper or message board, I wouldn't expose my machine to the risk associated with the Flash browser.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    5. Re:who cares by Anonymous Coward · · Score: 0

      You realize w/out javascript, the web would be heaven.
      FTFY

    6. Re:who cares by UncleFluffy · · Score: 2

      w/out Javascript and w/out Flash, the web would be a much more useful (and usable) place.

      --

      What would Lemmy do?

  14. Why so much regulation? by maxwell+demon · · Score: 1

    IPv4 addresses are a scarce property. And we know a mechanism which fits quite well for handling scarce properties: The free market.
    I'm not at all someone who thinks the free market is the cure for everything, but this is a case which fits exactly the case for free market: Make IPv4 addresses the property of the individual holders, and allow them to buy and sell. If they get scarce, the price will grow, just as the price of land grows if land is scarce. And if the IP addresses show up as property in the balance sheets, a growing price means there's more incentive to move to IPv6, in order to sell those IPv4 addresses.

    --
    The Tao of math: The numbers you can count are not the real numbers.
    1. Re:Why so much regulation? by Anonymous Coward · · Score: 0
      "just as the price of land grows if land is scarce"

      Or money is cheap. It's not that simple now, eh? We all know how that ended up.

    2. Re:Why so much regulation? by Surt · · Score: 1

      I think a lot of people think that the free market has been an utterly catastrophic mechanism for handling scarce properties. It has resulted in massive wealth concentration as clever individuals leveraged small differentials to exploit others to increase those differences, which is pretty much the opposite of what nearly everyone wants out of the market.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    3. Re:Why so much regulation? by u38cg · · Score: 1

      The main difficulty, as I understand it, is two-fold. The first is philosophical; those in charge of policy do not wish to move to such a system, and they are not really influencable. So there is no traction there. The second is that apparently such fragmentation of the IP space would make routing incredibly difficult, as in it would cause routing tables to grow exponentially. The first problem is potentially attackable, the second is more difficult.

      --
      [FUCK BETA]
    4. Re:Why so much regulation? by JesseMcDonald · · Score: 1

      IP addresses are neither scarce nor property. Like personal names, they are nothing more or less than the label by which a given host identifies itself. Others may or may not recognize that label, and the same label can be claimed by any number of hosts without any conflict, provided they aren't routed as part of a single network. For example, NAT gateways reuse the same address ranges for many different networks without conflict.

      Trouble only arises when the same address is used more than once in a single routed network, which is where ARIN et al. come in. No one is obligated to listen to them, but there has to be some organizing principle behind allocation of routable IP addresses on the Internet—other networks can have their own policies for the same addresses without any trouble—and these organizations currently serve that role. If they want to recognize private address-transfer agreements that is their business, but nothing obligates them to do so, and there are some rather good arguments against separating the IP address hierarchy from the physical layout of the Internet. For one, it would be disastrous from an infrastructure perspective to require every router to track every individual IP address, rather than the large, contiguous address ranges currently in use. The registrary would be perfectly justified in refusing to recognize such transfers, and reclaiming the addresses involved for independent reallocation. However, even if ARIN et al. do choose to allow private address trading the only actual property involved is the IP registrar's self-ownership in voluntarily publishing address allocation charts recognizing those trades. The addresses themselves are not owned by anyone.

      --
      "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
    5. Re:Why so much regulation? by rs79 · · Score: 1

      The obvious solution of course, is cooperation. Take network nnn. for example where nnn is the first octet of an non-swamp space ip. everybody in nnn cooperates, deployes as one big network and only they need to rout within nnn. Everybody else just goes "oh, nnn. is over there throw the packet that way" and the global routing table shrinks for each value of nnn that does this.

      this is easier for some values of nnn. than others :-)

      and it really hurts the long haul telcos.

      --
      Need Mercedes parts ?
    6. Re:Why so much regulation? by jonbryce · · Score: 1

      But then you will have speculators holding onto IP addresses just to make money out of them and not actually using them. This could easily be the next speculative bubble.

  15. Never! by PPH · · Score: 1

    They can pry 127.0.0.1 out of by cold, dead hands!

    --
    Have gnu, will travel.
    1. Re:Never! by Tony+Hoyle · · Score: 1

      Here, have a ::1

    2. Re:Never! by Anonymous Coward · · Score: 0

      They can pry 127.0.0.1 out of by cold, dead hands!

      If that's what it takes... so be it. Starting LOIC... targeting 127.0.0.1... Fire! ,DKJF***NO CARRIER

    3. Re:Never! by PPH · · Score: 1

      targeting 127.0.0.1

      Ha! Fooled you! I'm really at mouse-potato.com.

      --
      Have gnu, will travel.
  16. Yes, we do by Anonymous Coward · · Score: 1

    I'm chief technical engineer for a large ISP in Europe. Posting anon because this need not be correlated to my employer.

    We replace all network hardware every two years. Everything. Yes, you read that right, everything. Some equipment even sooner. Really.

    It costs more to maintain the older hardware than buy new gear and get more energy efficiency, more connections per rack, more customers per square foot of data center.

    If you really think a five year cycle is OK, then you're way, way behind the curve and your customers should really migrate to another service provider. Or you are in an area without competition perhaps.

    Spend a bit of money to reap in the big bucks. And boy, do we reap in the bucks, you wouldn't believe it...

    1. Re:Yes, we do by Anonymous Coward · · Score: 0

      Hahahaha. 10/10. Good troll.

    2. Re:Yes, we do by Splab · · Score: 1

      So all your customers have to reinstall their modems every second year?

      Personally I have no opinion about either 5 year cycle or ip v. 6 - it's not my department, I'm just saying that the router chugging along at home is IPv4 and it will be dead before my ISP is upgrading it.

      Oh and I call bullshit on your claim. I happen to work with some big ISPs in Europe and they are only upgrading when old stuff gives up - or once in a while - when they close a datacenter and centralize. Generally nothing gets upgraded unless needed.

    3. Re:Yes, we do by j+h+woodyatt · · Score: 1

      So, the good news for you must be that with the Internet filling up, you won't have to keep growing so fast and you can stop buying new equipment every two years.

      --
      jhw
  17. Sure.... by Anonymous Coward · · Score: 0

    I'll give a hint. Think of a large ISP in Europe that has an net profit of over a billion per quarter. Google the guy responsible for infrastructure. Give me a call during local business hours.

    1. Re:Sure.... by Anonymous Coward · · Score: 0

      Trying too hard now. 3/10.

    2. Re:Sure.... by Anonymous Coward · · Score: 0

      I know I can't satisfy anon without complete exposure, but I just can't do that for obvious reasons.

      You'll have to take my word for it or choose to disbelieve. Your choice. It's out of my hands.

      You're still welcome to give me a call on Monday.

    3. Re:Sure.... by Anonymous Coward · · Score: 0

      Yawn. 0/10.

    4. Re:Sure.... by Anonymous Coward · · Score: 0

      I admire your troll/counter-troll skills.

      If there was anything I could give you I would, but I can't. That's the way things are.

      You win this one, as I have to default. Nicely done. Well played. I have nothing more.

      It's a shame you're anon, although I do understand I can't hardly complain.

    5. Re:Sure.... by yuhong · · Score: 1

      I know I can't satisfy anon without complete exposure, but I just can't do that for obvious reasons.

      Yea, I know. Best things IMO to fix the problem if you can. What is the problem BTW?
      Anyway, I agree that calling you a troll based on that is extremely silly.

  18. Ya not so much actually by Sycraft-fu · · Score: 5, Insightful

    I work at a university which is an ISP, as most universities are. We are still using Cisco 6500s from about 10 years ago, and will continue to use those 6500s for some time. They are actually upgrading a few of the core routers soon, but basically only because the central network guys want new toys to play with, the 6500s work fine. Despite the massive increase in campus bandwidth, those 6500s work just fine. We'd probably have to move to something bigger than 10gbit connections to buildings (which we are actually just moving to now) before they wouldn't.

    Now the 6500s are flexible platforms, and you can buy new supervisors to do IPv6. We actually did this a couple years ago... At a cost of about $10,000,000. That is just to serve the 50,000ish users on campus. Also that is only the big core equipment. The edge equipment didn't have to be upgraded since it is all switched at that point.

    This idea that ISPs just trash tons of high end equipment every year is stupid. High end stuff doesn't get replaced until it is necessary, and that can be a long, long time. If you want them to buy all new hardware yearly, well then be prepared for your bill to go way up.

    Also, that isn't the only problem. IPv6 support is not good at all in the home. A lot of routers don't support IPv6. I bought a Linksys router/WAP about a year ago, one of the N ones even, no IPv6 support. So if my ISP went all v6 I'd have to rebuy it and you know people would be mad about that. Even computers are problematic. There's a lot of XP systems out there and it has no IPv6 support. Sure it can be installed, you really thing a non-technical user can handle that?

    Before IPv6 is feasible we not only need more ISP upgrades, we need more upgrades at home. Also, we really aren't going to need a good 4-to-6 setup. We need some way in the home that old devices that don't support v6 and can't be upgraded can get a v4 address that can then be routed transparently through the connection's v6 address. If that exists, I've not seen it.

    It is a complex issue, and hence not something that will get solved quickly. I don't think we'll really start seeing IPv6 adoption in a big way for several more years. Once device support is far more wide spread, and more network equipment has been upgraded, it'll be more feasible. Also, when IPv4 really DOES start to deplete, and by that I mean companies start to run out of addresses not just that the top level assignments are gone, then there'll be pressure to make it happen.

    People forget that the "running out" that is spoken of isn't that all addresses will be gone. It is that all available high level blocks will be allocated to regional registrars. They will still have space to allocate, and even when they run out most ISPs will still have space to allocate. It is when the ISPs start running out, that is when we are ACTUALLY running out of IPv4 space in a meaningful way, and there'll be pressure to move to something larger.

    1. Re:Ya not so much actually by Anonymous Coward · · Score: 0

      how many IPv6 compatible supervisors add up to cost $10 million?

      The ISP i work for has 3 6509s with 0 IPv6 support on those.

    2. Re:Ya not so much actually by Anonymous Coward · · Score: 0

      spoke too soon , the SUP720-3B units we have for each 6509 do support IPv6 at a cost of $28,000 each

    3. Re:Ya not so much actually by Anonymous Coward · · Score: 0

      Thanks for your Informative post, and explaining this problem clearly for those who do not understand.

    4. Re:Ya not so much actually by Anonymous Coward · · Score: 0

      Actually, IPv4 routing using IPv6 addresses is part of the capability.

      The low order 32 bits can be an IPv4 address. The router being talked to must then convert between the 128 bit IPv6 address,
      and convert to the 32 bit IPv4. No problem. Just use the low order 32 bits.

    5. Re:Ya not so much actually by kasperd · · Score: 1
      Take a look here http://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xml

      0000::/96 was previously defined as the "IPv4-compatible IPv6 address" prefix. This definition has been deprecated by [RFC4291].

      There is also ::ffff:0:0/96 which is used locally to provide a single API that applications can use to talk IPv4 using IPv6 addresses. But on the network it is still IPv4 with all the restrictions you get from that, the only purpose of this address format is for applications to not have to support both APIs simultaneously.

      --

      Do you care about the security of your wireless mouse?
    6. Re:Ya not so much actually by yuhong · · Score: 1

      Sure it can be installed, you really thing a non-technical user can handle that?

      It is really easy to do using the UI in Network Connections.

    7. Re:Ya not so much actually by saleenS281 · · Score: 1

      $10,000,000 to upgrade sup's? Unless you were upgrading 100+ 6500's (which would make your campus larger than pretty much any major corporation in the US), your campus either sucks at negotiating, or your numbers are more than a bit off. You could buy a fleet of Nexus 7k's fully populated for less than that at LIST price.

    8. Re:Ya not so much actually by Anonymous Coward · · Score: 0

      What is interesting is you won't be able to start a new ISP... easily without being able to acquire v4 addresses. Now we'll have even less competition.

  19. You don't actually control that redirection layer. by Anonymous Coward · · Score: 1

    Unless you personally own a root nameserver, you left out an important detail or two there.

    Nobody finds you by name without the co-operation of the authorities. Nobody.

    Those authorities would have to rewrite BGP from scratch to gain the same level of control over IP addresses.

    I did not sign the paper. I plan to keep ownership of the IPs that Jon Postel personally gave me, and if I sign the paper I will have given up that ownership. Fuck that. As the level of authoritarianism and media control continues to ramp up, my property rights become more and more valuable. The Nazis want 'em? Either buy them or take them, I will never give them up willingly. I'm already using them, to the benefit of my fellow human beings.

  20. XP isn't the core problem... by Crazy+Taco · · Score: 1

    Well, XP did come out over 9 years ago. It's not that surprising it didn't have good support (not much back then did). And by the time the core infrastructure is ready for IPv6, everyone will for the most part have switched to Windows 7, or at the least Vista. So I don't think XP is the core issue holding up the migration.

    --
    Beware of bugs in the above code; I have only proved it correct, not tried it.
  21. But why don't the ISPs do more? by Crazy+Taco · · Score: 1

    It's not like the ISPs are doing it just to piss you off.

    No, they aren't doing it just to make us mad, but they could be doing a whole lot more. ISPs are probably the biggest end buyers of consumer level wireless routers. Maybe I'm wrong about that, but they have to be a big chunk because so many consumers don't know how to set them up and therefore rent modems and wireless routers from the ISP. They have to be a relatively big bulk buyer. They could insist that no one gets the contract for new purchases unless they provide IPv6 capability on the home devices. That way the ISPs could upgrade all their renters, and they could tell everyone else that come such and such a date, they won't support non-IPv6 devices. And the ISPs could also negotiate a contract for massive bulk discounts on one or two varieties of home routers and sell them to consumers at cost, which would get the rest of their clients to upgrade. I mean, most people aren't going to completely panic over a one time cost of 30 bucks to replace their home router. It wouldn't be fun, but if you sell them on the idea with some good marketing about how it benfits them (like DTV did), you could probably get them on board.

    And the better home routers already have IPv6 support, especially those that can run DDWRT, so those users that bought expensive dual band n routers probably wouldn't have to upgrade at all.

    --
    Beware of bugs in the above code; I have only proved it correct, not tried it.
  22. Also, some home routers do support IPv6 by Crazy+Taco · · Score: 1

    And the better home routers already have IPv6 support, especially those that can run DDWRT, so those users that bought expensive dual band n routers probably wouldn't have to upgrade at all.

    And just to pre-empt anyone who argues it is too difficult for a non-geek to flash DDWRT onto a home router, remember that all Buffalo routers come with DDWRT as the factory default firmware, so actually you don't have to flash anything to get a home router with DDWRT and IPv6.

    --
    Beware of bugs in the above code; I have only proved it correct, not tried it.
    1. Re:Also, some home routers do support IPv6 by bbn · · Score: 1

      And just to pre-empt anyone who argues it is too difficult for a non-geek to flash DDWRT onto a home router, remember that all Buffalo routers come with DDWRT as the factory default firmware, so actually you don't have to flash anything to get a home router with DDWRT and IPv6.

      Only thing is that IPv6 support in DD-WRT sucks. I know, I am using it.

      On my office network I got a tunnel til HE. The tunnel setup works, but the RADVD config is broken, so I had to do it manually. It is not something the average John Doe would have accomplished.

      On my home network the ISP actually provides me with native IPv6. There is ZERO support for that in DD-WRT. Nothing. Zip. I made it work by using custom commands in the startup scripts and cheating a lot (how do you make a DHCP6-PD prefix request with no dhcp6 client?).

  23. Home Router Support exists by Crazy+Taco · · Score: 1

    almost no home router supports IPv6

    That's much less true these days. Buffalo routers ship with DDWRT as the factory installed firmware, and that means they all support IPv6. I'm sure they aren't the only ones that do this. And at any rate, if ISPs would start renting out Buffalo routers to customers they would soon have IPv6 capable equipment on a lot of their networks.

    --
    Beware of bugs in the above code; I have only proved it correct, not tried it.
    1. Re:Home Router Support exists by zach_the_lizard · · Score: 2

      IIRC, DD-WRT removed ipv6 support in some builds so they could cram in other features like...RIPv2. My Linksys router has no v6 support with DDWRT.

      --
      SSC
  24. Money, money, money by vlueboy · · Score: 1

    IPv4 managers: "Hey, guys, first come first served, and there's little left. Start worrying!"
    IP buyers: "AS IF!!! This affects the suckers coming in last place! My v4 internet won't just go poof! It's like the cockroach, the VGA port, the ball-mouse and the 4:3 TVs people got 10 years ago"

    When IPv6 legislation worldwide exists to do onto IPv4 what in USA digital TV legislation did to our trusty analog TVs here, we'll see a real deadline. Speaking IPv6 is like speaking Esperanto: cool if you do, but not useful enough for profit next to de-facto languages.

    Stuff like IPv6 non-support is what happens when the media fails to use the irrational madness they pushed behind our Y2K Apocalypse. "Banks will crash, MONEY will disappear" "Retirement benefit spreadsheets will fail, MONEY will disappear" and "Nukes will be launched ... reactors will melt down ... radioactivity will KILL; AND your MONEY won't be worth a thing in this apocalypse."

  25. Lame designs by Ruler4You · · Score: 1

    IMHBLO, the "upgrade" process is really a systemic institutionalized design for obsolescence built right into the entire 'technology' field. I've worked at some BIG names in "technology" for the last 20 years as we watched our economy change over to a technology based economy from a manufacturing economy. Granted, semiconductors are 'manufactured' but few can afford to build a Fab, especially in the U.S. Technology is a 'transition' industry. Where it leads I'm not sure of, but to have and allow (from day one) so many holes in that technology and the code that operates it indicates the industry has no intentions of "securing" it's "proprietary technology" or "code", maybe for ever but at least until it gets to the "final" solution, what ever that is.

  26. Not an option for us. by Suzuran · · Score: 1

    This isn't an option for us. We qualified for address space under ARIN's old rules, and as such, we own a directly allocated IPv4 /24. The requirements for IPv6 space are higher, and we don't qualify for an allocation. If we give up our IPv4 /24 we get nothing for it, we'll be at the mercy of our ISP for address space, and that will make it impossible for me to add redundant uplinks later.

    With this stuff in mind, I intend to defend my IPv4 allocation until such time as ARIN forcibly reclaims it.

    1. Re:Not an option for us. by DarkKnightRadick · · Score: 0

      Are you seriously that stuck on IPv4? How are the requirements for IPv6 space higher? How could you not qualify for an allocation? And who is "us"?

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    2. Re:Not an option for us. by Suzuran · · Score: 1

      "Us" means my employer, of which I am one of the founding employees. We don't qualify for an IPv6 allocation because the minimum IPv6 allocation size is larger than what used to be the minimum IPv4 allocation, and is far beyond our needs. We would not be able to justify the usage of an entire block, so ARIN won't give us one. (Which is good; We don't need that much space.) So I am not necessarily attached to my IPv4 block because it is IPv4, I am attached to it because it is mine.

      Since this is Slashdot, we'll use a car analogy: Assume that you have bought a new car, and shortly after your purchase, someone decides that the roads are too crowded and everyone who has less than 4 friends must ride a bus. Cars are now reserved for people who can fill all of the seats all of the time. Everyone who rides a bus must be going to places approved by the bus owners at times approved by the bus owners. Any travel otherwise is forbidden, unless you are taking a large group with you. Since I use my car to do my job, and the bus owners are very unlikely to accommodate my business needs aboard their bus, giving it up means I lose my job. So even though it's in the best interest of everyone else that I fall upon my sword and commit suicide so they can declutter the roads, I am too big of a chicken to become an hero, and I will selfishly hang on to my car until such time as someone comes to kill me and take it.

  27. Give me the money, then. by Hasai · · Score: 1

    [Bitter rant]
    Fine; you pony-up the cash I'll need to R&R all the stuff in my network that still doesn't bother to support IPv6. And while you're at it, how about coughing-up some funds so I can just get basic maintenance done?
    Go back to your Playstation, kid.
    [/Bitter rant.]

    --

    Regards;

    Hasai

  28. $200 Billion Ripoff by xiux · · Score: 1
  29. IPv6 is important. by Stween · · Score: 1

    Every time this discussion comes up, people fail to see the significance of IPv4 running out. It's 2010, and folks still get confused.

    The significance is this: There are massive growth regions in the world that will only be able to purchase IPv6 addresses within the next year or two. And if you aren't playing the IPv6 game, then you're shutting you and your customers off from all those various markets that will open up in years to come.

    There's only so much can be squeezed out of IPv4. But regardless of how much can be squeezed out of the existing space, the regional registries are likely to run out of /24's they can allocate within a year. See for a guesstimate: http://www.potaroo.net/tools/ipv4/index.html That is, in 2012, much expansion in growth regions WILL be IPv6 only.

    You're shooting yourself in the foot if you refuse to bring yourself up to date.

    1. Re:IPv6 is important. by rs79 · · Score: 1

      The counter argument is those v6 only networks just *might* want to talk to things like, oh, paypal, cracked.com and ten gazillion other v4 only sites. So they will have v4 connectivity - or else they really can't see most of the net.

      So I wouldn't worry about having a v4 only network.

      And, the newest fantasies for making v6 interoperate really require v4 addresses, which suddenly become very valuable. This is another reason ARIN wants them back.

      Also, have a look at the form 990s for the arin poeple. they make one hell of a lot of money... for doing what exacly?

      --
      Need Mercedes parts ?
    2. Re:IPv6 is important. by j+h+woodyatt · · Score: 1

      Which is why many of the big content providers are doing engineering trials of dual-stack IPv4/IPv6 service, i.e. they want to be able to reach those IPv6-only subscribers. The content providers who aren't doing that will be replaced by native and local content providers who will.

      --
      jhw
  30. Nobody should own more than /24 by George_Ou · · Score: 1

    It's ridiculous that companies own more than a /24 (256 IP addresses) since they're not using it for public visibility. Even a web site can mask thousands of servers behind a single IP. If they have multiple sites, let them have a /24 per site. This business of letting companies use multiple /16 or /8 (that's 16.8 million IPs) for private networks is ridiculous.

    People who say "just switch to IPv6" simply don't get it. The reason is that even after you "switch", you really haven't switched at all because you still have to have backward compatibility. So what's the point of adding IPv6 when you still have to fully support IPv4 to reach the remaining 99.9% of the Internet? At the end of the day, we're still going to run IPv4 for the next decade or more which is why nobody in the real world cares about IPv6. If it was truly a switch over, then fine. But nobody is fooled into believing it's anything but some type of dual-stack for the foreseeable future.

    We would all be better off if we made more efficient use of IPv4. We'll have to do that anyway even if we do switch to IPv6 (which won't happen) because of the need for backward compatibility.

    1. Re:Nobody should own more than /24 by lseltzer · · Score: 1

      What are ARIN's contractual obligations for address ranges they have allocated? Can they just decide to give notice that addresses will be rescinded?

    2. Re:Nobody should own more than /24 by George_Ou · · Score: 1

      That is an interesting question. I don't know.

    3. Re:Nobody should own more than /24 by kju · · Score: 1

      It's ridiculous that companies own more than a /24 (256 IP addresses) since they're not using it for public visibility.

      This is really a utterly stupid comment. Have you ever heard about companies in the so called ISP business? I'm very sure that you are using the services of one of these companies. Did it occur to you that this company might have more than say 250 customers?

    4. Re:Nobody should own more than /24 by JesseMcDonald · · Score: 1

      Even if they could do that without violating any contracts, they still have to consider the diplomatic ramifications of that sort of unilateral action. No one is obligated to turn to ARIN for IP addresses; ARIN has the authority it does only because people need someone to allocate routable Internet addresses, and ARIN currently fulfills that role. Switching to someone else would carry a high cost, to be sure, but were ARIN to annoy enough well-placed organizations by rescinding their addresses it could become a realistic possibility.

      --
      "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
    5. Re:Nobody should own more than /24 by that+IT+girl · · Score: 1

      And in other news, 640K ought to be enough for anybody.

      --
      10 FILL MUG WITH COFFEE
      20 DRINK COFFEE
      30 GOTO 10
    6. Re:Nobody should own more than /24 by jonbryce · · Score: 1

      He means people like the Ford Motor Company. They should be getting a handful of IP addresses from their ISPs at their various sites around the world, not an entire /8.

  31. Just let it work itself out by Anonymous Coward · · Score: 0

    I like when they run out of IPv4 just start handing out IPv6 and let them worry about the upgrades. It'll fix itself.

  32. Seriously? Seriously! by bananaendian · · Score: 1

    It isn't just hardware that is the problem. Have a look at support forums for Windows Server 2008 R2 for example. The amount of problems there are at getting IPv6 working 'seamlessly' at every level and service in mixed network environment is a nightmare. The dual IPv4/IPv6 implementations for network interfaces and services are full of riddles and holes. No wonder even Microsoft's own engineers propose 'solutions' like "turn off IPv6". Well that is actually what every admin I know who has struggled with 2K8R2 has done. As long as you don't 'need' IPv6 for anything yet, why bother. There is enough other shit to shovel meanwhile - we'll deal with it when it comes.

    --
    www.tribalnetworks.org - helping tribal people around the world to own their own means of high-tech communications
  33. I never said ISPs by George_Ou · · Score: 1

    I mean individual companies. An ISP should selling to multiple companies is different. Of course there would still be exceptions of an individual company needed more than 256 per site. My point is that most of these legacy companies are sitting on blocks of 65K or 16.8M addresses and they're using it as an internal IP scheme. That's the problem I have.

  34. Easy way to fix all this by Anonymous Coward · · Score: 1

    Google should just announce that in six months, some class of Google content will appear on IPv6 only. Start with "all new Youtube videos will be cut off at 5 minutes on IPv4, or will go full length on IPv6."

    With that one move, every ISP in the world will be forced to finally, immediately do what they were supposed to already, and go IPv6.

    Meanwhile consumers will demand IPv6 Routers. Those with routers upgradeable to DD-WRT can just do the firmware switch.

    Router firms can do a massive IPv6 firmware rollout, and IP consultants will have a field day.

    Let's get this done.

  35. ARIN can drop dead by Joe+U · · Score: 1

    I wouldn't mind selling one of the Class C's I still have. I don't think I ever signed an agreement saying I wouldn't back in 1994 with the Nic. And honestly, I don't give a fuck what ARIN says, they can't revoke them without permission. If they contact me, I'm not granting it, and I have no wish to sign an agreement with them.

    Yes, one of my class C's is still live, although now unrouted and behind NAT. (The other one is in a test lab, which isn't a huge deal to change)

    Basically, ARIN, start seizing these at your own class-action peril.

    1. Re:ARIN can drop dead by rs79 · · Score: 1

      You aint alone, bub. Anybody else with an allocation going that far back will have at least, your attitude.

      --
      Need Mercedes parts ?
  36. So, by Anonymous Coward · · Score: 0

    What you all are tiring to say is .. well .. we're all screwed?

  37. Efficient Use, Transition, Replacement by bearded_oneder · · Score: 1

    As with any finite resource, management strategies typically follow the course of more efficient use, bridge transition to a more plentiful resource, and finally adoption of the new resource.

    IPv4 will be no different. Unused addresses or public addresses used on private equipment WILL BE reclaimed - albeit not without some nasty fights. Four to Six gateways and ISP NATs will stretch the resources a bit more. Finally, IPv6 will be gradually adopted at a pace that is not a financial shock to the big players.

    Along the way, power brokers and power hoarders will try to exploit the situation for greater control of the internet or segments thereof.

  38. Efficient Use, Transition, Replacement by bearded_oneder · · Score: 1

    As with any finite resource, management strategies typically follow the course of: more efficient use, bridge transition to a more plentiful resource, and gradual adoption of the new resource. There is nothing you can do to thwart or change that reality unless you have the charisma to foment a revolution or you're grotesquely rich and powerful.

    IPv4 will be no different. Unused addresses or public addresses used on private equipment WILL BE reclaimed - albeit not without some nasty fights. Four to Six gateways and ISP NATs will stretch the resources a bit more. Finally, IPv6 will be gradually adopted at a pace that is not a financial shock to the big players.

    Along the way, power brokers and power hoarders will try to exploit the situation for greater control of the internet or segments thereof.