Slashdot Mirror


The Impending IP Crisis

Factomatic writes "With the supply of IP addresses expected to run out by 2005 due to the popularity explosion of the Internet and the expectation that everything from your phone to your washing machine will soon have its own IP address, Alex Lightman, CEO of Charmed Technology and chairman of last month's North American IPv6 Global Summit tells the New York Times "we're going to need something like 100 IP addresses for each human being." IPv6 will increase the supply of addresses from 4 billion today to a number in excess of 35 trillion that is "so big that there's not a word for the number," says Cody Christman, director of product engineering for Verio, which offers IPv6 in San Francisco, Washington and elsewhere. The article is a good layman's backgrounder on the looming IP crisis."

765 comments

  1. Imminent death of IPv4 predicted!! by krog · · Score: 2, Interesting

    Great, another "we're running out of IPs, really, for real this time guys we mean it" story. I mean, sure, IPv6 will eradicate this problem (while introducing a slew of new ones) but IPv4 is fine for a while. We should just revoke the IPs for China and other firewalled nations who dont' play nice with DARPAnet.

    1. Re:Imminent death of IPv4 predicted!! by BWJones · · Score: 2, Funny

      Don't forget the spammers. We can take a few IPs away from them as well.

      --
      Visit Jonesblog and say hello.
    2. Re:Imminent death of IPv4 predicted!! by operagost · · Score: 2, Funny

      Hey, if all of China is behind a firewall anyway, that should work. Just give them one public IP and let them put the rest of the nation behind 10.x.x.x and 172.16.x.x.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    3. Re:Imminent death of IPv4 predicted!! by Jeremiah+Cornelius · · Score: 2, Funny
      The number of spammer's IP's are relatively insignificant...

      A possibility of success for SCO would see the resultant world-wide demand for IP addresses drop to a manageable level: Somewhere's about a hundred and seven, or so...

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    4. Re:Imminent death of IPv4 predicted!! by Troed · · Score: 5, Insightful

      No, we should withdraw all the A-class networks that are unnecessarily allocated to US companies.

      OTH - I'd rather move to IPv6.

    5. Re:Imminent death of IPv4 predicted!! by The+Spoonman · · Score: 2, Insightful

      Agreed. In the last 5 companies I was an administrator, only one had public IPs on their machines. The company had bought a couple of class-Cs a few years back...then put them behind a natting firewall (no wonder they needed a new admin). There are very few reasons any company would need more than one or two public IPs. Okay, much larger companies will need more to cover a large range of campuses, but since the vast majority of companies are small/medium size (under 1000 employees), they're rare. As for phones needing a public IP, why? Hell, there's really no reason an ISP needs to give out public IPs, either. Well, maybe one: customers who have need of a VPN w/ their company. No problem, a lot of broadband ISPs already charge extra for the "right" to use this type of technology, force the issue by paying a little extra for an IP. It would also cut down on viruses and worms a little, as those machines can only really be hacked by people behind the same firewall now.

      Okay, that was a bit of a ramblin' rant, but this really pisses me off. I'm tired of hearing how we're running out of addresses when the simple solution is to stop friggin' using them!

      --
      Which is more painful? Going to work or gouging your eye out with a spoon? Find out!
      http://www.workorspoon.com
    6. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      This is just another way for the government to control you!

      Don't give in!

    7. Re:Imminent death of IPv4 predicted!! by VPN3000 · · Score: 3, Interesting

      I don't see this as being much of a crisis. I've worked for several companies that employ ~10,000 people, most of which have systems connected to the network.

      I remember in 1995, every Windows box had it's own public facing IP. Then over the years, everyone who could use NAT was moved over to private IP space.

      The 'crisis' is really another example of media fear-inducing hype. Worst case senario, your ISP will begin issuing private IPs for for customers with basic accounts.

      Yes, some things will break. But there's not much out there that doesn't function in a NAT enviroment from a client standpoint.

      It'd also save ISPs a lot of headache with customers running unauthorized services.

      I can already see the call to tech support..

      customer "My web server/P2P/Warez FTP/etc doesn't work now that you changed my account to use a private IP."

      ISP "Well, sir. You can upgrade to a business class account and get a static, public IP address."

      customer "DOH."

      I don't know about restricting the usage of IPs in countries that the US has a political agenda against. That would seem to defeat the whole idea behind the Internet. At least, that idea that was lost when Ebay and Amazon started suing everyone under the sun. It would keeps us going for a while longer, but I can see the NAT thing happen before that.

      Personally, I would like to see one of the educational networks grow to a decent size and allow commoners onto their network with the restriction of no commercial activity. How I miss visiting Usenet and content outnumbering SPAM.

      Also, doesn't Mercedes and a bunch of other companies that don't need an excessive number of IPs still have their own Class A? I know when I worked at an ISP that gobbled up a bunch of other companies in the late 90's, they were forced to hand over tons and tons of IP addresses because they could not prove they were actually being used for anything useful. That's what I was told, mind you I could see something underhanded going on since public IPs are quite a commodity these days.

    8. Re:Imminent death of IPv4 predicted!! by ShaiHulud-23 · · Score: 1

      Don't forget the spammers. We can take a few IPs away from them as well.

      Most spam seems to be routing through China these days anyway. Birds, meet stone.

    9. Re:Imminent death of IPv4 predicted!! by Ian+Jefferies · · Score: 3, Funny

      Okay, that was a bit of a ramblin' rant, but this really pisses me off. I'm tired of hearing how we're running out of addresses when the simple solution is to stop friggin' using them!

      Would the last person to leave the Internet please turn off the routers?

      --
      A physicist is an atom's way of thinking about atoms
    10. Re:Imminent death of IPv4 predicted!! by Tackhead · · Score: 4, Interesting
      > The 'crisis' is really another example of media fear-inducing hype. Worst case senario, your ISP will begin issuing private IPs for for customers with basic accounts.
      > Yes, some things will break. But there's not much out there that doesn't function in a NAT enviroment from a client standpoint.
      > It'd also save ISPs a lot of headache with customers running unauthorized services.

      *applause*

      Port 25 filtering would finally make sense - no more luzers with open exploitable proxies spewing bilge from attbi.com, rr.com, pacbell.net, comcast.net, and so on.

      Add to that the possibility of doing ingress filtering, and you've got something that wouldn't just be less expensive for tech support, but a little safer for Joe Luser, whose unpatched box would be on a private subnet.

      If the skript kiddie can't talk to port 135, 137, 138, 139, 445, or 1900 of Joe's box, he's gonna have a harder time 0wning him.

    11. Re:Imminent death of IPv4 predicted!! by Cheeko · · Score: 2, Interesting

      You mean like HP which now has two Class A's (HP and DEC) and a couple of class C's from the combine companies.

    12. Re:Imminent death of IPv4 predicted!! by aldoman · · Score: 3, Funny

      Uh, this would break a lot of other stuff aswell.

      IM file transfers : broke
      Video Confrencing: broke
      voice over IP: broke
      host a game (on xbox live for example): broke

      now, i dont know about you but most of the people do one of the above things regually. IM has latley became the killer app of the internet (for the younger people).

      This would reduce the internet to one way communication - something that I dont want.

    13. Re:Imminent death of IPv4 predicted!! by AndroSyn · · Score: 4, Insightful

      I disagree. Using unique IP addresses whenever possible is the way the internet is supposed to work. This NAT stuff is just an awful, awful hideous hack. The correct solution is IPv6, not NAT ourselves forwards and backwards.

    14. Re:Imminent death of IPv4 predicted!! by Suidae · · Score: 0, Interesting

      we should withdraw all the A-class networks that are unnecessarily allocated to US companies.

      And EDU's too. There are many universities with many tens of thousands of IP addresses, most of which are unused. One I know of has at least one class A, a couple B's and several C's, and they have a grand total of about 6800 addresses in use.

      I agree that there are a number of protocols that these places use that simply cannot be NATed, but IMO they need to quit catering to these broken-ass apps, NAT the system and tell the users to get software that plays nice.

      We would have plenty of IP addresses for then next decade or so huge chunks weren't being wasted like this.

    15. Re:Imminent death of IPv4 predicted!! by NecroMancer · · Score: 2, Insightful

      IMHO, NAT would almost be completely unnecessary if the IP space was better used. All registries have such statistics, just check for yourselves in the APNIC, ARIN, RIPE, and others...

      Nevertheless, there is so much you can (NOT!) do with NAT, especially peer-to-peer and applications that use UDP.

    16. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      > It'd also save ISPs a lot of headache with customers running unauthorized services.

      And tell me what makes for an unauthorized service... my isp EXPLICITLY allows running servers, and actually, to make the internet usefull, it is none of the ISPs business what you use it for.

      Then, if you actually read the article (gasp, idiotic idea, I know) you'd have read about the fact that people are connecting more and more stuff to the net.

      The ONLY situation where it makes any sense for me to connect my microwave to the internet is where it also allows me to program it using my palmtop wherever I am, that simply requires it to be reachable in one way or another. Is it really upto ISPs to tell me if I can do that or not? Thats a stupd moronic idea really, do you want to go back to the days that phone companies could tell what you could connect to their network or such? go get a fucking clue.

      Then last but not least for all the fans of NATting... its not just broken applications that don't work, something like ipsec doesn't work either. NAT has a few big advantages, but is far from the solution for this problem.

    17. Re:Imminent death of IPv4 predicted!! by dissy · · Score: 1

      > No, we should withdraw all the A-class networks that are unnecessarily allocated
      > to US companies.

      Why dont we just allocate the 1.3rd of our A classes that arnt assigned?

      OH, thats right, people want everythng for free and wont pay for it.

      So, instead of paying for IP space that is unused, youd rather see used and paid for Ip space being yanked away from companys to be given away for free id imagine to the people bitching and whining that we are out of IPs.

      Great plan there comrad!

    18. Re:Imminent death of IPv4 predicted!! by The+Spoonman · · Score: 4, Insightful

      In a way, we're not talking about the Internet here. We're talking about a company's, or even an ISP's, private network which also has access to the Internet. Giving those machines puplic IPs is not only a waste of address space, but a security risk. Those that need to access the Internet don't need public IPs. Those that need the Internet to access them, do. Forcing the world into a MAJOR move to IP6 just because you consider NAT a "hack" is unreasonable. NAT works, and works well. There's nothing I can't do behind NAT that I can't do with a public IP (including VPN, that's just easier with a public). The correct solution is to not give Nancy-in-accounting's printer a public IP, or worse, have to force accounting to upgrade that printer because its hardware doesn't support IP6.

      Shame on you for suggesting otherwise.

      --
      Which is more painful? Going to work or gouging your eye out with a spoon? Find out!
      http://www.workorspoon.com
    19. Re:Imminent death of IPv4 predicted!! by The+Spoonman · · Score: 2, Funny

      especially peer-to-peer

      Really? Huh and all this time I've been grabbing and sharing off of Kazaa on my machine behind a NAT router. Silly me, I must've imagined all that porn I downloaded. Man, do *I* have a sick imagination! :)

      --
      Which is more painful? Going to work or gouging your eye out with a spoon? Find out!
      http://www.workorspoon.com
    20. Re:Imminent death of IPv4 predicted!! by Electrum · · Score: 2, Insightful

      I agree that there are a number of protocols that these places use that simply cannot be NATed, but IMO they need to quit catering to these broken-ass apps, NAT the system and tell the users to get software that plays nice.

      You're right, let's get rid of all games.

    21. Re:Imminent death of IPv4 predicted!! by Electrum · · Score: 2, Insightful

      Hell, there's really no reason an ISP needs to give out public IPs, either.

      Because no one plays games online, right?

    22. Re:Imminent death of IPv4 predicted!! by Electrum · · Score: 3, Funny

      I can already see the call to tech support..

      customer "My web server/P2P/Warez FTP/etc doesn't work now that you changed my account to use a private IP."


      Customer: "Why can't I play games online anymore?"

      Consider an RTS game such as Starcraft. If you and your friend both have a private IP, you can't play. NAT is not a good solution.

    23. Re:Imminent death of IPv4 predicted!! by peccary · · Score: 4, Insightful

      What? "broken"?? My god, referring to the correct, as-designed intended use of the protocol as BROKEN!

      I know, let's just forget about Host Requirements, and about a richly-interconnected fully-reachable peer-to-peer network. That old Internet stuff is just "broken". Let's build us a hierarchical circuit-switched network, and then appoint a monopoly to manage it!

    24. Re:Imminent death of IPv4 predicted!! by FauxPasIII · · Score: 1

      > NAT works, and works well.

      As a CS professor of mine once said, "In theory, theory and practice are the same; in practice, they are not."

      NAT works terrifically in theory. In practice, lots of things you would want to do are horribly borked. There's a reason why any protocol more complex than one or two simple pipes totally craps itself between NATted hosts. While we admins tend to bitch at the protocols themselves (netmeeting, NFS) there's no limitation in the IP spec that says they should keep it to one unidirectional TCP pipe... NAT imposes that unique limitation.

      --
      25% Funny, 25% Insightful, 25% Informative, 25% Troll
    25. Re:Imminent death of IPv4 predicted!! by cshark · · Score: 1

      Is it 2005 now? I thought we were running out in 2003! Oh no, that's this year, er, it was five years ago. I'll believe it when I see it, and if this article holds true, we should see it long before IP 6 is implemented. Or maybe we'll just push it back again. I'm not holding my breath.

      --

      This signature has Super Cow Powers

    26. Re:Imminent death of IPv4 predicted!! by The+Spoonman · · Score: 1

      I play games online. :) But, I see what you're saying, game servers. Okay, but if that's the reason to move, too bad. "Boss, we need to spend the next few months and a ton of money upgrading every machine to IP6 'cause the gamers can't get to their servers."

      --
      Which is more painful? Going to work or gouging your eye out with a spoon? Find out!
      http://www.workorspoon.com
    27. Re:Imminent death of IPv4 predicted!! by stealthyburrito · · Score: 1

      Let's not limit it to /8 address space either. I worked for a rather large company (in it's industry) which had registered 127 Class C networks. We only used about 6 public IP addresses out of ~32,000 available (2000 hosts using hide NAT). I suspect there are thousands of companies out there like that could just as easily use RFC1918's and sell back the surplus networks.

      -SB

    28. Re:Imminent death of IPv4 predicted!! by Pii · · Score: 1
      But NAT is here and now, and enjoys very wide usage.

      Who in their right mind would develop an application in this day and age that could not be made to work in a NAT'd environment?

      I mean, if a tire manufacturer introduced a new tire line today that didn't work on asphalt, would you be blaming the paving crew?

      Most roads are made of asphalt. Most network environments make use of NAT. That's the lay of the land. Application developers are foolish not to accept that reality, and for failing to build their products in such a way that they may function in a perfectly normal network scenario that they're likely to encounter in the vast majority of their customers' sites.

      --
      For those that would die defending it, Freedom
      has a sweet taste that the protected will never know.
    29. Re:Imminent death of IPv4 predicted!! by William+Baric · · Score: 1

      No, it's the opposite. Question is : how much is an IP address worth? Personnaly, I would gladly pay $5/month for a static IP and I'm pretty sure almost everyone would accept to pay $1/month for one. This mean an IP address is worth at least $1/month. Now tell me... How much companies and universities pay for their IP addresses?

      I'm sure if companies and universities were paying the market price for their IP adresses a lot of problem would be solved.

    30. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      Someone's a bitter X.25 user, aren't they?

    31. Re:Imminent death of IPv4 predicted!! by AndroSyn · · Score: 2, Interesting

      Well see, private networks should still have public addresses. Just because the address space is public doesn't mean that you still don't use firewalls. NAT != firewall nor does it equal security. As for Nancy's printer, it can keep using its IPv4 address, as IPv6 machines can talk to anyways.

      Now consider this, say if your internal networks are using 10.0.0.0/8 for its addresses. What happens when your company merges with another and the networks get integrated and suddenly you realize that the other company you are merging with also uses the same address space. Now suddenly you are faced with the task of renumbering lots and lots of devices, reconfiguring routers, firewalls, servers, printers, etc, etc.

      I'll agree that NAT can be useful given the current situation, but its a hack to put off the fact that we are running out of IP addresses. With IPv4 you can't even assign one address per person in the world.

      Also I noticed in your parent post of having ISPs give their customers private addresses. Consider if internally they number one way themselves, and then customers NAT themselves. You end up going through how many layers of NAT? And what does this solve, other than breaking whole design philosophy of IP in the first place.

      Ever here of fixing the cause rather than the effect?

      Shame on you for wanting to break the Internet.

    32. Re:Imminent death of IPv4 predicted!! by racermd · · Score: 1

      Well said. I'd like to "second" your comment, even thought working through NAT is a terrible PITA. Despite this, I run all of my own systems through a NAT device of some sort, as the single IP is all I really need. Since NAT is here to stay, and rather popular due to broadband carriers' stupid self-imposed limitations ("You only get 1 IP address, and it's from our DHCP server. That's it."), it only makes sense to work the bugs out of the system now. When (not if) IPv6 isn't enough to handle everyone's needs, we'll be looking for yet another solution.

      Here's a possible solution: Every person is assigned a single static IPv6 address that they're able to use for personal, non-profit reasons, just like an apartment building has only a single street address. For the individual systems (apartments), private addresses (unit numbers) are assigned behind the NAT box. It may not be elegant. It may not even be pleasing to work with. But it's a solution that works and won't over-allocate public IP addresses.

      --
      My sources are unreliable, but their information is fascinating. -- Ashleigh Brilliant
    33. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      Ah, but there is a certain infrastructure cost. Replacing RPC protocols with SOAP, for example, is not free.

    34. Re:Imminent death of IPv4 predicted!! by jez9999 · · Score: 3, Insightful

      Sounds to me like one of many Mozilla standards zealot arguments.

      A: Why doesn't Mozilla popup image ALT text as a tooltip?
      B: Because it's not meant to do that, the standard says so.
      A: But nearly every other browser does it!
      B: But the standard doesn't say you should.
      A: But many websites use this functionality anyway!
      B: But the standard doesn't say you should.
      A: These sites are *already using* this functionality! Why are you building a browser that doesn't work properly with a large number of websites, and when implementing this functionality wouldn't hurt anyone, and may even help accessibility??
      B: Because the standard doesn't say you should.
      ad infinitum...

    35. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      Mainly 7 year old games with obsolete designs. Modern ones work fine (as clients) over NAT.

    36. Re:Imminent death of IPv4 predicted!! by William+Baric · · Score: 1

      I'm all for IPv6 but these apps could work behind NAT if they stop relying on specific ports for their connections. And the truth is : it's easier to change a protocol than to change an infrastructure.

    37. Re:Imminent death of IPv4 predicted!! by asdfghjklqwertyuiop · · Score: 2, Insightful

      I agree that there are a number of protocols that these places use that simply cannot be NATed, but IMO they need to quit catering to these broken-ass apps, NAT the system and tell the users to get software that plays nice.

      Um, you have it backwards. There is nothing broken about those apps. They are using the internet the correct way. NAT is breaking them. These places need to quit crippling their users to cater to broken-ass networks.

    38. Re:Imminent death of IPv4 predicted!! by Nurgled · · Score: 3, Insightful

      Hell, there's really no reason an ISP needs to give out public IPs, either.

      NAT works okay when I'm controlling the box doing it. I can hack in special stuff to handle esoteric protocols which expect a public IP.

      If my ISP runs the box doing NAT, there's suddenly a bunch of things I won't be able to do anymore, and I'll promptly switch ISPs to one which will let me use the Internet as it's intended.

    39. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      Comparing IP translation to Javascript standards is a pretty weak comparison.

      In fact, many stateful inspection engines exist and applications like NetMeeting and RPC do bad things which are anethema to other practices, like embedding the real Src ip in the packet. Nevertheless, you can make RPC work through a checkpoint firewall, as well as netmeeting.

      Microsoft invented the entire concept of plug and play protocol to work between linksys routers (and others) with windows xp to address the very fact that applications need to make dynamic translation rules on the fly.

      You may as well throw out IPSEC, GRE and every other encapsulation protocol that makes things work because it wasn't envisioned for IPv4.

    40. Re:Imminent death of IPv4 predicted!! by 4of12 · · Score: 4, Insightful

      I like the idea of lots of IPv6 addresses, enough to provide for ISPs to provide each subscriber with a static IP address.

      Open relay? Source of spam?

      Guess what? When re-connect you get that exact same address that is going to be at the receiving end of irate spam recipients!

      No more evading consequences through the magic of DHCP.

      And, for one-time lusers that change ISPs after each offense, the responsible ISP that has clear identifying information (I had to show a driver's license to get my account) about said spammer can post `em to a blacklist. Irresponsible ISPs can simply have themselves blacklisted wholescale.

      --
      "Provided by the management for your protection."
    41. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0
      "There's nothing I can't do behind NAT that I can't do with a public IP"


      You certainly can't run a service on two servers on the same port behind a NAT, but you can with two adresses, of course.

    42. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      As a former ISP owner, it would have been nice to force users to let us know they wanted to run game servers - and then put a static NAT translation in for them.

      In practice, it was totally unreasonable to implement - even if you put the policy in a EULA - you'd still get irate users calling you bitching that "Unreal won't work" - omitting the fact they were hosting a server, of course.

    43. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      We could simply eliminate the reserved space for IP multicast. That would reclaim some space.

      Imagine what internet radio could accomplish if the net were multicast enabled?

      And before some private corp type jumps up and down and says they use multicast internally, well - hey - get over yourself. Multicast is dead. Get with the program and buy a Microsoft Media Server.

    44. Re:Imminent death of IPv4 predicted!! by Hard_Code · · Score: 2, Insightful

      The Mozilla argument (B) is correct. Your argument should not be "everybody does it" (everybody does lots of shit that sucks too), but "the standard should be UPDATED to require this feature because it enhances usability".

      --

      It's 10 PM. Do you know if you're un-American?
    45. Re:Imminent death of IPv4 predicted!! by jez9999 · · Score: 1

      By arguing for Mozilla to do this, we are effectively asking for the standard to be updated. Many of the Mozilla coders are involved in standards, and they are the stubborn *!&££*! who are preventing this feature from being implemented :-) 'Their way is always best'. Pah.

    46. Re:Imminent death of IPv4 predicted!! by The+Spoonman · · Score: 1

      NAT != firewall

      No, but all it takes is one "genius" to figure out he can acces the whole Internet without the restrictions his company's IT department places on him by just setting up a modem and dialing his ISP. He doesn't understand that he's just opened up the whole network, made even worse so by the fact that all those now-unprotected machines can talk back to the hackers easier.

      What happens when your company merges with another

      I change the address ranges in my DHCP servers and go back to work a couple minutes later.

      You end up going through how many layers of NAT? And what does this solve, other than breaking whole design philosophy of IP in the first place.

      Philosophy tells you there might be a god, not where your packets went. Hardly an issue. I'm currently in the process of upgrading the software on my Linux router. I've got it running on another machine which stands between my personal machine, and the rest of my private network, which is then once again behind another NAT firewall. No problems here. Since I don't personally route every packet that leaves my machine, I couldn't give a flying rat-fuck how it gets to its destination.

      Ever here of fixing the cause rather than the effect?

      Yes, and that's what I'm suggesting. IP6 is just a bandaid, because in 10 years when even my penis has it's own IP address, we'll be back in the same boat. At that time the running gag won't be "they used to believe 640K was enough memory for a computer, then 2 megs, then 512 megs", it'll be "they used to think 100 billion addresses was enough, then 100 google".

      Shame on them for not learning to just not be wasteful.

      --
      Which is more painful? Going to work or gouging your eye out with a spoon? Find out!
      http://www.workorspoon.com
    47. Re:Imminent death of IPv4 predicted!! by Deadbolt · · Score: 1

      Maybe YOUR penis will need only one IPv6 address, but mine will require at least ten. /not funny, so no bonus.

      --
      "Honey, it's not working out; I think we should make our relationship open-source."
    48. Re:Imminent death of IPv4 predicted!! by i_am_nitrogen · · Score: 1

      It's impossible to run out if IPv6 addresses. There are more IPv6 addresses possible than there are particles in the universe! Even if you give everyone on the planet an average of one hundred twenty seven IP addresses you'll still have a lot of space left over. NAT for the purpose of sharing a single "real" IP address is just a neat trick; nothing more. NAT does have uses, but those are in the realm of transparent proxies and the like.

    49. Re:Imminent death of IPv4 predicted!! by realdpk · · Score: 1

      What games won't work with NAT? Out of the last 50 or so networked Windows games I've played, none have had any trouble.

    50. Re:Imminent death of IPv4 predicted!! by OldHawk777 · · Score: 1

      I agree China could get by on one or two internet IP addresses, and just use the public domain 10.X.X.X IP addresses for their private networks. It is what should be done around the world, but ....

      OldHawk777

      --
      Unaccountable leaders are masters, and unrepresented people are slaves. How do US and EU fare?
    51. Re:Imminent death of IPv4 predicted!! by Abalamahalamatandra · · Score: 1

      There may be more possible addresses than atoms, but definitely not routable networks.

      A big part of a reason that we're in the current situation we're in with IPv4 is that DARPA used to love to hand out Class A blocks like candy to anybody that asked.

      Methinks that should provide you with a bit of a clue as to the inaccuracy of your statement.

    52. Re:Imminent death of IPv4 predicted!! by Breakfast+Pants · · Score: 1

      Yes but what you don't realise is you are only grabbing off of people who AREN'T NATed. If you had a direct connnection you could grab from everyone who is behind a NAT and everyone with a direct connection(The only people you are currently grabbing from). A NATed machine can't grab from another NATed machine, in Kazaa at least but also in emule and probaly many others.

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    53. Re:Imminent death of IPv4 predicted!! by The+Spoonman · · Score: 1

      No, but you get extra points for that fantastic sig. Best I've seen today!

      --
      Which is more painful? Going to work or gouging your eye out with a spoon? Find out!
      http://www.workorspoon.com
    54. Re:Imminent death of IPv4 predicted!! by The+Spoonman · · Score: 1

      Sure they can. I do it all the time.

      --
      Which is more painful? Going to work or gouging your eye out with a spoon? Find out!
      http://www.workorspoon.com
    55. Re:Imminent death of IPv4 predicted!! by misleb · · Score: 1
      NAT does work VERY well for corporate users (and admins). It is an artificial limitation on a business to have to assign public IPs for every device on their network. What happens when a company goes over 255 hosts? Should they register for another class C or, God forbid, get a whole new /23 supernet and have to reip their internal network even though not ONE of those hosts needs to be accessible from the internet?

      NAT really only breaks things for home users running silly video protocols or doing IRC/DCC or some game. Fine, give them public IPs for their machines. My DSL provider (Speakeasy) allows me to purchace additional public IPs. I don't think this practice is going to bring the death of IPv4 by 2005. The real problem is businesses that have excessivly large chunks of the public space used on computers that don't need them.

      I heard the argument about two companies merging with conflicting private address space... First of all, what are the chances of this if each one uses a suitably arbitrary (but not overly large) chunk of the private space? Second of all, have you ever heard of DHCP? Jeez.

      In general, I think NAT is a great way to go... as long as the option to have a public IP is always available, like with Speakeasy.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    56. Re:Imminent death of IPv4 predicted!! by ckaminski · · Score: 1


      Great, so now we have port collision. Oh wait, you're going to have to dole out an ARP broadcast so the NAT server can grant you, and only you, that port number.... Hmmm, maybe we'll call it the Dynamic Port Configuration Protocol?
      </sarcasm>

      It's bad enough that I have to share 65,000 ports with my four roommates, who may or may not have a clue, and start a Counterstrike server on the port I'm doing my ssh tunnels on; I cannot imagine the pain and suffering of users and ISP call centers alike, if 200+ customers at a time started doing this.

    57. Re:Imminent death of IPv4 predicted!! by ckaminski · · Score: 1

      All sarcasm aside, you also make a lot of sense with this. There's good reason to research adding "Service Location Protocols" and "Service Publishing" to dynamic dns hosts as extensible fields, say:

      XPORT ckaminski:cstrike[server name]/port

      The problem with your statement is that right now, and for the forseeable future, it's just as unattainable as a total IPv6 changeover. Software has to get into the habit, CORBA like, of announcing itself to the public, and of looking at central directories for information.

      Then the security aspects of this also require intense scrutiny. IPv6 may be more attainable, since it's backwards compatible to IPv4. But your statement bears weight, in that it is the ultimate ideal.

    58. Re:Imminent death of IPv4 predicted!! by DonGar · · Score: 1

      I once wrote a NAT engine (for the obscure Firewall/Plus), and I use NAT at home since I can't seem to bring myself to pay $5/month for a number.

      Regardless, the technology was a bad idea, should never have been implemented, and should never have been allowed to be popular. It's delayed a change that would solve many problems, and gets harder to make the longer we put it off.

      Instead most of the people using them have problems, and have applications that are broken without understanding why.

      Nowadays, many applications are never written because they just won't work in our modern NAT infested internet.

      If we had to have some way to share an IP address SOCKS proxies would have been SUCH a better idea. Your applications (or you IP stack) have to support the proxy, but EVERYTHING works, not just the standard only pull data down stuff.

      --
      plus-good, double-plus-good
    59. Re:Imminent death of IPv4 predicted!! by tez_h · · Score: 4, Funny
      As a CS professor of mine once said, "In theory, theory and practice are the same; in practice, they are not."

      Abuse! Abuse!
      I mean, this could go on forever:

      Poster1(p1): "The word 'theory', in practice, has more meanings than in theory."

      Poster2(p2): "Yes but theory and practice are closer in theory than in practice."

      p1: "I don't want to read your theory about practice; practise your theories!"

      p2: "Bah! Your theory and practice only hold together in theory, not practice."

      p1: "What?! Shove this practice into your theory!"

      p2: "Oh yeah, theory this!"

      p1: "You short, mustachioed, german, national-socialist pig!"

      p2: "Godwin's law! Godwin's law!"

      etc, etc, etc.

      <yawn>

      -Tez

      --
      Haskell, the static-typed, lazy, polymorphic, programming language.
    60. Re:Imminent death of IPv4 predicted!! by Bakaneko · · Score: 1

      I've thought about this, and the realization I came to is that somebody just needs to invent a plug-in system for NAT firewalls. Something that uses signed processor independant byte-code or the like.

      The system I see is that you buy your NATing router from LinkSys with the "GameServer Inside" logo, or download and install gameservd from Freshmeat. This is a little daemon running on the router which can be connected to from a trusted host inside the NAT region, and have a game server byte code downloaded to it. It automatically sets up the ports, does the proxying, etc etc, and walla, you've got mini server running on a real IP that you connect to from inside the wire, and which others can connect to (include other game servers out there) from the outside.

      Just a thought.

    61. Re:Imminent death of IPv4 predicted!! by pumpkin2146 · · Score: 1

      No, but it will mean you need 20gig of ram in a router to hold the internet routing table :/

    62. Re:Imminent death of IPv4 predicted!! by Lumpy · · Score: 1

      This NAT stuff is just an awful, awful hideous hack. The correct solution is IPv6, not NAT ourselves forwards and backwards.

      you know what... if we switch to V6 tommorow my house will STILL BE under a NAT.. I like NAT, it adds a bit of script-kiddie-proofing in line.. coupled with a properly configured firewall and it works absolutely perfectly.

      No I dont need all 6 of my machines to have a presence on the internet... I dont WANT THEM TO.

      NAT is great, and it should be fricking required for all workstations.

      Internet sevice Servers and single points to a network entry are the only things that need a internet IP address. It's pretty much stupidity to give everything a seperate IP address on the net. If I want to set my home toaster's toasting settings from my hotel room in china, I'll simply tell my house server to do it for me.

      Moving to V6 has more features that are important... More IP address is the least of the benefits.

      --
      Do not look at laser with remaining good eye.
    63. Re:Imminent death of IPv4 predicted!! by dissy · · Score: 1

      A /20 from ARIN (4096 IPs) costs $2500/year.
      This comes down to $0.61 / IP / Year.

      You are willing to pay about 20x that (Monthly vs Yearly as well)

      That is how much IP space costs. That is what Universitys pay as well as large companys.

      This is also what it would cost YOU or anyone else.

      So, what are you talking about again?

    64. Re:Imminent death of IPv4 predicted!! by MntlChaos · · Score: 1

      ALT stands for alternative. that's XOR, not OR. plain and simple.

    65. Re:Imminent death of IPv4 predicted!! by DoomHaven · · Score: 1

      I had problems getting Master of Orion 3 over Gamespy's software to work with NAT.

      --
      "Don't mind me cutting myself on Occam's Razor"
    66. Re:Imminent death of IPv4 predicted!! by martyn+s · · Score: 1

      You're really showing only one side of the argument. I mean, don't you understand the value of having well defined standards that everyone followed?

    67. Re:Imminent death of IPv4 predicted!! by Breakfast+Pants · · Score: 1

      I'm not saying you can't download files. I'm saying you can't download from a nated machine if your machine is behind a nat.

      " True, however sharing from a NAT connection to another NAT is problematic since there is no way for one of the parties to address the other (as is required for a peer to peer connection). If only one of the parties is NATed, it can still initiate connections with a regular connection (this is how Kazaa and gnutella clients allow uploading for clients behind a firewall). However nobody can initiate a connection with the NATed box because it doesn't have an address. Thus if the majority of users is behind NAT, that would effectively kill p2p networks because it would be hard to establish a connection between the majority of nodes in the network.

      However, broadband providers have an interest in p2p since it is a major reason for their clients to have broadband in the first place. A cheap modem connection will handle mail and instant messaging pretty effectively. Only when you start downloading mp3/movies/... you need the bandwidth they offer. Healthy p2p networks create a demand for broadband.

      My hope is that as ipv4 addresses get scarcer, adoption of ipv6 will finally happen. This would largely remove the need for NAT."

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    68. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      If I can't run a server on my connection and have it work ok with a couple friends, then it's broken.

    69. Re:Imminent death of IPv4 predicted!! by Electrum · · Score: 1

      Mainly 7 year old games with obsolete designs. Modern ones work fine (as clients) over NAT.

      They key phrase is "as clients". Are RTS games such as Starcraft obsolete? If two people behind NAT want to play a game together, they have to channel all their packets through a central server. This increases bandwidth and latency.

    70. Re:Imminent death of IPv4 predicted!! by Electrum · · Score: 1

      What games won't work with NAT? Out of the last 50 or so networked Windows games I've played, none have had any trouble.

      You don't play RTS games, do you? Try playing an RTS game such as Starcraft, Warcraft, C&C Generals, etc., with a friend who is also behind NAT. It won't work. The only "solution" is to channel all packets in both directions through a central server, thus increasing bandwidth and latency.

    71. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      You are so dense. Fine create a problem for people 2000 years from now but you will create a problem eventually and everyone then will think you were a dumbass.

    72. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      Not everyone can just switch ISPs. What you'll probabyl end up doing is paying your ISP extra for a real IP address, and paying even more if you want a static.

    73. Re:Imminent death of IPv4 predicted!! by i_am_nitrogen · · Score: 1

      Look, seriously... There simply cannot possibly be more people than there are particles in the universe. The Earth is only supposed to be able to sustain about one billion people according to some estimates, to ten or eleven according to others. If we ever begin colonizing other planets, which seems unlikely at our current rate, other technologies will need to be developed for communicating at such long distances with such high latencies, unless we figure out some way to transmit at the Planck energy, allowing us to bend spacetime into a loop and make the distance between two points very small, so that signal transmit time is also very small.

      Consider the number of neutrons/protons required to create a person. Divide the number of particles in the universe by that number, and that's how many individuals could have their own single IP address. Divide that number by 256, and that's how many individuals can have 256 IP addresses, etc.

      Even 2000 years from now, it's impossible, without insane mismanagement like giving away millions of IPv6 addresses to individuals, to run out of IPv6 addresses.

    74. Re:Imminent death of IPv4 predicted!! by Slime-dogg · · Score: 1

      I still don't believe that 35 trillion addresses will be enough. I remember a time when some stupid guy once said "640K should be all the memory anyone needs," or something like that.

      --
      You need to restart your computer. Hold down the Power button for several seconds or press the Restart button.
    75. Re:Imminent death of IPv4 predicted!! by perlchild · · Score: 1

      Right on...
      And let's not forget the advantage of a new version to redesign around old bugs...

      A lot of people on this thread don't like how nat isn't bidirectional, and how that affects games. Well let's MAKE those games "ipv6 compatible" by making sure they play better with non-public ips... We have the perfect excuse, we're rewriting a LARGE portion of the ip stack.

      I can just see the tv ads, you want to play on my net, play by the rules.

    76. Re:Imminent death of IPv4 predicted!! by SiChemist · · Score: 1



      ALT text is an accesibility feature, intended for the visually impaired.

      The title="popup text" feature is implemented as popup text in Mozilla.

      The usability feature is already in place as a web standard. Webmasters have only to implement this feature (and other browsers support it).

    77. Re:Imminent death of IPv4 predicted!! by FauxPasIII · · Score: 1

      > But NAT is here and now, and enjoys very wide usage.

      The same is true of NFS and NetMeeting, and I'd sooner take a caning than try to make them run through NAT gateways on a regular basis. Even FTP, as relatively simple as it is, is a headache and requires, at the least, some ugly application-layer traffic inspection on the firewall to handle properly.

      While there are plenty of reasons to give everyone a public IP, there's just no good reason for using NAT -except- the scarcity of IPv4 addresses. Anyone who claims you need NAT to hide internal machines from external traffic needs to spend 5 minutes learning how to configure a firewall.

      --
      25% Funny, 25% Insightful, 25% Informative, 25% Troll
    78. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      The Mozilla argument is to twist every standards ambiguity into an excuse to be gratuitiously incompatible with Microsoft in order to SAVE THE WEB!!! Thus ensuring their 1% marketshare.

      And your solution is to propose that standards boards sit around and argue about tooltips? I've got a better solution. Mozilla is irrelevant and can now safely be ignored. Bye.

    79. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      The Mozilla people are lying -- the standard in no way prohibits tooltips for ALT attributes.

      Nor do you really want standards that are so "well defined" that they specify behavior down to that level.

    80. Re:Imminent death of IPv4 predicted!! by Suidae · · Score: 1

      Seems like it would be simpler to allow users inside the NAT to request a forward (they have around 50,000 ports to choose from), and inform the game server of the port that the client will be listening on.

    81. Re:Imminent death of IPv4 predicted!! by Suidae · · Score: 1

      you can't download from a nated machine if your machine is behind a nat.

      Without the correct ports forwarded.

    82. Re:Imminent death of IPv4 predicted!! by Breakfast+Pants · · Score: 1

      No shit, forwarding ports is a completly different issue. If the port is forwarded, its no longer behind a nat as that port loses any nat like features it may have had. You can forward port 80 to one computer behind your nat but that doesn't mean that every computer on your nat can run a webserver on port 80. If you have the port forwarded, that port acts almost just like you aren't using a nat at all; but its only for ONE computer, nat is designed to share between many computers.

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    83. Re:Imminent death of IPv4 predicted!! by Cat_Byte · · Score: 1

      hehe...imagine the routing tables on this. Sys Admins would commit suicide.

      --
      Two roads diverged in a wood, and I - I took the one the bus load of girls just went down.
    84. Re:Imminent death of IPv4 predicted!! by Cat_Byte · · Score: 1

      I've set up many NAT networks and these problems do not exist if it's set up correctly. Everyone is assuming NAT = 1 IP address in a PAT style configuration. NAT pools can hold whatever range you own and assign to it. Set up a class C pool (or whatever /# you desire), port forward inbound to those who need netmeeting or whatever so they have the virtual IP address to their machine with only the ports you allow, problem solved.

      --
      Two roads diverged in a wood, and I - I took the one the bus load of girls just went down.
    85. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      My Kazaa works great behind a NAT and I have absolutely zero port forwards for it. People are uploading from me right now on the machine sitting in the other room with a 10.0.0.19 ip addy. Then again I'm talking about Network Address Translation & not Port Address Translation.

    86. Re:Imminent death of IPv4 predicted!! by fyonn · · Score: 2, Insightful

      it's not as simple as you're indicating, not by a long way.

      No, but all it takes is one "genius" to figure out he can acces the whole Internet without the restrictions his company's IT department places on him by just setting up a modem and dialing his ISP.

      thats irrelevant to the discussion. the loon can do that whether the co uses public or private ip's. the network isn't suddenly more vulnerable because it's on public addresses.

      I change the address ranges in my DHCP servers

      definately not as easy as that. dhcp is great for workstations but you'll also have servers on static's that need to be accessed by all and sundry, routed networks that may clash, vpn's from site to site that need reconfiguring, internal DNS/WINS all needs to be redone. it's a major hassle for a medium size company and up and if you're not careful it'll become a routing nightmare. oh yeah, don't forget the fun that ensues when you have internal firewall's that need reconfiguring too

      re double NAT: Hardly an issue

      nowadays it's not a huge issue... usually. some older nat implementations do things slightly differently and you can get issues with double nat.

      lots of protocol's work fine over NAT, web browsing, dns, irc (but not dcc) etc, but there are other protocols that are more complex, and not due to design flaws, but because they have to be. audio/video conferencing is a case in point. it's not silly at all, at my last company we had one organisation with multiple high bandwidth (ie, 4meg, 30meg, even 155's and 622 meg lines) lines connecting two dozen sites for both data and, of massive important to them, video conferencing. internet telephony is a complex protocol due to needing to coordinate mulitple callers etc, and it needs lots of seperate data streams. and it's something that is seriously growing in useage around the world.

      nat makes it bloody difficult and requires you to start forking out for expensive firewall's with application level packet inspection to eke out the data it needs to nat it all properly, it's also expensive in processing time on the fw. if it were all ip6 publically address packets then alot (thought, not all) of that work would go away.

      NAT is a dreadful hack and while it's working now, the direction we're moving things in is making it more and more annoying. ip6 has some good ideas in it and the massive store of addresses is very useful.

      I can see a time fairly close to now when every mobile phone will have it's own ip6 address, and no, I don't think it's excessive at all. ppl will have icq (or somesuch) running on their mobiles, they'll be sync'ing their address books over bluetooth 8 (UWB edition) and their phoens will be working out who in the room is an ideal love match, and why shouldn;t they?

      I seriously expect that mobile providers will start assigning ip's to phones and I reckon it'll start with ipv6 addresses (as I also expect it'll start in europe, and ripe will never allocate that many ip4 addresses).

      thoughts?

      dave

    87. Re:Imminent death of IPv4 predicted!! by fyonn · · Score: 1

      which is what UPNP is all about isn't it? msn messenger telling it's local linksys router what ports it wants open and thereby bypassing all those firewall rules you put in?

      dave

    88. Re:Imminent death of IPv4 predicted!! by Anonymous Coward · · Score: 0

      Heh, that's like when they were initially trying to resolve the Y2K shit, I think we got our first Y2K compliant computer in 97/98, so I was about 17, and I said to my dad "While they're at it, why not make it 01997?" He laughed his ass off and said "That's like 8000 years from now! If they're still using this stuff then, then they've got bigger problems!" But it was a perfectly valid arguement, I mean, do you seriously think people will remember Y2K or read about it in history books 7500 years later?? No, and if we're still around, I wouldn't be surprised if it happened again. If it was setup then, it would carry into future systems until the time came that it was needed.

      I don't believe we'll ever run out of IPv6 addresses on Earth, but when the day comes that we are colanizing other planets, and we have tons of space crafts flying around, connecting to the Internet to check their email or what-have-you, it just might become an issue again.

    89. Re:Imminent death of IPv4 predicted!! by rocca · · Score: 1

      NAT router ... $30
      Firewall ... $1000+

    90. Re:Imminent death of IPv4 predicted!! by VPN3000 · · Score: 1

      There aren't many "fans of NATting", as you put it. I am giving the realistic approach many ISPs may take into consideration when dealing with the lack of IP space and the costs associated with changes to infrastructure.

      I like the smarty response where you say "if you actually read the article (gasp, idiotic idea, I know) you'd have read about the fact that people are connecting more and more stuff to the net". Man, that screams of trolling. Of course people are connecting more things to the net. That's why we are discussing the issue. Pardon me for pointing out the obvious.

      NAT is not a good solution, just a cheap fix for those companies who are looking for 3Q and 4Q numbers to show their investors. Investors don't care, as of yet, about the technical details. All they want to see is a profit posted (or the least amount lost per share) when the results come out. If the Net was governed by which technology was the best and there were unlimited resources to pump into making sure everything was as good as it could be, then yes, we would already be using ipv6 without a doubt. But when there's 800,000k worth of work involved with upgrading (man hours, hardware, planning, testing, etc, etc), and your company is already in the hole for the year due to a sluggish economy, then it's not going to get done until it absolutely has to. In the meantime alternatives must be found to delay such changes until they are absolutely needed.

      I hope the above can seep into that inflamitory brain of yours. I don't see why I am responding to such a silly post by an Anon Coward though. :)

      Good for you that your ISP allows you to run servers. My current ISP allows such activities, as well. Yet, the last 3 I had did not allow such activites and there were no alternatives for broadband connectivity. Even though your ISP does allow such things, it's not something that someone with a basic account can demand as part of their $39.99/mo. TOS agreements can, and are often, rewritten without notice or warning. There is no legal right to do anything on your ISPs hardware that they don't specifically grant. That's not to say that they will do anything if you mildly violate a TOS, typically they will want your $$$ unless you are generating enough traffic that their NOC will notice or complaints from other users.

      "Is it really upto ISPs to tell me if I can do that or not?"

      Now that's the dumbest question I've heard in a while. YES. Does your ISP's hardware belong to you? Does US law specifically state that you have some kind of rights associated with your access to the Internet via your ISP? No. You pay them a monthly fee to access the Internet, through THEIR hardware, on their terms. They will offer service that will please the grand majority of people so that they may attract more customers, but no, you have no right to say you can carry on whatever type of communication you wish because "you have a say" in the matter. Your "say" is when you cancel an account and find an ISP who's TOS allows you to do what you want.

      I grow weary of people who think they own the Internet. It reminds me of doing Tech Support years ago and people demanding that I fix their phone line because I sold them Internet service. This would often be due to no dialtone on their data line, or a similar non-ISP related issue. I would often sit there and daydream about how this person acts when in various other situations.. "I bought a cat from your store last week, and well, it doesn't help me with the laundry. I want my money back! NO, I HAVE A RIGHT TO DEMAND THIS!! I PAID YOU $9 AND WANT IT TO WIPE MY BOTTOM, TOO". I digress.

    91. Re:Imminent death of IPv4 predicted!! by DonGar · · Score: 1

      If the application uses a fixed port number, and if you have enough external IPs to handle all of the internal machines, and if you don't mind having the extra admin work to keep updating your rules, then yes that works.

      But if those aren't all true, then it doesn't. And all of those cases are frequently not true.

      1) Many useful apps don't have fixed ports to listen on, instead they use lookup services. See anything based on RPC, Corba, etc. If you need to be able to run more than one copy of the application at a time, then multiple ports are REQUIRED.

      2) ISPs are significantly limiting the number of IPs available. Like my home network where they charge me $5/month for one additional address. Unless I cough up the money, I can't SSH to more than one machine (and yes, I know the tricks around it, when they work, and when they don't).

      Without the crutch of NAT, the address space would be much larger, and ISPs would never have been able to establish charging for address as a legitimate thing.

      3) The admin work is a big barrior. If I want to do video chat with my mother, I have to drive 4 hours to her house to reconfigure her firewall. She's smart, but that's more than she can handle technically, and there is nobody else I can ask to do it. And what happens when lightning kills the cable modem, and it all has to be reconfigured?

      Many large businesses run NAT for both security, and to deal with address space issues. I've seen a number of these networks through my consulting work. I have never seen network admins that would reconfigure the firewall just because one of their users want's to use AIM file transfers.

      They may knowingly allow all kinds of funny things through an SSH port forward, but they won't begin to touch a config file (other than account creation) on a per user basis.

      This means that small non-technical users are screwed. Anyone running unusual non-standard applications is screwed, anyone without enough address space that they don't need NAT in the first place is screwed, anyone so lazy that they don't want to have to reconfigure their security everytime they change which network applications they use is screwed, and anyone on a large corporate network is screwed.

      Now, are you really so sure that NAT works just fine and that people should just quit complaining?

      --
      plus-good, double-plus-good
    92. Re:Imminent death of IPv4 predicted!! by Suidae · · Score: 1

      If the port is forwarded, its no longer behind a nat

      Not true at all, its still NATed, it just receiving forwarded data.

      You said:

      you can't download from a nated machine if your machine is behind a nat.

      Without qualifying the statement that port forwarding can provide a limited solution to that problem.

      Obviously port forwarding isn't a solution for large networks, but your statement, as you made it, is only partially correct without the qualifier.

    93. Re:Imminent death of IPv4 predicted!! by Suidae · · Score: 1

      Sounds good to me, as long as the router has a capability to deny if I want it to configure it to do so.

      I recognize the security problem of allowing any application to put holes in the firewall like this, but the small office/home equipment that supports these features isn't generally installed for its firewall features, its installed for its NAT features. Most home users would consider it a good thing that it lets their apps do what they were designed to do. Perhaps an off by default option to enable it?

      Am I missing a bigger issue with it?

    94. Re:Imminent death of IPv4 predicted!! by Cat_Byte · · Score: 1

      I am merely pointing out the apps that people are saying do not work with NAT which DO work.

      1) true
      2) this was my point in an earlier post
      3) you could have saved 4 hrs of driving by hosting on your end.
      AIM file transfers are usually blocked at businesses anyway. For home use I'm running on satellite internet with a 10.x.x.x ip address externally and using XP internet connection sharing to a 192.168.0.x network. I have no firewall rules configured in my firewall to allow incoming connections and I can transfer files via aim/icq/yahoo, I can share files on kazaa, I can do lots of things people were listing as things that made NAT bad. I cannot host apps such as netmeeting or a game because I have no real IP but it doesn't stop me from playing or using it by attaching to someone who does have a real IP. Firewalls can be set up to allow everyone to use file transfers as well as other apps without it being on a per-user basis if it is configured correctly on a real firewall but hopefully not in a business environment.

      Main point was that most of this did work and people were saying it didn't. It sounded alot like people were using PAT instead of NAT. If they were using one external IP using port tranlation then yeah...all of the apps listed so far would not work correctly.

      --
      Two roads diverged in a wood, and I - I took the one the bus load of girls just went down.
    95. Re:Imminent death of IPv4 predicted!! by DonGar · · Score: 1

      Maybe my last reply was a bit more adamant than it should have been. I get frustrated, because I knew (and said loudly) that NAT was a huge hack when it was new. I knew as it was going to cause problems as it became more popular, but obviously, I could have no effect on the process.

      Now that they are popular, most users don't understant that they cause any problems at all, much less what they are or why. And I'm one of the people (like yourself, and other readers here) who gets stuck trying to working around from both a sysadmin point of view, and as a network app developer.

      For example, I'm involved in a (closed source) project right now using BitTorrent style technology that will probably fail because it can't handle more than about a third of the users being behind NAT firewalls. And this is after considerable effort to work around limitations of who can connect directly to who.

      In particular (without custom port forwarding rules that you can't expect the average user to configure), one box behind a NAT firewall cannot connect directly to another box behind a NAT firewall.

      Other effects are things like the fact that games must now use a star connection pattern, not a ring or a mesh (and the improved response times that might come from that). Any technology that allows individuals to communicate without a third party involved becomes either difficult or impossible (instant messaging without a central server, conference software, shared whiteboards, etc).

      I just get frustrated about it all, because I see an artificial barrier to entry for an important area of network development.

      --
      plus-good, double-plus-good
    96. Re:Imminent death of IPv4 predicted!! by CowboyMeal · · Score: 1

      Where in the HTML spec does it say that user agents shouldn't show alt text in the tooltips?

      --
      Your credit card information wants to be free.
  2. Jeez... by TopShelf · · Score: 5, Funny

    Who needs a new word to describe the number of possible addresses? It's just 1/2.9387358770557187699218413430556e+61st of a google.

    --
    Stop by my site where I write about ERP systems & more
    1. Re:Jeez... by Anonymous Coward · · Score: 1, Informative
    2. Re:Jeez... by Anonym1ty · · Score: 5, Funny

      Isn't the number a googol? and the search engine google?

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

      Actually, it just so happens that there is a word for this number. Some people must not have paid attention in Chemistry class.

      It's a mole.

      Or more precisely, 1.1 mole.

    4. Re:Jeez... by dbenhur · · Score: 2, Informative
      A googol is 10E+100.

      Ipv6 addresses are 128 bits, so there are 2^128 ~= 3.4E+38 addresses. Log10(2^128) ~= 38.5.

      So IPv6 has a bit over the cube-root of a Googol addresses.

    5. Re:Jeez... by Anonymous Coward · · Score: 0

      1.1 mole? How did you figure that?

      1 Mole = 6.022e23
      2^128 = 3.4e38, although I believe only 64 bits will be used for the actual adress
      2^64 = 1.8e19 which is on the order of millimoles..

    6. Re:Jeez... by sp1nl0ck · · Score: 1

      When I first read the headline, I read IP as intellectual property - which kinda shows where the headlines have been recently.

      OTOH, given the whole RIAA/MPAA/DMCA carry-on at the moment, maybe it did mean intellectual property, and the wrong story just got pegged on...

      --
      War is God's way of teaching Americans geography
    7. Re:Jeez... by lightsaber1 · · Score: 1
      actually, a googol is 10^100, not 10E+100, since that's 10 x 10^100 = 10^101

      but otherwise, so what? There are a lot of devices out there considering the entire world, and there are a lot of IP ranges that are wasted on ISPs/companies that don't use them all at once, and on specific ranges reserved for personal use.

      perhaps if we reorganized we could come up with a lot more to hold us for a while, but if *everything* eventually has an IP address, I can envisage running out in the not too distant future.

  3. Imagine the uses by zubernerd · · Score: 5, Funny

    To quote the article "Such sensors could allow people to operate devices from anywhere there is an Internet connection." and "Now that the address space is available, the next step is figuring out how to use it."
    I've got an idea, a internet connected toilet. "Using a cellphone in Los Angeles", I could flush the toilet at my home remotely and have the toilet seat drop down automatically (you know, to keep domestic tranquility). I could even call the toilet to see if anyone is using it.
    I better go patent it...

    --
    Accentuate the positive, don't waste your mod points on the negative.
    1. Re:Imagine the uses by General_Corto · · Score: 5, Funny

      Fine, but I'm going to patent the Denial Of Sewage attack. Toilet blockages, here we come!

    2. Re:Imagine the uses by Ablar · · Score: 0

      I think Japan already beat you to it.

    3. Re:Imagine the uses by PhilHibbs · · Score: 5, Funny
      Fine, but I'm going to patent the Denial Of Sewage attack.
      Otherwise known as the Flushdot Effect
    4. Re:Imagine the uses by ldspartan · · Score: 2, Insightful

      Thinking about it a bit, that could actually be a problem.

      Imagine the impact all the toilets in a couple square blocks of New York City flushing simultaneusly would have on the water supply.

      --
      Phil

    5. Re:Imagine the uses by $rtbl_this · · Score: 1

      I think the /. crapflooders may have prior art.

      --
      "Are you being weird, or sarcastic?" said Emma. I said I didn't know because I get the two feelings mixed up.
    6. Re:Imagine the uses by Anonymous Coward · · Score: 0

      Why would you want to remotely control your toilet, or anything else for that matter? Even if you did, you wouldn't want everything on a separate IP address anyway. It'd suck to have to open a dozen IP connections, one for each device. Why not just open up one port at one internet available IP address and send commands to query/modify device state all in one fell swoop, thus cutting down latency. But noooo.. that would make too much sense.

    7. Re:Imagine the uses by kinnell · · Score: 1

      ...if it had a built in stool sample analyser, it could automatically send you an email with nutritional or medical advice.

      --
      If I seem short sighted, it is because I stand on the shoulders of midgets
    8. Re:Imagine the uses by Anonymous Coward · · Score: 0

      Further modification of your invention could be a real pain in the ass for unwanted visitors.

    9. Re:Imagine the uses by Anonymous Coward · · Score: 0
      Shhhhhh!!!!!

      Something like that would put The Turd Report out of business!!!

    10. Re:Imagine the uses by moonbender · · Score: 2, Informative

      Believe it or not, some (Japanese) toilets actually do that already. I'm not sure if more than a proof-of-concept one was built and how sophisticated the analyser is, but at some level it's been done. :O

      --
      Switch back to Slashdot's D1 system.
    11. Re:Imagine the uses by cesspool · · Score: 2, Funny

      hrm, i think you must be referring to the 'FlushLog Event'

    12. Re:Imagine the uses by perimorph · · Score: 1

      I've always heard that did happen in places during the series finale of M*A*S*H on TV. But I'm not old enough to remember, so it could just be an urban legend.

    13. Re:Imagine the uses by Dynedain · · Score: 1

      Actually, the fraternity at MIT that has a B level block of IP addresses already has a toilette that can be flushed remotely.

      --
      I'm out of my mind right now, but feel free to leave a message.....
    14. Re:Imagine the uses by GlassUser · · Score: 1

      Watch out or the goatse guy will clog your pipe.

    15. Re:Imagine the uses by dasmegabyte · · Score: 4, Interesting

      Alright, so I'll have 100 devices that require an IP. I could see that, although I fully intend to become a luddite sometime after OS 10.5 comes out. My question is this: does each device that has internet connectivity NEED its own IP?

      And of course, the NAT community says NYET.

      The end user's desire for privacy and security combined with the world's ISPs' need to cut down on the number of machines running active web/ftp/samba/gopher/finger servers over their lines (and essentially bypassing their commercial services, which is where the real money is), will eventually mean that all consumers will be given a single IP, or less, from their provider. And you'll have to make do or pay a huge fee.

      (What, you think just because IP banks are massive with IPv6 that your ISP is just going to give you a shitload of them? No dice, kid. They'll make you pay just like everything else, and try to tell you it's a deal.)

      But this is not necessarily a bad thing. Most connection sharing devices -- routers, gateways, access points, etc -- also act as a pretty good form of security. They close devices off from the rest of the internet, unless you explicitly allow internet users in. I'm pretty much unworried about the threat of hackers getting into my printer; all i have to worry about is hackers getting into the router. And a single path of entry makes it easier to cut them off as well.

      Sure, you can get a personal router with IPv6. But you don't HAVE to, and a lot of people won't. So the current scheme is forcing people to use slightly better security. And while roughly 4 billion addresses isn't enough for every widget on the planet, it's far more than the number of conceptual groups on the planet. One IP per organization or per household...should be enough for a LONNNNNG while.

      --
      Hey freaks: now you're ju
    16. Re:Imagine the uses by Dukael_Mikakis · · Score: 1, Funny

      Yeah, I can't wait until the day when I can do this:

      $ ssh washing_machine
      $ put laundry
      $ select detergent
      $ wash (Wash Again SHell)

      Never even have to leave my bed.

    17. Re:Imagine the uses by Lord_Dweomer · · Score: 1
      And if your iToilet has a bidet, may god have mercy on your soul.

      --
      Buy Steampunk Clothing Online!
    18. Re:Imagine the uses by fermion · · Score: 2, Interesting
      The geeks want IPv6 because it is there. IP addresses for all, too plentiful and too cheap to meter!

      The electronics manufacturers want IPv6 to boost sales. Everything having an IP address means everything will need hardware and software to support connectivity. No one will notice another $100 on a refrigerator or tv. Of course, these appliances will be network ready, and will cost another $500 to be network enabled.

      The telcos are wondering why the hell they need to pay for IPv6 upgrades since they are making money selling IP addresses one at a time to the consumer. The ISPs are fighting NAT technology to drive these profits, and drive the myth of scarcity, thus increasing the profits.

      The hackers are crackling wildly at the new opportunities to snoop, spy, and cause general mayhem. Everything addressable from anywhere. Denial of service attacks on the cable box. The meat industry will hack into refrigerators, check for sufficient quantities of dead animals, and, if it doesn't find it, plant child porn or terrorist plans on the computer.

      The sane of us are sitting back chuckling knowing it will happen when it becomes necessary, just like the migration to 10 digit dialing and portable phone numbers.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    19. Re:Imagine the uses by Igmuth · · Score: 1

      I'd personally be more concerned about the sewage system. Most toilets tend to empty alot faster than they refill.

    20. Re:Imagine the uses by ldspartan · · Score: 2, Funny

      I'm not a civil engineer, but for some reason I'd think the sewage system would have a larger capacity (and pipe diameter) than the water system. Seeing as wastewater is more dense (generally) then clean water and all.

      But hell, I'm just a CS nerd. I don't know shit :)

      --
      lds

    21. Re:Imagine the uses by Anonymous Coward · · Score: 0

      There was an article in a newspaper in Colorado a few years ago talking about the wastewater facilities. As I remember, they could tell whenever the Broncos were playing, since "the tide would come in" (their words - really) during commercials.

    22. Re:Imagine the uses by SquadBoy · · Score: 1

      But you still need Internet legal addresses to NAT to and their are *many* areas where it would be really nice to be able to do one to one NAT with Internet legal addresses. Of course even if devices have their own Internet legal address you can still run it through ACLs in your router and your firewall and control ports and in the example of VPN overcome all the downsides to NAT so yes this is a good thing and no NAT does not solve the problem

      --

      Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
    23. Re:Imagine the uses by Anonymous Coward · · Score: 0

      Sorry, Microsoft already has prior art on the internet toilet (the iLoo)

    24. Re:Imagine the uses by takev · · Score: 1

      accourding to the RIPE rules (The IP regulartor in Europe) every always-on (this means ADSL or other broadband) user will get a /48 (which most times will be used as a 16bit subnets and 64bit host addresses).

      Only dial up services may give out a single (random allocated) IP address.

    25. Re:Imagine the uses by fyonn · · Score: 1

      using your 3G video cellphoen, you could check out the "bowlcam" remotely!

      reminds me of a simpsons episode...

      dave

    26. Re:Imagine the uses by fries · · Score: 1

      Guess what? NAT is not as friendly as a firewall with 'block all' 'pass out blah keep state' .. if
      you are able to deploy NAT, you are able to deploy
      a firewall. If you are concerned about security,
      just block everybody from everything and only allow
      outbound connections. Same as NAT, without the NAT
      headaches. IPv6 needs no NAT, having uniquely
      addressable devices (even if all they listen to are
      ipsec packets) is a bonus of IPv6, not a point of
      frivolty.

      --
      Todd Fries .. todd@fries.net .. OpenBSD, because security matters!
  4. What's wrong with IPv6 by wayward_son · · Score: 3, Interesting

    Sounds like a solution to me.

    It's just going to be a pain in the ass to get every one switched over, though.

    1. Re:What's wrong with IPv6 by sporty · · Score: 5, Informative

      Not too hard.

      Backbones should switch over first, proxying ipv4 over ipv6, then propogate downwards.

      When it hits users, they'll have an ultimatum. Upgrade within the next 180 days, or j00 are fux0red.

      As for the OS and device makers, simply make dhcp check ipv6 first, then fallback to ipv4. That'll be transparent for all the chuckleheads who would ignore the "switch" thing.

      --

      -
      ping -f 255.255.255.255 # if only

    2. Re:What's wrong with IPv6 by deman1985 · · Score: 2, Insightful

      The problem is an IPv4-based internet. If it had been designed to allow for future expansion of addresses, there would be no problem, but since every backbone and every router built prior to IPv6 standards being implimented has 4-byte addresses, then the entire world has to be transitioned before IPv6 addresses can go into commercial use.

      Does it need to be done? Eventually, yes. Is it an emergency? Not at all. Not every single device out there has its own global IP address and they never will, people. There's no reason for them to work that way, and doing so would only clutter the already messy network we call the internet.

    3. Re:What's wrong with IPv6 by kwerle · · Score: 1

      It's just going to be a pain in the ass to get every one switched over, though.

      Most of "everyone" are windows users. What is the state of their IPv6? If it works, then most of the work is mostly done...

    4. Re:What's wrong with IPv6 by garymm · · Score: 2, Interesting

      would this mean new firmware for every router/DSL modem on the earth? honest question

    5. Re:What's wrong with IPv6 by gbjbaanb · · Score: 1

      I think IPv6 is backwards compatible with IPv4 - an IPv4 address will still be recognised as a valid IPv6 address, just one with lots of 0s in it.

    6. Re:What's wrong with IPv6 by funkman · · Score: 4, Funny

      Damn short sighted engineers! Who would have thought we'd have more than 4 billion networked devices over 20 years ago!

    7. Re:What's wrong with IPv6 by xanadu-xtroot.com · · Score: 1

      would this mean new firmware for every router/DSL modem on the earth? honest question

      Terchnically, yes, I suppose it would. I mean here it's easy for me to cd /usr/src/linux and add support for it into my kernel, compile and reboot (OK, OK, and play with my iptables rules as well, but...). But it's not that easy with all those devices. I suppose it's possible that the ISPs could blast a new image at the user when they are connected, though, assuming that the devices are flashable.

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    8. Re:What's wrong with IPv6 by jaredmauch · · Score: 5, Insightful
      I don't mean to flame you, but I'd like to address the technical issues surrounding your statements.

      Backbones are already upgrading to IPv6 enabled software and hardware. My employer has plans to run dual-stack IPv4 IPv6 later this year which means that any existing IPv4 customer can give us a call saying "enable v6" and we can do it that day. (assuming they have their hardware/software in place). No tunneling, no 6to4 gateways, it'll just work. I see no long-term viability of the 6to4 gateways, in the same way that we didn't see caches go mainstream for every internet user. (yeah yeah, some of you will claim bittorrent is a large distributed cache, and while that might be the case, i'm talking about for most of the general public, the AOL/IE users that don't know how to spell IP).

      If you also see one of my previous comments on IPv6 here about who is supporting it (note, what you might define as a backbone isn't what the rest of the network might..) and has existing routes in the tables, you'll get an idea of who is at least prepared for the new future of impossible to read ip addresses.

      If everyone runs dual-stack v4v6, you'll see the ability to access your existing services while continuing to be able to gain access to the IPv6 content. Personally, I've seen that in cases like where a RedHat release comes out, I can get faster transfer rates going to the IPv6 mirror than the IPv4 mirror. Everyone is hammering the v4, which makes the v6 available for me :). I'm just waiting for Linksys (now cisco) and the other consumer product people to realize that they need to upgrade their devices so they can do IPv6 nat for those cablemodem routers, etc..

      Here's where I think that the local loop (dsl, cable) providers can go and start to seriously make money and make IPv6 viable: IPv6 enable your network, then offer VoIP services over SIP enabled devices. This way you don't run out of numbering space (ip and pstn). (Trivia: how many ips would it take to convert the existing PSTN network to VoIP, if each phone number required an IP address).

    9. Re:What's wrong with IPv6 by AndroidCat · · Score: 1
      When it hits users, they'll have an ultimatum. Upgrade within the next 180 days, or j00 are fux0red.

      Slap a NAT-like converter box at the border of your network. Creamy IPv6 on the outside, crunchy IPv4 on the inside. Some network devices like printers won't be a simple software upgrade.

      --
      One line blog. I hear that they're called Twitters now.
    10. Re:What's wrong with IPv6 by riflemann · · Score: 3, Interesting

      Backbones should switch over first, proxying ipv4 over ipv6, then propogate downwards.

      Please do a bit of research on the interoperability of Ipv6 and Ipv4. A large proportion of the Ipv6 effort has been on efforts to ensure amooth migration and interoperability. You dont need an ultimatum, just let both work then gradually turn off Ipv4-only services. No one will notice if its done correctly.

      As for the OS and device makers, simply make dhcp check ipv6 first, then fallback to ipv4. That'll be transparent for all the chuckleheads who would ignore the "switch" thing.

      Fyi...

      All dual stack implementations today first attempt to use IPv6 versions of protocols, and only if that fails do they resort to Ipv4. All of my boxen for example will do the following:

      1. Do DNS lookup

      2. Get IPv6 address and IPv4 address for hostname.

      3. Attempt to connect to IPv6 address first.

      4. Otherwise try Ipv4 address

      Any correctly written application will automatically use IPv4 and IPv6 without special intervention. The IPv6 bind() call binds to both v4 and v6, for example.

      So, your concerns have already been addressed. :)

    11. Re:What's wrong with IPv6 by N3WBI3 · · Score: 1

      IF were going to force NAT just stick with IP4 and start taking some of the class A's and B's back

      --
    12. Re:What's wrong with IPv6 by sporty · · Score: 1

      hmm.. damnit. so someone hit the button already

      --

      -
      ping -f 255.255.255.255 # if only

    13. Re:What's wrong with IPv6 by AndroidCat · · Score: 1

      There's going to be pockets of legacy hardware and software that can't be upgraded. Hide them behind a box while the rest of the world goes IPv6.

      --
      One line blog. I hear that they're called Twitters now.
    14. Re:What's wrong with IPv6 by gmack · · Score: 1

      Windows XP comes with support out of the box but 2000 needs patching. Everyoneone else on windows will need to upgrade their OS.

    15. Re:What's wrong with IPv6 by SN74S181 · · Score: 1

      Why would I need my home router (connected to DSL) to do IPv6? I am connected via PPPoE, and as far as the rest of the world is concerned I'm just one IP address which my ISP can update/replace any time they like. I am definitely not going to use up a whole subnet full of IP addresses locally. And frankly, I am glad to not have boxes with static and publically accessable addresses here at home.

    16. Re:What's wrong with IPv6 by Anonymous Coward · · Score: 0
      What's wrong with IPv6?

      If this scheme were put in place, then there would be no scarcity of addresses. Without scarcity, you can't have a market.

      Without a market, you can't have trade. Trade is the foundation of our capitalist system. Therefore, IPv6 is unAmerican.

      In fact, IPv6 is communist. They try to create so many addresses that they can push agendas like "addresses to each according to his needs". If that approach were workable, then why can't governments make everyone rich just by printing money? Obviously, that would be absurd.

      Make no mistake, the push for IPv6 is just an attempt to steal sharholder value from the businesses that manage our IPv4 network resources. The looming shortage of IPv4 addresses will make these businesses more valuable, not less. These businesses will help to create wealth and generate tax revenues. It's unbelievable that in this economy some people want to snuff out one of the few sectors that show real revenue growth potential.

    17. Re:What's wrong with IPv6 by Anonymous Coward · · Score: 0

      Do we really want to force people to upgrade to the latest software? It's not like there will be IPv6 patches for Win98.

      I only see a mass-upgrade as beneficial if people are aware of the option when they have to make a choice.

      Besides, there's no reason an ISP can't run NAT for their IPv4 clients. Combine that with HTTP and FTP proxies, and everything is all set.

    18. Re:What's wrong with IPv6 by Anonymous Coward · · Score: 0

      > ISPs could blast a new image at the user when they are connected, though, assuming that the devices are flashable.

      Many such devices are flashable, but know what?

      I BOUGHT the dsl modem I am using, it is owned by me and not by the ISP. Morover, if you take 100 of their dsl customers you are likely to find 5 brands and 20+ different types of dsl modems. It might be different where you live, but here it is the norm that the end user, not the ISP owns the modem.

      Pushing an image is not an option because the ISPs do not own the modems. Also, many routers and dsl devices simply do not have an ipv6 implementation yet, so for now you can't make the images for those either.

      Hint: investigate and think before you post...

    19. Re:What's wrong with IPv6 by Anonymous Coward · · Score: 0

      Twit, nothing would need to occur on a DSL modem, which is a layer-2 device. A Bridge. It only looks at MAC addresses. It'll pass the traffic between your machine, and the upstream router till the cows come home, whether you'r running IPv4, IPv6, IPX or Appletalk.

    20. Re:What's wrong with IPv6 by xanadu-xtroot.com · · Score: 1

      Pushing an image is not an option because the ISPs do not own the modems.

      OK, your ISP does not own *YOUR* "modem". Yes, I then agree, for them to blast you something like this would be wrong (and probably VERY bad for your connectivity). I will not disagree with you there, but, for a lot of other people that "rent" their "modems", this is a viable option for the ISP.

      Hint: investigate and think before you post...

      Perhaps you should look at it from other angles as well...

      (Full Comment) for everyone else.

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    21. Re:What's wrong with IPv6 by quantum+bit · · Score: 1

      Most of "everyone" are windows users. What is the state of their IPv6? If it works, then most of the work is mostly done...

      XP or "better". Windows 2000 does have an IPv6 stack from Microsoft Research, but it doesn't support doing DNS lookups over IPv6 so you HAVE to be dual-stacked. On a v6-only network 2k won't work.

      The only hope for those of us who hate XP is that somebody will write an open source full-featured IPv6 stack for it, which the odds of are something like 0.

    22. Re:What's wrong with IPv6 by len_harms · · Score: 1

      You can still do NAT with ipv6. There is no real reason you can not. If you tell a computer to do something it WILL do it. You tell it that its address is something it will use that. The proper way to do that sort of thing is with your mac address and access control lists. This way you do not have random computers popping up in your network and they have free roam of your network. This has become more important with things like 802.11. However do not doubt that NAT will go away. Its to usefull for that.

      The only thing that bugs me with NAT is the hoops you have to jump through to get some software to work. Some of it just doesnt work. Yet these people are doing nothing 'wrong' with what they write. They just now have to take into account something they shouldnt have to be bothered with, what the network is doing. Its a network layer implementation issue leaking into the app layer.

      My question is what ever happened to IPv1, IPv2, IPv3, and IPv5?

      Why were those types inadequate? Are they still around? Or are they just called something else I didnt know?

    23. Re:What's wrong with IPv6 by jroysdon · · Score: 1

      Further, if Linksys, etc. came out with IPv6 aware devices, and at first the were acting as NAT/proxy to IPv4 and at the same time tunneling routers for IPv6, and eventually just IPv6 on both sides with NAT/proxy for old IPv4 hosts to get to IPv6. It's only a matter of time, especially with Cisco buying Linksys.

      Plus, the beauty of IPv6 is that so long as your tunnel broker remains the same, your IPv6 site address should as well, and your if you're using EUI-64 you're PCs will remain the same (using the auto-assigned IPv6 address from their MAC address), so things like DynDNS (or maintain your own DNS) could get you to all your PCs at home without a VPN tunnel. Eventually when things flip-flop and there is more IPv6 traffic and all the ISPs go IPv6 native, you wouldn't need the tunnel broker and for sure you're home net would just stay the same.

      I've yet to mess with IPv6 IPSEC, but naturally you could encrypt as well (or just SSH as I do).

      I'm mainly jazzed as I just got my /48 up and working with Sprintv6.net and BGP4+ today (still not native, but tunneling through only 2 Sprint IPv4 routers to get to the 6Bone cuts latenacy from 200-300ms back down to nearly normal).

      I plan to start mirroring more and more content and providing it only via IPv6 ;-)

      ftp://r2.ipv6.artoo.net/pub/

    24. Re:What's wrong with IPv6 by mrogers · · Score: 1

      Why didn't they just steal the code from BSD like they did with IPv4?

  5. Not so much a crisis... by Tom7 · · Score: 4, Insightful

    Yeah, but those 100 IP addresses can be behind a household NAT and share a single IP address. With the way people use the internet today, I'm not sure the crisis is so serious...

    1. Re:Not so much a crisis... by HuskerDu · · Score: 3, Informative

      Yea, but NAT really does cause more problems than its worth when you consider IPv6 an alternative. Things like IPSEC and such do not work through nat without non-standard encapuslation and such.

      The world would be better without NAT.

    2. Re:Not so much a crisis... by binaryDigit · · Score: 4, Informative

      That's fine but unless you're talking about incoming originating comms. With NAT, you have to rely on ports instead of ips to address specific items. This means a mod to your dns (or whatever replaces it). You can't just assume that the cell phone port is port 32768, since the household may have several different cell phones (or toasters, or tv's, or whatever). Not a huge problem, but it does require more changes than would simply assigning everything it's own unique id.

    3. Re:Not so much a crisis... by paranode · · Score: 1
      Actually IPv6 addresses work differently than the current IPv4. The IP address is a long mangled form of the MAC address. When they say they want everything out there on the internet with its own address, they mean it.

      Though still it shouldn't be impossible to use NAT, but I would imagine it won't be as transparent to the user as it is right now. (ie Linksys routers, etc).

    4. Re:Not so much a crisis... by lauterm · · Score: 1

      Amen, brother. No news here. The emergence of NAT has dramatically slowed the rate at which IPv4 addresses are being used up.

    5. Re:Not so much a crisis... by PhilHibbs · · Score: 1, Flamebait

      Isn't NAT illegal in the U.S., or just in some states?

    6. Re:Not so much a crisis... by Jeff+DeMaagd · · Score: 3, Insightful

      I agree. For a lot of those devices, I wouldn't want the IP address to be acessable from the outside world anyway.

      If I need to remotely access stupid sensors, then I'd rather remotely access a single program on a server at or behind the firewall that handles that sort of thing, and hides the particulars to boot.

    7. Re:Not so much a crisis... by Anonymous Coward · · Score: 2, Informative

      I agree, but networking devices are getting smarter and smarter. The idea of NATing only L3 (IP) information is dying -- more and more, NAT devices are becoming application aware, and they are NATing L4 ports and L7 payload (e.g. Active FTP NAT, where the port command is issued in the L7 payload itself, and needs to get NATed on L4).

      I agree that this is not so much of an issue due to NAT, and as NAT gets smarter (L7), then this is even less of an issue. But its still a stop-gap... eventually IPv4 will run out of addresses regardless.

    8. Re:Not so much a crisis... by RevDobbs · · Score: 2, Insightful
      You can't just assume that the cell phone port is port 32768, since the household may have several different cell phones (or toasters, or tv's, or whatever).

      So, how different is this from running several websites on one machine? Your home gateway (or maybe a specialized cell phone gateway) can route the packets to the appropriate device based on header values (DEVICE_NAME, MAC_ADDRESS, evil bit, etc.).

    9. Re:Not so much a crisis... by Tom7 · · Score: 1

      Not a huge problem, but it does require more changes than would simply assigning everything it's own unique id.

      Assigning everything its own unique ID requires us to upgrade the entire infrastructure of the internet. How can this be more work?

    10. Re:Not so much a crisis... by Fulcrum+of+Evil · · Score: 1

      Things like IPSEC and such do not work through nat without non-standard encapuslation and such.

      IIRC, IPSEC was deliberately designed to not work with NAT because the designers had a grudge against NAT.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    11. Re:Not so much a crisis... by binaryDigit · · Score: 1

      So, how different is this from running several websites on one machine? Your home gateway (or maybe a specialized cell phone gateway) can route the packets to the appropriate device based on header values (DEVICE_NAME, MAC_ADDRESS, evil bit, etc.)

      That was my whole point, that it wasn't a big deal, just not as simple as addressing a specific device. Your routers will have to become more intelligent to forward properly. Compare this to using dns (bob.cellphone.smith.com, mary.cellphone.smith.com, masterbd.tv.smith.com, toaster.smith.com) to address the devices. The latter way fits easily into existing infrastructure.

    12. Re:Not so much a crisis... by Anonymous Coward · · Score: 1, Interesting

      Because we have to do so eventually anyway?

      Upgrade the internet: it gets faster and ends up with more addresses.

      Don't upgrade: the internet runs out of addresses and suddenly everyone has to be a NAT/Firewall expert.

      Having one point of entry can be a *real* drag. Lets say someone makes up a cool protocol to communicate securely with IP enabled items in your house. Suddenly, you can cancel the sprinkler system when you see it getting stormy outside, or you can tell the oven to pre-heat to 450F just as you are leaving to head home (etc etc). Now, lets say everything has an IP. Wonderful, you connect to the IP, you get authenticated, you are cookin with gas.

      Now, you have one IP. Suddenly, you have to set up a forward for EVERY damn item in the house. You can't assume ports for different services because you may have more than one of those services running. And now, lets put interoperability in and contemplate trying to connect to someone else's home-grown NAT setup.

      Thanks, but I'll go with more IP's over more NAT's. NAT's are nice for giving a lot of computers access to the internet, but not good for putting a lot of services on the 'net itself.

    13. Re:Not so much a crisis... by Cramer · · Score: 3, Insightful

      Idiot. *sigh* The only problems NAT causes are to crappy implementations that make assumptions they shouldn't be making. (i.e. putting address info within the data of the protocol.)

      IPSEC works perfectly fine through NAT -- I do so all the time without "non-standard encapuslation and such". The only part of IPSEC that will not work through NAT is header authentication and the various non-standard implementations that cryptographicly sign the entire packet. If the crypto integrity covers the packet header, then altering the address(es) within the header invalidates the packet.

    14. Re:Not so much a crisis... by dasmegabyte · · Score: 1, Insightful

      I disagree. Protocols which don't work well over NAT are poorly engineered, so IPSEC is one of them. You can't assume every PC is on the internet with its door open any more than you can assume people use the default port or the same implementation of an IP stack. There are plenty of great reasons to have NAT'd machines, even with IPv6. My personal favorite is load balancing. If you want to control load balancing, and not rely on the requesting client to do it for you, a NAT-based routing device is an elegant solution. It optimizes queue speed by minimizing the lag effect of long requests and provides an extra layer of security. I'm thinking of F5's BigIP, which I absolutely love. All requests come in on the same IP, they all leave on the same IP -- but there's a bank of machines on the internal network serving the request. It's transparent to the end user...no www-16 prepended to the URL, unless you want it there.

      --
      Hey freaks: now you're ju
    15. Re:Not so much a crisis... by Tom7 · · Score: 1

      I'd love if we could throw out the whole internet and use IPv6 instead. I'd love if we could throw out a lot of legacy technologies, like x86 and C and ASCII and gas engines. But doing this requires a lot of changes to infrastructure!

      NAT is great because it's an endpoint-based solution. Stuff like uPNP can be deployed at a single site to make NAT better, and we don't have to touch a single router. (Network guys should read their own influential papers !)

    16. Re:Not so much a crisis... by tzanger · · Score: 1

      Things like IPSEC and such do not work through nat without non-standard encapuslation and such.

      AH won't work because the packets are being mangled, but ESP works just fine. I've set up dozens of Win2k--SuperFreeS/WAN links, many of them behind NAT.

    17. Re:Not so much a crisis... by ajs · · Score: 1

      All requests come in on the same IP, they all leave on the same IP

      Well, yes and no. One of F5's early claims to fame was their implementation of topographically unique inbound and outbound paths. Granted, the IP never changed, but "on the same IP" is ambiguous in your above statement.

      but there's a bank of machines on the internal network serving the request. It's transparent to the end user...no www-16 prepended to the URL, unless you want it there

      That's called load balancing, or address aggegation, or whatever your vendor of choice calls it. Every device that is capable of more than simple switching can do this, now.

    18. Re:Not so much a crisis... by gmack · · Score: 1

      Uhh no.. that's a singular option for assigning IPs to ethernet cards in a /48 space where the MAC is embedded as to the last part of the ip6 address. Thankfully it's not the only option.

      Personally I don't like IPs to change when I swap network cards.

    19. Re:Not so much a crisis... by Suidae · · Score: 2, Insightful

      NAT really does cause more problems than its worth

      If my cable modem provider would give me access without charging extra for every computer I attach, I would be happy to do without NAT. I don't see that happening, even if they have 50 bazillion addresses available, not when they can make another 5 bux a month per machine.

    20. Re:Not so much a crisis... by HuskerDu · · Score: 1

      Sorry, I made an assumption that the previous poster was talking about PAT [Port Address Translation] or one-to-one NAT. Back to IPSEC... the esp IP packet, due to the fact that it doesnt have source and destination port designations that PAT uses to distinguish different connections, gets "lost" in a PAT.

    21. Re:Not so much a crisis... by HuskerDu · · Score: 1

      Jesus... Way to screw up another post.

      PAT is in other words one-to-MANY NAT. /me bashes head on keyboard

    22. Re:Not so much a crisis... by Merk · · Score: 1

      One big reason they can get away with charging $5 a month for another IP is that there is some scarcity to IP addresses. Once IPV6 comes out I'm 100% sure they won't do this. It would just be absurd for them to pretend that with 6 x 10^23 per square meter of the Earth's surface, they can't provide you with more than 1 address.

      Instead, they'll have to come up with a sane way of billing people, based on the amount of bandwidth they use, the frequency with which they use high-priority traffic, or something similar.

    23. Re:Not so much a crisis... by Anonymous Coward · · Score: 0

      Even if each device is given its own IP, we still have to deal with ports as one device could be running multiple services, therefore multiple ports are necessary.

    24. Re:Not so much a crisis... by Anonymous Coward · · Score: 1, Informative

      According to the designers of the kame implementation, IPSEC was explicitly designed to be point to point or one to many. The ability to determine the source of an ipsec packet is part of the protocol.

      If you use NAT and you can't use header authentication then you do not support IPSEC completely, and actually, you make 1 of the 2 primary uses for IPSEC impossible, hence it is absolutely correct to say that NAT and IPSEC are incompatible. That one specific use happens to work doesn't change that.

      This was not done because the makers had somethign against NAT but because NAT and the idea of an authenticated point to point connection are simply incompatible.

    25. Re:Not so much a crisis... by Anonymous Coward · · Score: 0

      > NAT devices are becoming application aware, and they are NATing L4 ports and L7 payload

      That is a hack, and one that causes new problems whenever a new protocol is thought up.

      FTP is broken, and has been since its incarnation for the simple reason that it could as easily have been implemented as a multiplexed protocol, which would have prevented the need for this connect back idiocy.

      Any protocol that do such stuff makes assumtions about infrastructure that it can't make, and that are in many cases wrong.

    26. Re:Not so much a crisis... by xThinkx · · Score: 1

      Your home gateway (or maybe a specialized cell phone gateway) can route the packets to the appropriate device based on header values

      Right, because the average home luser will know how to configure and maintain a gateway/DNS. NAT requires a lot of work compared to ipV6 if it were implemented and everything just got its own ip. Remember, the common person isn't going to have the ability or want to maintain such a "complicated" system as NAT. The average luser will want an IP (just like a phone number) for each device. For example, even though most cell phones allow users to create a phone book that attaches names to numbers, a very simple 1-user DNS of sorts, there are STILL tons of ignorant people out there who dial the 10 digit number EVERY TIME. How hard is it to set the time on a VCR? I guarantee you at least 1/2 of the VCRs in the world are blinking 12:00. Devices should be available to the user with as little configuration as possible. Giving the user a device and saying "Here's your new techToilet, just connect to the following number and it will give you a list of commands" is a lot easier than saying "Here's your new techToilet, connect to this address, through this port, as long as that port isn't occupied, and make sure your techToilet is configured to use that port...."

      On the bright side, imagine the possibilities with almost everything having an IP. A few ideas I like

      • Leave your windows down in the car, just connect and remotely roll them up (a lifesaver if you drive one car to work and leave another at home)
      • Actual remote start on a car (warm the car up way before you see it)
      • Adjust heat/lighting/TV/music in your house so you can wine 'em and dine 'em by the fire with Barry White playing in the background
      • Remotely tell your Woznet device to shut down/alarm when you realize where it is
      • Receive remote alerts on everything, "The dishes are done", "Your car is being tampered with, press 3 to alarm"
      • Parents remotely monitor what their kids are watching on TV (I don't wanna hear any shit privacy people, you buy the TV, you get to know what whoever is watching it is watching)
      The list could go on and on, but the point is, the more stuff that's connected, the more benefits are possible (not quite 100% existant) for the user and us all.
      --
      Let's get one thing perfectly clear, I did not vote for George W Bush, and I do not endorse what he does or says.
      "
    27. Re:Not so much a crisis... by Nurgled · · Score: 1

      I think the original poster was saying that in the olden days we had "conventional ports" for services. We still have this for the older, more-ingrained services on the Internet. The conventional port for a web server is port 80, and the conventional port for SMTP is 25.

      Protocols of old are built on these assumptions. For example, MX and A records in DNS do not include port information, so in order to have a domain accepting mail the recieving server must be listening on port 25.

      We have DNS which provides reasonably-friendly names for hosts, but it doesn't map to a particular service. A single host will often have a multitude of different names which are all interchangable to get any service. If we are to stop using standardized port numbers, we will need to extend DNS so that 'www.google.com' can resolve to 216.239.39.99 port 80, not just 216.239.39.99 and leave the 80 up to the client to guess.

    28. Re:Not so much a crisis... by pHDNgell · · Score: 1

      NAT's are nice for giving a lot of computers access to the internet, but not good for putting a lot of services on the 'net itself.

      This should be emphasized. The internet has an abundance of consumers, but is greatly lacking in producers. We need more people making stuff and making stuff happen.

      --
      -- The world is watching America, and America is watching TV.
    29. Re:Not so much a crisis... by realdpk · · Score: 1

      There's no scarcity now - why would they stop charging once IPV6 comes out? It's not like ARINv6 won't charge the ISPs for the blocks they get.

    30. Re:Not so much a crisis... by RevDobbs · · Score: 1
      The average luser will want an IP (just like a phone number) for each device.

      No, the average user doesn't want an IP address or anything specific at all; he just wants it all to work. It is cake to setup up a wireless, or even a wired, network with little more than plugging together some consumer devices and maybe clicking around a webpage.* Telling your gateway "I have two refrigerators, here are there model #'s" would be just as easy.

      *Yes, it's a lot harder to setup up a secure wireless network, but it appears that few outside of this circle have the know-how to, or even care about, doing so.

    31. Re:Not so much a crisis... by smallpaul · · Score: 1

      If my cable modem provider would give me access without charging extra for every computer I attach, I would be happy to do without NAT. I don't see that happening, even if they have 50 bazillion addresses available, not when they can make another 5 bux a month per machine.

      If McDonald's had their way, they would charge you $30.00 (or at least $10.00) per hamburger. But they don't. Why do you think that is? Perhaps: competition.

    32. Re:Not so much a crisis... by yggdrazil · · Score: 1

      It wouldn't be very useful for your work computer, home computer, laptop, mobile phone and refrigerator to share the same IP-address through NAT. What if all the above needs to run a web server on port 80? Secondly, they all probably get IP connectivity from different providers, which makes it kind of difficult to let them share the same IP-address.

      Secondly, NAT breaks a lot of useful stuff. I wouldn't call an internet connection behind NAT a proper internet connection. Specially if you don't control the router doing the NAT.

      NAT is not the answer. NAT is just an ugly hack.

    33. Re:Not so much a crisis... by jonfelder · · Score: 1

      I don't know about you, but many people only have one cable company that serves them. In addition many of these people cannot get dsl. If that company decides to charge $50 per computer there isn't a whole lot you can do about it except drop broadband service.

      Also, the reason why McDonalds doesn't charge $30.00 for a hamburger is because people wouldn't pay it. Even if McDonalds was the only fast food joint in town, most people wouldn't see a value in paying $30.00 for sandwich they could make much more cheaply at home. Why do you think McDonalds and every other fast food chain charges you $1.00 for a coke that consists entirely of water and about $.01 of coke syrup? Perhaps: because people will pay for it.

    34. Re:Not so much a crisis... by goofymonster · · Score: 1

      Perhaps...but an ugly hack that has left the door open for v4 to continue to work until when...2005 supposedly? You may not have the power to control the NAT specifically, but I'm pretty sure if you tried really hard you could get a web page working on a port other than 80. The connections to home users won't be from Comcast for the TV and toaster, ATT for the toilet and Sprint for your PC. They will all route through a single provider (choose any one of the above or select other. The real issue will be trying to keep routing tables for a hundred-gazillion gadgets out there. I'm pretty sure my 7500 fully loaded won't cut the mustard.

    35. Re:Not so much a crisis... by jroysdon · · Score: 1

      Except when you forgot to tell your Tivo to record something and you want to talk to it remotely (I do this often, via SSH port forwarding, but lucky me I have 9 static IPs). Or you forgot a file on your home PC, and DAMN it sucks if you've got PPPoE and that IP keeps changing and for some reason your DynDNS service is flaking on you. Or you want to check your network of webcams while on vacation, but you don't want to publish them on the web (perhaps you've got a secure webserver at home). How about you want a lawn care service to manage your internet-enabled sprinkler system? Perhaps you've got a "smart" fridge, cupboards and trash that tracks all the food you have at home (or don't have), and you want to be able to get to it from your Palm, or a terminal at the store. I could go on and on with "silly" ideas that could actually take off if we had a reliable way to get to devices on our home networks.

    36. Re:Not so much a crisis... by jroysdon · · Score: 1

      Actually it can be used in as small as space as /64. Online stores, etc., are simply going to just love IPv6 and using the EUI-64 address as a "super-cookie."

      Not in reply to your post, but the previous post: it's not that long or mangled: It's simply your MAC with ff:fe padded inbetween and changing the first byte from "00" to "02". For instance:
      00-50-DA-22-91-49

      in EUI-64 would be: ::0250:DAff:fe22:9149 (note that I kept ff:fe lower-case to make it more readable).

      Personally, I love it. If you use radvd to advertise the LANs network address and the "well-known DNS IP" as secondary bindings on up to 3 servers on your network (could be anycast servers for really high redundancy) you really don't need DHCP at all as the client will just figure it all out automagically.

    37. Re:Not so much a crisis... by Tom7 · · Score: 1

      All of this stuff could be handled with endpoint solutions. (Except for dynamic IPs, and there's no reason to believe that wouldn't be a problem with IPv6, either). Port forwarding in NAT is the simplest, and stupidest way, but we could easily create a "home device network" protocol and run that all off the single external IP. (uPNP is trying, sort of.) This would be easier than IPv6 because it doesn't require changing the infrastructure of the entire internet.

  6. Bigger numbers. by Anonymous Coward · · Score: 5, Funny

    IPv6 will increase the supply of addresses from 4 billion today to a number in excess of 35 trillion that is "so big that there's not a word for the number,"

    how about "thirty six trillion" ?

    1. Re:Bigger numbers. by leshert · · Score: 5, Funny

      You forgot to put your pinky up to your lips.

    2. Re:Bigger numbers. by rleyton · · Score: 1
      Or how about a googol, which is 10^100 (written out as the numeral 1 followed by 100 zeros).

      That's big, I think you'll agree.

      --
      ooooooh! What does this button do? - DeeDee, Dexters Lab.
    3. Re:Bigger numbers. by brakk · · Score: 1, Funny

      Eleventy-billion!!!!!

    4. Re:Bigger numbers. by Surak · · Score: 3, Insightful

      IPv6 will increase the supply of addresses from 4 billion today to a number in excess of 35 trillion that is "so big that there's not a word for the number,"

      how about "thirty six trillion" ?


      I know. The whole statement is pointless. He may as well have said that IPv6 will increase the supply of addresses from 4 billion to a number in excess of 10 (...yada yada.) There are LOTS of numbers between 35 trillion and numbers that have no name.

    5. Re:Bigger numbers. by I.A.N.A.T. · · Score: 2, Funny

      IPv6 will increase the supply of addresses from 4 billion today to a number in excess of 35 trillion that is "so big that there's not a word for the number,"

      how about "thirty six trillion" ?


      Uhh...that's *three* words. RTFA.

      --
      Just because the U.S. is the greatest country in the world doesn't mean we're superior...oh wait, yes it does.
    6. Re:Bigger numbers. by questamor · · Score: 1, Funny

      It sounds a very kiddy thing to limit to. Like the following conversation between two kids:

      K1: "My dad is bigger than your dad and he's as strong as fifty neanderthals"!

      K2: "Well my dad is as strong as FIFTY ONE neanderthals"

      K1: 'shit. got me there'

    7. Re:Bigger numbers. by Esion+Modnar · · Score: 1

      So hyphenate it. Thirty-six-trillion. Voila! One word! Jeebus.

      --

      They say the first thing to go is your penis. Well, it's either that or your brain. I forget which...
    8. Re:Bigger numbers. by God!+Awful+2 · · Score: 1


      how about "thirty six trillion" ?

      Damn... I was betting that this remark would come within the first 3 posts. Looks like it took about 5.

      -a

    9. Re:Bigger numbers. by CGP314 · · Score: 1

      That's three : )

    10. Re:Bigger numbers. by BTWR · · Score: 1

      I agree. Just today there was an article on cnn.com about there being "70 Sextillion Stars" in the universe (70 million million million).

    11. Re:Bigger numbers. by mechaZardoz · · Score: 1
      or 3.6 quadrillion

      see: powers of ten

    12. Re:Bigger numbers. by Usquebaugh · · Score: 1

      But not as big as a googol plex

    13. Re:Bigger numbers. by Anonymous Coward · · Score: 0

      So hyphenate it. Thirty-six-trillion. Voila! One word! Jeebus.

      Hey, I can do that too! You-are-a-fucking-moron.
      One word.

    14. Re:Bigger numbers. by 4of12 · · Score: 1

      There's plenty of names for large numbers here.

      We need some good old-fashioned hyperinflation to help teach people about numbers with lots of zeroes.

      --
      "Provided by the management for your protection."
    15. Re:Bigger numbers. by frankthechicken · · Score: 3, Funny

      That K1 kid just gave up too easily, I'm pretty sure the usual arguments ran until the expected final twist of the sword,

      "Oh yeah, well my dad is as strong as INFINITY neanderthals!" And the reply of

      "That's nothing, my dad is as strong as INFINTY PLUS ONE neanderthals"

      Which is where I tended to get beaten up as I tried to explain the general stupidity of the concept expressed, usually compounded by my rection to their statement of

      "I'm a gonna give you an INFINITY PLUS ONE amount of beatings boy"

    16. Re:Bigger numbers. by Zuke8675309 · · Score: 1

      "But our amps go up to eleven!"

    17. Re:Bigger numbers. by Jester99 · · Score: 1

      Both your dads are wimps. My pop's got the strength of INFINITY TIMES INFINITY Neanderthals! :)

    18. Re:Bigger numbers. by stuuf · · Score: 3, Informative

      2^128=3.4028236692093846346337460743177e38

      According to the chart, thats 340 undecillion

      --

      Everyone is born right-handed; only the greatest overcome it

    19. Re:Bigger numbers. by Anonymous Coward · · Score: 0

      ... in excess of 35 trillion

      how about "thirty six trillion" ?

      hmmmmm i think i would stick to thirty-five trillion or more precisely in excess of thirty-five trillion rather than arbitrarily either: a) rename the numeral 5 as "six", or b) choose 36 trillion as a number in excess of 35 trillion.

      It is interesting how stupid people get when faced with really big numbers.

    20. Re:Bigger numbers. by Surak · · Score: 1

      Ummm...my pop's got the strength of ZERO MINUS INFINITY Neanderthals! Oh wait...

    21. Re:Bigger numbers. by dsmoses · · Score: 1

      Technically, there is not a word for the number. The key point being "A" word. There are multiple words that could be combined to represent the number. "thirty six trillion" is actually 3 words.

      But then anything over 20 would be regarded as "so big" by this definition.

    22. Re:Bigger numbers. by Anonymous Coward · · Score: 0

      Now it's three words and two hyphens, which is even less short.

    23. Re:Bigger numbers. by leshert · · Score: 1

      Indeed. The fact that a number has no name is irrelevant, since there are names for numbers both larger and smaller than the number of addresses in IPV6. You could easily say, "This rock is enormous: its mass in kilos is equal to 214.198748 times pi--a number that doesn't even have a name!"

    24. Re:Bigger numbers. by noah_fense · · Score: 1


      its actually 2^128 or about 3.403x10^38 address available for IPv6

      -n

    25. Re:Bigger numbers. by jrobertray · · Score: 1

      Actually, it's three hundred forty undecillion two hundred eighty-two decillion three hundred sixty-six nonillion nine hundred twenty octillion nine hundred thirty-eight septillion four hundred sixty-three sextillion four hundred sixty-three quintillion three hundred seventy-four quadrillion six hundred seven trillion four hundred thirty-one billion seven hundred sixty-eight million two hundred eleven thousand four hundred fifty-six.

    26. Re:Bigger numbers. by Tackhead · · Score: 1
      > Technically, there is not a word for the number. The key point being "A" word. There are multiple words that could be combined to represent the number. "thirty six trillion" is actually 3 words.

      How about "Assload"? IPv6 allows for an assload of IP addresses.

      Once you get past 35 trillion, I don't think it matters if it's a metric assload or an imperial assload.

    27. Re:Bigger numbers. by Anonymous Coward · · Score: 0

      Yes, and you probably got that by typing:

      (format t "~R" (expt 2 128))

    28. Re:Bigger numbers. by ParadoxDruid · · Score: 1

      Simple question that I googled and still haven't seen an answer to:

      How long is the IP address under IPv6?

      There are still servers that I visit (for games, etc), using the real IP address... like 131.107.164.10, a great Halflife server.

      That's 11 digits... I think I could easily remember 16 to 20 or so. Beyond that, I think I'd be straining to keep the different IP addresses all serperate in my head.

      So, how long is an address under the new proposal?

      --
      This statement is solely an opinion. Kindly take it as such in all cases.
    29. Re:Bigger numbers. by Anonymous Coward · · Score: 0
      Now it's three words and two hyphens, which is even less short.

      "Thirty six trillion"
      "Thirty-six-trillion"

      You count the chars; they're both the same len.

    30. Re:Bigger numbers. by Anonymous Coward · · Score: 0

      Anybody here know what an "ad hominem argument" is? It's used frequently here.

    31. Re:Bigger numbers. by Lxy · · Score: 1

      Dr. Evil: "We will give you four MILLION IPs!"
      Number 2: "Sir, we currently have 4 million IPs"
      Dr. Evil: "Oh, really... Then we will give you Thirty Six TRILLION IPs!"

      --

      There is no reasonable defense against an idiot with an agenda
      :wq
    32. Re:Bigger numbers. by Detritus · · Score: 3, Funny
      You should have said:

      "That's nothing, my dad is as strong as Aleph One Neanderthals"

      I read too many math books when I was a child.

      --
      Mea navis aericumbens anguillis abundat
    33. Re:Bigger numbers. by Anonymous Coward · · Score: 0

      128 bits. You are unlikely to remember actual complete IPv6 addresses - first of all, they are in hex, and many parts are optional.

      IPv6 is not exactly a new proposal, it has been present and usable in plenty of operating systems and routers for quite a while now.

      An IPv6 address might look like e.g. fe80::230:65ff:fe1d:739f (the address for the wireless LAN on my laptop - even if you don't use IPv6, interfaces are assigned automatic addresses with the fe80 prefix based on their MAC address).

    34. Re:Bigger numbers. by ParadoxDruid · · Score: 1

      Wait... doesn't that mean that to be accessible, every server (heck, every IP) will need to pay for domain registration?

      What am I missing.. If I have a home network under IPv6, how will I identify computers? Currently, my computers are 192.0.0.3 (desktop), 192.0.0.5 (laptop), etc...

      How will I identify them if the dang address is too long and obtuse to remember?

      --
      This statement is solely an opinion. Kindly take it as such in all cases.
    35. Re:Bigger numbers. by Virtex · · Score: 1

      Or, more specifically:

      2^128 = 340,282,366,920,938,463,463,374,607,431,768,211,45 6

      340 undecillion, 282 decillion, 366 nonillion, 920 octillion, 938 septillion, 463 sextillion, 463 quintillion, 374 quadrillion, 607 trillion, 431 billion, 768 million, 211 thousand, 456

      However, some numbering systems differ on the names they give to large numbers. For example, 10^9 can be either a billion or a thousand million, depending on your locality.

      --
      For every post, there is an equal and opposite re-post.
    36. Re:Bigger numbers. by frankthechicken · · Score: 1

      Yeah, it's one of those classic moments where I look back, realise what I should have said to destroy their arguements, in this case:-

      "Oh yeah, well my dad is as strong as 2 to the power of infinity Neanderthals"

      Though after a moment or two, I'm sure I would have still received my rightful beating

    37. Re:Bigger numbers. by Anonymous Coward · · Score: 0

      I never have liked that term, since it doesn't make sense in the 'bunches of three' that is our modern decimal system. One googol would be written as (spaces provided for line breaks):
      10,000,000,000,000,000,000,000,000,000,0 00,000 ,000,000,000,000,000,000,000,000,000,000,000 ,000,000,000,000,000,000,000,000,000,000,000

      I say we should officially name the number which corresponds to 10^99 to be the "decigoogol". Then we can rename the above number to be "ten decigoogols", since it obviously is at the 'tens' level. And no one will have any problem understanding exactly what we mean, because it will be metric.

    38. Re:Bigger numbers. by leshert · · Score: 1

      [cue ominous music]
      Dr. Evil: "We will deploy a world-wide network to which any business or personal computer can connect, called the [finger-quotes] "Internet". However, we will build into the [finger-quotes] "Internet" a limitation of four billion addresses. A few years later, when the network grinds to a halt because of the lack of address space, we will give out increased address space for... a hefty ransom..." [pinky-to-mouth]
      Number 2: Ahem... the Internet has been deployed, it is running out of address space, and the IETF is working on deploying IPv6, which provides a larger address space.
      Dr. Evil: Shit. Well, why don't we just do what we always do: find a vulnerability in Windows and send everyone an Outlook virus.
      [nods of agreement]

    39. Re:Bigger numbers. by aminorex · · Score: 1

      I wonder if this might be ( the smallest number which cannot be specified using less than 14 english words ) .

      --
      -I like my women like I like my tea: green-
    40. Re:Bigger numbers. by Bladzalot · · Score: 1

      Dude that was the funniest ever, you made my day, thanks :-)

    41. Re:Bigger numbers. by dacarr · · Score: 1

      Well why have over "thirty six trillion" when you can have (pinky to lip) over "three hundred forty undecillion"?

      --
      This sig no verb.
    42. Re:Bigger numbers. by Anonymous Coward · · Score: 0

      how about "thirty six trillion" ?

      That's three words! (and thirty-six-trillion won't work either).

  7. Okay, so what are we waiting for? by Trigun · · Score: 1

    Let's just deploy it! Nevermind the fact that a lot of equipment has to be upgraded. Never mind that nobody's really been playing with it, nevermind we're all in a recession. Let's just do it.

    1. Re:Okay, so what are we waiting for? by reidbold · · Score: 0, Funny

      Oh god! Billion dollar multi-national corporations will have to HIRE NEW PEOPLE to make the changeover! Capitilism is failing, the sky is falling!

      --
      -Reid
    2. Re:Okay, so what are we waiting for? by Trigun · · Score: 1

      No, but Mom&Pop shops will have to. Small businesses will have to. People being hit hard by the recession will have to.

      Quick and painless this is not, otherwise we would have done it a long time ago.

    3. Re:Okay, so what are we waiting for? by reidbold · · Score: 1

      What, they'll have to apply a patch to their router?

      --
      -Reid
    4. Re:Okay, so what are we waiting for? by Anonymous Coward · · Score: 0

      newsflash: recession ended (mathematically) in november 2002 ... wake up and read

    5. Re:Okay, so what are we waiting for? by Trigun · · Score: 1

      If only it were that easy. Dollars to donuts that not every single home lan gateway can be upgraded via firmware.
      Not to mention the patch to their operating systems, the new need for firewalls which are properly configured. Hell, most people don't even change the default passwords on their routers. Port scan your network for open web ports some day. 90% of them are DSL or Cable routers with default passwords.

      You think there's a problem with script kiddies now, wait until there are 2*10^38 potential addresses to own, running unpatched, unfirewalled, unadministered typhoid mary of the internet operating systems.

    6. Re:Okay, so what are we waiting for? by Anonymous Coward · · Score: 0

      newsflash: Mathematically, we shouldn't be here. Yet here we are.

      Let me be the first to assure you that the recession is NOT over, especially when the recent tax cuts have to be paid back, war in Iran and Syria breaks out, and the U.S. starts drafting citizens.

  8. Money talks by Kombat · · Score: 4, Insightful

    As with everything like this, the powers-that-be (i.e., the telcos and ISPs) will drag their heels until they are either forced to change, or they are convinced it will increase profits. Expect the changeover to go extremely slowly. Expect providers to try every trick in the book to milk their existing network for every last day they can possibly profit from it. The fact that the economy is in the toilet doesn't help either.

    --
    Like woodworking? Build your own picture frames.
    1. Re:Money talks by binaryDigit · · Score: 1

      As with everything like this, the powers-that-be (i.e., the telcos and ISPs) will drag their heels until they are either forced to change, or they are convinced it will increase profits

      What cads, for them to drag their heels on such a lofty goal at the expense of profits and even survival (for many of them in this "economy that is in the toilet"). Of course every nerd will run right out and purchase ipv6 hardware/software (or take the time to upgrade if no purchases need to be made) immediately without "dragging their heels" regardless of their financial situation or they're convinced that they can download porn faster and regardless of whatever else is going on in their lives at the moment.

    2. Re:Money talks by ibpooks · · Score: 1

      That's because THERE IS NO INCENTIVE WHATSOEVER to upgrade. Why in the hell would a company spend money on personnel, training, equipment, planning, customer change-overs, etc when the network will work just like it did before? I'm certainly not willing to pay more for my cable modem to get an IPv6 address when the IPv4 one works just fine, no one else is either. It's not like the ISPs manufacture money -- it all comes from you and I.

    3. Re:Money talks by stonecypher · · Score: 3, Insightful

      As with everything like this, the powers-that-be (i.e., the telcos and ISPs) will drag their heels until they are either forced to change,

      Except that there's been v6 connectivity for sale in almost every major city for years, now. Notably, Pair Networks has offered it since 1999. IIRC, and this might be wrong, Internet2 has been v6 since early on, maybe since day one.

      or they are convinced it will increase profits

      It will, as soon as the number of v4-only software and devices stops rising. Integration of IPv6 support into the RADs that all these software weenies use will help, though it's sort of a chicken-and-egg problem: nobody's gonna provide v6 connectivity until there's something to do with it, and nobody's gonna support it due to the hassle and the fact that they don't know anyone that has it.

      It would be nice if Internet2 would open some of its resources to the real, messy internet; that'd be the sort of kickstart that'd get the whole goddamn thing underway.

      Expect the changeover to go extremely slowly.

      That's why we're making another IP, instead of replacing it altogether with something new. In theory, it shouldn't much matter; NAT and some dedicated hackery should make the two sort of kind of interoperate a little bit.

      Kinda. (grins)

      Expect providers to try every trick in the book to milk their existing network for every last day they can possibly profit from it

      Yeah. That's called "good business." Besides, the fiber and wire don't need to be replaced; just the routers, and in some cases the end connection equipment (DSL modems that only do PPPoE, for example.)

      By the way, I hate alcatel.

      The fact that the economy is in the toilet doesn't help either.

      Um, yes it does. Labor costs are down. Material costs are down. Land costs are down. Telcos aren't hurting so badly that they can't keep up the constant hardware upgrades they're doing. The economy actually helps quite a bit. They do the work for cheap, make estimations based on current market usage, then the money comes back (like it always does,) usage goes through the roof when people have enough money to try to change the way we buy dog food ("the net is the future, man pass the bong, I'm gonna be rich",) telcos overearn predictions, foolish investors think they're a good investment, they get money, the ceos do something horrible and amoral, everyone gets horrified and starts asking for inquiries, all the money goes away, and so it goes.

      --
      StoneCypher is Full of BS
    4. Re:Money talks by Jackazz · · Score: 1
      and what is wrong with trying to turn a profit instead of jumping to install every new technology?

      why don't you invest billions of dollars in a new network and show them who the boss is!

    5. Re:Money talks by mnmn · · Score: 1

      The fact that the economy is crap is exactly why the governments should push for ipv6. The resulting sales of software and hardware to the companies will create a small economic boom.

      And yes we dont need 100 IP addesses each since 1 megabyte of RAM is all we need right now. I dont mind my watch transferring the latest news from my friend's watch in the wilderness while my glasses stream the data in to display it. Sometimes I do think ipv6 has too many addresses and can be less bloated in the header(how many thousands of IP addresses can each person use if the population was 100 billion?), but anything is better than the pinch of ipv4 right now especially in asian countries where the geeks cannot run their own apache servers.

      --
      "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    6. Re:Money talks by Anonymous Coward · · Score: 0

      Please explain to me what the hell your cablemodem has to do with getting an IPv6 address?

      The cablemodem's job is to give you an ethernet link. The IPv6 protocol is encapsulated within the link. A cablemodem is perfectly capable of handling ipv6.

      Furthermore there is an incentive to upgrade if the Internet does run out of address space. I for one would love to see an end to NAT. It is a constant pain in the ass to deal with. ISPs would have no reason not to give customers more than one (if not many) IP address, short of being greedy pigs.

    7. Re:Money talks by djmitche · · Score: 2, Informative

      Has anyone looked at the major carriers? Most mid- to large-scale ISPs will now provide IPv6 transit to those who ask. If you ask and the answer is no, there are other ISPs out there that will say yes. The backbones are ready, and the effects are reaching into ever-smaller ISPs. Clients are just waiting for the need.

    8. Re:Money talks by jroysdon · · Score: 1

      UUNET/MCI: IPv6 is not a service we offer at this time.

      Sprintlink: Non-production 6Bone tunneled-only, they'll be testing dual-stack IOS code in very limited deployment in 8 months. No SLAs available.

      SBC (not that I'd call them "large-scale, but definately midsized, and they just happen to be my DSL ISP and that of a number of large clients with T1s and government clients with DS3s): "Huh, what's IPv6?"

      HE.net is more of a hosting provider, but I know you can get native IPv6 from them.

      I hear NTT/Verio will be rolling out IPv6 here soon (already have it in Japan).

      Care to name some more ISPs you can go native IPv6 with in the US and provide some linkage to back it up?

      But I do suggest emailing and calling your ISP. Let them know you want it. Hell, let them know what it is in most cases.

    9. Re:Money talks by jroysdon · · Score: 1


      Looks to me as if Pair Networks is more a webhosting company. Much easier to "deploy" IPv6 in that sort of enviroment. Get a leased line to an 6Bone peering site, enable some BSD/Linux routers (as Cisco didnt' even have production IPv6 code a year ago), and there you go.

      Perhaps I googled for the wrong Pair Networks?

  9. Is no one using NAT? by ivanmarsh · · Score: 0

    I would have thought that the invention of NAT would have taken care of this. You only need one IP address per organization/company/household.

    Is it time for private networks to be manditory?

    1. Re:Is no one using NAT? by Anonymous Coward · · Score: 2, Informative

      Well yes and no.

      NAT works fine for most things, ie. web browsing and the likes. Running services on machines behind NAT isn't difficult either. But wow does it ever become a nightmare if you try to play games behind NAT. Let's face it, the average user does not have the desire to play around with udp port forwards and transparent proxies and dum dum dum just to get starcraft to work.

      And let's not forget broadband ISPs wanting you to pay for extra machines even when you're using NAT (and threatning you, too). So if they're going to make you pay for an extra IP or two, what's the point of doing NAT?

    2. Re:Is no one using NAT? by Anonymous Coward · · Score: 0

      Redistributing out the IPv4 ip addresses would work, too. Places like MIT have a stupid ridiculous number of them. They have so many IP addresses that they _retire_ them when they retire a machine.

      IPv4 is a fine standard, but the way they're divided up is just moronic. Moving to IPv6 should be done as soon as possible, because it's eventually going to happen anyway. If it's done now, maybe it'll pokke the economy in the ass.

    3. Re:Is no one using NAT? by ivanmarsh · · Score: 2, Interesting

      We're going to switch the entire world to an unproven, currently widely unsupported IP stack based on the idea that gamers are too stupid to forward a udp packet?

      If you've got your machine running with a public address and your not behind a firewall you're an idiot and your input into the future of the internet shouldn't hold much weight.

      If you are running a firewall it's one more minor step to forward a packet. ...or go spend $70 on an internet gateway router that you can fill in two boxes on (IP Address and port) to do port forwarding.

      I run a home private network and a corporate network with 600+ nodes on it and I'm using 5 IP addresses.

      Most ISP's that charge per machine are actually charging per routeable IP. I've had that conversation with Charter. They don't care how many machines you're running on your private network as long as they aren't nabbing IP's from the DHCP.

      Perhaps it's time to find a new ISP?

    4. Re:Is no one using NAT? by Anonymous Coward · · Score: 0

      dude i'm a network admin, and you don't have any idea what you're talking about. i think you're a windows user, and you work at dairy queen.

  10. Duplicate story... by brooks_talley · · Score: 4, Insightful

    I'm sure I saw this exact same post on /. in 1998. Except then it said we'd run out of addresses by 2000.

    Hello? There's this thing called NAT, you see, and in many ways it's preferable to not have every one of your 100 IP-enabled devices sitting there on the real internet just waiting to get hacked.

    Cheers
    -b

    1. Re:Duplicate story... by I.A.N.A.T. · · Score: 0

      Hello? There's this thing called NAT, you see, and in many ways it's preferable to not have every one of your 100 IP-enabled devices sitting there on the real internet just waiting to get hacked.

      Well, I for one hope that someone hacks my washer and dryer and starts em so I don't have to actually *type out* 'cycle start -extra_rinse Y -cycle_type delicate -second_spin Y -no_buzzer'
      yay for the days of just pushing the button on the front of the thing. you know, when you put the clothes in....
      and really, what does an ip-enabled coffeemaker do that one with a timer doesn't? I mean, besides sending you an IM when your coffee's done. Don't you have to actually walk to the fucking thing to put in ingredients/take out finished product anyway? Are we going to have to carry a PDA around now, just so the fridge opens? Sometimes I think we should all go back to reel mowers and boiling coffee on the stove. Pretty soon we're all going to look like fucking veal cattle.

      --
      Just because the U.S. is the greatest country in the world doesn't mean we're superior...oh wait, yes it does.
    2. Re:Duplicate story... by Anonymous Coward · · Score: 1, Funny
      Hello? There's this thing called NAT, you see, and in many ways it's preferable to not have every one of your 100 IP-enabled devices sitting there on the real internet just waiting to get hacked.

      Tell me about it, it took me weeks to get my electric bidet back on line after it was 0wn3d.

    3. Re:Duplicate story... by vadim_t · · Score: 1

      There's a fairly unknown thing, called "firewall" that can let you have 100 computers with an IP on the internet for each, while still denying access from the internet to them. Works as well as NAT for "protection", except that when you want to let two people play the same game you can allow it without any problems.

      BTW, a firewall doesn't help that much against getting hacked. Having secure services is much more important.

    4. Re:Duplicate story... by Neophytus · · Score: 1

      and when you have multiple instances of an app that both need specific ports fowarded, it creates a problem

    5. Re:Duplicate story... by Anonymous Coward · · Score: 0

      I'm sure I saw this exact same post on /. in 1998. Except then it said we'd run out of addresses by 2000.

      Er, yes... But see what happened was we missed a decimal in the calculations, and now the end of the world is going to be in... Oh, wait, wrong one.

    6. Re:Duplicate story... by PhunkyOne · · Score: 1
      I can just see it now, all of your 100+ household appliances getting hacked because they are wide open the net. Those damn script kiddies, why couldn't they have stole my credit card numbers instead of thawing my freezer, overflowing the toilet, and turning my airconditioner to 45F.

      Remember the good old days when people just defaced your website or sent you spam :)

    7. Re:Duplicate story... by inertia187 · · Score: 4, Funny

      The things we think of as futuristic always changes by the time that date gets here. "Where's my flying car?" I asked my grandmother what she thought was "futuristic" when she was a kid. She told me that everything would be attached to those scissors things that extend. She and I didn't know what they were called. Back then, some phones would be attached to the wall with this invention, and it was super high tech for the day. Her idea of futuristic was to have everything in the kitchen on this rig. Coffee maker, spice rack, everything.

      Now, had they actually made a kitchen with this device, she would have seen how ridiculous it was.

      Just because Bill Gates thought the idea of IP addresses assigned to everyone and everything doesn't mean it was a good idea.

      --
      A programmer is a machine for converting coffee into code.
    8. Re:Duplicate story... by Merk · · Score: 4, Informative

      Say you have 5 servers behind a NAT box, all running SSHD. How are you going to set them all up so that they can have incoming connections? Sure, if your NAT box is a good one you can manually set up port forwarding, but that's a pain.

      What about strange services like FTP that require 2 different connections? They're always a pain when using NAT, so you need to find some means of dealing with them.

      What about games? Say 3 people behind one NAT box want to play the same online game at the same time? What about filesharing applications that want to allow incoming connections?

      NAT != firewall. If you're using it like it is, expect to get hacked anyhow. Besides, if you don't want a particular device to be exposed to the IPV6 world, you are free to put it behind a NAT box or a firewall, it just means that the machines that you want to have routable addresses can have them.

      I already want more IP addresses. I have a server which hosts websites for various domains, but only uses 1 IP address. That works for HTTP because it sends the hostname as part of the request, but nearly every other protocol doesn't. That means that I can't deal with HTTPS easily, and makes configuration of things like mail much harder. If each host could have its own IP then it would make management and configuration much easier. It would also make it possible to have much more fine-grained control over services and access to various IPs.

      I can just picture you when they finally start selling flying cars: "Hello? I already have transportation, it's called a car. In many ways it's better to move slowly in gridlock. At least that way if you have an accident you're only moving 4 miles per hour!"

    9. Re:Duplicate story... by chef_raekwon · · Score: 1

      dude

      the answers to these questions, and more, can be found on the internet.

      the sshd thing is simple to solve. change the bloody port on each server. do you have to use 22?

      fsck ftp. use sftp. and scp.

      NAT!=firewall, but NAT + IPTABLES does.
      so, dont expect to get hacked, unless the hacker is quite good --- and most of them routers/dsl modems, etc, have this built in.

      some people need a few more ips for SSL, this I will grant you, because of the nature of the protocol, but...aside from that, you can serve up hundreds of websites on the same IP. those that require IPs for SSL should get them. Not everyone on this planet needs an SSL enabled website, or even an IP, let alone 100.

      --
      We're like rats, in some experiment! -- George Costanza
    10. Re:Duplicate story... by Merk · · Score: 0, Redundant

      The workarounds for many of these problems exist, but they're not solutions, they're workarounds.

      Which is easier to type? "ssh box1.mydomain.com" or "ssh nat.mydomain.com -p 10022"? Using a default port for various services is a very handy thing. Most programs assume the default port for a given service, and when they do offer an alternative sometimes you have to dig around in the "advanced" menu to choose it. For a while in Mozilla there was no obvious way to choose a non-standard mail port, for example. If I want to let my mom use a mail server i'd rather just give her a machine name rather than have to make it complicated.

      The "use sftp/scp" solution fails the mom test too. If I want to allow my mom to upload pictures of the latest trick the dog learned, I'd like to be able to say "Ok mom, open up Safari. Ok, now type: ftp, colon, double forward slash (the ones that lean to the right mom), then ftp dot mydomain dot com..."

      Aside from those difficulties, NAT is just a hella-inelegant solution. The way the TCP/IP and UDP/IP were designed, machines are distinguished by an address, services are distinguished by a port. It's simple, clean, easy to use... NAT breaks that model.

      Do most off-the-shelf routers use IPTABLES? If so, that's great, but kinda useless. The configuration interface they offer doesn't let me do what I want to do with IPTABLES. If I can't tweak the settings the way I like then it's essentially not running a firewall as far as I'm concerned.

      As for getting hacked through the NAT box, it's easy. Someone port-forwards mail, web and filesharing through the box to their desktop machine. Suddenly any mail exploit is available to the Internet. The user feels comfortable because they've got a firewall, but the "firewall" just forwards all malicious traffic right to the target machine.

      The only firewall-like capability that the off-the-shelf NAT routers offer is that ports are not explicitly open like they are on Windows machines. But that's a pretty weak form of protection.

      The no-NAT model of communication is so much more straightforward. If I want to get a packet from machine A to machine B, I fill in the appropriate headers, and voila. NAT adds complexity that really doesn't need to be there. It also severely reduces the flexibility of the whole system.

      NAT has its places, but it is not the solution to every problem. It is good for allowing web browsing from a non-routable IP address, Anything more complicated than that becomes a bigger and bigger headache. Why bother with the headache, just use a real firewall and make all the address routable!

    11. Re:Duplicate story... by SCHecklerX · · Score: 1

      If you are NATing, then you are already using a firewall. You can firewall real addresses without having to NAT them, you know.

    12. Re:Duplicate story... by asdfghjklqwertyuiop · · Score: 0, Redundant

      the sshd thing is simple to solve. change the bloody port on each server. do you have to use 22?

      Gotta ssh into one of my machines at home. What port was that on again? 8022? 9022? Can't remember... I'll just try 8022 and see... oops, 8022 is machine X, 9022 must be the machine I want. Port numbers are so much more intuitive than hostnames.

      Time to add a new machine to the network. Its running sshd. Gotta log into the NAT router and figure out what port can be used. And remember that it was that port.

      Boy, that is so simple. Almost as simple as just sshing to machinex.domain or machiney.domain.

      fsck ftp. use sftp. and scp.

      Yeah, just fsck every other protocol too that happens to assume that the network is set up the correct way.

    13. Re:Duplicate story... by Nurgled · · Score: 1

      It would be nice if web browsers would start to support SFTP in similar vein to how they support FTP.

      It's handy to be able to fall back on a web browser (which pretty much everyone has) rather than having to download and install a special client for a one-off task.

      The only major complication is that SFTP does not (to my knowledge) have a standard way to do an anonymous login.

    14. Re:Duplicate story... by chef_raekwon · · Score: 1

      you make some very valid points.

      however, i see some confusion in your user base ---
      on one hand, we see your mother trying to upload anything (which im sure it will be hard, NO MATTER what protocol you use, and im not being personal) and on the other hand, we talk about port forwarding to internal servers.

      for the most part, and i'd be a bit slim on this number, but 80-90 percent of people who buy dsl/routers, with the built in firewall, simply have all of the ports closed. They arent trying, and usually dont have a server to port forward to...let alone their Desktop...
      however, if they needed to, the setup of the router is identical to iptables setup. you tell the interface what port you need opened, and to where...its quite simple really.
      ----and who port forwards filesharing?

      agreed that NAT isnt extremely elegant...but, there really should only be a single point of reference for smaller networks...in fact, even in large networks, with routed IPs, they too only have a single or few points of reference to the internet....these are the basis for security...

      as for SSHD, it is rather easy to recall 5 machines (from the other post) -- just put them in order....port 1001, 1002,1003,1004,1005. whats so hard about '-p 1001'? its only an extra 6 strokes...and if you create a little script, called 'firewall', or a script called 'webserver' and a script called 'mailserver' you dont even need to type or remember anything. its already done....

      ofcourse, these _are_ 'work arounds', but isnt that what Linux is?

      --
      We're like rats, in some experiment! -- George Costanza
    15. Re:Duplicate story... by Merk · · Score: 0, Redundant

      Regarding my mother: she's good enough to use IE to upload a file using FTP (if I walk her through it). I'd be the one setting up port-forwarding so she can upload the file to me. She would not be able to do SFTP or SCP because there's no friendly GUI for doing it already loaded onto her computer.

      I'm not sure what you mean about a single point of reference for networks. If you mean all traffic should flow through a small number of routers, sure. If you mean that most machines should be behind a NAT box, I don't agree. I think they should be behind a firewall, but NAT shouldn't be used instead of a firewall.

    16. Re:Duplicate story... by booch · · Score: 1
      Say you have 5 servers behind a NAT box, all running SSHD. How are you going to set them all up so that they can have incoming connections? Sure, if your NAT box is a good one you can manually set up port forwarding, but that's a pain.


      At that point, you'd probably want an SSH Proxy. Besides, proxies provide a lot more security than packet filters.


      What about strange services like FTP that require 2 different connections? They're always a pain when using NAT, so you need to find some means of dealing with them.


      FTP should die. It's counter to all networking principles to have the server initiate a connection back to the client. Besides, most of the time you'll want the security of SSH/SCP. If not, use a proxy on your NAT box.

      --
      Software sucks. Open Source sucks less.
    17. Re:Duplicate story... by Anonymous Coward · · Score: 0

      ...except FTP has had a workaround for NAT and firewalls since about 1998. It's called Passive Mode.

    18. Re:Duplicate story... by Anonymous Coward · · Score: 0

      Yeah, the whole world should revolve around what your fucking mother has loaded on her machine.

      Get real you fucking crybaby.

      NAT has its place. Get over it!

    19. Re:Duplicate story... by ysachlandil · · Score: 1

      Who says we are about to run out of IP's???

      Last time I checked the bogons list (bogons are networks that are reserved by IANA), more than ONE THIRD of all the IPv4 addresses are still reserved, eg: ready to be given out!

      So that means there are still more than 1 billion IP's left, I think that's plenty to get to 2010

      (And another thing, if IANA/RIPE/ARIN/whoever wanted us to use/test/play with IPv6, why are they killing off 6BONE?)

      --Blerik

    20. Re:Duplicate story... by chef_raekwon · · Score: 1

      the AC post made me laugh...
      i guess he wasnt following the thread.

      anywho...my point is this: NAT should be used in conjunction with a firewall. it just makes sense...
      we'll agree to disagree

      and on a lighter note --- WinSCP2.2 is available and is a really easy to use app for windows...
      might make your life easier with mom.

      cheers!

      --
      We're like rats, in some experiment! -- George Costanza
    21. Re:Duplicate story... by Merk · · Score: 1

      My mom uses OS X, which does make her life easier, but means things like this don't help much. *shrug* Think I should introduce her to the Terminal?? ;)

      Anyhow, I agree that NAT/Firewall is a good solution for many things, but I think that the emphasis should be on firewall rather than NAT. My personal opinion is that a machine which needs 2 way communication with the Internet (which really is most of them) should by default be given a routable IP and then protected by a firewall. That opinion is scary for most network admins, but it just means that they can't be lazy about the firewall.

  11. Actually... by Kickstart70 · · Score: 0, Funny

    I'm kind of hoping to not have any IP addresses in 10 years. I'm becoming rapidly overwhelmed by technology even though I've been a working linux admin for 10+ years.

    1. Re:Actually... by Shriek · · Score: 0
      I'm becoming rapidly overwhelmed by technology even though I've been a working linux admin for 10+ years

      I thought you have been a Linux admin for the past 13 years?!?!
  12. Impending IP Crisis announced ... by Etyenne · · Score: 1, Funny

    ... film at 11.

    --
    :wq
  13. New security implications... by southpolesammy · · Score: 4, Funny

    I wonder how long it will be before we have a washing machine buffer overflow...

    Apartment dwellers below the afflicted system should take precautions now....

    --
    Rule #1 -- Politics always trumps technology.
    1. Re:New security implications... by Gothmolly · · Score: 1

      Or a toilet buffer overflow.

      --
      I want to delete my account but Slashdot doesn't allow it.
    2. Re:New security implications... by Anonym1ty · · Score: 1

      Or having your toilet get a DOS attack and FLOODED off the net

    3. Re:New security implications... by Anonymous Coward · · Score: 0

      The only thing I don't get is why a washing machine has become a mission critical device needing immediate repair.

      I'm all for this internet doohickey, but I'm not totally opposed to calling up the repair guy...or *gasp!*, trying to fix something mechanical myself.

    4. Re:New security implications... by sharkey · · Score: 1
      I wonder how long it will be before we have a washing machine buffer overflow...

      That's what the drain in the floor is for, isn't it?

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  14. So big by tchdab1 · · Score: 1

    "...a number in excess of 35 trillion that is "so big that there's not a word for the number..."

    Um, I think 35 trillion, 350 trillion, or whatever, is a good word for the number, don't you?

    1. Re:So big by I.A.N.A.T. · · Score: 0

      Um, I think 35 trillion, 350 trillion, or whatever, is a good word for the number, don't you?

      What makes all you idiots think that thirty-five trillion or three hundred and fifty trillion or however many trillion is ONE WORD? it doesn't say 'a number so big it cannot be described at all', it says a number so big there isn't A WORD for it. the largest number you can express in ONE word is ninety. (shut the fuck up about infinity, yeah, I heard you. If you think infinity is a number, write it out for me.) Anything larger than that requires qualification. Yes, the guy's a dumbass...but not for the reasons you're supposing.

      --
      Just because the U.S. is the greatest country in the world doesn't mean we're superior...oh wait, yes it does.
    2. Re:So big by jonfelder · · Score: 1

      Why is everyone quibbling over this point? He's not saying that there aren't numbers in excess of 35 trillion that aren't named (i.e. 36 trillion). He's saying that the number of addresses is more than 35 trillion and it's so big there isn't a word for the number.

      This of course isn't true it's ~340 undecillion...but that's a seperate point.

      35 trillion is just an arbitrary value he picked...yes he could've picked 350 trillion...or a 1 quadrillion...or any other largish number to illustrate the point that it's a !%*#$ large number of addresses.

  15. i'm missing what here is 'news'... by *weasel · · Score: 5, Insightful

    unless a new prognostication that 'the end is nigh, in 2005' passes as news. everyone knows it's gonna happen. just as we all know that with NAT and proxies, most of it can be safely delayed by tech companies until they have an outside fiscal force to upgrade.

    and i doubt my fridge will have an IP address anytime -before- ipv6 starts to be rolled out en masse.

    as with all pure tech - it needs that killer app. something needs to come out that is so fantastically great that everyone has to have it - and it needs to require ipv6. until then - at best we'll be going dual-mode.

    good luck finding that app, and educating users what it is, and what it does.

    --
    // "Can't clowns and pirates just -try- to get along?"
    1. Re:i'm missing what here is 'news'... by Anonymous Coward · · Score: 0

      >and i doubt my fridge will have an IP address >anytime -before- ipv6 starts to be rolled out en >masse.

      has anyone even asked WHY your appliances haveto have an IP address?

      we go along with these stupid premises like lemmings.

      Im still waiting to see how these darn tooting computers are gonna make our office 'paperless' (remember that canular?)

      zack

    2. Re:i'm missing what here is 'news'... by *weasel · · Score: 1

      my frige needs an ip so they can charge me absorbitant rates to automatically populate a web-accessible shopping list when i'm out of milk, or even charge me more to have milk ordered and shipped.

      any failure to deliver on a paperless office though, is solely due to bad, misdirected or understaffed IT. if your office wants it, you have it.

      --
      // "Can't clowns and pirates just -try- to get along?"
    3. Re:i'm missing what here is 'news'... by CubicDDD · · Score: 1

      as with all pure tech - it needs that killer app

      Hey, IPv6 got MP3-Streams !

    4. Re:i'm missing what here is 'news'... by CanSpice · · Score: 1
      and i doubt my fridge will have an IP address anytime -before- ipv6 starts to be rolled out en masse.
      Fry's in Portland, Oregon, was demoing a fridge that was internet-ready. Here's a picture.
    5. Re:i'm missing what here is 'news'... by jroysdon · · Score: 1


      Actually, last I heard the 6Bone's 'end was nigh,' slated for 6/6/2006.

  16. Do the math by L.+VeGas · · Score: 1, Funny

    IPv6 is only 50% bigger than IPv4.

    Someone needs to recheck their figures.

    1. Re:Do the math by Anonymous Coward · · Score: 0

      This is official the worst troll ever on slashdot.

    2. Re:Do the math by eht · · Score: 1

      IPv4 = 2^32 = 4,294,967,296
      IPv6 = 2^128 = 3.4028236692093846346337460743177e+38

      Yep, looks like someone needs to check their figures, and I think it's you.

    3. Re:Do the math by L.+VeGas · · Score: 1

      Ha ha. You're trying to trick me.

      4 * 1.5 = 6

      IPv4 * 1.5 = IPv6

    4. Re:Do the math by eht · · Score: 1

      Sorry, I wasn't aware you were going for the humor angle.

    5. Re:Do the math by L.+VeGas · · Score: 1

      Probably because it was way more stupid than funny.

    6. Re:Do the math by lauterm · · Score: 1

      Actually, IPv4 is a 32 bit addressing scheme allowing for 2^32 or a little over 4 billion addresses. IPv6 is a 128 bit scheme allowing for 2^128 or 3.40e38 address. That is the current number raised to the power of 4. I hate to link to the enemy but it is the only place I could readily find the info.

    7. Re:Do the math by Pontiac · · Score: 1

      OK explain your math then..

      IPv4 is a 32 system..

      every added bit doubles the number of addresses.
      so where 32 bit addressing has 4294967295 addresses

      A 33 bit system would have 8589934591 address.

      IPV6 is a 128 bit system..
      Do the math!

      --
      If you think it's expensive to hire a professional to do the job, wait until you hire an amateur. --Red Adair
    8. Re:Do the math by Anonymous Coward · · Score: 0

      Christ, you idiots! He was making a joke. 6 is 50% bigger than 4.

    9. Re:Do the math by shish · · Score: 1

      erm... if you add one byte, you get another 255x the address space. IIRC IPv6 uses six bytes instead of four, so you'll be getting 65535x the current address space.

      IPv4 = 255.255.255.255 = 4228250625 (4 thousand million)
      IPv6 = 255.255.255.255.255.255 = 274941996890625 (274 million million)

      I use millions because IIRC the US has different sized billions to everyone else...

      Sure there's still addresses reserved to be cut out from that, but not *that* many.

      --
      I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
    10. Re:Do the math by Anonymous Coward · · Score: 0

      Not in Binary..

      6=110

      4=100

      both 3 bits :)

    11. Re:Do the math by eht · · Score: 1

      It's funny enough, but it's like the April Fools days articles here on slashdot, funny sure, but sometimes hard to tell between what is a joke and what is meant to be serious.

    12. Re:Do the math by Mooncaller · · Score: 1

      I would have figured most people would heve seen the joke. I guess some /.ers were partying a little to heavy last night. So instead of being a joke it has become a troll. And look at the number of bites it got. WOW!

  17. each ip has 65k ports! by ender_wiggins · · Score: 1

    Dont rely on ips, but use the ports! its not like most ISP's will give you a class c range for your house! just get one and use diffrent ports for your fridge.
    didnt we have an artical about this with china? someone really wants everyone to go with ipv6.

  18. The evil NAT by Anonymous Coward · · Score: 1, Informative

    Well, you know what everyone is going to do until IPv6 becomes a reality... NAT everything to death.

    That ruins the original point of the internet while giving everyone the illusion that they've found the answer. I've even heard of some ISP's that only issued 10. addresses. We need to start telling people that NATing is not the answer before we are going to get people to see the problem for what it is. And once they see, they will begin to switch over to IPv6.

    1. Re:The evil NAT by beernutz · · Score: 1

      Ok, so what the HELL is wrong with NAT? It seems an elegant solution to me. In addition to allowing you to route ports to ONLY the machines you want, it allows you to add machines as you wish, with out the worry that it is just sitting open and bare to the world.

      --
      (stolen from DaBum) I am dyslexia of borg - your ass will be laminated.
  19. IP Shortage by RadioDude · · Score: 1

    Has it occurred to anyone that many of us don't WANT every light switch in our homes to have an IP address? We don't NEED to hear, at 0300, a disembodied voice from the kitchen saying "this toaster has committed an illegal operation and will be shut down". We don't need hackers flushing our toilets, opening and shutting the garage door at random, etc.

    1. Re: IP Shortage by deman1985 · · Score: 1

      Personally, i wouldn't mind hackers flushing the toilet in my apartment in case one of my roomies doesn't think to... ;)

    2. Re: IP Shortage by caluml · · Score: 1

      You complete idiot. Do you honestly think that is why people want IPv6? Numbnuts.

  20. overdramatic by sstory · · Score: 4, Insightful

    Isn't this a little overdramatic? Crisis? Having to switch to an updated protocol is a crisis?

    1. Re:overdramatic by Surak · · Score: 1

      THE *SKY* IS FALLING! THE SKY *IS* FALLING! THE SKY IS *FALLING*!

      Doomsday is here! When the IP addresses run out, The Dark Lord Sauron and his minions shall RULE MIDDLE EARTH! Muhahahahahah!

      Puhleeze. Between NAT and IPv6 I think we've got this covered. :)

    2. Re:overdramatic by bheerssen · · Score: 1

      It's a crisis for the people who implement the protocols: ISPs and so forth. So, yeah, it's a crisis - just not one of earth shattering proportions.

      --
      (Score: -1, Stupid)
    3. Re:overdramatic by Anonym1ty · · Score: 1

      How long before IPv6 is accused of being the next fasionable Mark of the Beast?

  21. IP assignment by deman1985 · · Score: 2, Insightful

    Or perhaps there should be just one IP address assigned to every person and then you can have a device ID for everything they own. Why does each device need a globally recognizable unique ID? It would seem to make much more sense to go the device ID route, since then if you know a person's individual IP, you can say that I want to send a message to "so and so's pager" or "so and so's home computer".

    Making an allocation of 35 trillion addresses is all great and good, but the underlying question is... why?

    1. Re:IP assignment by failedlogic · · Score: 1

      Have to agree.

      Society has always faulted programmers and engineers for making the world too complicated. Now the opportunity comes about to give every human thousands of IPs so every posession - wether convienient/practical or not - could have an IP address. This just leaves room to abuse w/ the system.

      Who will regulate giving each washing machine, etc an IP? Why do this? Will it become more complex for the user to use said device?

    2. Re:IP assignment by pdreker · · Score: 1

      Where is the difference? Just consider the e.g. first 64 bits of an IPv6 address as your single personal IP and the following 64 bits are the device ID...

      The only real difference is, whether all your number are "en block" or if they are scattered throughout the available numberspace. Due to the hierarchical nature of the net (you'll probably want to use the same internet connection for all your devices in the same space) most of the number would be consecutive anyways. And using DNS makes it completely unnecessary to actually think about all those numbers unless you're the techie...

      Patrick

      --
      Signature? Who? Me?
    3. Re:IP assignment by vadim_t · · Score: 1

      What nonsense. Let's say my network is 192.168.0, I'm allowed to have up to 253 (0 and 255 are reserved) devices, so my fridge would be 192.168.0.3. And there you go, it's already possible with the current system. No need to invent "device IDs" and strange things like that.

      IPv6 adds more address space, making this kind of thing even easier. You get a subnet with millions of IP addresses, and can assign a number to almost every piece of dust in your house if you want.

      The point of 35 trillion addresses is not to use them all, either. It's to simplify organization and routing. If an IP address was made of a country code, province code, city code and area code, routing would be fantasically easier. A situation where 34.* goes to Spain, 1.* goes to the US, and so on is pretty much ideal.

    4. Re:IP assignment by deman1985 · · Score: 1

      You obviously did not understand the point of my device ID thought. Having such an ID (whether this is accomplished by NAT and router ports or making something new) would allow for global access to my devices--phone, pager, home computer, work computer-- while still giving each person in the world only one IP address. Certainly, a home network could still be setup such that, to the devices, they see an internal net address like 192.168.x.x, but if most people's only reason for getting IPv6 pushed is for global device access, then a formal device-id assignment would do just that without consuming a separate IP for each device.

      Something that most people fail to recognize is that, even if each device is given its own IP address, do you honestly believe it will be in any kind of consecutive order? That your phone will magically have the address right after your home computer? Not likely. If things work in the future anything like they do now, with each provider company taking posession of blocks of IPs, then your phone will have something completely different from your computer, which makes it essentially useless for grouping your devices together and/or convenient global access.

      The best we can hope for with IPv6, assuming this pipe dream of "an ip for every device" comes true, is that governments would truely assign every registered citizen with their own small block of IPs to do with whatever they please and that provider companies would allow you to actually use them on your home computer, phone, pager, etc. At least then there can be some logical organization to things; I can have my base (home) IP as 1.0.65.24.148.50, my phone as 1.0.65.24.148.51, etc. It would be something a person could memorize like their SSN.

    5. Re:IP assignment by vadim_t · · Score: 1

      So, what's the difference between 192.168.0.3 and 192.168.0.1:3, or whatever system you use to define this "device ID"? Looks like different ways to write the same thing to me.

      The idea with IPv6 is indeed to give everybody a subnet. A /48, IIRC, which gives you more address space than all of IPv4.

      But anyway. Suppose you have this "device ID" invention of yours. How does *it* guarantee that numbers are consecutive? Do devices talk to each other and decide on a sequence? Does a server decide? (DHCP) Do you number them manually? (setting IP addresses by hand). Also, how do you implement this extension? It sounds like it would require changes anyway, so we might just move to IPv6 instead since it offers other advantages too.

      On a related note, why do you need to know the device ID? Do you know the IP of google? That's what we have DNS names for. If you had IPv6, or enough IPs, consecutive IPs or not, you'd simply run a DNS server. phone.deman.com would be your phone, laptop.deman.com would be your laptop, and you'd have fridge.deman.com and toaster.deman.com.

    6. Re:IP assignment by deman1985 · · Score: 1

      The device id would be more of a theoretical, accepted "standard" for organization of IP addresses. By default, your cell phone should have your IPv6 base address with an offset of, say, 5. In the case of adding it on to IPv4, you have your router running on your WAN ("base") address right now. Access port 5, for example, of the router with the equivalent of port forwarding or a proxy enabled to get access to your phone on the internal network-- which can have whatever the hell internal address it wants since nobody cares.

      Again, let me emphasize, this is more of a standard for organization than changing anything on the technical side. So, no, there would be no changes other than for routers to be intelligent enough to configure the appropriate port forwarding and/or proxy.

    7. Re:IP assignment by vadim_t · · Score: 1

      That still doesn't solve much.

      First, for something like this you need to do something. Configure NAT, enter IP addresses, whatever. Grandma doesn't know about IP addresses and ports. But I believe that grandma would be quite happy with a box that assigns IPs automatically, which IPv4 and IPv6 are perfectly capable of doing with DHCP.

      Second, messing with ports is well, annoying. What happens with this when you get 13 devices? Port 13 is daytime, which has a pretty good purpose. You'd have to avoid known ports to avoid problems. So you'd use something from the unreserved range, ending with ports like 64001.

      Third, true, now the device can have any address you want. You just have to care about the port now. Pretty much the same level of inconvenience, IMO.

      Fourth, you still haven't explained how is this system going to ensure device IDs are contiguous.

    8. Re:IP assignment by deman1985 · · Score: 1

      1) If the router is intelligent enough to impliment this over DHCP, all the better-- I did not say DHCP couldn't be used, in fact my point was exactly that existing technology can do this. 2) Indeed, this isn't an ideal solution necessarily, and the number I gave was only an example-- I did not intend for ports to actually start at 1, because I am well aware that the lower range is pretty well cluttered. However, if you work with easy to remember numbers starting at, say, 64000, then programs for calling someone's phone can easily take advantage of that with port 64005, for example. If pagers are standardized to offset 6, then they send messages to port 64006. 3) No, it is not the same inconvenience, because your router address (either on the local or the global side) is a KNOWN address. Once you know that, and assuming the persons network is configured according to the standard, then you KNOW (are guaranteed) that you can access their phone by contacting , port 64005 or whatever the standard dictates. 4) Finally, I never said they would be contiguous, only that they would be *known* addresses/ports, based upon your base address. I don't care whether there are any gaps in my allocated address/port set, only that they are known. The way things are currently, there would be no guarantee that my phone could be accessed in my own address space, and even if that's the case, that it would be a predetermined offset from my address base, which makes it basically useless to give my phone a global address in the first place.

    9. Re:IP assignment by vadim_t · · Score: 1

      Okay, but then we can avoid all this port and NAT mess completely. If you're happy with having just one port going to every device there's an easier way. Tunneling everything through HTTP with virtual hosts.

      Now, standarizing pagers to port whatever is a mess. What if some companies don't follow the standard? What if it's a company with 200 pagers, page everyone?

      All this is very messy in comparison to using proper DNS. Say, company Widgets Inc. has 100 employees. It's easy, having IPv6 they have enough addresses for 2^48 devices. The employee takes the pager to the sysadmin who registers the MAC address. DHCP then takes care of the IP. DNS then gives you things like john.laptops.widgets.com and john.pagers.widgets.com. Sending messages is easy, we can just send an email to john.pagers.widgets.com.

      So what we have? We can trace what device makes connections to outside. Wouldn't you like to know who's the rogue employee who keeps paging somebody 500 times a day? With NAT all that would come from the same IP and require examining logs, supposing they exist, and quite a lot of cooperation of the company from which the connections are coming. With one IP per device the admin just has to find who has that IP, and DNS even identifies the device. Seriously, it's much easier to act on a complaint "I'm getting 500 messages a day from 192.168.1.25" than on "I'm getting 500 messages a day from somewhere in your company"

      We also can have unrestricted communication. My coffee maker, toaster and server all have a web server on port 80.

      The mess with standarizing what things are on what port by default is also avoided. For example, how does a cell phone work? Does it use the pager port for SMS and another one for other stuff? Or it has its own?

  22. uh oh by paranode · · Score: 1
    "so big that there's not a word for the number,"

    And here I was hoping there were some intelligent engineers behind this endeavor. Doh!

  23. "so big that there's not a word for the number"... by WIAKywbfatw · · Score: 1

    So big that there's not a word for the number, huh?

    How about I come up with a bigger number and give it a name? Say, 1 followed by 100 zeros (10 to the power 10) and call it something funky like, I dunno, a googol.

    Huh? Whassat? Whatcha mean prior art? Someone thought of it already? Son of a...

    --

    "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
  24. Not again... by Delphix · · Score: 3, Insightful

    Why does every human need 100 IP addresses? Home routers seem to solve a lot of the problems. A simple IP Masq fix...

    As for the days of every appliance in our homes having an IP... I think that dream of the late 90s has been shelved for a while. It'll probably be decades, if ever, before our fridges are calling up to get food delivered...

    The average home generally has a couple PCs / laptops...maybe an XBox or PS2 connected to net.

    1. Re:Not again... by st0rmshad0w · · Score: 1

      "As for the days of every appliance in our homes having an IP... "

      Yeah no kidding, don't even make me whip out my "all-it-needs-to-do-is-make-fscking-toast" rant.

      As long as there is NAT, there is no shortage of IP's

    2. Re:Not again... by khallow · · Score: 1
      Why does every human need 100 IP addresses? Home routers seem to solve a lot of the problems. A simple IP Masq fix...

      Yea! It's so selfish! And you know the Americans are going to have like 100,000 apiece...

      As for the days of every appliance in our homes having an IP... I think that dream of the late 90s has been shelved for a while. It'll probably be decades, if ever, before our fridges are calling up to get food delivered...

      Seriously, embedded CPUs are all over the place. Naturally, you want to hook them to an ethernet network (since it's cheap and works). And a lot of those devices are eventually going to require some sort of Internet access.

    3. Re:Not again... by Anonymous Coward · · Score: 0

      Seriously, embedded CPUs are all over the place. Naturally, you want to hook them to an ethernet network (since it's cheap and works). And a lot of those devices are eventually going to require some sort of Internet access.

      For what? So you can check your e-mail from your washing machine? CPU != need for internet access.

    4. Re:Not again... by unixwin · · Score: 1

      Everyone needs 100 IP's because
      1. The article says so
      2. Everyone (will) have it and so must you
      3. No there is *NO* link between the Verio guy trying to sell you his service and IP6 :)
      4. Firewall ppl. can sell their IPv4 & IPv6 enabled gazillion dollar firewalls, along with lifelong blood sucking of training, certifying,retraining, and basically beating you senseless with their products
      5. All machines can then be hacked and everyone can have a field day turning on/off and rooting other ppls microwaves, washing machines, cell phones et. all
      6. NAT is *BAD* ;) have you seen how much commercial vendors bend their interpretations of it and how far out PPTP,VPN and IPSEC configuring are..
      7. Calls of this sort will be common..."hello this is sears may I help you"... "er...my microwave is 0wn3d"

      --
      -- everyones not everybody and neither is everybody like everyone.
    5. Re:Not again... by vadim_t · · Score: 1

      Again you people with NAT and masquerading. It is very hard to play a game online with my brother (who also lives here) because I have one IP. NAT will forward either to my computer or to his, not both. So the only chance we have to play at once is to use different ports, and not all games support that. Two IPs would have made this problem inexistent.

    6. Re:Not again... by cybercuzco · · Score: 1

      My IP address is 127.0.0.1 ;-)

      --

    7. Re:Not again... by Anonymous Coward · · Score: 0

      So what you're saying is that your games are broken? What makes you think that IPv6 is going to change your ISP's policy with regard to allocating addresses? What makes you think it will implement IPv6 before you're bored with the games you play now? Maybe you'll have more luck getting a game company to patch its broken game.

    8. Re:Not again... by vadim_t · · Score: 1

      Eh, tell that to Microsoft. It's standard DirectPlay. Ports 47624 and 2300 to 2400 on UDP. Most cheap DSL "routers" don't even allow doing NAT with so many ports. Mine for example won't accept port ranges, and is limited to 32 entries.

      Of course, I can still play, but because I disabled that function and use a Linux box instead. Not everybody can do that though.

    9. Re:Not again... by dev11 · · Score: 1

      I wonder how much of the actual IPv4 address space is actually used? There is a tremendous amount of wasted space in the current IPv4 allocation Check out this and look at class A assignments. Intelligent allocation and renumbering along with NAT could put off this "crisis" for another 20 years I bet. But as long as you have to renumber, you might as well just switch to IPv6 anyway.

    10. Re:Not again... by khallow · · Score: 1

      For example, if a piece of industrial equipment has an Internet connection, then it can be troubleshooted from a remote location. Ie, a vendor can diagnose a problem without having to send an engineer in first. Wouldn't it be nice if that broken washing machine could be diagnosed remotely without you having to deal with the increasing deficit customer support?

    11. Re:Not again... by chill · · Score: 1

      Why does every human need 100 IP addresses? Home routers seem to solve a lot of the problems. A simple IP Masq fix...

      The first thing that comes to mind is home automation, ala X-10. IP addresses to everything would greatly facilitate the "smart home" concept. You could monitor the electricity usage of everything plugged in, optimizing for efficiency.

      NAT has problems when BOTH ENDS are NATed. Good luck with online gaming, voice chat, etc. when BOTH ends have unroutable addresses. While it can be done, it is a real pain to configure.

      Just because everything is addressable from everywhere doesn't mean you can't funnel your home segment through a choke-point firewall. (Hmmm...that was a pun, and I didn't even mean it!)

      --
      Learning HOW to think is more important than learning WHAT to think.
    12. Re:Not again... by dnoyeb · · Score: 1

      NAT? get real. Would you be willing to accept a NAT address from your ISP? And why not?

      Maybe you can answer what is wrong with your assertion yourself.

    13. Re:Not again... by Anonymous Coward · · Score: 0

      It's funny that nobody notices that an IP address really gives you a 48-bit address, not a 32-bit address.

      There's a 16-bit identifier for the destination port, after all.

    14. Re:Not again... by Anonymous Coward · · Score: 0

      Broken game? NAT breaks the IP semantics. 1.2.3.4:5 is an adress of one host with a specific port. With NAT it could be any host and fscking port you're trying to talk to. Kind of defeats the idea of certain ports for certain services.

    15. Re:Not again... by silas_moeckel · · Score: 1

      I think you should put the blame squarly where it belongs the applications that dont nat (pat) well are broken. UDP can easily be used to have two hosts behind a firewall talk assuming they can talk to a group of non natted servers first. There are protocals to request tcp ports be forwarded from specific hosts. Even with that being said I think everybodys issues are not with NAT devices but rather PAT devices NAT does not realy conserve IP addresses rather it translates them PAT translates ports unfortunatly low end devices incorectly call it NAT.

      --
      No sir I dont like it.
    16. Re:Not again... by asdfghjklqwertyuiop · · Score: 1

      It's funny that nobody notices that an IP address really gives you a 48-bit address, not a 32-bit address.

      There's a 16-bit identifier for the destination port, after all.


      Nobody notices it because the port number is not part of the address at all. The port number is transport-layer specific. The port numbers for TCP are completely independant of those for UDP. And some transport layer protocols don't even have port numbers (such as ICMP, GRE, the IPSec protocols...).

    17. Re:Not again... by vadim_t · · Score: 1

      Yeah, the only problem with this is that it'd require quite a rewrite. I suppose all DirectPlay games work like this. I know that at least Baldur's Gate 2 and Mechwarrior 3 have this problem. And since they're quite old I doubt anybody will bother rewriting networking for them.

      I know two people who I can't play with because of this exact problem. They don't have a spare computer to use as a Linux router either. There are *many* computers behind NAT these days, so the ability to work by talking to a non-NATed computer doesn't help much when all the computers are behind NAT.

    18. Re:Not again... by pascalb3 · · Score: 1

      You guys are looking at this the wrong way. You should be asking "Only 100 addresses per person?" When everything else in life is supersized, why not the amount of IP addresses for myself? I need my boxers to talk to my rug to tell it it's time to locate the dirty laundry in my room for a cleaning. With nanotechnology just around the corner, all my dirty clothes will be able to coordinate with one another (via IPv6) and walk to the washer to get cleaned. Everything I touch should have an IP address so that I am constantly connected!

    19. Re:Not again... by silas_moeckel · · Score: 1

      In your case it would seem a VPN setup would aleviate the issues.

      --
      No sir I dont like it.
    20. Re:Not again... by vadim_t · · Score: 1

      Right, VPN. I have tried a VPN on Win2K before. Saying that it was horribly slow would be an understatement. This is 256/128K DSL connections we're talking about. Perhaps on a T1 it would be decent, but what I had was pretty horrible and I got rid of it as fast as I could.

      Besides, I think there are issues with making PPTP VPNs work with Linux routers. It's been proved to be insecure too, although for this particular application it doesn't matter much.

    21. Re:Not again... by pHDNgell · · Score: 1

      I think you should put the blame squarly where it belongs the applications that dont nat (pat) well are broken.

      I wouldn't go as far as to suggest that something 100% compliant with internet protocols is broken because it doesn't work with a hack someone came up with in those protocols.

      NAT is a hack, it breaks well designed protocols as well. Think of P2P negotiation. iChat seems to have done a somewhat decent job in working around some NAT limitations when negotiating peer to peer communication by attempting both the address that's being reported externally and the address that's being reported internally, however, I still can't talk to my wife from work because both ends are natted through a single point bastion host on the public side, and we're using similar private addresses behind the NAT.

      This means that unless iChat one or both ends can negotiate with the NAT device to arrange a special port for point to point communication, it's not going to happen. No voice or video chat for me.

      Is this because the protocol iChat is using is broken? Consider that, even when I'm not there, there are at least two iChat users in my house and at least two iChat users at my office. Without proper addressing, how is this supposed to work?

      --
      -- The world is watching America, and America is watching TV.
    22. Re:Not again... by Mooncaller · · Score: 1

      The statement "There will need to be 100 IP addresses for every human" is NOT the same as "Every human will need 100 IP addresses."

    23. Re:Not again... by caluml · · Score: 1

      Arrrgh. Not another connect-to-my-toaster rant.
      How about have-the-ability-to-connect-to-it-should-I-like-to -without-some-fucked-up-kludge-like-NAT. If you still think NAT is a neat idea, you've never tried to do anything interesting with a network. Just because IPv6 allows you to address any address, doesn't mean that you can't have a firewall (non-NATting) to say what addresses people can and can't get to on your IPv6 network, does it?

  25. Cody by Timesprout · · Score: 1

    a number in excess of 35 trillion that is "so big that there's not a word for the number," says Cody Christman

    Cody i think the word you are looking for is actually a combination of two words, its a shitload of IP addresses

    --
    Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
    What truth?
    There is no dupe
  26. A bit bigger than 35 trillion by kooganani · · Score: 1

    The actual number of IPv6 addresses available is 3.4 x 10^38, or 3.4 million trillion trillion trillion. Seems like a pretty big number, although a 10MB hard drive seemed massive when I was thirteen. The main thing that bums me out is that IPv4 is so much more convenient to remember and type. I guess some lucky sysadmins will have networks that spell out easy-to-remember phrases using only letters A-F.

    1. Re:A bit bigger than 35 trillion by wanderers_id · · Score: 1

      I want dibs on BAD ABE FCC FED! Other options are at Internet Anagram Server.

      Would ABE DAFF please stand up? Don't forget that we can also have FCC, BAD, FED, FDA, and DEAD! Don't forget the 1337-speak! FADE:DEAD:F001:2FA7

    2. Re:A bit bigger than 35 trillion by praxim · · Score: 1

      I was very excited about the possibility of having a "BABE CAVE" IPv6 address until I realized that that's, you know, not possible... Damn you and your typos!

    3. Re:A bit bigger than 35 trillion by Iron+Monkey · · Score: 1

      You could still have a BABE CAFE, which is arguably almost as good!

      --
      If my enemy's enemy is my friend, what happens if my enemy is his own worst enemy?
  27. Oh Puleeeze! by hoggoth · · Score: 3, Informative

    > "we're going to need something like 100 IP addresses for each human being."

    We already have 65534 IP address for each human being. They are 192.168.0.0 to 192.168.255.255.

    Use NAT. Problem solved.
    Enjoy the IPs. You can thank me later.

    --
    - For the complete works of Shakespeare: cat /dev/random (may take some time)
    1. Re:Oh Puleeeze! by FrostedWheat · · Score: 1

      Use NAT. Problem solved.

      NAT is a problem itself. A quick-fix for the lack of IP's, and the sooner we don't need it the better.

    2. Re:Oh Puleeeze! by gumpish · · Score: 1
      We already have 65534 IP address for each human being. They are 192.168.0.0 to 192.168.255.255

      But in a 32-bit address space there are only some 4 billion "real" addresses available.

      The current world population is around 6 billion. Granted, not everyone on the planet lives in their own home, and many nations don't have the resources to enjoy the technology saturation most slashdot readers enjoy, but you can see that your solution won't last for long.
    3. Re:Oh Puleeeze! by Anonymous Coward · · Score: 0

      NAT is a problem itself. A quick-fix for the lack of IP's, and the sooner we don't need it the better.

      I'm sick of IPv6 fanboys saying this. What's the problem? What part of this "network the whole house" dream would you have a problem using NAT for? I can handle every little bit of it better with NAT than with unique IPv6 addresses.

      What sense does it make to make my coffee maker have an internet routable IP address? Why would I want the whole world to have access to all my appliances?

    4. Re:Oh Puleeeze! by JanneM · · Score: 1

      Nah. It only works within the same domain. I can't address a device of mine no matter what network it happens to be connected to. Consider having a file server that would push changes to me without me having to actively periodically sync with it. Or IP telephony where you can reach me on my laptop wherever I currently am, as it keeps its own address no matter what.

      The big thing with IP6 really isn't the larger address space itself, but that we leave behind the idea of nested domains (other than the 40 bits or so each and every user gets to allocate as they wish).

      --
      Trust the Computer. The Computer is your friend.
    5. Re:Oh Puleeeze! by Anonymous Coward · · Score: 0

      All of the ISPs seem to think I only want one IP address. Even if we all magically switched to IPv6 tomorrow I don't see that I could stop using NAT. They all seem deathly afraid that I'll compete with them if they give me full services.

    6. Re:Oh Puleeeze! by drightler · · Score: 1

      That's great with IPv4's 4.2 billion addresses, so if we handed one IP to each person to use for NAT, what will the other 2 billion (at time of this posting) do?

      --

      blah blah blah....
      drightler@technicalogic.com
    7. Re:Oh Puleeeze! by lfourrier · · Score: 4, Informative

      rfc1918 says we have:
      10.0.0.0 - 10.255.255.255 (10/8 prefix)
      172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
      192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

      so you are very pessimistic

    8. Re:Oh Puleeeze! by smoondog · · Score: 1

      You are totally correct. Companies, home users, even academics are moving to NAT quickly. I bet we could even see a *reduction* in needed IP's if trends continue as they are....

      Combine that with virtual servers and dynamic IPs and suddenly static IPs aren't as valuable as they once were.

      -Sean

    9. Re:Oh Puleeeze! by FrostedWheat · · Score: 1

      I'm sick of IPv6 fanboys saying this. What's the problem?

      If everyone used NAT, we'd not be able to send files to eachother. P2P or VoIP just wouldn't work. Yea, most smart NAT devices can look at the protocol and work out what ports need to be opened - but if the protocol changes? What if the data is encrypted? (IPSec)

      Then your screwed :)

      And I'm not an IPv6 fanboy .. I just think NAT is a dead end.

    10. Re:Oh Puleeeze! by jared_hanson · · Score: 1

      Sure, NAT effectively solves the address shortage problem that IPv4 has. I'm not entirely sure it is a real effective solution, but it works, and I can't argue that.

      IPv6 brings a lot of other improvements to the table besides just a greater address space. One of the main things is more prioritization of routing. This will specifically benefit areas such as VoIP and streaming media, improving quality of audio and helping to eliminate choppy video. Other improvements are there in security and network configuration issues as well.

      Article link for more information: IT-Director.com

      --
      -- Fighting mediocrity one bad post at a time.
    11. Re:Oh Puleeeze! by packethead · · Score: 1

      What about the 169.254/16 that Uncle Bill uses for people that can't config their own IP's (dummy net)\

      --
      .sig
    12. Re:Oh Puleeeze! by jasondlee · · Score: 1

      Until your cable company decides to try to stop you from doing that. It could happen. Or they could at least try... ;)

      jason

      --
      jason
      Have a good day?! Impossible! I'm at work!
    13. Re:Oh Puleeeze! by Cato · · Score: 1

      This is a real FAQ, but IPv4 is easily capable of doing QoS (many of my telco customers do it today) and IPSec as well. That article has some huge mistakes in it and is clearly written by someone who doesn't know IPv6 well - IPSec is NOT mandatory in IPv6, and I shudder to think of the scalability issues if it was, given that most routers struggle with a large number of host to host SAs or tunnels. The author also seems to think that IPv6 gives you flow-level QoS - while it does have a flow ID, that's really not important for most people since flow-based RSVP is not going anywhere even in IPv6 land.

      The main reason to go for IPv6 is address space, and this will happen first in AsiaPac as well as for mobile phones and the DoD (from Oct 2003 IPv6 is mandatory for procurements).

    14. Re:Oh Puleeeze! by zaf · · Score: 1

      And don't forget about 127/8. Where most people should stay, anyway.

    15. Re:Oh Puleeeze! by Godeke · · Score: 1

      Of course, another "improvement" is that every packet can be efficently billed to the QOS that it uses. Large companies will be able to "color" packets with green to get good transmission, and everyone else will live on the idle bandwidth left over.

      The law of unintended consequences might just come up and bite us on the "hey, I can efficently bill this packet" butt.

      --
      Sig under construction since 1998.
    16. Re:Oh Puleeeze! by joshv · · Score: 1

      Try one IP per household. Nowhere near 4 billions households on the planet. People do share computers and internet connections.

      -josh

    17. Re:Oh Puleeeze! by FroMan · · Score: 1

      Bah, we all know that no one would ever need more than 640 ip addresses.

      --
      Norris/Palin 2012
      Fact: We deserve leaders who can kick your ass and field dress your carcass.
    18. Re:Oh Puleeeze! by Anonymous Coward · · Score: 0

      replace 'everyone' with 'very few' and replace 'many' with 'most'

    19. Re:Oh Puleeeze! by Anonymous Coward · · Score: 0

      Not everyone uses NAT. Your argument is meatless. If everyone ate the diet of the average American there would be global famine. If everyone took volume of gold equal to their body size, there wouldn't be enough gold. If everyone used the phone at the same time, you wouldn't get through. What do all of these things have in common? They don't happen.

    20. Re:Oh Puleeeze! by Anonymous Coward · · Score: 0

      It would work for a number of decades at least. It doesn't mean we need to make it, but that doesn't mean we should create unnecessary waste by migrating faster than is necessary.

    21. Re:Oh Puleeeze! by SN74S181 · · Score: 1

      The idea of actually paying for the amount of data you transfer should have a lot of appeal to most people, who don't transfer a lot of data.

      It should send shivers through the Free Software community, who have thrived in a world of flat fixed distribution costs. Suddenly, downloading every single Red Hat ISO might not have the appeal it now has. Sites might start having to charge people to download the Linux kernel source tarball... The Kernel developer mailing list will start to cost money to subscribe to....

      And spam will die.

    22. Re:Oh Puleeeze! by Anonymous Coward · · Score: 0

      Like my phone, snail mail, freeway, and front door spam?

    23. Re:Oh Puleeeze! by FrostedWheat · · Score: 1

      Not everyone uses NAT. Your argument is meatless.

      But it is becoming more common. As more people get online (esp. in regons that don't get many IP addresses) then it's usage will have to increase. There are ISP's today in smaller countries that use NAT to get there customers online, sharing maybe 5 or 6 addresses between a few hundred people.

      So for most people, yea, they don't need NAT. I agree. But you cannot accept NAT as a replacment for proper routable IP addresses. It goes against the whole idea of the internet, that every computer or device can serve data.

      Would you rather have a world where the various ISP's or big companys control the only 'real' IP addresses? Where you have to pay them to setup port forwarding on there address to your server?

    24. Re:Oh Puleeeze! by drightler · · Score: 1

      The parent said "for each human being". I was simply following that logic.

      --

      blah blah blah....
      drightler@technicalogic.com
    25. Re:Oh Puleeeze! by zangdesign · · Score: 1

      Yes, but people who use the 10 net are sooooo last century, being academics with their heads buried in the sand and old-school hackers who refuse to give up their 1GHz machines for the newer 2GHz machines.

      172 and 192 rule, though. I've had such a better computing experience with 172 and 192 than I'm converting all devices in my house to use those networks.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    26. Re:Oh Puleeeze! by lfourrier · · Score: 1

      no, only lazy (use 10.0.0.x, it is enough for home, and all at the bottom of the keypad)

    27. Re:Oh Puleeeze! by hoggoth · · Score: 1

      > one IP to each person ... what will the other 2 billion do?

      Ummm, continue to eat grubs and dig holes to pee in like they do now?

      "Mmsah, hand me that stick to crush these termites into an edible paste."
      "Here Pabi we have no more sticks, but this scrap of bone will do."
      "Hey Mmsah, I hear they don't have enough IP addresses for us."
      "Mmmm that really sucks. Now I'll have to use NAT."

      --
      - For the complete works of Shakespeare: cat /dev/random (may take some time)
  28. IP by KillerHamster · · Score: 1, Funny

    When I first glanced at the headline, I thought, oh no, not another SCO article! Well, this doesn't sound quite as serious. I, for one, don't WANT my washing machine to have an IP address. I have visions of my underwear getting 0wNeD...

    1. Re:IP by nacturation · · Score: 1
      I, for one, don't WANT my washing machine to have an IP address. I have visions of my underwear getting 0wNeD...

      Have you forgotten that you're a geek on Slashdot? You can only wish your underwear would get 0wNeD.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  29. IPv6: A Protocol of Failure by Anonymous Coward · · Score: 4, Informative

    While IPv6 fixes many problems in IPv4, the developed world will not embrace IPv6 until many shortcomings in the protocol are addressed.

    1. Cisco routers suck at IPv6. Many of cisco's routers use the router's CPU to process IPv6 packets instead of the fast-path. The reasons for this are explained in the next few points. While Juniper's routers are substantially better at IPv6 than cisco's, IT managers are often restrained by insane corporate policy that dictactes the use of cisco.

    2. There are too many addresses. There are 16.7 million addresses per square metre of the earth's surface, including the oceans. This is overkill. The world does not need more than the 4 billion addresses available with IPv4, and I challenge you to come up with an application that requires that many. Assuming that you can actually come up with one, it could easily be solved with Network Address
    Translation, or NAT as it is commonly known.

    3. IPv6 addresses are too large. An IPv6 address is 128 bits in size - 64 bits of which are reserved for addressing hosts, and 64 bits of which are reserved for routing. One thing that is cool with IPv6 is address autoconfiguration. Take your 56-bit MAC address on your ethernet card, ask for 64-bits of network prefix, bang it together with EUI-64 and you are set. The problem with a 64-bit network prefix is that routing tables become massive. Just do the math and you'll see that extreme amounts of memory are required to hold routing tables.

    4. The IPv6 header is too large. An IPv4 header compact at 20 bytes in length, while the IPv6 is bloated at 40 bytes. That's right people, each one of your IP packets has twice as much overhead as before.
    While this may not sound much, IP networks have a requirement that the minimum MTU supported must be 576 bytes. That means that where you might have got 556 bytes of data in your IP packets, you now get 536 bytes. This means that downloading stuff will take 3.4% longer.

    Sure, IPv6 allows for nice hacks, but is it really ready for prime time?

    1. Re:IPv6: A Protocol of Failure by Anonymous Coward · · Score: 0

      1. ...While Juniper's routers are substantially better at IPv6 than cisco's, IT managers are often restrained by insane corporate policy that dictactes the use of cisco.

      juniper has a fantastic line of core routers, what they don't have is a line of small routers for branch offices. nor do they have switches, firewalls, or vpn devices. cisco isn't they best at any one thing, but they are pretty good at everything.

    2. Re:IPv6: A Protocol of Failure by LS · · Score: 1

      So what? I have some numbers too

      * Software is 10 times as it was 4 years ago. OHH NOOO!

      * Websites have 15 times the graphics as 5 years ago. WOE IS US!

      * Entire CDs are transmitted across the internet. THE HORROR!

      For real though,

      1. This is a problem with insane corporate policy, not IPv6

      2. What is "too many addresses"? NAT is a HACK. Why are you so short sighted? Perhaps microscopic devices may have IPs in the future, and these 16.7 address won't be enough. Bill Gates said that 640k was enough for anyone a few years back...

      3. Hard drives, memory, and CPUS are always getting faster. Extreme amounts of memory today are miniscule tomorrow.

      4. Holy shit, 3.4% longer? I'm sure that the average sustained transfer rate across the net is increading much more than 3.4% a year, so what's the big deal about 3.4 percent?

      LS

      --
      There is a fine line between being a cultivated citizen and being someone else's crop. - A. J. Patrick Liszkie
    3. Re:IPv6: A Protocol of Failure by Cato · · Score: 1

      This is a re-post of a posting in an earlier story - see my home page link for rebuttals including mine, it's the one about DoD IPv6. Almost everything in this post is wrong but I'm not going to re-post...

    4. Re:IPv6: A Protocol of Failure by siphoncolder · · Score: 1
      2. There are too many addresses. There are 16.7 million addresses per square metre of the earth's surface, including the oceans. This is overkill. The world does not need more than the 4 billion addresses available with IPv4, and I challenge you to come up with an application that requires that many. Assuming that you can actually come up with one, it could easily be solved with Network Address Translation, or NAT as it is commonly known.
      Thank god you posted this as Anonymous Coward. Otherwise you'd run the risk of having your name next to Bill Gates on the "Eating Their Words" plaque.

      "640K ought to be enough for anybody."

      --
      i'm amazed that i survived - an airbag saved my life.
    5. Re:IPv6: A Protocol of Failure by dsmoses · · Score: 1

      So the solution is obvious: use my new IPv5 Protocol.

      Maybe this will catch on better than my 3-digit year idea...

    6. Re:IPv6: A Protocol of Failure by riflemann · · Score: 5, Informative

      1. Cisco routers suck at IPv6.

      Cisco is working on hardware support for IPv6 for most platforms. As it becomes more widespread, they will develop full hardware routing for all devices. It's a chicken and egg problem, but a lot of people have decided to start somewhere.From what I've seen, there has been more interest in getting IPv6 running in the last 6 months than there ever has been.

      2. There are too many addresses.

      NAT doesnt work when you have devices that need to be addresses externally. What NAT-Portfw port is your device 'X' listening on? Hmm?? IPv6 is designed such that address space is _not_ a resource, but a method of being able to access _any_ device attached to the net. I dont _want_ to have to explain to someone why I want an address. I just want the thing to work.
      Another benefit is address management. With Ipv6, the days of deciding how big your subnets are will be numbered. Every subnet has trillions of addresses. Nowadays you have to wonder whether your subnet needs a /24, /25, /26, etc. Yuck! With Ipv6, you never have to worry - there's enough space in _one_ subnet to scale indefintely. No more subnet-resizing games.

      3. IPv6 addresses are too large.

      Ipv6 is designed to be very hierarchial. The top organisations get /32s, the next one down get smaller subnets (/48), etc. The routing table will no longer be populate with tiny piddly subnets (eg /24s today). Go into an aggregate and things will behave.
      And as for the routing table size, modern routers have oodles of memory, on average 512Mb RAM. A full BGP table of 130k routes takes up around 64Mb of that at most. IPv6 will have better aggregation, so smaller numbers of routes, and my the time it gets large, standard memory on routers will not have a problem storing the table.

      4. The IPv6 header is too large.

      3.4% longer if you use a 576 MTU. Use a sensible 1500 byte MTU and your downloads will not be much slower at all. Anyway, the elimination of fragmenting, the simplification of subnetting, and the many other benefits will far outweigh your 20-byte concerns. See my other post on security too (no more network host scans).

      IPv6 is not ready to fully replace IPv4 overnight now, sure. But it's gaining a heck of a lot of momentum and by the time your concerns will actually become enough to be worried about, they will have been either solved or rendered moot.

      Another nice thing about IPv6 (at least now), is that it's a return to the good ol' days of the net when everyone was friendly with each other. 15 years ago you askes someone for addresses or transit and you were quite likely to get it for next to nothing. Ask for addresses or transit/peering with IPv6 today - you're likely to get it, with a friendly response. it's a great community.

    7. Re:IPv6: A Protocol of Failure by BlueWonder · · Score: 1
      IP networks have a requirement that the minimum MTU supported must be 576 bytes.

      While this was true in the original IPv6 proposal, it was decided in 1997 to increase the minimum MTU for IPv6 to 1280 bytes.

    8. Re:IPv6: A Protocol of Failure by Illserve · · Score: 1

      There are 16.7 million addresses per square metre of the earth's surface, including the oceans. This is overkill. The world does not need more than the 4 billion addresses available with IPv4, I challenge you to come up with an application that requires that many.

      Outer Space

    9. Re:IPv6: A Protocol of Failure by bigpat · · Score: 2, Insightful

      "There are too many addresses. There are 16.7 million addresses per square metre of the earth's surface, including the oceans. This is overkill. The world does not need more than the 4 billion addresses available with IPv4, and I challenge you to come up with an application that requires that many."

      How about the PC? Since there are around 6,306,837,471 people on the planet right now, so already there aren't enough addresses even theoretically possible for everyone to connect to the internet, forgeting all the servers and network routers. But the most limiting factor to giving out IP addresses is the fact that you can't just get an IP address from some guy in Egypt, because part of the address indicates what network you are on, so to imply that there are 4 billion globally available addresses is just dumb math and disregards the nature of IP routing. The only potential way for the wired Internet to remain as it was intended, an end-to-end international communication network, is for IPv6 to be deployed globally so that to say that you are connected to the real internet means an IPv6 internet.

    10. Re:IPv6: A Protocol of Failure by sirket · · Score: 1

      When did MAC addresses increase in size from 48 bits to 56 bits?

      -sirket

    11. Re:IPv6: A Protocol of Failure by tesmako · · Score: 1
      It is obvious why we need 128 bit adressing, you remember the way it sounds on slashdot whenever an article about x86-64 or any other 64-bit architecture gets posted? Lots of whine about not needing it and so on and replies that explain that it is nice because one can unify the adress-space and adress harddrives and such in the same space as ram.

      What I propose is that we with IPv6 go with really unified adress-spaces, lets give every bit of storage on earth a IPv6 adress, then we can freely adress anything we please in the same adress-space. Will be just wonderful for all of mankind. Or something like that.

    12. Re:IPv6: A Protocol of Failure by Brandon+Hume · · Score: 4, Interesting

      I'm not sure you know what you're talking about.

      1. Cisco routers suck at IPv6 because Cisco has been dragging its ass getting a production release of IOS which supports v6 out. That will be fixed this summer, I'm told. And considering the problems Cisco has been displaying in IOS, are you sure it handles IPv4 that much better?

      Your points 2, 3, and 4 are just the same thing repeated: "IPv6 addresses are big".

      2. IPv6 has ROOM TO GROW. It takes the /64 link-local address, and pastes on a 64 bit length for routing, and gives you an IP. You get your autoconfiguration, and your routing, and it's nice and neat. 64 bits is a perfectly reasonable size of data to expect to deal with at any particular time; we're already moving into a 64-bit computing world.

      If you want an application that requires loads of addresses: cellphones. Pagers. PDAs. You can NOT use NAT for millions of remote communications devices trying to talk to *other* remote communication devices. NAT *breaks* things. Anyone who has tried to connect a machine behind a NAT to a remote machine which is also behind a NAT knows what this is about. (And if you have to manually configure a port forwarding, or designate a DMZ, then something is broken!)

      I'm getting tired of the "IP-enabled fridge" remarks. Someone suggested something like that a long time ago as a "you possibly could", and people who don't understand the technology and don't want to understand the technology jumped on it as an example of pointless waste, as if such things were the driving force behind v6. It isn't.

      3. You don't understand how IPv6 routing works. IPv6 does NOT take the IPv4 world of "a.b.0.0/16 is reachable via c.d.e.0/24 which is reachable via z.y.0.0/16 AND x.w.u.0/24 and..." IPv6 routing is a strict tree to explicitly combat that problem. How do you get to abcd::/32? You go through abc::/24.

      *Reducing* the size of the core routing tables is an EXPLICIT DESIGN GOAL of IPv6.

      4. Again, you haven't done any research. IPv4 networks have a minimum MTU of 576 octets. The minimum MTU for IPv6 is *1280* octets. Yes, the header is larger. But the payload capacity has risen to match it. Your transport efficiency has not decreased.

      I think you need to do some more reading on this protocol. And try, if you can, to not fixate yourself on the size of the address. If that was all that mattered, we'd all be using Appletalk.

      --
      Brandon Hume
      hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/
    13. Re:IPv6: A Protocol of Failure by HTH+NE1 · · Score: 1

      There are too many addresses. There are 16.7 million addresses per square metre of the earth's surface, including the oceans. This is overkill. The world does not need more than the 4 billion addresses available with IPv4, and I challenge you to come up with an application that requires that many.

      Reasonable limits aren't.

      Two digits for the year wasn't enough. A fixed 256-byte buffer isn't big enough for a single line of user input. 200 area codes aren't enough. 640K is not enough memory for anybody. Consumers do need single-disk storage in excess of 128 GiB (137 GB). 4 billion IP addresses isn't enough.

      We keep hitting up against "reasonable limits" that someone thought was "more than enough". Time passes and we find they aren't reasonable and we can no longer be limited by them.

      Unreasonable limits are.

      Limits are always unreasonable. If you can't be unlimited, then let your unreasonable limits be unreasonably huge. Capacity should exceed expected utilization by several orders of magnitude because you do not know what the future may need.

      We don't design for what we can think of now; we design for what we will think of in the future.

      In the meantime, I have an application that will require more than the 4 billion addresses available with IPv4. That application is the Internet. And if you think the whole of the Internet could live in a smaller address space, then let's limit ourselves to only 1,048,576 routable IP addresses for the whole world right now and use a whole lot more NATs and see if that's reasonable.

      --
      Oh, say does that Star-Spangled Banner entwine / The myrtle of Venus with Bacchus's vine?
    14. Re:IPv6: A Protocol of Failure by ZapfDingbats · · Score: 1

      Assuming that you can actually come up with one, it could easily be solved with Network Address Translation, or NAT as it is commonly known. NAT is a neat concept and solves interesting problems, however it has serious practical shortcomings. As an example there are several incompatibilities between NAT and IPSec, restricting the combined use of the two with the simplest form of NAT and tunneled-mode IPSec (see http://www.ietf.org/internet-drafts/draft-ietf-ips ec-nat-reqts-04.txt) 4. The IPv6 header is too large. An IPv4 header compact at 20 bytes in length, while the IPv6 is bloated at 40 bytes. That's right people, each one of your IP packets has twice as much overhead as before. Ah, but it is necessary. First, IPv4 defines 8 bits for the "Type of Service", used by some options. We are running short of those bits too, and historically some clashes have already occured where the same bit is used for two different purposes. Second, with IPSec and other IP options, your IPv4 header can already use close to the 40-byte limit for the IPv4 header. So the 2-to-1 "advantage of overhead" of IPv4 is not always present. The IPv4 header is already used up to its full potential. There is no more room. While this may not sound much, IP networks have a requirement that the minimum MTU supported must be 576 bytes. That means that where you might have got 556 bytes of data in your IP packets, you now get 536 bytes. This means that downloading stuff will take 3.4% longer. In practice, however, one seldom sees an MTU constraint of 576 bytes. 1500 bytes is the accepted standard in the litterature and seems by far the most common MTU on the Internet.

    15. Re:IPv6: A Protocol of Failure by Anonymous Coward · · Score: 0

      You said: "There are too many addresses. There are 16.7 million addresses per square metre of the earth's surface, including the oceans. This is overkill. "

      Bill Gates once said: "640k should be enough for anyone."

      See why your comment is stupid? You can't predict the future. I'm sure that the ARPAnet folks never envisioned that come 1995, everyone and their dog would want on the internet.

    16. Re:IPv6: A Protocol of Failure by Anonymous Coward · · Score: 0

      "To the MOON, Alice!"

    17. Re:IPv6: A Protocol of Failure by frost22 · · Score: 1
      IPv6 does NOT take the IPv4 world of "a.b.0.0/16 is reachable via c.d.e.0/24 which is reachable via z.y.0.0/16 AND x.w.u.0/24 and..." IPv6 routing is a strict tree to explicitly combat that problem. How do you get to abcd::/32? You go through abc::/24.
      LOL - this is hilarious nonsense. This would be the end of all peering. Tis protocol already exists - its name is spanning tree and it fails with more than a few hundred nodes.
      --
      ...and here I stand, with all my lore, poor fool, no wiser than before.
    18. Re:IPv6: A Protocol of Failure by Ayanami_Rei_II · · Score: 1

      2. There are too many addresses...

      This sounds too similar to the 640K argument, somehow I thought people would have learned by now...

      3. IPv6 addresses are too large...

      See above.

      4. The IPv6 header is too large. An IPv4 header compact at 20 bytes in length, while the IPv6 is bloated at 40 bytes...

      IIRC, IPv6 dropped the checksum & fragment headers, so that routers don't have to handle them anymore. Since checksums need to be computed at each hop (I don't know about fragment assembly), I'd think that the spped up would more than offset the transit time for the larger header.

    19. Re:IPv6: A Protocol of Failure by Brandon+Hume · · Score: 1

      Spanning tree fails over a certain level because of the machines trying to negotiate their structure among themselves. (It is a link management protocol, not a real "routing" protocol...) The structure of IPv6 routing is mostly a matter of policy (and thus, yes, it can be farked by the same bad design decisions that made a mess of IPv4 routing).

      Regardless, the lesson has been learned, and the core routers will not have to deal with a massive routing table with IPv6, if for no other reason than people seeing what has already happened, and not having a legacy mess to preserve.

      And to a certain extent, yes, IPv6 will limit the concept of multihoming in the traditional sense. It relies more on multiple IPs per machine (one prefix per upstream), the DNS, and intelligence on the part of the client to try multiple AAAA/A6 records.

      --
      Brandon Hume
      hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/
    20. Re:IPv6: A Protocol of Failure by Anonymous Coward · · Score: 0

      Like it or not - DOD and DARPA is moving toward IPv6 and so the rest of the companies that do business with DOD. Yeah, changing sucks but then if it werent for change, we would still be using modem dialup

    21. Re:IPv6: A Protocol of Failure by jroysdon · · Score: 1

      1. I'm a CCNP/CCDP, so I don't think I'm unbaised enough to comment on this.

      2. Too many addresses? Yeah, and 640K of memory is more than anyone will ever need.

      3.
      a.When was the last time you surfed to a website by putting in the IP? Everyone uses DNS. For common devices netadmins will use IPv6 addresses such as 2001:401:ce0a::1 and not the EUI-64.

      b. Actually, when not using EUI-64 you can use as much of the address space as you want for the network portion, just like with IPv4 CIDR.

      c. 48-bit MAC address

      d. Longer network prefix doesn't bloat routing tables, bad address allocations do. Many ISPs are treating IPv6 allocations the same as IPv4 and being stringent knowing that just because a router can do IPv6 doesn't mean it magically has more RAM.

      4. I'd say the bulk of the "civilized" world uses 1500 MTU anyway, or for the poor PPPoE folks 1492 MTU. Screw dial-up ;-p

      Sorry to be so nit-picky, I'm tired. I'm sure you've had days like this too ;-)

    22. Re:IPv6: A Protocol of Failure by frost22 · · Score: 1
      Regardless, the lesson has been learned, and the core routers will not have to deal with a massive routing table with IPv6, if for no other reason than people seeing what has already happened, and not having a legacy mess to preserve.
      You still don't get it.

      Hierarchical routing must fail because internet routing is - in its very essence - a complicated graph of contractual relations between a large number of participants (ISPs). Hierarchical routing would force all ISPs to fall back to the good old "NSFNet backbone" concept (shove all traffic upstream) - a concept that has proven inadequate in very early internet days and has been long since abandoned.

      Independant bilateral peering is one of the key concvepts that have made the internet successfull - a technology that prevents peering between isps is doomed to fail.

      I essentially expect IPv6 to be routed with some kind of BGP/6 evetually, and the only advantage we will see over todays routing is a better design of adress allocation practices.

      Large routing tables, btw, are not really a problem in the long run anyway. Technology growth in router memory will easily catch network growth within the next ten or twenty years - I consider Moore's law much more predictable and reality-tested than all that internet-growth-hype.
      --
      ...and here I stand, with all my lore, poor fool, no wiser than before.
    23. Re:IPv6: A Protocol of Failure by Anonymous Coward · · Score: 0

      1. Cisco routers suck at IPv6.
      >yay

      2. There are too many addresses.
      3. IPv6 addresses are too large.
      > this is not true as ipv6 addresses are aggregrated, so depending on the heirarchy that the router is, it only need to see a certain prefix to route properly

      4. The IPv6 header is too large.
      > minimum MTU for ipv6 is 1280

      + ipv6 routers dun fragment forwarded packets

  30. valuable IPv4 numbers? by MacBrave · · Score: 2, Interesting

    I wonder if once the world goes to IPv6 the old IPv4 numbers would become more valuable, sort of like a low numbered /. account.......

    1. Re:valuable IPv4 numbers? by Poopdbq · · Score: 1

      No

  31. Gah by gclef · · Score: 1

    "Coming crisis?" We've presently got about 100 /8's unallocated to anyone right now. According to a previous slashdot story, we go through them at a rate of 2 /8's per year. Goign by that math, we've got 10 years left. In reality, it'll happen before that, but in two years? No way. There's just no way in hell that we're going to allocate 100 /8's worth of IP space in two years.

    Don't get me wrong, IPv6 is kinda cool, but there's no rush. Anyone who tells you otherwise is selling something (like this guy).

    1. Re:Gah by IWannaBeAnAC · · Score: 1
      Yeah, apart from screwing up the maths, you are right. Looking at the IP address assignments, there are many, many as-yet unallocated addresses. Everything from 83/8 to 126/8, for example.

      What I suspect is happening is that IANA have basically stopped giving out addresses (or are doing so at a very slow rate), not because there is any immediate risk of running out, but because giving out addresses would give the impression that IPv6 will not actually be needed. The more IPv4 addresses that are issued, the more network infrastructure depends explicitly on IPv4, the harder it is to change it later.

      In reality, the 'crisis' of actually running out of IP addresses is completely fictitous. Even when the last IPv4 host on the net is finally turned off, IANA will probably still have millions of IPv4 addresses that were never assigned. But that doesn't change the underlying problem, that NAT is a poorly functioning hack and no matter what other hacks are layered on top, IPv4 just isn't good enough to use as the primary communications protocol for the whole of humanity. There is a good reason for that: the designers of IPv4 thankfully wern't arrogant enough to even begin to assume that the net would become as ubiquitous as it has.

    2. Re:Gah by dissy · · Score: 1

      The problem isnt that we are running out of IPs.
      Its that people dont want to PAY for IPs.

      Pretty big difference.

      "A /8 costs what?!?!? No way are we paying for that. We will just bitch an moan that we have no IPs of our own!"

      Then people assume we are out of them, because no company wants to look cheap.

      Stupidity at its finest.

  32. Re:100 ips per person. by Anonymous Coward · · Score: 0

    One for each of your IQ points.

  33. Sooner or later... by DJ+Rubbie · · Score: 0, Funny

    We will run out of IPv9 addresses... http://www.faqs.org/rfcs/rfc1606.html

    --
    Please direct all bug reports to /dev/null
  34. Re:"so big that there's not a word for the number" by WIAKywbfatw · · Score: 1

    That should, of course, read "10 to the power 100". Damn keyboard.

    I wish I could claim to be the first to screw up a post on Slashdot but there's already a wealth of prior art for that...

    --

    "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
  35. Say... by blues5150 · · Score: 1

    is this like the Y2K crisis?

    --

  36. Quoth Billy G: by Malicious · · Score: 0
    Sounds firmiliar...

    "No one will ever need more than 64k of RAM."
    -Bill G.

    --
    01101001001000000110000101101101001000000110001001 10000101110100011011010110000101101110
    1. Re:Quoth Billy G: by Anonymous Coward · · Score: 0

      That is not a real quote from Bill Gates, that's something some linux asses put to his name in some smear campaign.

    2. Re:Quoth Billy G: by funkman · · Score: 1

      Note only is the quote wrong. It also urban legend.
      http://www.usnews.com/usnews/biztech/gatesivu.htm

  37. "we're going to need something like 100 IP addresses for each human being."

    Of course, the -real- issue here is why HomeSec intel can't figure out a way to track citizens^W potential terrorists that doesn't require the use of 95 IP addresses.

    I mean, I thought the whole point of the new agency was to consolidate and eliminate redundant systems...

    --

    Obliteracy: Words with explosions

  38. Pr0n IP address time! by Wacky_Wookie · · Score: 1

    Whats your Pr0n IP address you ask, and how do you find it?

    Much like your Pr0n name of course!

    Instead of your street name and your mothers maiden name mixed together, you take your street address and your mothers date of birth!

    for me:
    Street address number: 221
    Mothers DOB (fake, duh): 31/10/54 (Canadian/British date system)

    So my Pr0n IP address would be:
    221.31.10.54

    Try it, it's fun for the whole family!

    1. Re:Pr0n IP address time! by Anonymous Coward · · Score: 0

      31/10/54 (Canadian/British date system)

      Thanks for clearing that up. I thought maybe your mom was born on the 10th day of the 31st month. Whaa?

    2. Re:Pr0n IP address time! by Wacky_Wookie · · Score: 1

      It was ment to be part of the joke however, I've had people from the US attack my posts simply 'cus they thought I did not know which order dates "Always go in".

      Hell, forget the internet, I've had Amercain tourists who thought I was kidding when when I told them that we used a diffrent date system in Canada. I have a hard time switching between the two myslef, and I'm greatfull if someone makes it clear which system they are using.

  39. Why not 64 bits? by expro · · Score: 1

    IPv6 will increase the supply of addresses from 4 billion today to a number in excess of 35 trillion that is "so big that there's not a word for the number," says Cody Christman,

    Am I the only one who thinks 36 trillion does not seem all that inexhaustible, only expanding by an order of 4 thousand? Once you start assigning subranges, etc., it seems like you could exhaust them. Why didn't IPV6 go to something much larger like 64 bits? On the other hand, it makes for a good excuse for still having anonymity behind NAT firewalls.

    1. Re:Why not 64 bits? by Alan+Shutko · · Score: 1

      Why didn't IPV6 go to something much larger like 64 bits?

      Gee, maybe because they did. They went to 128-bits.

    2. Re:Why not 64 bits? by expro · · Score: 1

      Sorry, I erroneously relied on the number 36 trillion cited in the submission.

  40. 100 addresses per human being? by pstreck · · Score: 2, Insightful

    Why on earth would you need 100 addresses per human being? I can for see needing two at most, one for your home and one for your "mobile communication device". Your home would have a router and use private addresses for all your home devices. Your "mobile communication device" would have a router and use private address for all your other devices via bluetooth or whatever comes next. Does this not make sense, or I am being short sighted?

    --

    Later,
    Phil
    1. Re:100 addresses per human being? by Carrion+Creeper · · Score: 1

      not all technology is based on individuals

      you need IPs for all the web cams in public places so the fed can spy on us!

      well, maybe it would be easier to have a camera for each person... so three, at most

    2. Re:100 addresses per human being? by (H)elix1 · · Score: 1

      Why on earth would you need 100 addresses per human being? I can for see needing two at most

      Never had a bitter ex-girlfriend, I see...

    3. Re:100 addresses per human being? by JanneM · · Score: 5, Insightful

      Because your other devices will want to keep their identity even when not at home. Imagine having an IP-based telephone as a (slightly contrived) example. You want to be able to route to it no matter what network it resides on at the moment.

      I use my laptop in a number of places; home and at the department is the most common places but also others. Moving from place to place is a bit of a pain, though - I need to get a new IP address, change the SMTP server and so on, and setting up other stuff so I am allowed to access it no matter where I am is painful and error prone. If my laptop could keep its identity irrepsectively of where it is physically located on the net it would simplify life a whole lot for me.

      NAT works pretty well for the stuff we do today, but it precludes a lot of interesting uses, and is actually quite painful compared to the possible alternative.

      --
      Trust the Computer. The Computer is your friend.
    4. Re:100 addresses per human being? by Telex4 · · Score: 2, Interesting

      I think when they say we need 100 addresses per human being, they may be referring to the total number (so about 650bn?), not the number that each human uses. Not all IPs are tied to individuals... Slashdot, Google, games servers, FTP servers, DNS servers, all kinds of services require IPs, and so I suppose they're saying that if we dished all of these out to individuals, we'd each get 100. Sounds a little excessive to me, but what do I know? :-)

    5. Re:100 addresses per human being? by pstreck · · Score: 1

      personally i don't want my laptop, or much of anything I can think of to be directly connected to the internet. that's just poor security.

      --

      Later,
      Phil
    6. Re:100 addresses per human being? by E-Rock · · Score: 1

      What's wrong with DHCP? The device picks up an IP based on location, with all the required local network settings. Its 'identity' doesn't change. Have that DHCP give out addresses in the private range and put it all behind a NAT and you're using 1 public IP for all the workstations.

    7. Re:100 addresses per human being? by kwan3217 · · Score: 1

      IPv6 has 128 bits, which is 3.4e38

      6b people on earth, each one gets 5.67e28 addresses

      Give each one a computer with a billion transistors in it, and you have 5.67e19 addresses per transistor.

      Surface area of the Earth, in m^2: 5.11e14. Each one gets 6.6e23 addresses

      Mass of Earth in grams: 5.9e27. Each one gets a mere 57 billion addresses.

      Estimate of number of atoms in the Earth, assuming solid Iron: 3.6e49. Uh oh, this is not enough addresses! 105 billion atoms have to share the same address!

      I think we should move to 256 bit addressing. There are an estimated 10^76 atoms in the entire visible universe, and 256 bits would give each one its own address.

      Anyway, the whole point of this is sparseness, and not having to care about conserving addresses. If I had an IPv6 subnet, on a purely numerical basis I could solve the IPv4 address shortage problem all by myself. If I decided to be stingy and keep something like 100 devices on 2^40 addresses, the evil portscanners would have to scan 2^33 addresses on average to find one of my machines. With any reasonable use of bandwidth, this would take longer than the present age of the universe, and would therefore invalidate one of the worst of the skr1p7 k1dd13s t001z.

      --
      Lots of technical and environmental problems are solved by the application of vast amounts of nuclear power
    8. Re:100 addresses per human being? by Kevin+Stevens · · Score: 1

      100 does seem to be a bit much, but think less in terms of people, and more in terms of devices- think alarm clocks that use network time servers linked to GPS to always keep your time right (no more running around the house after power outages to reset all the clocks), cars hooked up to the internet to deliver news, traffic, etc to you on the morning commute. Think net connected webcams to keep an eye on your house while youre away. it goes on and on, cellphones, pda's, cable boxes, VOIP phones. This is a list devised in a few minutes so yeah some of the examples seem like overkill- but also take into account the plummeting prices of electronics. I dont think wireless networks that work pretty much flawlessly with as much of a market saturation as internet access is science fiction; and once that occurs, adding wireless capability to everyday items (for whatever reason) is cheap enough where that net connected alarm clock isnt such a silly idea anymore. IPV6 is meant for the very long haul, and applications not even dreamed of yet.

    9. Re:100 addresses per human being? by quasi_steller · · Score: 1

      No, the total number is much (much! much!) bigger than 650 Billion (6.5E11) the total number is more like 3.4E38. Assuming that there are 10 billion people on earth, this works out to 3.4E28 ip addresses per person. I figured out that there are more than enough ip addresses to assign an address to every penny in a earth sized volume of pennies.

      Of course, we will never use up that many IP addresses, but that is exactly the point! IPV6 should also help computer security a little. It is very easy to scan a few IPV4 addresses and eventually find a computer, but in IPV4 the addresses actually used are so sparce, that it would be difficult to find an actual address by just scanning.

      --
      ...interesting if true.
    10. Re:100 addresses per human being? by Dukael_Mikakis · · Score: 0

      Remember that the human population is growing. We must be able to accomodate this.

      In decades we might only have 99 or even 98 IPs per human being!

      Where's IPv8?!?

    11. Re:100 addresses per human being? by Anonamused+Cow-herd · · Score: 1
      Why is this comment coming up so much? This seems like a no-brainer to me. For 20 bytes in the header, and no decrease in efficiency due to an increase in Minimum Transmission Unit size, this is not a question of "why would you need 879430380423849023809 addresses," it is a question of "why the hell not?"

      First off, I can think of a billion ways we could increase the number of IPs used. For example, in the future, each internet-connected software application could have its own IP, if we wanted. That would address a ton of security concerns, as well as minimizing port allocation problems within the machine. Let's imagine this new world, shall we:

      1) No scans for active hosts -- nobody is going to waste their time scanning trillions of addresses, I don't think. Even if latency improved a thousandfold, it would take forever to find an active host, especially if each "host" is an application with an assigned IP that does not respond to pings. Think of it this way -- you would have to scan all of the ports of every possible host out of trillions just to find a POSSIBLY active application, not even a computer, since the other programs on the computer have other IPs. This is true even if the computer were running 100,000 processes, all with unique IPs.

      2) People are harping about how they would prefer to have "private" addresses. What they don't seem to understand is that this, in a way, could be a private IP system. It's just a different kind of privacy. If you want something public, make it public with broadcast dns, or whatever replaces dns. If you want it private, just don't announce it. If I have a web server running but nobody can find it, that is effectively private. But rather than being a private like "behind locked doors," it is private like "one grain of sand on the beach that only I know the location of."

      So I suppose that is my answer to your question -- why not? Having that many IP addresses will allow programmers and engineers to start making things in new ways. It will be fast, easy, and probably more secure, all at the cost of 20 bytes per packet. Doesn't sound like a bad deal to me.

      --
      -----[0_o]-----
      We are not amused.
    12. Re:100 addresses per human being? by gilesroberts · · Score: 1

      IP enabled telephone a contrived example? Except that I'm currently posting to slashdot on my telephone. Which is IPv6 compatible.

    13. Re:100 addresses per human being? by mrogers · · Score: 1

      If you can use a device form anywhere without changing its address, won't this break ingress/egress-based filtering and introduce a whole new range of spoofing problems?

  41. NATural IP by mr_beanz · · Score: 1

    And in the meantime, you can just use this with NAT to get all the benefits of a true IP address: www.naturalip.com

  42. more info on IPv6 by H0NGK0NGPH00EY · · Score: 3, Informative
    --
    Do not read this sig.
  43. Re:Eh? by Chatmag · · Score: 1

    Here is a list of names for big numbers

    --
    Pete Carr Owner Chatmag.com
  44. Just out of curiousity... by TalMaximus · · Score: 1

    As far as assigning IP addresses to appliances and other household electronics, wouldn't it be better to require some type of routing/dhcp system. What I mean by this is at my house we have one public IP address, but several computers that utilize that connection. We use a router which takes on the identity of that IP address and then it acts as a DHCP router giving private addresses to everything connected to it. Couldn't the same DHCP/Routing technology be used in order to reduce the excess number of public IP address would have if there were a seperate address for every appliance, computer, etc?

    1. Re:Just out of curiousity... by WebMasterJoe · · Score: 1

      I was thinking it would make more sense to have a sort of "master" device with an IP, and each "child" device would be listening to the "master" on a different protocol, like bluetooth (yes I know it's an oversimplification but bear with me, we're talking about the future), and maybe allocate 24 bits for addressing these devices. After all, if each person has a need for 100 IP addresses, would we want them to all be wired, and independent of each other? Seems to me they would have to be organized and listening to one or two master devices, at which point I have to wonder why they'd all need to be external devices. Not to mention synchronization. I don't want my synchronization efforts to be carried out to each phone, PDA, PC, TV, etc. I want the appointments and phone list to be stored on the master device(s) and those devices can beam out updates to my other stuff.

      --
      I really hate signatures, but go to my website.
    2. Re:Just out of curiousity... by TalMaximus · · Score: 1

      I like that idea and I wonder what technology is being developed to cater to such a need. A friend of mine did his graduate project on a programming structure called symantics (spelling?) which seemed to follow suit with this type of thinking. The programming code used an idea similar to xml in which custom tags were created for a television (for example) and then different methods could be performed within each tag based on the object they were a member of. It was pretty interesting but as you can tell from my description (which does not do his project a bit of justice) that I know very little about it.

    3. Re:Just out of curiousity... by Ashtead · · Score: 1
      Now, NAT is a pain in the neck, so I can well see the need for IPv6. However, the idea of dynamic configuration of local equipment DHCP-style sounds like it would be useful.

      Otherwise, would we have to set addresses of our household equipment using thumbwheel-switches or some software equivalent? "Lemme see -- the boiler-room controller gets X.0.0.0.100, the fridge gets X.0.0.0.101" and so on where X is all the higher-bits of the house IPv6-address.

      Even if parts of the address is predetermined (as it is with devices for I2C-buses or PCI Cards). I guess that one could have the devices figure out their addresses by trying them in order and see what is available...

      Then there is the naming of these, what would the hostnames be? Since we are on a global network, would it all have to be something unique like "fridge1.someroad99.12345.tld", "boilercontrol.someroad99.12345.tld" and so on and so forth. This probably would work when moving to somewhere with another language, so the fridge may become "kjøleskap.enellerannenvei171.9990.no" or some such. Looks like some kind of in-house DNS server would be very useful here.

      All this is assuming that we want to have our household appliances on the 'net at all. I am perfectly capable of buying new food as it is being eaten, I don't need my fridge to put in an order for more beer and onions and whatever by itself. Still this could be useful for some people.

      --
      SIGBUS @ NO-07.308
  45. So big... wha? by stonecypher · · Score: 1

    Did I misunderstand what he said? 281,474,976,710,656 isn't that big a number, and that doesn't take into account the various blocked ranges that I'm sure I don't know about in IPv6, things along the lines of 127.0 and 192.168 and so forth... ... though if that is what he meant, the word is "trillion." Kinda like the messenger, but not named after a Tricia.

    --
    StoneCypher is Full of BS
  46. [yawn] by xdroop · · Score: 1
    IPv6 has been "two years away" for the last eight years.

    Wake me up when it's really here.

    --
    you should read everything on the internet as if it had "but I'm probably talking out of my ass" appended to it.
  47. Simple solution. by grub · · Score: 1


    Every country needs a NAT gateway at the border. Yes I'm joking.

    --
    Trolling is a art,
  48. Made up words? by Toasty981 · · Score: 1

    "Actually, 35 trillion is low," said Cody Christman, director of product engineering for Verio, an Internet service provider that now offers IPv6 technology to customers in several cities, including San Francisco and Washington. "It's much bigger than that. It's so big that there's not a word for the number."

    Great! Because technology terms aren't confusing enough for most people as it is, we're resorting to making up words. Imagine a future Slashdot article:

    "IPv6 will have eleventy billion addfroozles! It will be based on the fragtisticalweezle specification!"

    You think dealing with clueless management types who just throw buzzwords around is bad *now*, wait until they get to make things up!

    1. Re:Made up words? by satterth · · Score: 1

      How many Library of Congress' is that?

      --
      Being called a dork on Slashdot must be like being called the retard in special ed.
  49. English by limekiller4 · · Score: 1

    From the blurb:
    "IPv6 will increase the supply of addresses from 4 billion today to a number in excess of 35 trillion that is "so big that there's not a word for the number," says Cody Christman, director of product engineering for Verio."

    It's a shame when a Verio rep has to dance around the word "google" out of fear of a lawsuit.

    --
    My .02,
    Limekiller
    1. Re:English by Jackazz · · Score: 1
      It's much easier to mod me down than to post an intelligent reply.

      Yeah, if i had mod points...

    2. Re:English by praxim · · Score: 1

      He didn't have to. The word is "googol," and happens to be much larger than 35 trillion.

    3. Re:English by limekiller4 · · Score: 1

      I wrote:
      "It's a shame when a Verio rep has to dance around the word "google" out of fear of a lawsuit."

      praxim replied:
      "He didn't have to. The word is "googol," and happens to be much larger than 35 trillion."

      Any suggestions on how I could have made this any more obviously a joke?

      --
      My .02,
      Limekiller
    4. Re:English by praxim · · Score: 1

      Sorry, I was busy fighting someone on IRC about exactly why NAT would suck more than IPv6 and my ability to detect humor went out the window.

  50. Why, precisely by panurge · · Score: 1

    In what world am I going to need 100 distinct and presumably public IP addresses? I'm not arguing that the present system does not need an eventual move to something better, even though half the world has never, apparently, made a phone call let alone used a web browser, but isn't this just talking up a problem that doesn't yet exist? If I need internet access to every gadget in my house, I would prefer them to be behind a firewall with some kind of remote control security system. I really do not want script kiddies emptying the paper bins on my printers. I don't want my washing machine engaging in IRC with a Whirlpool serviceperson without my having some sort of control over it. Or am I just paranoid?

    --
    Panurge has posted for the last time. Thanks for the positive moderations.
    1. Re:Why, precisely by kwan3217 · · Score: 1

      Just as 640k ought to be enough for anybody, 100 ip addresses hought to be enough. Right? Trust me, when you have 2^40 addresses to yourself, you will think of something to do with them, if just make your network sparse, so the evil bad scanners have to scan 2^35 empty addresses per machine of yours they want to find.

      --
      Lots of technical and environmental problems are solved by the application of vast amounts of nuclear power
  51. Microsoft Math by reidbold · · Score: 1
    from this microsoft article .
    The most obvious distinguishing feature of IPv6 is its use of much larger addresses. The size of an address in IPv6 is 128 bits, which is four times larger than an address in IPv4. A 32-bit address space allows for 2^32 or 4,294,967,296 possible addresses. A 128-bit address space allows for 2^128 or 340,282,366,920,938,463,463,374,607,431,768,211,45 6 (3.4 × 1038) possible addresses.
    So obviously 2^128 = 4 x 2^32. Or, 2^128 = 2^2 x 2^32. 2^128 = 2^34. Gooo microsoft math.
    --
    -Reid
    1. Re:Microsoft Math by An+Ominous+Coward · · Score: 1

      As it states quite clearly, the ADDRESS ITSELF is four times larger, not the number of distinct IP addresses yielded by the increase in address size.

      I love it when Slashbots make fools of themselves trying to slander Microsoft.

  52. How? by Mr_Silver · · Score: 1
    We're going to need something like 100 IP addresses for each human being

    I've never seen the attraction of assigning an IP to your left testicle, but whatever turns you on I suppose.

    --
    Avantslash - View Slashdot cleanly on your mobile phone.
    1. Re:How? by Unregistered · · Score: 1

      I've never seen the attraction of assigning an IP to your left testicle, but whatever turns you on I suppose.

      I know. I prefer to have just one global IP for my genitals and use NAT to address all the individual parts.

  53. Yes its such a crisis by pacman+on+prozac · · Score: 3, Informative

    ...that IANA decided to hold onto 80 or so class A's. I doubt they could even allocate all that space by 2005.

    Dont believe me? get it straight from the horses mouth

    Perhaps if the organizations bemoaning the lack of IP space stopped hogging so much of it there wouldn't be such a shortage.

    1. Re:Yes its such a crisis by RevMike · · Score: 1
      Don't forget that the US MIL is already converting to IPv6. So the 8 or so class A blocks they have should be candidates for return to the pool.

      Hmm, HP and DEC both have a class A. Surely the could do fine with just one...

      May be this is an issue in 2010.

      Honestly, more and more major organisations want to put their clients behind a firewall. NAT works fine for this, especially when VPN is used to pierce the firewall for appropriate usage. Virtually noone wants every device on their net available to the public.

  54. human error by 514x0r · · Score: 1

    It allows us to create billions of new sensors that can instantly communicate, taking human error out of the equation," Skynet went on-line on Monday, August 4th, 1997 and becomes self aware at 2:14 a.m. August 29th, 1997........

    --

    !(^((ri)|(mp))aa$)
  55. hm by EMH_Mark3 · · Score: 1

    Isn't this a dupe from a couple of years ago?

    --
    Burn the land and boil the sea, you can't take the sky from me
  56. 100 IP addresses per human being?? by GillBates0 · · Score: 1
    "and we're going to need something like 100 IP addresses for each human being."

    WTF are they going to do with a 100 IP Addresses per human being??? Maybe their grand plan is to assign an address to each body part or something.

    Great! So my brain could send lightning fast, low-overhead UDP requests to my organs, instead of bulky nerve impulses.

    --
    An Indian-American Hindu committed to non-violent thought/speech/action alarmed by the global explosion of radical Islam
    1. Re:100 IP addresses per human being?? by Santos+L.+Halper · · Score: 2, Funny

      Maybe your brain is going to start identifying body parts by IP address. If you get a serious neck injury, your brain will start frantically pinging your feet to see if they still respond, stuff like that.

      --

      "Ask not for whom the bone bones. It bones for thee." --Bender
    2. Re:100 IP addresses per human being?? by oojah · · Score: 1

      WTF are we ever going to do with more than 640K of ram?

      Are you saying that you'd prefer to have just one publically addressable ip address?

      Cheers,

      Roger

      --
      Do you have any better hostages?
  57. more than 35 trillion per square meter of Earth by asmithmd1 · · Score: 3, Informative

    The number of IP addresses IP6 will allow is truely astronomical, 6.65x10^23 addresses for every square meter of the Earth's surface. More than enough for everyone to have an internet controlled Etch-A-Sketch

    1. Re:more than 35 trillion per square meter of Earth by Surak · · Score: 4, Funny

      The number of IP addresses IP6 will allow is truely astronomical, 6.65x10^23 addresses for every square

      Heh. Reminds of a REALLY old joke: For a good time call Avogadro 6.022*10^23!

      Ha! I kill me! I'll be here all week.

    2. Re:more than 35 trillion per square meter of Earth by Nexus+Seven · · Score: 1

      for every square meter of the Earth's surface...
      truely astronomical...

      Surely you mean "truely terrestrial"

    3. Re:more than 35 trillion per square meter of Earth by Vindicator9000 · · Score: 2, Funny

      yeah, and no one will ever need more than 640K of RAM, either.

    4. Re:more than 35 trillion per square meter of Earth by asmithmd1 · · Score: 1

      When IP4 was designed it was ridiculous to think every person on earth would have a computer. They got burned as now many people have more than one. To picture the IP6 space; every current IP address has 4 billion X 4 billion IP addresses, for good measure each of those addresses has 4 billion addresses. We won't run out until we want to assign every molocule on earth an address

      The real question is, how much will our power consumption go up because of the increased header length

    5. Re:more than 35 trillion per square meter of Earth by Anonymous Coward · · Score: 0

      is this the first time we can report an etch-a-sketch was slashdotted?

    6. Re:more than 35 trillion per square meter of Earth by dasmegabyte · · Score: 1

      Really, 6.65x10^23?

      That's eerily similar to Avagadro's Number (6.022x10^23), the amount of "stuff" in one Mole of anything.

      Does this mean we have more than a Mole of IPs?

      --
      Hey freaks: now you're ju
    7. Re:more than 35 trillion per square meter of Earth by PKFC · · Score: 1

      3.4 x 10^38 theoretical IPv6 addresses does have a name for the number: 340 decillion.

    8. Re:more than 35 trillion per square meter of Earth by Glock27 · · Score: 1
      The number of IP addresses IP6 will allow is truely astronomical, 6.65x10^23 addresses for every square meter of the Earth's surface.

      Ah, for a total of 3.40e38 total? That would be a 128-bit address.

      More than enough for everyone to have an internet controlled Etch-A-Sketch

      It's enough for each grain of sand in the Etch-A-Sketch to have a unique address.

      One hopes we'll have some form of planet-wide NAT for IPv7 (GalaxyNet).

      --
      Galileo: "The Earth revolves around the Sun!"
      Score: -1 100% Flamebait
    9. Re:more than 35 trillion per square meter of Earth by PKFC · · Score: 5, Funny

      Pardon me. The ACTUAL number is:
      Three hundred forty undecillion two hundred eight-two decillion three hundred sixty-six nonillion nine hundred twenty octillion nine hundred thirty-eight septillion four hundred sixty-three sextillion four hundred sixty-three quintillion three hundred seventy-four quadrillion six hundred seven trillion four hundred thirty-one billion seven hundred sixty-eight million two hundred eleven thousand four hundred fifty-six.

      Or just: 340 282 366 920 938 463 463 374 607 431 768 211 456

    10. Re:more than 35 trillion per square meter of Earth by grnbrg · · Score: 1
      Three hundred forty undecillion two hundred eight-two decillion three hundred sixty-six nonillion nine hundred twenty octillion nine hundred thirty-eight septillion four hundred sixty-three SEXtillion four hundred sixty-three quintillion three hundred seventy-four quadrillion six hundred seven trillion four hundred thirty-one billion seven hundred sixty-eight million two hundred eleven thousand four hundred fifty-six.

      Eh heheheh. Heh heh. Heh. He said 'sex'. Hehehehe.

      :)


      grnbrg

  58. There's no shortage of space. by drwho · · Score: 1

    There's no shortage of IP space. The problem is really a political one. There is much space assigned to various US DoD organizations. At first glance, this is not surprising, as the Internet grew from Arpanet/Milnet. But now, most of this stuff for security reasons has moved off of the Internet, which is reasonable. Why haven't they turned in their allocations?

    What's even worse, DoD actually was assigned, by IANA, two NEW class A spaces in 1998 (214.0.0.0 and 215.0.0.0 , i.e. 214/7) -- for WHAT REASON?

    Something stinks at IANA.

    I am also not very pleased with ARIN. They seem to exist to serve only themselves and huge corporations. Their fee structure is set up to crush the small ISPs. The yearly fee for small allocations is high, but in bulk it is almost a reasonable price, except when you figure out they're doing basically no work for $20k. I understand the technical reasons for wanting to aggregate IP space (simpler routing tables around the world), so they want end-users with 'portable' IP space to turn them in, or at least stop using them. Not so great for hobbyists and geeks who like to switch ISPs but keep their IP space.

    ARIN needs to seriously stop being pricks to the small guys and start rethinking how to accomplish their goals. I have some ideas. But slashdot is no place to get into a technical discussion of this. Hell, I don't know if anyone is reading this who cares, or even would know what I was talking about.

  59. My God... by chrisgeleven · · Score: 1

    ..someone think of the children! The dreaded EOL of IPv4 is upon us!

  60. check your math... by xactoguy · · Score: 1

    100 /8's left, 2 /8's per year = 50 years left, unless you wanted somebody to read your numbers differently?

    --


    And so we go, on with our lives
    We know the truth, but prefer lies
    Lies are simple, simple is bliss
  61. To those who say we have enough IPv4 space by riflemann · · Score: 5, Insightful
    There are people who have stated that we've only used up around 60% of the IPv4 space and we have plenty more to last for a long time yet.

    I want to see IP as more of a general resource like electricity or water. You just plug anything into your wires/pipes, and it gets full access to the resource. Want more things getting water such as a washing machine? Then just run another pipe to it and it's got access. The current hacks of NAT are equivalent to only being allowed to install one tap in your house, and "proxying" the rest with buckets. Why cant it be like a water or electricity supply?

    Those saying 'we have plenty of space left' obviously dont realise that the reason for this is that the current allocation policies for IPv4 make it impossible to get space for arbitrary devices. Yes, if you only allocate one IP address per gateway, of course you wont run out for a while. But that then mandates the use of ugly hacks such as NAT. A single tap per house/organisation.

    To make full use of the potential of the net, one must be able to freely allocate IP addresses to any devices that want them, no matter how trivial it may seem today. Back when IP was invented, it was never in anyones wildest dreams that there would be an address shortage. There were barely a hundred hosts yet 32 bits of space. Look at what's happened in 20-odd years!

    Lets not make the same mistake today.

    1. Re:To those who say we have enough IPv4 space by Tiny+Elvis · · Score: 1

      Tell me about it.. my setup at home uses NAT and it is a pain in the ass trying to access my electric toothbrush from work. I need to make sure it is charging!!

    2. Re:To those who say we have enough IPv4 space by Anonymous Coward · · Score: 0

      why exactly do you want IP to be like water? additional IP addresses will not make 'more' as in your anology of the water pipe.

    3. Re:To those who say we have enough IPv4 space by Anonymous Coward · · Score: 0

      ok, NAT maybe be an "ugly hack" but thinking about you anology... it sounds like you would be creating a _bandwidth_ shortage.

    4. Re:To those who say we have enough IPv4 space by Zoop · · Score: 1

      You just plug anything into your wires/pipes, and it gets full access to the resource.

      Your analogy falls down, because your house has only one access point to each utility, unless you are Tank Girl, stealing from Water and Power.

      So yes, insofar as you have electrical devices or water-using applicances that don't overload your line/pipe, you are fine, but your house has only one.

      Exactly like NAT.

    5. Re:To those who say we have enough IPv4 space by poot_rootbeer · · Score: 1

      To make full use of the potential of the net, one must be able to freely allocate IP addresses to any devices that want them, no matter how trivial it may seem today.

      Who's in charge here, the devices, or the people?

      "The Internet" has already become too big to be represented by a single amorphous cloud where any arbitrary point within the cloud can communicate with any other arbitrary point. When every node was a centralized server on a college campus, this model made sense -- but in a future where every toaster and washing machine has an IP, that kind of global accessibility is actually counter-productive.

    6. Re:To those who say we have enough IPv4 space by aserra · · Score: 1

      Having IPv4 as a utility service is all well and good, but the NATing/Proxying (or "buckets" in your case at least give a level of security and control over the devices in your house. It makes getting to those devices just that much harder and allows *YOU* to set up *YOUR* network as you see fit.

      To make full use of the potential of the net, one must be able to freely allocate IP addresses to any devices that want them, no matter how trivial it may seem today.

      I do this already with my cablemodem/router/firewall/DNS setup I have at the house. I have approximately 10 devices all with their own IP addresses and only use 1 public address. If I wish, I can place a server in a DMZ and route the traffic accordingly.

    7. Re:To those who say we have enough IPv4 space by Anonymous Coward · · Score: 0

      Your analogy falls down, because your house has only one access point to each utility, unless you are Tank Girl, stealing from Water and Power.

      Few analogies are perfect, but this is silly. The physical "one access point" of network access is irrelevant to having a single network address, because one connection can carry traffic for multiple addresses.

      Perhaps cell phones would be a better analogy. The connection is huge, but there's only one electromagnetic spectrum coming into your home. Still, you can hook up any number of devices and they just work. With the NAT version, you have one wireless phone and run a bunch of cable to it to connect the others.

      So yes, insofar as you have electrical devices or water-using applicances that don't overload your line/pipe, you are fine, but your house has only one.

      Exactly like NAT.


      Completely irrelevant to NAT, you are blinded by your one connection = one address idea. If you had real addresses for each machine, you would still be limited by the bandwidth of your single connection. Hell, if you had multiple connections, you would be limited by their combined total bandwidth.

    8. Re:To those who say we have enough IPv4 space by Anonymous Coward · · Score: 0

      Back when IP was invented, it was never in anyones wildest dreams that there would be an address shortage. There were barely a hundred hosts yet 32 bits of space. Look at what's happened in 20-odd years!

      Oh, no!, if we implement IPv6, in 20 years, the earth will be littered with trillions of computers per square meter...

      if the space is there, why not use it?

    9. Re:To those who say we have enough IPv4 space by 1029 · · Score: 1

      WHAT? You must have never run a new pipe anywhere in your house/yard have you? You have exactly 1 pipe for water coming to your property (think of it as your 1 IP address). From there you branch it off and can run it where ever you want, but it is still coming from that 1 same original pipe (think of this as your NAT).

      So basically you are splitting 1 main point of entry into many applications. To try and compare having individuals IP addresses to a water system would mean that you would have 10-20 individual pipes coming from the water company all the way to your front door, which simply isn't the case.

      And where you got the idea to throw buckets into this analogy I suppose I'll never know...

      --
      - I love animals. I try to eat at least one a day.
    10. Re:To those who say we have enough IPv4 space by frost22 · · Score: 1
      ...but the NATing/Proxying (or "buckets" in your case at least give a level of security and control
      Thats an old myth. NAT is'nt security. If you want security, by all means, have it. Your NAT device could do 100% the same security without NAT (just call that statefull acl). NAT and security are unrelated concepts.
      ... with my cablemodem/router/firewall/DNS setup [...] I have approximately 10 devices all with their own IP addresses and only use 1 public address. If I wish, I can place a server in a DMZ and route the traffic accordingly.
      Nope.

      You can can gate them - but your gateway has to have full understanding of every single of the protocol involved and even then there are numerous protocols that you just can't NAT.

      And, yes, even protocols people use. Suggestion - have two or more PCs behind your NAT box play Microsoft Games over the Internet using direct play.

      Face the ugly truth. NAT is Evil!
      --
      ...and here I stand, with all my lore, poor fool, no wiser than before.
    11. Re:To those who say we have enough IPv4 space by Jeff+DeMaagd · · Score: 1

      I don't think those analogies apply.

      There is only one single point of water and power entry to a house, it is up to the distribution system inside the house to distribute the resource. The outside world doesn't need to know what IP each tap or plug is, that should be an internal matter.

      If there is a problem of uneven IP allocation, then fix it. No need to make a technological solution to a political problem.

    12. Re:To those who say we have enough IPv4 space by reverend0 · · Score: 1

      But most consumers don't want to purchase a separate device so that they can remotely check their air conditioner, hot water heater, stereo, etc. There has to be some sort of public access that could be tied into. A server for everyone home doesn't seem to fit into the non-geeky mind.

  62. Crisis my ass, Ever hear of NAT? by nurb432 · · Score: 0, Redundant

    Seriously though, every device on the face of the planet does *not* need its own private address. ( or have an IP at all, but that's a different discussion )

    Of the devices that really need outside connectivity, I bet less then 1/3 need their own, so NAT will take care of the other 2/3.

    --
    ---- Booth was a patriot ----
  63. Bigger than 35 trillion....it cant be done surely? by noelp · · Score: 1
    "so big that there's not a word for the number," says Cody Christman

    Seeing as a googol is 10 thousand trillion trillion trillion trillion trillion trillion trillion trillion I think he may need to reconsider that statement.

    --
    'Internet! Is that thing still around?' - Homer Simpson
  64. It's not netcraft, but oh well. by Lord_Slepnir · · Score: 1

    It is official; North American IPv6 Global Summit confirms: IPV4 is dying One more crippling bombshell hit the already beleaguered IPV4 community when IDC confirmed that IPV4 market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent North American IPv6 Global Summit survey which plainly states that IPV4 has lost more market share, this news serves to reinforce what we've known all along. IPV4 is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
    You don't need to be a Alex Lightman to predict IPV4's future. The hand writing is on the wall: IPV4 faces a bleak future. In fact there won't be any future at all for IPV4 because IPV4 is dying. Things are looking very bad for IPV4. As many of us are already aware, IPV4 continues to lose market share. Red ink flows like a river of blood.
    RFC 1001 is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time RFC 1001 developers Cody Christman only serve to underscore the point more clearly. There can no longer be any doubt: RFC 1001 is dying.
    Let's keep to the facts and look at the numbers.
    RFC 1067 leader Theo De Raadt states that there are 7000 users of RFC 1067. How many users of RFC 1189 are there? Let's see. The number of RFC 1067 versus RFC 1189 posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 RFC 1189 users. RFC 1256 posts on Usenet are about half of the volume of RFC 1189 posts. Therefore there are about 700 users of RFC 1256. A recent article put RFC 1001 at about 80 percent of the IPV4 market. Therefore there are (7000+1400+700)*4 = 36400 RFC 1001 users. This is consistent with the number of RFC 1001 Usenet posts.
    Due to the troubles of Charmed Technology , abysmal sales and so on, RFC 1001 went out of business and was taken over by Verio who sell another troubled OS. Now Verio is also dead, its corpse turned over to yet another charnel house.
    All major surveys show that IPV4 has steadily declined in market share. IPV4 is very sick and its long term survival prospects are very dim. If IPV4 is to survive at all it will be among OS dilettante dabblers. IPV4 continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, IPV4 is dead.
    Fact: IPV4 is dying

  65. Relax, folks by Anonymous Coward · · Score: 0

    This is far from the end of the world. So what if everyone needs 100 IP addresses inside their house? There is nothing that says they have to be universally unique. NAT technology can allow a single IP to server the entire needs of a house.
    Use the non-routable addresses inside your house. Only the gateway needs to know or care the internal IPs in your house.

    So if we give ONE IP per household, we're still ok, even if we run out of them. Nothing prevents taking the NAT idea a level higher, like a zip code. Nothing prevents DHCP, where you only lease an IP for a temporary amount of time...

  66. Are We or Aren't We? by davemac30 · · Score: 2, Interesting

    Could it be that people who have a vested interest in the adoption of ipv6 are more likely to try and alarm us about the impending IP crisis?

    Here's an alternative view from Paul Wilson, director general of APNIC, which suggests that we have 20 years left at the current growth rate.
  67. IPv6? by FrostedWheat · · Score: 1


    I'm still using IPX you insensitive clod!

  68. -1 Blazingly Obvious by Anonymous Coward · · Score: 0

    Who modded this up?

  69. The real reason: by Anonymous Coward · · Score: 0
    The push for IPv6 has nothing to do with "running out of IP addresses." That problem has been solved with NAT. What TPTB really want wide adoption of IPv6 for is elimination of dynamic IP addresses, an infrastructure for surveillance, and the ability to much more easily block traffic to or from particular nations, based on geographic allocation of addresses.

    ~~~

  70. Article Title by aastanna · · Score: 1

    "The Impending IP Crisis" is a good title for Slashdot. In my RSS feed I can't tell if it's going to be something about Intellectual Property (copyrights, patents, etc) or IP addresses...

    Quite frankly, I was disappointed.

  71. IP's aren't the problem, bandwidth is by sc00p18 · · Score: 1

    Sure, IPv6 will be great and all, but frankly I couldn't care less. We should be concentrating on getting fatter pipes everywhere. 56K Modems are ridiculous. Even cable/dsl is pretty slow, especially when it comes to upload bandwidth. Once everyone has sufficient bandwidth (well, sufficiently more than today), then we can worry about giving every device its own address.

  72. Sure there is NAT but.. by Anonymous Coward · · Score: 0

    When you run out of IP ranges to assign, how are you going to get everybody to consolidate their IPs under NAT to make more room? Sure its possible, but the human aspect of the problem is evil.

  73. Why bother trying to use the 35 trillion IPs by Anonymous Coward · · Score: 0

    In the article is ends with:
    "Now that the address space is available, the next step is figuring out how to use it."

    Why bother. By the time any real services could be setup all but a few ideas won't be "patent Blocked". Trying to develop a good idea when it's Patent Blocked would be too expensive to pay off the lazy Patent Owner.

    Patent Blocking. You heard it first on /.

  74. "Shortage?", not quite by dcavanaugh · · Score: 1

    As long as broadband ISPs are out there trying to sell additional IP addresses for home LANs and misleading customers into thinking these additional addresses are necessary, there cannot possibly be a real shortage.

  75. NYT quality by Anonymous Coward · · Score: 0
    There has been lot of discussion about editorial quality of NYT.
    "The new standard will also offer better security. The current addressing system has been a frequent target for
    hackers,
    who take over parts of networks with unused IP addresses to create illegal Web sites or initiate attacks.
    Hackers
    have also hijacked packets of information as they are handed off between networks. Because each IPv6 address will be attached to a particular user or application, it offers what Mr. Lightman called end-to-end security, ensuring that information traveling over various networks across the globe arrives at its intended destination."

    Where is the fish? IPv4 does all that same. Not that IPv6 is bad idea. I think NYT is trying to SCO me.
  76. 3y3 c0nt35t y0ur a55ert|0n, s|r! by Anonymous Coward · · Score: 0
    Firstus postus, beeeeeeotchae!!!!

    Bow down and worship my interminable crusade to garner accolades!





    pleeeeeeease?!!!

  77. useless justification by markbo · · Score: 1
    With an almost unlimited supply of addresses, every new washing machine, for instance, could have its own IP address, allowing it to alert a service person electronically of a needed repair before it stopped working in the middle of a cycle.


    I love these justifications for new technologies/services/protocols. How about having a product that alerts the user AT THE MACHINE before seeing the need for remotely alerting a technician?

  78. What the number loks like... by lauterm · · Score: 1

    340,282,366,920,938,463,463,374,607,431,768,211,45 6

  79. when did /. become a Rupert Murdoch company? by deviator · · Score: 3, Insightful

    These articles remind me of FOX news... total sensationalism to drive advertising & page views.

    Whether you "approve" of NAT or not, the truth is that it is a very effective band-aid that has hindered the progress of IPv6 because it works so well. We'll be on IPv4 for at least another ten years.

  80. Is this another y2k situation? by Alpha27 · · Score: 1

    Seriously now, do I need 100 IPs? This is really sounding more like overhype than a realistic world outcome. This expectation that I need 100 is ridiculous.

    I'm going to ramble a bit on possible examples to prove a point that each human does not need 100 IPs.

    Let's look at it this way.
    Why would a 1-2 yr old need 100 IPs?

    • Their tonka truck or barbie ferrrari now has upload capabilities?
    • The stroller digitally syncs the mileage to the home base station
    • The baby monitor is now using Wi-Fi to transmit data and allows for web cam uploads.
    Hell the kid can't even grip the remote correctly! They can't even whip their own parallel port (read into it as you may).

    Now lets look at the more tech savvy user.

    • My cellphone is now referenced by an ip instead of a phone number. By the way, I'm hosting a pr0n site from my cell phone.
    • My TV, Microwave and Washer/Dryer get updates from the web. You never know when yuo need to hack your rinse setting.
    • My car gets its fuel by email and has a built in webcam so you can see the bumper sticker on the car in front of me. If I'm caught speeding, the cop can email me my ticket directly to my car. They can tell me to pull over too. Wow.

    According to the article Stanford Univ. has 17 million IPs compared to India's 2 million. The problem is the old allocation of the IP addresses. If a company can't use it, cough it up and reallocate.

    Also, why would my own devices need dedicated IP addresses? If I'm on my home network, the machine gets an internal IP address. There's no need for my machine to use anything else. I don't run into issues playing online games. I currently use a Dynamic IP from my DSL provider to access my home box and I can port forward as needed.

  81. Another advantage of IPv6 by riflemann · · Score: 4, Insightful
    IPv6 has a nice advantage over IPv4 that I havent seen mentioned many places before. This is one on security.

    One of the major contributing factors to problems such as spammers and crackers is that it's so darn easy to scan subnets in IPv4 for open hosts. It can take under a minute to scan a complete /24 for hosts with open ports.

    Now with IPv6 this situation is different. Each subnet has 64 bits of address space. That is, 18446744073709551616 IP addresses per subnet. Now, if someone could portscan at the rate of 100 addresses per second (pretty impressive), then each subnet would take 5.8 billion years[0] to scan for hosts. For one subnet! And to put this in a wider context, each site in ipv6 has 65,000 subnets. Effectively making network scans a thing of the past, and massively increasing security of the 'net.

    Of course, one can still scan known hosts (eg from web server logs), but doing that is a heck of a lot harder - you'd need to get them in the first place.

    [0] Said with appropriate finger quotes.

    1. Re:Another advantage of IPv6 by ptr2void · · Score: 1

      This _might_ prevent spammers from finding an open relay. I doubt it. At least as long as there are any IPv4 hosts around, they'll just scan and abuse IPv4 hosts. And Internet4 won't go away within a few months.

      Do you want to split Internet6 mail from Internet4? Might be a good idea. We coult get rid of Sendmail that way. ;-) Make encrypted transmissions the default. Demand a real return address. Unfortunately, it won't happen. IPv6 has acceptance problems as it is (chicken-egg-wise). Introducing a new MX system won't ameliorate that.

      Anyway, what has this to do with security? Public servers have static, well-known (say "DNS") IPs anyway. Private hosts used to have dynamic IPs in the IPv4 world. This *might* shift a bit with IPv6, making your host easier to track by malicious crackers (once it has been located at a given IP address).

      So in what way does the address room of IPv6 buy us security? (Yeah, theres IPSec and whatnot part of IPv6, but we're pondering the addresses here.) If anything, IPv6 addresses decrease security (but not by much).

    2. Re:Another advantage of IPv6 by Trifthen · · Score: 1

      Many ISP's also portscan their customers to make sure nobody is running evil services, partly to increase security. With this large of an increase in IP space, it's much easier to hide in the vastness of that space. Hence it'll be much much easier for a black hat to hide, hop addresses, and so on - all within one subnet.

      So, while this may get rid of script kiddies as they have no boxes to hack anymore, the really dangerous people will essentially be untrackable. Ouch. Then again, they already are, this just makes it easier for them. Heh.

      --
      Read: Rabbit Rue - Free serial nove
    3. Re:Another advantage of IPv6 by AstynaxX · · Score: 1

      You post assumes that neither network speed nor processing power will increase in future. These are assumptions we know to be false. So, network scanning will die off temporarily, but it will be back once hardware catches up (much like how older cryptographic keys had to be scrapped because modern processors could factor them out brute force nowadays)

      --
      -={(Astynax)}=-
      "Darkness beyond Twilight"
    4. Re:Another advantage of IPv6 by quantum+bit · · Score: 1

      This is simply a case of the brute-force approach being easier. Once confronted with a huge address space, sniffing the traffic to see if anybody's connecting to any "evil" services becomes easier than portscanning, so the ISPs will do that instead.

      And since each customer (assuming they stick to the spec) gets their own /64, it's quite easy to pull the plug on a blackhat who simply hops around in his own subnet (block the whole subnet).

    5. Re:Another advantage of IPv6 by /dev/trash · · Score: 1

      That's just one machine, I am sure that there will be a distributed set of tools that reduce that scan time down a bit.

    6. Re:Another advantage of IPv6 by Anonymous Coward · · Score: 0

      Incidentally, even "known" hosts in logs may change addresses. Microsoft's IPv6 stack uses two different autoconfiguration schemes: one is MAC based, and always there for inbound connectivity purposes; the other is randomized and used for most outbound connectivity. The randomized one changes every few hours. For people accessing web sites, this is the one that will hit the logs.

  82. Bullshit! by Fefe · · Score: 5, Informative

    IPv6 is bad because Cisco routers suck. No, wait, "Many of Cisco's routers" suck. You can' be serious! Once IPv6 gets off the ground, IPv6 will become fast path and eventually IPv4 will be dropped to legacy mode.

    About your point 2: IPv6 does not actually give out all those 2^128 IPs. The first half is for the network part, the second 64 bits are for the host part. This is necessary because autoconfiguration (which is really great, by the way!) uses a 64-bit part. The IPv6 autoconfiguration is stateless, by the way, which means it will also work without a DHCP server and it won't need reboot if the routers were down when the autoconfiguration process started.

    The point about having this many addresses is that you never ever want to have to come into the remote possibility to have to switch to IPv8 because IPv6 is too small. And when you rant about the IPv6 header being 20 bytes larger than the IPv4 header, consider that the overhead of the TCP header (20+ bytes), the HTTP header (300 bytes), the Email header (500 bytes?), ... most of the internet protocols are very wasteful. On the other hand, they are easily debuggable with relatively simple tools. This is a trade-off, obviously, and IPv6's choice is not per se good or bad, it's just different. We will see whether it will have a significant overhead. I say getting rid of spam is a better way to reduce bandwidth requirements on the internet than talking about header sizes.

    IPv6 is ready for prime time. People are using it (I, for example). You can buy access to IPv6-native backbones. All the major OSses support it. There is really no excuse not to be already using it.

    1. Re:Bullshit! by batura · · Score: 1

      There is really no excuse not to be already using it.

      And you call his post bullshit? I've got absolutely no reason to use IP6, but plenty of little green reasons why not.

    2. Re:Bullshit! by Florian+Weimer · · Score: 2, Interesting

      IPv6 is bad because Cisco routers suck. No, wait, "Many of Cisco's routers" suck. You can' be serious! Once IPv6 gets off the ground, IPv6 will become fast path and eventually IPv4 will be dropped to legacy mode.

      On most Cisco high-end routers, upgrading to larger IP addresses requires soldering (or replacement of fundamental router components, which amounts to the same thing). At the moment, only one or two linecards for the GSR series support IPv6 routing at wire speed (and the multi-purpose CPUs on the others are far too slow to route anything of importance). The 65xx/76xx series requires hardware upgrades which are not yet available AFAIK (several TCAMs have a word width which is too small for IPv6).

      IPv6 is ready for prime time.

      Not at a global level. The current approach to global routing is so discouraging that many people plan to continue using NAT (and IPv4) to gain the routing flexibility they need.

      All the major OSses support it.

      Only with a very reduced feature set, and most currently deployed embedded systems don't support IPv6 at all. For example, IPsec for IPv4 is much more widely available than for IPv6.

    3. Re:Bullshit! by NilsK · · Score: 2, Interesting

      IPv6 is ready for prime time. People are using it (I, for example). You can buy access to IPv6-native backbones. All the major OSses support it. There is really no excuse not to be already using it.

      Privately, you can use it, correct. In an commercial environment you can not really setup an IPv6-network, because there are many devices not supporting ist. At least printers are a show stopper. All those other devices (barcode-scanners, IP-Phones, cameras .. whatever speaks IP today) is part of the infrastrucure and has to be IPv6-capable to start using it.
      So at first we have to get the vendors to make the devices capable of IPv6, then wait for about 5 years and then we can use it in a commercial area.

    4. Re:Bullshit! by evbergen · · Score: 1

      IPv6 is ready for prime time. People are using it (I, for example). You can buy access to IPv6-native backbones. All the major OSses support it. There is really no excuse not to be already using it.

      Except that connectivity provides you with little but the feeling of driving on a nice highway from nowhere to nowhere.

      As Dan Bernstein says: what use is IPv6 if you can't use it to talk to www.cnn.com and smtp.hotmall.com?

      IPv6 should have encompassed the whole IPv4 space.

      IPv6 is to IPv4 what the Itanic is to IA32. IMHO, the IETF should have gone the Opteron route.

      Cheers,

      Emile.

      --
      All generalizations are false, including this one. (Mark Twain)
  83. How long are IPv6 addresses? by ParadoxDruid · · Score: 1

    Simple question that I googled and still haven't seen an answer to:

    How long is the IP address under IPv6?

    There are still servers that I visit (for games, etc), using the real IP address... like 131.107.164.10, a great Halflife server.

    That's 11 digits... I think I could easily remember 16 to 20 or so. Beyond that, I think I'd be straining to keep the different IP addresses all serperate in my head.

    So, how long is an address under the new proposal?

    --
    This statement is solely an opinion. Kindly take it as such in all cases.
  84. Impending?! by mekkab · · Score: 4, Insightful

    As a networking engineer, I am very concerned about the impending doom of IPv4 addresses running out.

    But I am even more-so concerened about the sun burning out, because that would mean catastrophe for the human race! (not to mention it would mess up our nift wi-fi stuff!)

    Seriously- with stop-gaps like NAT and ISP's recycling IPs from a pool for all users, its not gonna kill us.

    Let cell phones work out this ipv6 thing, then tunnel, then upgrade piece by piece.

    --
    In the future, I would want to not be isolated from my friends in the Space Station.
  85. Is it just me or... by BJZQ8 · · Score: 1

    Is it just me or is 2001:0700:0700:0003:0290:27ff:fea2:477b much harder to remember than 209.174.99.125? I think that the IP crisis is best resolved by proxying and redirecting, not adding more numbers. But maybe it's just me...

    1. Re:Is it just me or... by MImeKillEr · · Score: 1, Interesting

      Is it just me or is 2001:0700:0700:0003:0290:27ff:fea2:477b much harder to remember than 209.174.99.125?

      Yup. Much easier to remember the current scheme than it is to remember what basically looks like a friggin' MAC address.

      Heck, I can't remember my MAC address 2 minutes after looking it up.

      Two questions:

      1) Why are they going this route? I mean, they're only using alpha characters A through F, right? Wouldn't they get more addresses by simply adding another four octets? It seems like it'd be easier to remember 198.163.192.99.147.80.112.6 than that listed in the article..

      2) What would be come of 127.0.0.1?

      Someone with good math, pipe in and give the formula for the proposed IPv6 vs. the current scheme with four additional octets?

      --
      Cruising the internet on my TI-99/4A @ a whopping 300 baud!
    2. Re:Is it just me or... by praxim · · Score: 1

      1) IIRC, the goal is to not have to memorize an IPv6 address.

      2) It becomes ::1. I think that's pretty easy to deal with. (IPv6 address are collapsible, so zeroes can be omitted.)

      For more information, check (shameless plug) http://www.lug.psu.edu/presentations/ipv6.pdf, an overview of IPv6.

  86. You have the solution!!! by dlosey · · Score: 1

    To solve the "I pee" crisis, you need a networked toilet. Drinking less coffee might help too.

  87. I call FUD!!! by PSaltyDS · · Score: 0, Flamebait

    This is such FUD!!! There is a pure sales agenda behind the drive for v6. V6 has advantages over v4, but they come at extreme costs and the customers DON'T WANT IT! The garbage about 100 addresses for every person is just stupid hype that harkens back to the internet-connected-toaster days! AAAARRRRRrrrrgh!!!

    Warning - Blood pressure exessive. Bleed me before my head explodes!

    --
    Any technology distinguishable from magic is insufficiently advanced. - Geek's corollary to Clarke's law
  88. It's Worse Than Y2K! by jazman_777 · · Score: 1

    Better stock up! I recommend Gold and Guns (don't forget the ammo!).

    --
    Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
  89. Re: Not again... (average?) by driftingAimfully · · Score: 2, Insightful
    The average home generally has a couple PCs

    That'll be the average home out of the thin slice of humanity that can afford two PCs. I suspect, although have absolutely no evidence to support it, that the average is nearer 0.05 PCs per home.

    Sorry, I didn't mean to be so annoyingly righteous :) You're right about the IP stuff.

  90. NAT fixes everything is tired by ughhgu6 · · Score: 2, Insightful

    NAT for your car?
    NAT for your PAN?
    NAT on a plane?

    How many protocols have been kludged up because of having to get around NAT?

    Easier VPN's and Voice/Video are two things I can think of.

    On a slightly different note, anyone who says NAT's good for security...wow.

  91. So Big? by Anonym1ty · · Score: 1

    "so big that there's not a word for the number,"

    Maybe we should just call it Googol? (Google?)

    Sorry don't hate me, I had to.

  92. NAT, not. by saintjab · · Score: 2, Insightful

    I see a lot of individuals saying, oh we can just NAT. Well thats not the point here. For many environments NAT is not a functioning option. Not to mention, until the ISP and providers are running IPv6, we are still forced to route at the gateway. It's not NAT, but it's also not truly IPv6 either (read: 6to4 host). This is all great planning for the future but right now IPv6 is simply something to play with and get used to for the future. I'm running it at home, have been for some time (using 6to4 unfortunately) and I've not really seen any great benefits. There will be great benefits in the future, but we are not really able to enjoy them yet. At least until the infrastructure that delivers my connectivity is upgraded I won't. Until then I'll have to enjoy the dancing turtles (kame) and hope it catches on soon.;p

    --
    "Reality is a crutch for people who can't handle drugs" - George Bernard Shaw (1856 - 1950)
  93. what about giving ip address to pets/farm animals by Anonymous Coward · · Score: 0

    Hey we can make use of the addresses by assigning ip address to all our pets so that we can track them down or communicate remotely with them. Also the farmers can have IP address for all their farm animals so that they know which one is effected with foot-and-mouth virus.

  94. Re-claim unused address space by packethead · · Score: 3, Interesting

    It's probably been mentioned, but what about companies that have a single or multiple CLass "A"s that could just NAT? I was at a Ford dealership recently and noticed that they had a printer on a public address. Now it was probably NAT'd behind a router, but 5h1t! NAT an RFC 1918 address, not a public one!

    --
    .sig
  95. Novell : always ahead of the times by Gothmolly · · Score: 1

    When Novell introduced IPX, they clearly must have been thinking to way beyong IP6. IPX should give something like 4 googles worth of addresses?

    --
    I want to delete my account but Slashdot doesn't allow it.
    1. Re:Novell : always ahead of the times by pe1chl · · Score: 1

      The IPv6 address space is 65536 times larger than the IPX address space.

    2. Re:Novell : always ahead of the times by Gothmolly · · Score: 1

      IP-X
      It was a joke, get it? IP-10 ?

      --
      I want to delete my account but Slashdot doesn't allow it.
  96. The True Crisis by Nonki · · Score: 1

    The true crisis will be that with 100 IP's for each person, assigned to everything from your toilet to your coffee machine, not only will your computer be hacked but now any electronic appliance in your home has the potential to be controlled by a hacker. I think this would be great fun however, just think of it -- hacking into your buddy's electronics making them all erratically switch on and off, change channels, flush, whathaveyou.

  97. You guys are all being asses. by Elwood+P+Dowd · · Score: 1

    Obviously, whether we'll need 100 IPs per person is pretty debatable. Ever, let alone soon.

    However, right now, I'd like to have five IPs. My provider charges me $5/month/IP. I realize, that's just my provider trying to milk me, but I'd *love* for IPv6 to be rolled out right now. It would make a million things so much easier.

    I'm a leech on Kazaa, BitTorrent, Gnutella. I can't share, because of NAT. Think about how many users out there are slowing down P2P systems (including legal ones like Steam), that would be contributing if it weren't for NAT.

    --

    There are no trails. There are no trees out here.
    1. Re:You guys are all being asses. by DukeyToo · · Score: 1

      Maybe you know this already, but you can give up your leechiness, by opening and forwarding the relevant ports to the PC you are using. Most NAT boxes support some form of doing this. Once I did that, BitTorrent was much more pleasant :)

      Although I did have to start worrying about the shiny new security hole. Oh well, you can't have everything.

      --
      Most writers regard truth as their most valuable possession, and therefore are most economical in its use - Mark Twain
    2. Re:You guys are all being asses. by Elwood+P+Dowd · · Score: 1

      Unfortunately, with my NAT box, that means I have to turn off DHCP. I don't want to give up that convenience.

      I realize that part of my problem may be unique, but still, many, many potential peers out there are not peers, simply because they can't receive transfer requests.

      I've never understood why my Gnutella clients won't let me poll an ultrapeer for push requests (a la AOL IM file transfers). Maybe it's in the protocol, but I've never seen it happen. It still wouldn't let me transfer files to another user behind NAT, but it'd be a step up.

      --

      There are no trails. There are no trees out here.
    3. Re:You guys are all being asses. by Quill_28 · · Score: 1

      Just curious, why would you want DHCP on your router in the first place?

      You have plenty on non-routeable ip's, why bother with DHCP?

      Do you have new computers constantly connecting to your networks, and don't want to enter an ip address for them?

      Just curious.

    4. Re:You guys are all being asses. by Elwood+P+Dowd · · Score: 1

      Yeah, more or less. A few of my friends have iBooks, and I'd love for them just open up and run. Also, my roommates have two computers, and I'd prefer to never, ever, ever have to touch them.

      I've got a project computer that never seems to be running the same operating system for over a month or two.

      If it were just my machines, I'd probably be fine without DHCP. It's just so convenient.

      --

      There are no trails. There are no trees out here.
  98. And in related news... by buffy · · Score: 1

    Every computer, including ATM machines, cars, airplanes, weapon systems, and your inflatable sex doll will cease to operate correctly on January 1, 2000. This so called "Y2K Bug" will bring civilization as we know it to an end.

    -buf

    1. Re:And in related news... by bucky0 · · Score: 1

      Although a lot of embedded systems which don't handle years fared just fine, the reason we didn't have any sort of a meltdown was because there was billions of dollars put into fixing old systems.

      Looking at what happened and saying that there was no threat is silly.

      --

      -Bucky
    2. Re:And in related news... by buffy · · Score: 1
      Looking at what happened and saying that there was no threat is silly.

      Ok...I'll give you that, but at the same time...looking at what happened and saying it wasn't blown out of proportion is silly as well.

  99. Oh come on by cxreg · · Score: 1

    everyone knows that 24 is the highest number

  100. IPv6 is coming, but for other reasons by McMuffin+Man · · Score: 2, Insightful

    The shortage of IP addresses has been a "crisis" for over a decade now. CIDR and NAT have pretty much kept it under control, and could continue to do so for a while yet. As people have been pointing out, we only need a unique address for each personal accessory if we need end-to-end connectivity from my left shoe's inflation co-processor to every networked nipple ring in Norway.

    Nonetheless, IPv6 is moving forward, and for a much simpler reason: money. The US military recently placed a deadline on IPv6 deployment, and they will no longer buy anything unless it's ready for IPv6 or its vendor promises it will be soon. Many of the key companies in the networking market need to sell to one part or another of the US DoD.

    This requirement is putting IPv6 support on the development schedules of many companies that had been perpetually putting it off. Expect the US military and government to push ISPs for stronger IPv6 support so they can interoperate with their suppliers in their preferred fashion.

    In other words, if you don't have a killer ap, get a killer user.

  101. Impending IP crisis... by Psx29 · · Score: 1

    I thought we were already in an IP crisis...I mean look at all the crazy patents and these companies like SCO?

  102. The killer app by Jeedo · · Score: 2, Insightful

    The killer app that you're looking for are 3G cell phones,
    Every 3G cell phone has to have a IP address, and thats quite alot if you're talking about IPv4 addresses.. So a solution must be found, which people will find in IPv6.
    I expect IPv6's rise to be concurrent with 3G's adoption.

    1. Re:The killer app by Anonymous Coward · · Score: 0

      Now all we need is a killer app for 3G.

  103. -1 TROLL! by Anonymous Coward · · Score: 0

    I was about to bite this, but nah, forget it.

  104. portable IPv6 effect on route summarization? by mdouglas · · Score: 1

    Has any thought been given to how IPv6 is going to effect route summarization? Under IP4 user ip's are suballocated by ISP's to users, the ISP's themselves are supposed to announce one aggregate route for all their users. If everyone gets an IPv6 block assigned directly from the numbering authority the internet routing table is going to be staggeringly enormous. Check out the CIDR Report which details current aggregation effeciency losses under IPv4.

  105. There is a word for the number by adenied · · Score: 5, Informative
    2^128 is: 340,282,366,920,938,463,463,374,607,431,768,211,45 6

    Which is: 340 undecillion, 282 decillion, 366 nonillion, 920 octillion, 938 septillion, 463 sextillion, 463 quintillion, 374 quadrillion, 607 trillion, 431 billion, 768 million, 211 thousand, 456.

    A far cry from "35 trillion". To give you an order to this magnitude, some Australian scientists recently announced that there are 70 sextillion stars (give or take) in the known universe.

    It may be pedantic, but someone who is so blinded by their work that they make hysterical claims that there's no word for the number they're pushing doesn't make me want to buy into their idea so quickly.

    1. Re:There is a word for the number by Cheeko · · Score: 1

      Another number that I heard quoted in a previous story is that there will be more IPv6 addresses than there are particles in the known universe. Whether this is true, I have no way of telling, but doing a comparison with the number of stars, it seems like a modestly reasonable claim.

  106. There is a way to say the number.. by pope1 · · Score: 1
    pope1@mobius:~$ bc -l
    bc 1.06
    Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc.
    This is free software with ABSOLUTELY NO WARRANTY.
    For details type `warranty'.
    #IPv4
    2^32
    4294967296
    #IPv6
    2^128
    340282366920938463463374607431768211456
    quit
    p ope1@mobius:~$ number 4294967296
    four billion.
    two hundred ninety-four million.
    nine hundred sixty-seven thousand.
    two hundred ninety-six.
    pope1@mobius:~$ number 340282366920938463463374607431768211456
    three hundred forty undecillion.
    two hundred eighty-two decillion.
    three hundred sixty-six nonillion.
    nine hundred twenty octillion.
    nine hundred thirty-eight septillion.
    four hundred sixty-three sextillion.
    four hundred sixty-three quintillion.
    three hundred seventy-four quadrillion.
    six hundred seven trillion.
    four hundred thirty-one billion.
    seven hundred sixty-eight million.
    two hundred eleven thousand.
    four hundred fifty-six.
    pope1@mobius:~$

    There! See?
    Its just a little over 340 undecillion.

    Whats so hard about understanding that? =)~

    As a side effect of performing that silly
    computation i vote "nonillion" as the funniest
    numeric suffix in the universe.

    --
    /* * pope1 */
    1. Re:There is a way to say the number.. by r55man · · Score: 1

      1.1 mole

  107. Re:Not so much a crisis... (I can't resist) by Dorothy+86 · · Score: 0

    If NAT is a problem wih IPv6, then why can't everyone go to the brand new IcuP?

  108. Switch by Alton_Brown · · Score: 0

    I'm writing to share a tragic little story.

    My Dad has a PC that my sister and I used to use for our homework assignments. One night, I was writing a paper on it, when all of a sudden it went berserk, the screen started flashing, and the whole paper just disappeared. All of it. And it was a good paper! I had to cram and rewrite it really quickly. Needless to say, my rushed paper wasn't nearly as good, and I blame IPV4 for the grade I got.

    I'm happy to report that my sister and I now don't have to share IP's thanks to IPV6. It's a lot nicer to work on than my dad's IPV4 was, it hasn't let me down once, and my grades have all been really good.

    Thanks, Verio.

    Ellen Feiss

  109. There *is* a word for this number by Anonymous Coward · · Score: 2, Insightful

    IPv6 will increase the supply of addresses from 4 billion today to a number in excess of 35 trillion that is "so big that there's not a word for the number," says Cody Christman, director of product engineering for Verio, which offers IPv6 in San Francisco, Washington and elsewhere.

    How about 1.1 mole

    Cody Christman's high school science teacher must be very disappointed. :=)

  110. Names of Numbers by The+Famous+Brett+Wat · · Score: 1

    You'd be surprised at how big numbers can be and still have names. (For what it's worth, I prefer the American names over the British ones, and I'm Australian.)

    --
    proof, n. A demonstration that a conclusion is implied by certain premises and axioms.
  111. Didn't I Read about this in 1996... by richmlpdx · · Score: 1

    and 1997...
    and 1998...
    and 1999...
    and 2000.............

  112. Global Ethernet? by PetoskeyGuy · · Score: 1

    Is it just me or does this seem like a step backwards? It's kind of like using MAC addresses instead of IP, just a laywer higher. I don't want every machine I have to be accessable from the internet. Besides if IP addresses were not allocated correctly, then reallocate them. IBM doesn't really need Millions of addresses. I think this bit of future is the same as those jet-powered-bubble-domed-tail-fin cars being in every garage.

    I can't wait for the new NEWBIE sites to pop up. Instead of Click here for Porn! (http://127.0.0.1/) it will be Click here for Porn! (http://2002:0440:C00C:3003:0000:CF00:C0A8:2E2E/)

    HA Sucker!

    1. Re:Global Ethernet? by man_ls · · Score: 1

      Shouldn't that be

      Click here for Porn! (http://::1)?

      That is, iirc, the IPv6 local loopback.

  113. My company has a ton of IPs... by smkndrkn · · Score: 2, Interesting

    ...that they do not use. This is because they were one of the first companies on the scene when the Internet started. But we have TONS and TONS of IPs that are not in use. I bet that if companies like mine gave all the un-needed IP space back we'd be better off for a while.

    --
    ======== In the future, everything will be artificial. ========
    1. Re:My company has a ton of IPs... by Anonymous Coward · · Score: 0

      very true. I'm in the same situation. 12 class Cs and have 3 not in use, and as time goes on we are using LESS and LESS IPs.

      Why? We are using NAT more and more. When our ISP first started we were giving away half a class C or a WHOLE class C for our customers use, but with viruses/worms/crax0rz/ etc., many of our customers welcome the chance to move to NAT.

  114. Why so many IPs? Simple... by psxndc · · Score: 1
    Why does every human need 100 IP addresses?

    Simple. Every person will have RFID tags in everything they wear, use or eat. You gotta supply IPs for all those tracking devices.

    psxndc

    --

    The emacs religion: to be saved, control excess.

  115. RIAA vs. IPv6 by thePancreas · · Score: 1

    better quality audio and faster video streaming. nuff said

    --
    I went to battle MC Escher, but drew a blank
  116. Hello, NAT and port-mapping??? by Anonymous Coward · · Score: 0

    I'll be damned if I'm going to sit appliances in my home on a public IP address, especially if Microsoft has anything whatsoever to do with the software under their hoods-- I'd rather not have some punk kid setting my hot water heater's thermostat to "Boil" from his bedroom in Uzbekistan while I'm at work.

  117. A "file server"... by Anonymous Coward · · Score: 0

    ...should only be pushing out files, no?

  118. Forgetting about NAT? by x00101010x · · Score: 1

    I consider myself a technophile. I've got a lot of gear at home and I'm in the process of putting a number of sensors and controls on the internet.

    However, the last thing I'd do is put each device out on it's own IP for the world to see. Wouldn't it be great fun for hackers to find an exploit in the new GE refrigerator and go spoiling all the food in every apartment in NewYork during the heat of summer? As if it didn't smell enough...

    Even if I had 100 devices at home, each one would just have a port mapped from my gateway device (a $200 WalMart special running RH9). I seriously doubt I'm going to have around 65k devices that need to be exposed to the net.

    So, my cell may have it's own IP, and maybe my car, but that's still just 3 internet IP addresses for a technophile. Any other web enabled gadgets I want can be routed through the Home/Car/Cell connection.

    I really see no problem here. Besides, even though web enabled devices will spread from the techies out to main stream consumers, we're still talking upper middle class and up. And mostly just in the US/Canada/EU/Japan.
    I could see 3 to 10 IPs per person tops, and that's far from a crisis.

    Now, you could argue, more sites and businesses on the net will take up more addresses, but many of the hosting solutions I've looked at offer a "virtual" server on a shared physical box, probably using host headers and such (neat trick, read the host header and redirect the requests to a specific site based upon the URL in the request, even IIS does it).

    --
    DONT PANIC
  119. IP addresses running out... by Anonymous Coward · · Score: 0

    ... any day now. Been hearing this since 1996 how we will all make the move to IPv6. Don't see this happing quickly and just really don't care at this point.

    Suppose we will be talking up IPv7 or IPv8 someday though.

  120. No word for it? by hesiod · · Score: 1

    > a number in excess of 35 trillion that is "so big that there's not a word for the number,"

    If it's so far in excess of 35 trillion, why was 35 trillion even mentioned? If it's between 35-36 trillion, then those are the words to describe it. If it really IS far in excess of 35 trillion, why bring it up at all? Just say "more than we will use in the considerable future," or some other equally vague phrase.

  121. IPv6 crisis already ? by zdzichu · · Score: 1

    There's something with IPv6 addres mentioned in article:

    traceroute to 2001:0418:000C:0003:0000:CF00:C0A8:2E2E (2001:418:c:3:0:cf00:c0a8:2e2e) from 3ffe:8010:18:10::1, 30 hops max, 16 byte packets
    1 3ffe:8010:18:10::1:1 (3ffe:8010:18:10::1:1) 59.674 ms 7.615 ms 6.824 ms
    2 amba6.bydg.pdi.net (3ffe:8010:18:1::1) 67.952 ms 71.454 ms 69.572 ms
    3 6bone-gw.6bone.pl (3ffe:8010:18::1) 69.778 ms 71.762 ms 69.695 ms
    4 from-icm.6bone.atman.pl (3ffe:8010:9f::2:1) 79.676 ms 76.49 ms 69.673 ms
    5 3ffe:81d0:ffff:2:: (3ffe:81d0:ffff:2::) 380.154 ms 438.2 ms 429.549 ms
    6 fe-tu0.pao.ipv6.he.net (3ffe:81d0:ffff:1::1) 409.868 ms 545.375 ms 539.485 ms
    7 * * *
    8 * * *

    ;->

    --
    :wq
  122. Question the Messenger by truffle+pig · · Score: 1

    This seems like a ploy by this "Charmed Technologies" to grab headlines. 100 IP Addresses per person? I would imagine we might need this someday, but when you follow the link to the Charmed Tech website you start to understand why that guy thinks this is an immediate need. They are trying to sell wearable computers and IP enabled sunglasses.

    This seems like a sky is falling news release to get their name out there and get people thinking about wearable computing.

    I wouldn't get too upset about it as it were. But this is no reason not to think about IP6 as we are going to need it eventually.

  123. 100 IP's per human... by rjoseph · · Score: 1

    ...and yet my broadband provider still rapes and plunders me every month for my own static IP?

  124. Ask a psychologist about 7 plus or minus 2 by Anonymous Coward · · Score: 0

    You know, that's the idea that supposedly went into the decision behind the 3-3-4 split for phone numbers in the US (and the NANP by extension). People can remember numbers that are in that general area. This is getting stretched a bit thanks to the requirement to dial 10 digits in some areas, but the general idea applies.

    Look at IPv4. I can remember just about all of the important IP addresses in my life. The systems at work, my routers, my stuff at home, and then some. They're short numbers, and they are all within a couple of simple blocks.

    Now look at a typical IPv6 address. It's scary. There's a lot of stuff going on there. 8 blocks of 16 bits? That's pretty dense in terms of information storage. I can't imagine remembering them.

    Look at it this way: how many MAC addresses do you remember? Those are only 48 bits. IPv6 is 128. Ouch.

    My unscientific reason for why IPv6 hasn't taken off is that the numbers look scary and people feel unconfortable when looking at them. I sure do. It would be different if there was a pressing reason for me to change, but there isn't, so why should I bother trying to learn these things?

  125. I need 100 IP's? by Tragedy4u · · Score: 1

    "we're going to need something like 100 IP addresses for each human being."

    I need 100 IP's? Then why does my ISP still try and charge me when I want more than one, those bastards they're ripping me off!?!?!

    Ok ISP's make with the 99 other IP addy's!

  126. "so big that there's not a word for the number" by swillden · · Score: 3, Informative

    Is that right? Lessee:

    2^128 = 340,282,366,920,938,463,463,374,607,431,768,211,45 6

    A number which everyone knows should be verbally expressed in English as:

    Three hundred forty undecillion two hundred eighty two decillion three hundred sixty six nonillion nine hundred twenty octillion nine hundred thirty eight septillion four hundred sixty three sextillion four hundred sixty three quintillion three hundred seventy four quadrillion six hundred seven trillion four hundred thirty one billion seven hundred sixy eight million two hundred eleven thousand four hundred fifty six.

    That's in the American naming system, of course. In the British system, it would be:

    Three hundred forty sexillion two hundred eight two thousand three hundred sixty six quintillion nine hundred twenty thousand nine hundred thirty eight quadrillion four hundred sixty three thousand four hundred sixty three trillion three hundred seventy four thousand six hundred seven billion four hundred thirty one thousand seven hundred sixty eight million two hundred eleven thousand four hundred fifty six.

    (Interesting to note that the British version is nine characters shorter, plus has the capability to scale much higher without extension).

    In the interest of brevity, I shall forgo the Spanish, Italian and French versions, and I regret to say that I can't count that high in any other languages, though I'm certain it's possible.

    So, I think the number is *quite* adequately named, thank you. Now there's not a single word for it, but few numbers have single-word names, simply because there are too many numbers, too few phonemes and no real need. If you want a single-word approximation, "undecillion" should do nicely, or "340 undecillion", since Mr. Christman seems to find that form acceptable. The ideal expression is, of course, "two to the hundred twenty eighth", which is short, completely accurate and gives a strong hint as to the origin of the value (a string of 128 bits).

    Yes, I *am* the guy everyone avoids at parties.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    1. Re:"so big that there's not a word for the number" by oojah · · Score: 1

      I would guess that you're from the US. I hope so, otherwise this post will look daft :)

      I'm a Brit and in my experience British people tend to leave out less words than Americans in numbers. Personally I'd say "Three hundred and forty undecillion two hundred and eighty two decillion..." . The lack of the "and" pains my ears.

      Also, I would be much more likely to take "two to the hundred twenty eighth" (with or without an "and" :) as meaning 2^(1/128). I would say "two to the power of a hundred and twenty eight" if I felt like being very clear and "two to the hundred and twenty eight" or "two to the one two eight" if I felt lazy.

      I mention this only because you described your expression as ideal which it isn't really to me. One man's medicine, another man's poison. Certainly, I am more likely to understand it (and be able to comprehend it) than the expanded versions.

      Aren't languages fun!

      Cheers,

      Roger

      --
      Do you have any better hostages?
    2. Re:"so big that there's not a word for the number" by swillden · · Score: 1

      I'm a Brit and in my experience British people tend to leave out less words than Americans in numbers. Personally I'd say "Three hundred and forty undecillion two hundred and eighty two decillion..." . The lack of the "and" pains my ears.

      Actually, most Americans would also say "and", but, technically, "and" should be only used to introduce a fraction, as in "twenty and one quarter". I forget where I picked that up, but I remember it as being a fairly authoritative source -- as much as any source can be authoritative on a language as dynamic as English, anyway.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    3. Re:"so big that there's not a word for the number" by SwissJon · · Score: 1

      Thank you for pointing out the correct way to say numbers in English.

      As you are clearly a pedant (and like me the sort of chap who gives Brits a bad name) I should remind you that you mean "fewer" words and not "less" words.

    4. Re:"so big that there's not a word for the number" by oojah · · Score: 1

      Yes, indeed. Thanks.

      A disclaimer - I didn't say that it was the correct way, just the way I would say it. See the other response to my post for an interesting take on the "and" situation.

      Cheers,

      Roger

      --
      Do you have any better hostages?
  127. So big there isn't a name? by NoMercy · · Score: 1

    A google is a very big number
    and if you take 1 and put a google of 0's after it, youve got a googleplex, so lets not say there not a word big enough for it.

  128. A new form of the 'remote control' syndrome by stuuf · · Score: 4, Interesting
    A similar revolution to what you are describing has already happenned in the audio/video/home theater industry. Remember when your VCR had that little door on the front that covered that huge array of tiny buttons for things like tracking, timers, tuning? Remember when you used a vcr? Now they have power, eject, channel, and transport controls. Everything else is on the remote that your universal unit can't emulate. Eventually the control panel on the washing machine will disappear in evolution, and you will have to run over to your pc, log into your washer, ener a password, start the cycle, etc. Or grab your cellphone and dial into your network's internet gateway (maybe dozens of routers away in timbuktu), connect to your home computer...

    Some devices weren't meant to be remote-controlled. And by some, I mean most. And even if they need to be, they don't need separate global IP's. People seem to forget that each of these 4 billion ipv4's have 65535 TCP ports.

    --

    Everyone is born right-handed; only the greatest overcome it

  129. It was 1999 actually by gosand · · Score: 1
    I'm sure I saw this exact same post on /. in 1998. Except then it said we'd run out of addresses by 2000.

    Hmm, not sure about the "running out by 2000" part, because the original article is long gone, but here is a Slashdot story from May 12, 1999.

    --

    My beliefs do not require that you agree with them.

  130. NAT will keep IPv4 alive past 2005 by blueworm · · Score: 3, Informative

    I don't think IPv4 addresses will run out by 2005, especially as more and more people/organizations implement more NAT. I work for a statewide ISP, and we've found that the new IP addresses we just got from ARIN a year ago are being returned to us in large numbers (thousands) by customers who are now persuing NAT solutions and using smaller subnets of 16 addresses or less.

  131. How will the transition happen? by Anonymous Coward · · Score: 0

    I was wondering why the transition to IPv6 hasn't happened yet... I can't just switch my computer because 1) my ISP doesn't know anything about IPV6; 2) my software is half-baked with respect to IPv6 support; and 3) none of the big sites are on IPv6.

    I was wondering why nobody was "taking the plunge".

    Then I read this article by DJ Bernstein.

    Ignore the general "djb-ness" of the article (i.e., I'm djb, I'm smarter than you, you assmunch), I suggest everyone read this carefully.

    Basically he is saying that there is NO clear path from here to IPv6 nirvana. And I totally agree, this is what I was feeling all this time.

    There is one addendum I would make though: IPv6 can happen globally when Microsoft decides to make it the standard. They are the only ones who can "centrally plan" the entire computer industry. Sad, yes.

    Do we want IPv6ms?

    Personally I vote for making NAT *much* more pervasive. Why does every ISP customer need an IP address, etc.?

    The only valid complaint about NAT I hear is that it breaks FTP.... B. F. D.

  132. WARNING! {Flash, Flash, Flash} by Chordonblue · · Score: 1

    Your computer is seeking an IP Address! You may be at risk!

    --
    "...Well, there's egg and bacon; egg sausage and bacon; egg and spam; egg bacon and spam; egg bacon sausage and spam..."
  133. You know you've been reading slashdot too long by TobascoKid · · Score: 1

    when you see IP in the headline and think intellectual property instead of internet protocol

    Tk

    --
    At some point, somewhere, the entire internet will be found to be illegal.
  134. IPv6: The Coming Address Shortage by handy_vandal · · Score: 5, Insightful

    Of course we'll run out of IPv6 addresses.

    Not right away ... but surely something will be invented that calls for more addresses.

    For example, teleportation might require separate addressing for all possible energy states of all elementary particles in the teleported object.

    Don't say it can't happen. Remember when 64k was all the memory anyone would ever need? and a megabyte hard drive was out of your price range?

    --
    -kgj
    1. Re:IPv6: The Coming Address Shortage by ivanmarsh · · Score: 2, Funny

      >For example, teleportation might require separate addressing for all possible energy states of all elementary particles in the teleported object.

      Doesn't the Heisenberg compensator eleminate the need for particle addressing?

    2. Re:IPv6: The Coming Address Shortage by Cyno · · Score: 1

      Actually IPv4 is theoretically enough for any population as paranoid as ours. Who really needs a live IP address these days anyhow?

      Everyone is so concerned about security they can't decide whether its good to have a valid IP address or NAT. Who is going to enforce this upon the attackers? Who is going to prevent THEM from using a IPv4 to IPv6 gateway or any other type of gateway into the network from an anonymous system.

      The purpose of IPv6 was for creating a network where everyone had their own IP address. That is no longer necessary and not exactly a good idea.

    3. Re:IPv6: The Coming Address Shortage by Tailhook · · Score: 1

      You don't have to dream up exotic applications to figure out how we'll end up running out of IPv6 address space. History will repeat itself and we'll run out of IPv6 the same way we ran out of IPv4; lack of foresight.

      Huge slices of the IPv4 space have been squandered on poorly thought out allocations. At one time it was common for a university or large corporation to grab up a class A, then proceed to actually use 2% of it. 16 million addresses are simply unavailable due to the 10.x.x.x subnet in RFC1918. That's enough space to operate about 250 class Bs ISPs each having about 250 class C subnets.

      When it gets down to brass tacks and we slice up the IPv6 space between the governments, schools, telecoms and other corporations and institutions, you can bet the same inability to predict the future will reveal itself and we'll screw it up all over again.

      IPv6 already has many built-in assumptions about the structure of the global Internet. The space isn't a free-for-all; there are official segregations at /32, /48 and /64 (probably others, haven't read the spec in a couple years.) There are "reserved" bits that, no doubt, most device firmware implemented today will assume can never be anything but zero. Unofficially there will be many more, and far more arbitrary segregations, with organizations acting in there own interest to acquire the largest possible piece of the pie. Who's going to tell the military they don't deserve a few million of those 4+ billion /32's?

      This is just another baby step in the history of networking. That you think it's a big deal, or some sort of "final solution", is due to a lacking sense of proportion about such technical trivia.

      If the global Internet (with IPv4) had existed prior to World War 2, you can bet that political forces would have had a say in the structure of the address space. Sovereign nations would have regulated the space with their own minders running the "official" routers. Enemy states would have claimed authority over the network and issued overlapping ranges. Militaries would have assumed control over vast swaths of space "in the national interest."

      Don't assume that there is some grand genius behind IPv6. People can talk all they want about the address space being larger than some vast collection of atoms. The fallibility of our limited intellects will always find a way to mess it up. Bank on it.

      --
      Maw! Fire up the karma burner!
  135. IPV6 better than NAT? by dpilot · · Score: 1

    Even if the Internet were IPV6, Adelphia would still only give me only one IP, and tell me not to put servers or a home network behind it. (Although for boku bux they'd rent me a garden-variety NAT box, and then let me have a home network.)

    --
    The living have better things to do than to continue hating the dead.
  136. I bet you that even under IPv6... by Tokerat · · Score: 1


    ...fscking RoadRunner will still charge me extra for using more than 3 IP addresses.

    --
    CAn'T CompreHend SARcaSm?
  137. re: bigger numbers by ed.han · · Score: 1

    googolplex? hey, isn't that the name of that new movie theatre that's going up? :D

    ed

  138. It has to be said... by felis_panthera · · Score: 1

    640K should be good enough for anyone.

    --

    The chains are broken
    Loki is free
    Ragnarok is at hand...
  139. In a related note... by Anonymous Coward · · Score: 0

    SCO has announced plans to license their IP to the world at large, for only a small monthly fee...
    -m

  140. New jokes by elviscious · · Score: 1

    I can't wait for all the new fat jokes -- That guys ass has it's own IPv6 address.

    Sure is nice to be a thin computer nerd

  141. another look at it.. by nachosternum · · Score: 1

    here's just a thought! how about every person gets an IP assigned to them via their ISP. once that IP has been given to the customer, if they want to use their cell, pda, blackberry, pager, what ever they need to use to get to the internet, they must go through that IP address and run NAT. so basically, each customer would be a gateway themselves for all of their devices. not to say that this will solve the IPv4 vs IPv6 issues but it may help reduce some of those needless IP assignments to people with a /20 that only need 2 addresses.

  142. Millions and billions by Andy+Dodd · · Score: 1

    Everyone defines millions and billions the same.

    The definition of the "giga" and "mega" prefixes vary though. Sometimes "giga" is 1024^3, sometimes it's 10^9. Mega is defined as either 1024^2 or 10^6.

    This isn't US-specific. Typically, the following use the power-of-1024 definitions:
    OSes, semiconductor storage (RAM/flash/ROM)manufacturers.

    The following usually use base-10 definitions
    All other storage mfrs. (Looks better on spec, and non-semiconductor storage isn't bound by practical constraints to being a power of 2), bandwidth measurements

    --
    retrorocket.o not found, launch anyway?
    1. Re:Millions and billions by th77 · · Score: 1

      I don't know... I could swear I heard somewhere that in Britain, "billion" could / used to mean "one million million."

      --
      Your favorite sig sucks
    2. Re:Millions and billions by daniel23 · · Score: 1

      > Everyone defines millions and billions the same.

      Right, with the only exception of the US who seem to have their private system.

      math US UK DE greek prefix abbr.
      10^9 billion milliard Milliarde gillion Giga- G
      10^12 trillion billion Billion tetrillion Tera- T
      10^15 quadrillion billiard Billiarde pentillion Peta- P
      10^18 quintillion trillion Trillion hexillion Exa- E
      10^21 sexillion trilliard Trilliarde heptillion Zetta- Z
      10^24 septillion quadrillion Quadrillion oktillion Yotta- Y
      10^27 octillion quadrilliard Quadrilliarde ennillion
      10^30 nonillion quintillion Quintillion dekillion
      10^33 decillion quintilliard Quintilliarde hendekillion
      10^36 undecillion sextillion Sextillion dodekillion
      10^39 duodecillion sextilliard Sextilliarde trisdekillion
      10^42 tredecillion septillion Septillion tetradekillion
      10^45 quattuordecillion septilliard Septilliarde pentadekillion
      10^48 quindecillion octillion Oktillion hexadekillion
      10^51 sexdecillion octilliard Oktilliarde heptadekillion
      10^54 septdecillion, septendecillion nonillion, noventillion Nonillion oktadekillion
      10^57 octodecillion nonilliard, noventilliard Nonilliarde enneadekillion
      10^60 novemdecillion decillion Dezillion icosillion
      10^63 vigintillion decilliard Dezilliarde icosihenillion
      10^66 unvigintillion undecillion Undezillion icosidillion
      10^69 duovigintillion undecilliard Undezilliarde icositrillion
      10^72 trevigintillion dodecillion, duodecillion Duodezillion icositetrillion
      10^75 quattuorvigintillion dodecilliard, duodecilliard Doudezilliarde icosipentillion
      10^78 quinvigintillion tredecillion Tredezillion icosihexillion
      10^81 sexvigintillion tredecilliard Tredizilliarde icosiheptillion
      10^84 septvigintillion, septenvigintillion quattuordecillion Quattuordezillion icosioktillion
      10^87 octovigintillion quattuordecilliard Quattuordezilliarde icosiennillion
      10^90 novemvigintillion quindecillion Quindezillion triacontillion
      10^93 trigintillion quindecilliard Quindezilliarde triacontahenillion
      10^96 untrigintillion sexdecillion Sexdezillion triacontadillion
      10^99 duotrigintillion sexdecilliard Sexdezilliarde triacontatrillion
      10^100 googol googol ein Googol

      The US-specials continue above the googol, this one number being communicable is nothing but an irregularity.
      Why this chaos? Like with decimal separators, date format, measures etc. Probably some game to test the degree of US dominance (will they use my expressions) or non-tariff trade barriors?

      A fine chart of number names is at
      http://www.uni-bonn.de/~manfear/large.php

      --
      605413? Yes, it's a prime.
  143. 35 trillion? by Rev.+DeFiLEZ · · Score: 2, Funny

    try:

    three hundred forty undecillion, two hundred eighty-two decillion, three hundred sixty-six nonillion, nine hundred twenty octillion, nine hundred thirty-eight septillion, four hundred sixty-three sextillion, four hundred sixty-three quintillion, three hundred seventy-four quadrillion, six hundred seven trillion, four hundred thirty-one billion, seven hundred sixty-eight million, two hundred eleven thousand, four hundred fifty-five.

  144. I like my buggy whip just fine! by Merk · · Score: 4, Informative

    I can't believe how many people have commented that there is no need for IPV6 because of NAT. Are you really willing to put up with the limits of NAT when you could give every computer its own routable address?

    NAT does a decent job of allowing you to surf the web using a non-routable IP address. For anything more advanced it starts working less and less well.

    I, personally have had many troubles with NAT:. Games which don't work properly unless they have huge ranges of ports exposed to the net. Instant messenger apps which fail in subtle ways. Brain-dead DHCP servers which don't properly pass on DNS settings, etc. Add to that the fact that the DHCP/NAT combination in most consumer boxes (like Liksys routers) is awful. You can port-forward from the router to a fixed IP address, but if you're using DHCP, you never know what machine will get that IP address! Even when it does work, there are far too many programs that don't work right when something is on a non-standard port.

    In fact, I don't just want each of my machines to have its own routable IP address, I want some machines to have multiple addresses. That way I can host multiple domains on a single machine and truly administer them differently. Right now HTTP sends a host neader so that you can have multiple domains on a single IP and things just work. On the other hand, HTTPS doesn't work like this, so you need a work-around if you want to use HTTPS. The simple truth is that today if you want to have multiple domains using anything other than straight HTTP on a single machine you really do need multiple IPs.

    For many people, NAT is a comfort thing. They think they don't have to worry about patching their systems because they're behind a dinky broadband router. Hint: that's security through obscurity. The devices you're buying aren't meant as firewalls, they're meant to let joe-consumer connect two computers to the Internet easily.

    The main reason I want IPV6 now is so that my damn Internet provider can't get away with charging extra for extra IP addresses. At the moment they can because they're relatively scarce, but I can't see them getting away with that with IPV6.

    If you're content with your buggy whip, that's great. But I personally have a use for at least 20 IPs that NAT won't solve. So don't make a blanket statement that IPV6 isn't necessary. Maybe not for you, but some of us can't wait to have it.

  145. Aren't IPv6 addresses a bit long? by sabNetwork · · Score: 4, Interesting

    I'm not an expert on IPv6 (nor IPv4 for that matter), but there is some practicality in question here.

    Can you memorize 204.172.4.36? Maybe not at first glance, but after you type it in a few times, you probably will.

    Can you memorize FEDC:BA98:7654:3210:FEDC:BA98:7654:3210? Definitely not at first glance, and very unlikely unless it is something which you must type every day.

    Some people's jobs depend on entering IP addresses, and IPv6 addresses are just so unnecessarily long that typing them is a total drag.

    ---

    Here's my RFC. 40-bit addresses. That gives you roughly a trillion addresses (a bit more actually), which is more than we should ever need. And you can write them in dotted-decimal format.
    Can you memorize 430.168.957.249? Probably.

    1. Re:Aren't IPv6 addresses a bit long? by Anonymous Coward · · Score: 0

      I don't know about you, but I read Slashdot at least once a day, and I still don't remember its IP address. However, I do make use of symbolic naming, so I can just query "slashdot.org". What makes you think that this can't scale up to IPv6?

    2. Re:Aren't IPv6 addresses a bit long? by sabNetwork · · Score: 1

      Of course, for browsing the web, you don't need to memorize IP addresses-- that's what DNS is for. But most people don't have DNS on their home computers. If I need to connect to a friend's computer, IP address is the way to go.

      Also, when configuring servers and firewalls, IP addresses are necessary; how wpuld you specify a netblock without using IP addresses? Or a DNS server address?

    3. Re:Aren't IPv6 addresses a bit long? by pe1chl · · Score: 2, Insightful

      Actually it doesn't.
      Even with IPv4 there is clearly a deficiency in the naming system, or at least in the way it has been implemented and managed.
      It was supposed to be multi-level, and it has been abused until it had only one-and-a-half level.
      The result is that all the usable names are taken, and there are by far not enough names to assign a name to every IPv6 address.

    4. Re:Aren't IPv6 addresses a bit long? by Nurgled · · Score: 2, Informative

      You are allowed to omit parts of IPv6 addresses when connecting to hosts in the same subnet as you.

    5. Re:Aren't IPv6 addresses a bit long? by riflemann · · Score: 1

      Can you memorize FEDC:BA98:7654:3210:FEDC:BA98:7654:3210?

      Why would I want to?

      1. This is not an IPv6 address one will see often.

      2. Most allocated IP addresses will use the prefix 2001::/16

      3. DNS will eliminate most things you have to remember

      4. You can manually configure addresses that you want to be remembered. The address 2001:bc4:face::1 is perfectly valid if you wish to use it.

      Maintaining easy to remember addresses is not a reason to use a smaller address space. If that was the case, we'd still be dialling with 5 digits, and each business would only have one number with a switchboard person routing external calls.

    6. Re:Aren't IPv6 addresses a bit long? by Anonymous Coward · · Score: 0

      I studied your example IPV6 address for a few seconds, then minimized the browser window and attempted to retype the address from memory in a text editor. Amazingly, I got it exactly right on the first try. Here, I'll do it again without looking: fedc:ba98:7654:3210:fedc:ba98:7654:3210. So much for your theory! Ha!

    7. Re:Aren't IPv6 addresses a bit long? by marnanel · · Score: 1

      But most people don't have DNS on their home computers.

      If a computer needs to be addressed, it can and should have a name in the DNS. Getting a DNS entry for your computer is trivially easy even if you don't have your own domain. There are only two reasons for not bothering to set up a name: either the machine doesn't commonly need to be addressed (because it runs no servers), or you actually prefer to type the IP address, and can remember it easily. The fact that IPv6 addresses aren't often easy to remember is just all the more reason to set up a name.

      --
      GROGGS: alive and well and living in
    8. Re:Aren't IPv6 addresses a bit long? by Anonymous Coward · · Score: 0
      Also, when configuring servers and firewalls, IP addresses are necessary; how wpuld you specify a netblock without using IP addresses?

      This is thinking in IPv4 terms. IPv6 has a lot of autoconfiguration. Believe me, you won't be entering addresses very often at all. Most hosts are completely and totally configured by the routers (the scheme is similar to DHCP, but with even less configuration).

      You don't need to specify a netblock on any of your hosts. That comes from the router, which is one device, one time setup. Heck, even that might come from an upstream router.

  146. more port numbers by Skapare · · Score: 1

    Actually, what we need are more port numbers. Limiting port numbers to 16 bits limits use to less than 65536 different classes of applications. Go try to register a well known service to get a port number for your remote toothbrush loading protocol. You might have a somewhat easier time registering the remote coffee heatup protocol.

    Now, should we go with 32 bits for port numbers? Or do we face a looming port number exhaustion crisis in a couple decades and need to go with 64 bits?

    --
    now we need to go OSS in diesel cars
  147. Your Application by Anonymous Coward · · Score: 0

    Greed, stupidity and pride.

    1)keeping up with the Jones
    If your company is big clearly you need a class A
    If your company has a class A then clearly you are big.

    2)heading them off at the pass
    You may need more public IPs in the future, but some bastards are hording them. So Grab some before other people can.

    3)Bob is your uncle
    We need some IPs (see I'm doing my job, I know stuff)

  148. numbers don't stop at 35 trillion by Anonymous Coward · · Score: 0

    no word for a number bigger than 35 trillion?

    how did astronomers come up with 70 sextillion then?
    http://edition.cnn.com/2003/TECH/space/07/22/stars .survey/index.html

    another "we're running out of IPs" story. as taco would say, "whatever, next."

  149. 35 trillions won't be enough! by christophe · · Score: 3, Interesting

    Fast forward 50 or 100 years... Everyone has Internet-enabled tools, chairs, glasses... whatever, because everything has a RFID inside, because the TPAA (Things producers Ass. of A.) wants to track everything, because some geeks have found a use to a connection between my pen and my fridge, because it is so easy and cheap...
    1) BUT this tendency to Internet-enable everything will expand to any file on my computer. A CD has a RFID/IP to connect it to the desk, why not every of my MP3? Why a book and not on e-book ? A computer will needs millions of IP addresses.
    2) Worse: we'll finish as virtual beings in the in virtual words (think Ultima Online in 2100). And we'll want everything in this world to have Internet addresses too. I'll ask my little desktop computer to create my own little Matrix, for me alone... and everything there has an address of the IPv6 space (to help me interconnect the real and the virtual world).

    And if it's not enough:

    3) Cyber beings (a few billions humans, much much much virtual intelligent creatures) find the world rather small for so many entities. Not enough computers on this small planet to compute all the worlds that each entity wants created for itself (and to run the compilation of the 10^15 lines of the brand new Linux 2.80.0). So the Metamegamatrix expands to Jupiter, Saturn and creates a Dyson sphere aroud the Sun, converting every joule of energy into computational power for the simulation.

    And in 2203, Slashdot makes headlines on IPv9 with 2048 bits addresses.

    --
    Christophe (Don't hesitate to point out my spelling and grammar mistakes, I want to learn - Thanks).
    1. Re:35 trillions won't be enough! by fries · · Score: 1

      You don't have to worry about extraplanetary networks using up IPv6 addresses. There is this thing called lag that tends to make standard IP (be it v4 or v6) somewhat unusable. Enter `IPN' (Inner Planetary Network), a networking mechanism for talking to intermittent, slow relay stations. There
      is even a viable reference implementation called SCCS (http://www.sccs.org).

      Jupiter will get its own IPv6 network, is my understanding of how networking on a celestial scale is to work.

      --
      Todd Fries .. todd@fries.net .. OpenBSD, because security matters!
    2. Re:35 trillions won't be enough! by christophe · · Score: 1

      >Jupiter will get its own IPv6 network, is my >understanding of how networking on a celestial >scale is to work

      OK. Now we're back to NAT, on a planetary scale, after everybody who used to do it in the 1990-2020 years died, and all OS deprecated their NAT-modules. Fine.
      Where is the progress ? ;-)

      --
      Christophe (Don't hesitate to point out my spelling and grammar mistakes, I want to learn - Thanks).
    3. Re:35 trillions won't be enough! by fries · · Score: 1

      Not nat. UUCP between two distinctly different networks.

      IPN is more or less UUCP with security. It forwards
      messages from one network to another.

      Perhaps I'm wrong, and Jupiter will get 2100::/8
      as a delegation. There certainly are enough IP's to do that.

      I guess I need to do more reading on the fundamental details of IPN.

      --
      Todd Fries .. todd@fries.net .. OpenBSD, because security matters!
  150. Boku? by Detritus · · Score: 1

    I think you mean beaucoup.

    --
    Mea navis aericumbens anguillis abundat
    1. Re:Boku? by dpilot · · Score: 1

      I'll plead ignorance rather than Francophobia. I wasn't deliberately de-Francing beaucoup into boku, but I'm sure not about to courriel anyone, either.

      --
      The living have better things to do than to continue hating the dead.
  151. Remote toilet interrogation by marnanel · · Score: 4, Funny

    I could even call the toilet to see if anyone is using it.

    MIT got there first: http, finger.

    --
    GROGGS: alive and well and living in
    1. Re:Remote toilet interrogation by fm6 · · Score: 1

      The FAQ page is missing. Does each commode have it's own IP address? A private network would make more sense in oh, so many ways!

    2. Re:Remote toilet interrogation by rastos1 · · Score: 1
      When I checked out it said:
      Pecker Lounge: *IN*USE* for 32 min
      Ouch.
  152. IPv6 Loopback is ::1 by TrentC · · Score: 1

    Actually it's "0:0:0:0:0:0:0:1", but in IPv6 you can represent a series of zero octets with a pair of colons. (You can only do it once though, beause otherwise how could you determine where the middle octet in "2002::19ef::127" is?)

    Google also found a mention of a proposal to define ::127:0:0:1 as an IPv4-compatible loopback address.

    Jay (=

  153. NAT & SPAM by ressu · · Score: 1

    How I miss visiting Usenet and content outnumbering SPAM. NAT actually makes locating spammers harder. Most companies (and people) using NAT do not track the connections made through that NAT gateway, thus a spammer behind the gateway would be pretty safe for a while. Well, as long as they don't do excessive spamming over long periods. Unique IP addresses make tracking a bit easier, as it's easier to point a Dial-Up user (for example) from the logs even after a long period of time, than it is to point a user behind a NAT gateway even few minutes after the incident.

    1. Re:NAT & SPAM by VPN3000 · · Score: 1


      It makes no difference whether they are behind NAT or not. The ISP would still be likely to use PPPoE for authenticating users. The issued private IP and the account will still be linked in the ISP's radius logs.

      Since you would have the gateway IP, you would have all you would need. Even if the client was connected through a public IP, the ISP still would have to check the same logs to see what account it was associated with.

      Your point is pointless. :)

    2. Re:NAT & SPAM by ressu · · Score: 1

      The problem is not the part where you track down the user using the IP address.. the problems begin when you go beyond that public IP address, lets play pretend:

      Company A has an internet connection and they get one public IP address, and for some edditional fun, lets assume the company has 50 computers.
      One fine day one user receives a virus, which creates a backdoor to the computer. (by creating a reverse tunnel ofcourse) Now the cracker is able to access the computer and decides to send some spam. The cracker is clever and sends small batches through a big pool of backdoored computers. This way the single computer would send a few mails in a day (for example) through multiple hosts. (makes it even more fun)

      A spam gets sent, reported and tracked to the ISP and to the client, but this is where the real fun begins. The network admin battles with his puny firewall, struggling to filter out real outgoing mail and pinpoint the origin (or just does it the old fashion way, goes through all computers)

      This would all be prevented if the client had a pool (lets say /64 prefix for IPv6) of IP addresses, the address would have been much easier to track down.

      Ofcourse, i admit this is a far fetched scenario, and full of holes, but that's the way i would do it if i was a spammer.

  154. IPV4 is Dying! by diablobsb · · Score: 1

    It is now official - Netcraft has confirmed: IPV4 is dying

    Yet another crippling bombshell hit the beleaguered IPV4 community when
    recently IDC confirmed that IPV4 accounts for less than a fraction of 1
    percent of all servers. Coming on the heels of the latest Netcraft
    survey which plainly states that IPV4 has lost more market share, this
    news serves to reinforce what we've known all along. IPV4 is collapsing
    in complete disarray, as fittingly exemplified by failing dead last
    [samag.com] in the recent Sys Admin comprehensive networking test.
    You don't need to be a Kreskin [amazingkreskin.com] to predict IPV4's
    future. The hand writing is on the wall: IPV4 faces a bleak future. In
    fact there won't be any future at all for IPV4 because IPV4 is dying.
    Things are looking very bad for IPV4. As many of us are already aware,
    IPV4 continues to lose market share. Red ink flows like a river of
    blood. Natted IPV4 is the most endangered of them all, having lost 93% of
    its core developer

    --
    I for one, welcome our new hot grits... PROFIT!
  155. Number of addresses by Anonymous Coward · · Score: 0

    What if I need a hundred and 1 IP addresses...?

  156. IPv4 NAT Good enough - I don't think so by tbaggy · · Score: 1

    For those who think IPv4 NAT is good enough, these are the drawbacks as compared with IPv6:

    1) NAT breaks the end-to-end connection model of IP
    2) NAT keeps a stateful connection table. If a NAT device is rebooted or looses its' configuration, the connection mappings are lost.
    3) NAT prohibits end-to-end security as the IP header can't be modified.
    4) If you use a 10.0.0.0/8 on one end of a network, and want to connect via NAT to another 10.0.0.0/8 network, you can't do it. Imagine connecting to a friends nat'd device when it uses the same IP schema as you use.
    5) Servers on the NAT subnet can't use the same external port (say 80). Externally, they must map to 80 and 81. If the number of servers in the NAT network is large, you can easily run out of NAT IP TCP/UDP Ports.

    NAT is good, but IPv6 is better.

    Bring on IPv6. Check out HS247 for more information.

  157. From the past? by BelugaParty · · Score: 1

    "and the expectation that everything from your phone to your washing machine will soon have its own IP address" Didn't people realize that there is no point in connecting their washing machine to the internet? And even if they want to, they don't have to get it an individual IP, they can just have it running on the house lan? I have four people in my house connecting to the internet with one IP. While I think getting more IP's is nice, I think that "your dishwasher/washing machine/toaster will need an IP" comment is really dated.

    1. Re:From the past? by Ashtead · · Score: 1
      Actually, putting the washing machine on the net might be a useful first step in figuring out where all the odd socks go.

      The second step would be to create some local and regional SETI-at-home style surveillance programs, this may eventually come up with some information on exactly where these vanish to.

      Now all we need is a good acronym and we'll be all set!

      --
      SIGBUS @ NO-07.308
  158. Apologies to the artist formerly known as Prince.. by freeze128 · · Score: 4, Funny

    I'm gonna subnet like it's 255.255.255.254.

  159. Riiight... by AyeRoxor! · · Score: 1

    "we're going to need something like 100 IP addresses for each human being."

    Exactly. In just a few years, Ethermopians are going to all have computers, cellphones, PDAs, etc. Lol. Guffaw, even. That's a good one.

    I consider myself pretty technology-elite, and of all the IP-run devices in my house, it only takes on IP thanks to NAT. I, for one, think the crisis of IPv4 will be solved by a combination of IPv6 and NAT, not just IPv6, and I'd bet some change that a) we won't run out of IPs as fast as "they" say we will, and b) even if we did, IPv6 wouldn't be implemented by the time "they" think it will be needed.

    /enjoy that link :P

  160. more numbers! by austad · · Score: 1

    You could just do what some girl I know did... She had a spreadsheet with all of the IP's for the network on it. She was assigning them in ascending order and was around .250. I asked her what she was going to do when she ran out of IP's, and she said it was OK, because she had the spreadsheet numbered to .300. :)

    --
    Need Free Juniper/NetScreen Support? JuniperForum
  161. Not 35 trillion, not even close... by Vexler · · Score: 1

    Do the math, people:

    2^128 = 3.4028236692093846346337460743 * 10^38

    Even Cisco got it wrong in one of its technology articles. The author claimed that it was "four times" the size of IPv4.

    *sigh*

  162. Words for numbers by Traa · · Score: 1

    Actually, there are words for really large numbers. And 2^128 isn't that large.

    Here is the full number:
    340282366920938463463374607431768211456

    and here is how you pronounce it in the american system:
    three hundred forty undecillion,
    two hundred eighty two decillion,
    three hundred sixty six nonillion,
    nine hundred twenty octillion,
    nine hundred thirty eight septillion,
    four hundred sixty three sextillion,
    four hundred sixty three quintillion,
    three hundred seventy four quadrillion,
    six hundred seven trillion,
    four hundred thirty one billion,
    seven hundred sixty eight million,
    two hundred eleven thousand,
    four hundred fifty six

    or in the European system:
    three hundred forty sextillion,
    two hundred eighty two quintilliard,
    three hundred sixty six quintillion,
    nine hundred twenty quadrilliard,
    nine hundred thirty eight quadrillion,
    four hundred sixty three trilliard,
    four hundred sixty three trillion,
    three hundred seventy four billiard,
    six hundred seven billion,
    four hundred thirty one milliard,
    seven hundred sixty eight million,
    two hundred eleven thousand,
    four hundred fifty six

    try it yourself

  163. even big numbers are named, duh by LuxFX · · Score: 2, Informative

    IPv6 will increase the supply of addresses from 4 billion today to a number in excess of 35 trillion that is "so big that there's not a word for the number," says Cody Christman

    Well let's take a look. IPv6 looks like this:

    2001:0418:000C:0003:0000:CF00:C0A8:2E2E

    So the highest number is 16^32, right? Which is roughly 3.4028 x 10^38.

    Which is a little over 340 undecillion. Want it exact? It's 340 undecillion, 282 decillion, 366 nonillion, 920 octillion, 938 septillion, 463 sextillion, 463 quintillion, 374 quadrillion, 607 trillion, 431 billion, 768 million, 211 thousand, 456.

    Plenty for everybody!

    Check out more names of big numbers.
    .

    --
    Punctanym: alternate spelling of words using punctuation or numerals in place of some or all of its letters; see 'leet'
  164. naive by Anonymous Coward · · Score: 0

    somehow i think its naive to think that something like ipv6 will solve everything. it seems that whenever there's greater capacity, the capacity gets used one way or another. so if ip4 gives every person 100 ip's and ip6 gives everyone, say, 100000 ip's someone will make a killer app that relies on the heuristic of there being a large number of cheap ip addresses for each person and you're back to square one. i dont think when they made ip4 they were thinking of coke machines and palm pilots with ip addresses.

    so perhaps the solution is a protocol which includes a "scaling protocol" so that one can simply add more ip addresses when necessary, automatically and implicitly in the protocol without breaking anything. the number of addresses would be unbounded. or for instance rather than having 4 bytes be the address, perhaps a "start byte" then an arbitrary number of bytes and then a "stop byte." sounds like a triviality. whats the flaw?

  165. Heisenberg Compensator by handy_vandal · · Score: 1

    Doesn't the Heisenberg compensator eleminate the need for particle addressing?

    It should, according to Star Trek: the Next Generation. But the Uncertainty Principle suggests that we shouldn't rely on fictional stuff to come true.

    --
    -kgj
  166. IP addresses for fridges by verloren · · Score: 1

    Fridges are devices designed to maintain cool temperatures within an enclosed space. That is all they do, yet only a very few, really high-end models are actually controlled by a thermostat. If fridges aren't equipped with the thing that would let them best do what they are made for, why would we realistically expect them to get an IP address, for {deity/obscenity]'s sake?

    Oh wait, marketing...

    Cheers, Paul

  167. Come and get it by Anonymous Coward · · Score: 4, Funny
    And EDU's too. There are many universities with many tens of thousands of IP addresses, most of which are unused. One I know of has at least one class A...

    That would be us here at MIT. And you can pry it out of our cold dead hands.

  168. Oh know, my VPN isn't working?! by Pii · · Score: 1
    That's funny... I VPN to my office, and countless customers sites every day, all from behind NAT'd connections.

    I've always thought it worked just fine. Is there something more that it should be doing, you know, other than providing me with the remote access I enjoy? Fetching my coffee perhaps?

    --
    For those that would die defending it, Freedom
    has a sweet taste that the protected will never know.
  169. only time will tell on usage needs by amigabill · · Score: 2, Funny

    >IPv6 will increase the supply of addresses from 4 billion today to a number in excess of 35 trillion
    >that is "so big that there's not a word for the number,"

    Said with the same confidence that Gates used when announcing that 640KB memory should be enough for anyone... :)

  170. Who needs IP addresses anyway? by Anonymous Coward · · Score: 0

    IP is a fad.
    Remember X.25.

  171. Gibson dystopia, of course by HiggsBison · · Score: 1
    The Bush/Ashcroft administration will need all those addresses so that they can crack down on all those evil "hackers". You know, heavy licensing like in "True Names". And of course you need an address for the napalm packs in your cyber-decks, so the corporate overlords can blow up your apartment while your out for some noodles, like in one of those Gibson cyberpunk books (can someone help me out here, my books are in storage).

    Anyone know the RFC that covers those napalm packs? I don't want the cyber-deck I'm building to be out of spec.

    --
    My other car is a 1984 Nark Avenger.
  172. Microsoft will love IPv6 by whoever57 · · Score: 1

    I mean, how many people will buy and install Trumpet Winsock to get IPv6 on their Windows 98 machines versus just upgrading to XP?

    --
    The real "Libtards" are the Libertarians!
  173. We've heard this before... by Anonymous Coward · · Score: 1, Insightful

    There are *huge* swaths of IPv4 space allocated to defunct organizations, wasted in various unallocated space, etc. Take the /8s, for example... I doubt *any* company with a /8 utilizes more than a tiny fraction of that space. There are *dozens* of /16s that aren't even routed. IPv4 could be stretched out for quite some time if ARIN were to actually do something besides collect checks.

  174. Nothing wrong with NAT in the home by WndrBr3d · · Score: 1

    I think people really have their thumbs up their butts when it comes to NAT in the home.

    I mean think about it, so some people need to recieve files and go all other 'special incoming packet' activity, well fine. Put your computer on the NATs DMZ. Problem Solved.

    I mean, if you think about it and all the issues brought up in this story come true, why would your washing machine need any access from the outside? If anything, keeping non-routable IPs on applications outside of your desktop PC should be welcomed! I'd be pissed if someone put my silk sheets on high insted of delicate! ;-)

    My point is, I think people are making a mountain out of a mole hill when it comes to NAT in the home. If you want extra IPs, pay for them. If not, Proxy and help save an IP for someone else.

  175. How about extending DNS instead? by whoever57 · · Score: 1

    If DNS were extended to:
    1. Enable more service lookups (like the MX records)
    2. return not only an IP address, but also a port number,
    much more sharing of IP addresses could be achieved. Imagine this: you want to connect to an SSH server. Your lookup requests the IP/port for the SSH server with name . Then your ssh client connects accordingly.

    Since we now have stateful firewalls, the difficulty of using random port numbers in firewalls can be accommodated.

    Perhaps we might want to limit the port ranges for known services to make things a little easier on firewall configuration.

    On the other hand, this would require changes to thousands of client programs to support the port lookup, so maybe it's a crazy idea.

    --
    The real "Libtards" are the Libertarians!
  176. I don't really see a problem here by wackoman2112 · · Score: 1

    The only problem here is that everyone is using too many IPv4 addresses. Why does every appliance or computer you own need to have a public IP address? It would better if they all have private addresses behind a firewall. If your washing machine (snort) needs to be accessed from the outside, you can simply forward the "washing machine" port on your one public IP address to your washing machine device.

    We also need to get the big corporations to give back the IP addresses we gave them back in the days when we thought we had an unlimited supply of IP addresses. HP alone has 16 million public IP addresses. (That's the equivalent of all addresses in the 10.0.0.0 network) So every computer in their company has its own public IP address, even though most are behind a firewall. The 10.0.0.0 network was invented for a reason!

    --
    /usr/bin/complain > /dev/null
  177. Hey um, fuck you? by Anonymous Coward · · Score: 0

    First off I didn't even fucking mention IPv6, I was just talking about the merits of NAT... and hold on now, because this is a hard concept, FOR THE AVERAGE USER.

    How many average Windows users you know run real firewalls? Thought so, prick. And even if those users do run some shitty firewall, they probably still don't have any idea how it works. And not everybody has $70 to throw around here and there.

    Oh, you run a private network? WOW. No really, CHRIST I'M AMAZED.

    Then onto the subjects of ISPs. Notice I said BROADBAND ASSHOLE. Most cable broadband providers DO WANT YOU TO PAY PER MACHINE. THEY REQUIRE YOU TO GET AN IP FOR EVERY MACHINE. NO NAT. GOT IT ASSFACE?

    Oh, of course... new ISP. Oh wait, WHAT ABOUT ALL THE PEOPLE WHO LIVE IN THE REAL WORLD? How many broadband ISPs where you live jackass? Most places have ONE cable provider. Then the other option is to go with a bullshit telco DSL line where they charge you $80/mo for a line slower than cable (oh yeah it's dedicated, big fucking whoop) and very often with RIDICULOUSLY LOW DOWNLOAD AND UPLOAD QUOTAS.

    We don't all live in your fucking fantasy world. And anyway, anyone who would brag about running a home network is a fucking little bitch who doesn't know anything about anything. So fuck you.

    Your response didn't even have anything to do with the parent, or indeed reality.

    Go ahead, mod me down. Who gives a fuck.

    1. Re:Hey um, fuck you? by ivanmarsh · · Score: 1

      You need more bran in your diet.

    2. Re:Hey um, fuck you? by Anonymous Coward · · Score: 0

      Bright response. Do they really pay you? Fucking boggles the mind.

      Go back to lowering the national IQ, go on now.

    3. Re:Hey um, fuck you? by Anonymous Coward · · Score: 0

      All views, opinions and alleged facts expressed by this tactless moron are protected by the constitution of the United States of America and should be taken as good natured and friendly unless specifically stated otherwise.

      Loooooooser.

  178. bullshit by pair-a-noyd · · Score: 1

    In the future, everything from automobiles to home appliances will be connected to the Internet, Mr. Lightman said, "and we're going to need something like 100 IP addresses for each human being."

    1. Bullshit.
    2. Why?

    I'll never, ever have need of 100 IP addresses. One is all I need. My router handles all my computer needs.

    I don't need nor do I want a toaster or refrigerator or a toilet with an IP address. My car doesn't need one (it's 28 years old anyway) and my cell phone doesn't need one. And when my son moves off to college next month I'm disconnecting my home phone and will only use my cell phone. Assigning IP addresses to household appliances is STUPID. Can you say ABUSE??

    Can you say PRIVACY?? I have about 7 or 8, maybe a few more PC's here at home but those are the ONLY modern things I use. Everything else I own and use is OLD/LOW tech and *I* retain total control over everything in my home.

    Maybe professor Warwick is masturbating to the idea of a connected world but a lot of us are not..

    1. Re:bullshit by Quill_28 · · Score: 1

      It this case the name fits the posting.

    2. Re:bullshit by pair-a-noyd · · Score: 1

      Yes, it does fit your posting.

  179. There is a word for the number... by ikewillis · · Score: 4, Informative

    The number, 2^128, or 340,282,366,920,938,463,463,374,607,431,768,211,45 6, can be read as:

    Three hundred forty undecillion,
    two hundred eighty-two decillion,
    three hundred sixty-six nonillion,
    nine hundred twenty octillion,
    nine hundred thirty-eight septillion,
    four hundred sixty-three sextillion,
    four hundred sixty-three quintillion,
    three hundred seventy-four quadrillion,
    six hundred seven trillion,
    four hundred thirty-one billion,
    seven hundred sixty-eight million,
    two hundred eleven thousand,
    four hundred fifty-six.

    That's a lot of IP addresses.

    1. Re:There is a word for the number... by reboot246 · · Score: 1

      That's almost as much spam as I get everyday.

    2. Re:There is a word for the number... by InterventionOne · · Score: 1

      Gee, at that rate I suppose they expect light bulbs to have internet connections as well...

    3. Re:There is a word for the number... by g_attrill · · Score: 1

      "Three hundred forty undecillion,
      two hundred eighty-two decillion,
      three hundred sixty-six nonillion,
      nine hundred twenty octillion,
      nine hundred thirty-eight septillion,
      four hundred sixty-three sextillion,
      four hundred sixty-three quintillion,
      three hundred seventy-four quadrillion,
      six hundred seven trillion,
      four hundred thirty-one billion,
      seven hundred sixty-eight million,
      two hundred eleven thousand,
      four hundred fifty-six IP addresses are
      enough for any universe"

    4. Re:There is a word for the number... by TheRealJFM · · Score: 1

      ....except for in any numbering system other than the US one. Such as the European one. EU: 1,000,000 = Million 1,000,000,000,000 = Billion US: 1,000,000 = Million 1,000,000,000 = Billion Thats another protocall that has to be worked out.

      --
      Joseph Farthing
      http://josephfarthing.com
    5. Re:There is a word for the number... by Trejkaz · · Score: 0

      That's not a word, that's 40 words. Or 50 words if you'd remembered to put the 'and's in, as per standard number-reading conventions. (55 if you count hyphenations as two words.)

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    6. Re:There is a word for the number... by Anonymous Coward · · Score: 0

      So what is the number between a million and a "billion" in europe? ie, 1,000,000,000?

      One thousand million?

    7. Re:There is a word for the number... by Zork+the+Almighty · · Score: 1

      yes.

      --

      In Soviet America the banks rob you!
    8. Re: There is a word for the number... by gidds · · Score: 1
      Yeah, well, that's what I was taught when I was very young, but here in the UK everyone's used the US (billion=1,000,000,000) system for ages.

      The difference is that we'd always put 'and' in after the hundreds:

      Three hundred and forty undecillion,
      two hundred and eighty-two decillion,
      three hundred and sixty-six nonillion,
      nine hundred and twenty octillion,
      nine hundred and thirty-eight septillion,
      four hundred and sixty-three sextillion,
      four hundred and sixty-three quintillion,
      three hundred and seventy-four quadrillion,
      six hundred and seven trillion,
      four hundred and thirty-one billion,
      seven hundred and sixty-eight million,
      two hundred and eleven thousand,
      four hundred and fifty-six.
      US long numbers just sound like a sequence of separate numbers to me: two hundred, forty, one thousand, fifty-two, six, three hundred, seven...

      I guess the advantage of the 'British' system is that it can cope more easily with very very very large numbers; the US system can cope more easily with fairly small ones. But since we tend to use exponential notation for the really big ones anyway, the US system is probably more useful for everyday use. (Much as it pains me to admit it!)

      --

      Ceterum censeo subscriptionem esse delendam.

    9. Re:There is a word for the number... by firewrought · · Score: 1
      That's not a word, that's 40 words. Or 50 words if you'd remembered to put the 'and's in, as per standard number-reading conventions. (55 if you count hyphenations as two words.)

      You may be following a different convention, but in the Saxon textbooks I used during middle school, the 'and' could only appear when introducing the fractional part (e.g., 3 million, two hundred, and 4 thousandths [3000200.004]). We did a lot of those word-expansion exercises.

      Colloquially, more 'and's are inserted, but in formal communications I've always seen (and used) the saxon convention.

      It's quite easy to believe that this is something that varies a lot across linguistic regions. Anybody know of any governing standards for mapping numbers to names? Somebody has to have formalized this.

      --
      -1, Too Many Layers Of Abstraction
    10. Re:There is a word for the number... by Anonymous Coward · · Score: 0

      Thank you! This proves that Alex Lightman is so full of shit. And this ain't NO where near a googolplex (i.e. 10^10^100).

    11. Re:There is a word for the number... by Juergen+Kreileder · · Score: 1
      So what is the number between a million and a "billion" in europe? ie, 1,000,000,000? One thousand million?
      "milliard"
    12. Re: There is a word for the number... by fyonn · · Score: 1

      Yeah, well, that's what I was taught when I was very young, but here in the UK everyone's used the US (billion=1,000,000,000) system for ages.

      I still do use that system actually. but you know something, this disparity in what "billion" means etc, is, unusually, not the fault of the americans (easy guys, I'm noly having fun with you). this one is actually the fault of the french.

      a french guy invented the words in the first place, AIUI to mean the british system (except at the time it wasn't the british system ;), ie a billion = 1,000,000,000,000 and that the words would go up in 6 digit groups. this got accepted in the uk and everyone was happy, then the french gov decided to change it to going up in 3 digit groups, making a billion 1,000,000,000. this happened a little before the american revolution, and guess who helped the americans to escape the tyranny of england? yup, the french. and so america took on the new style billion terms while england stayed with the old style.

      england eventually ended up taking on the new style to make discussions and comparisons with america easier and I beleiev that france have since chanegd back to the old style *sigh*.

      incidentally, as far as I'm concerned, the sequence goes, in 3 digit groups, thousand, million, milliard, billion, billiard, trillion etc.

      but then, thats just me :)

      dave

    13. Re: There is a word for the number... by TheRealJFM · · Score: 1

      I live in the UK, and the old on is the one i've seen used in school, universitiy etc....

      --
      Joseph Farthing
      http://josephfarthing.com
    14. Re:There is a word for the number... by jonathanhowell · · Score: 1

      That's an ip address for every star in the universe! With a few left over to boot.

  180. Killer App is Mostly a Myth ... by Mooncaller · · Score: 1
    The only true killer app was Lotus 1 2 3. Netscape came close to being one. A real killer app has four characteristics. It must do something that people need to do, whether they know it or not. It must be or become the only practical way to do that something when it is introduced. It must target a tech platform that has a potentialy mathamaticaly catastrophic adoption pattern. And finally, their needs to be another platform to be killed. This last ties in with number three.

    It is the third characteristic that that will enable the killer app effect. If PC had not already been comoditised when Lotus was introduced, it would not have been a killer app. Netscape misses, because even though it was the most practical, it was not the only practical way of "surfing the net".

    Now with that out of the way, I can get to my main point.

    as with all pure tech - it needs that killer app

    Man has been adopting new tech since we became man. The initial adoption pattern is almost always exponential, though the existance of several compeating technologies can make things interesting. If several compeating technologies share characteristics that are mutualy exclusive ( e.g. PCs and Macs both use software, but the software for one will not run naturaly on the other), the adoption pattern becomes somewhat unstable. This unstability can lead to catastrophies which pave the way for a killer app. But I digress. What happened with the PC was an unique phenonmina. It had never been seen befor. The term "killer app" was coined to describe the cause of that phenomina. In other words, it describes something that deviates from normal. So the concept that new tech needs a killer app to be adopted is just plain wrong.

    good luck finding that app

    Since the term "killer app" was first coined, people have beeen running around trying to find the next "killer app". Tech writers have been speculating on the nature of the next "killer app". But guess what, when the next killer app arrives, no one will recognise it as such untill after it has done its killing. That the potentialy killer nature of an app is knowable, probably precludes it from being a killer app. I would have included this as a characteristic of killer apps, but I have not proved it to be true. At this point, I concider it a conjecture. Anyway, one can identify the tech platforms that have characteristics which allow then to be affected by a killer app. And its not the desktop!

    educating users what it is, and what it does.

    Because of certain technological synergies, 3G, is the most likely area to be affected by some killer app. If this happens, no one will have predicted it. I feel that the potential for the arrival of a killer app is very high. I also feel that the definition of killer app might need to be tweeked a bit to include a set of apps from several sources that people start using together. The most likely place for this to happen is in the highschools. Its the users that will define the next killer app.

  181. 100 IP addresses per person by sharkey · · Score: 1

    But only 1/6th of the screen for text in online articles. Even Slashdot is more readable than the Times.

    --

    --
    "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  182. 100 each is very short-sighted by Eric+Smith · · Score: 1
    I don't believe we're really going to run out of IPv4 addresses in 2005. But claims that we need 100 per human being is very short-sighted. 100 each is more than enough for most people now, but as technology advances we will have much smaller and more ubiquitous devices.

    Fortunately, the IPv6 address space can provide for a lot more than 100 per person. By many orders of magnitude.

  183. how the hell are you going to remember site names? by Theobon · · Score: 1

    With 3.4^38 IPs even your home networks will need DNSing for you to find anything, nobody s going to remember that
    fe80::a34b:44f2:3905:932c is the fridge while
    fe80::a34b:5c32:3905:932c is the printer

    Even with a DNS over the internet site names will run out far before addresses do. Using ever permitation of alphanumaric characters for the site name it will take 25 characters to map every address. You try telling someone that your site is www.sutdjosntajutsnelsynzpref.org advertizing will be hell.

  184. More Overhype by Exousia · · Score: 1

    I particularly thought this statement was ludicrous: "every new washing machine, for instance, could have its own IP address, allowing it to alert a service person electronically of a needed repair before it stopped working in the middle of a cycle." This is utter nonsense. Devices such as these don't need fixed IP addresses. They could be allocated on damand, or hang off a single IP, whenever needed, as is already being done all over the place. The guy acknowledges this, and his redactor exampled is a friggen washing machine??? How remarkably stupid. Moreover, while IP address are limited to 32 bits, the concept of ports multiplies this by 65536! (Granted some ports are reserved.) This amounts to more than 280 trillion unique socket addresses. A given device (like a washer, or your toaster) doesn't need all the ports to a single fixed IP, even if it had a fixed IP which it doesn't need in the first place. Another non-problem to not worry about.

    --

    --Slashdot: News for Turds. Stuff that Splatters.
  185. frooglepoopilion by Axiom_1 · · Score: 1

    I believe the correct word for the number may be frooglepoopilion.

  186. just 35 trillion? by bob_jenkins · · Score: 1

    Come nanotech and the colonization of the solar system, that won't be nearly enough.

  187. I don't want all those public IPs! by michael_cain · · Score: 1

    I, for one, do not want all of the devices in my home and/or office to be reachable by just anyone on the public Internet. I would be much happier with an architecture based on some sort of household gateway and a standard way for a device that needs external access to install an interpreted service proxy module on the gateway. The module can be as simple as port fowarding, or quite complex. But I want the added security that I believe an interpreted environment will provide. Modules written in Java would be fine.

  188. "We're not even close", says the market. by mactari · · Score: 2, Insightful

    How much does it cost me to get an IP address for a year? About $150 including server space.

    Where I used to work (on-site gov't contractor) each machine had a "real IP". That's nothing 192.168.1.* can't fix. The issue is with the way people purchase huge blocks of IPs at once. If we'd stop selling 134.*.*.* to one entity, we'd be fine for a while longer.

    From one of the linked articles:
    In one solution, a single IP address is assigned to an entire network, which then gives out its own addresses to the devices attached to it.

    But such approaches are not long-term solutions, said Alex Lightman, chairman of a conference... to discuss the next generation of IP addressing, known as Internet Protocol version 6, or IPv6.


    I think Mr. Lightman is being a bit alarmist. There's no reason any ISP needs more than one IP.

    At any rate, as long as any schmoe can go and purchase an IP at an ISP/web host for nuttin', I can't imagine we're even close to out and that there aren't millions of IPs that we can consolidate before we get so alarmist.

    --

    It's all 0s and 1s. Or it's not.
  189. WRONG!!!11!!1! by Timbo · · Score: 1

    The IP address space will be exhausted in the GREAT IP CRUNCH OF 2010.

  190. Insightful by handy_vandal · · Score: 1

    Right on.

    --
    -kgj
  191. Will my grand-mother learn to firewall? by christophe · · Score: 2, Insightful

    When people are connected to the Internet, they usually obtain one public IP, usually not static. If the fridge, the DVD player, the printer, gets its own IP, it will be a private one, NAT-ed, and somewhat protected from the outside.

    The IPv6 world won't know NAT, as its goal is somewhat to destroy it. Someone from Australia could connect to my fridge if everything in house becomes connected. It all becomes wireless, you'll even forget that your camera is on the net. Even with a much greater address space, we'll all need to firewall our connections.
    I suppose that easy-to-use firewalls will be in every home in a few years. Still, any failure in programming them, any exploit in a well-known brand, could lead to a disaster for people much greater than having its computer hacked: fridge at 20C, heating at 40C, camera becoming a public webcam, TV and DVD giving back what you've seen yesterday, palm giving your agenda to the world...

    --
    Christophe (Don't hesitate to point out my spelling and grammar mistakes, I want to learn - Thanks).
  192. Hundreds of IP enabled devices? by dacarr · · Score: 1
    You mean like those newfangled networked refrigerators that are supposed to tell me when I'm out of low-fat milk?

    Hey! Imagine a beowulf cluster of those! I could get inventory for hundreds of gallons of milk in microseconds!

    --
    This sig no verb.
  193. A crisis? by /dev/trash · · Score: 1

    Maybe if MIT and the such would gibe up the Class A's they horde....

  194. Re:Apologies to the artist formerly known as Princ by Shriek · · Score: 0
    I'm gonna subnet like it's 255.255.255.254.

    All your subnets are still belong to me...
  195. It will still need to be upgraded: by km790816 · · Score: 1

    From an article on rediff.com: "According to a study by a team of stargazers based at the Australian National University, there are 70,000,000,000,000,000,000,000 (70,000 million million million, or 70 sextillion) stars in the known universe."

    That's 2^76. Leaving only 2^52 addresses per system...and that's assuming perfect routing. :-)

  196. IPv6 will be great for networking companies! by MtViewGuy · · Score: 1

    I can say that once IPv6 is widely adopted the biggest beneficiary will be companies making networking gear.

    This is due to the fact much of the hardware handling the world's Internet traffic are NOT IPv6 compatible. It could result in a major economic boom for networking companies as telecom companies around the world, web host providers, software companies and others scramble to enable IPv6 support. I'd hold on to shares of Cisco, Nortel Networks, etc. because they could really boom as the scramble to buy IPv6-compatible networking hardware takes off.

  197. What about the DOT.BOMB's? by Lester67 · · Score: 2, Interesting

    A few years ago I worked for a business oriented web hosting company (which also disappeared a little later in the dot.bomb crisis.)

    At the time, we were trying to buy up a considerable chunk of IP addresses from another company that had already gone tits-up. Due to bankruptcy courts, etc, the sale never went through.

    My question is, how many IP ranges are still out there that were purchased up, but never accounted for, or added back to the available population?

    If a company did fold, but held a chunk of IP addresses, how long can they sit in limbo before they are re-released back into "the wild"?

    I guess my bottom line question is: Are we really running out in 2005 due to a lack of availability, or mismanagement?

  198. some even have two Class A networks by daniel23 · · Score: 1


    and HPQ really should be forced to return at least one of them, not?

    --
    605413? Yes, it's a prime.
  199. Terry Gilliam might not think it's silly (n/t) by Jafafa+Hots · · Score: 1

    n/t

    --
    This space available.
  200. huh by prelelat · · Score: 1

    not to confuse this with the food or fuel crisis. This seems to be a much worse problem!

    I know this is news for nerds but don't you think they play this up a little bit too much you would think the internet had come to an end.

    Yeah its flame bait but so is everything thats posted on slashdot.

  201. Would anyone be interested in buying a class B? by bennomatic · · Score: 1

    I know of 65,000+ addresses which might be made available for the right price.

    --
    The CB App. What's your 20?
  202. When you don't have food on the table... by Anonymous Coward · · Score: 0

    ... who needs 100 IPs?

    Sod IPv6. Feed the world.

  203. An interesting idea by Pantheraleo2k3 · · Score: 1

    I know that this is somewhat OT, but I had to share. If this works out (I mean when), we will need some sort of hostname system to handle it. I propose something like this:

    Continent.Country.Province/State.City.OwnerName/ La stName.UserName/FirstName.Device Type.Identifier

    For example:

    NorthAmerica.UnitedStates.Washington.Redmond.Mic ro soft.BillGates.Computer.Work

    But wait! There's more! If Bill Gates wanted to call up Steve Ballmer, this is all he would need:

    SteveBallmer.Phone.Main

    You see, you leave off the parts that are redundant.

    Here's a wholesome family example:

    NorthAmerica.UnitedStates.California.SanFransisc o. Pirillo.Chris.Computer.Main
    to (IP phone, FTP, whatever)

    Gretchen.Computer.Main

    It's actually pretty simple, but please tell me how to improve it

    BTW the same could be used for a numeric system by making country and area codes

  204. not a crisis by Kallahar · · Score: 1

    NAT. You get to reuse the IP's! Imagine that!

  205. hell yeah! by makoffee · · Score: 1

    Hook me up with them 100 ips right now! FUTURE BE DAMNED!

    --
    -makoffee
  206. We are not running out of IP addresses by thogard · · Score: 1

    There are more than enough IPv4 addresses. They only run out because the smallest allocation is a /19 because old ciscos couldn't cope with large routing tables. IPv6 increases the memory requirement for the routing table by a factor of 4 and so most routers that are just copeing with full tables now, could not deal with the same routers using IPv6 without more memory. Keep in mind that many of thouse routers are still at a point where they can't have more memory added.

    The problem is all based on how routes are selected. In most cases, there is only one outbound route and a default route works great. Core routers need huge tables but they have custom hardware to deal with that situation. That leaves the dual homed small businesses but since you can't dual home a /26, there aren't too many of them.

    If the entire world was divided into /24 and a router had 15 interfaces it should take 8 megabytes of memory to determine where each packet goes and with content addressable memory (like used in cache), that decision would take much less than 2ns.

    The problem isn't running out of addresses, the problem is poor methods of dealing with the routing tables and that is only going to get worse with IPv6. It the routeing gets fixed, there are enough addresses for a very long time.

  207. Those were the days... by N8w8 · · Score: 1

    The only time I've ever actually heard the word "undecillion", was when I typed a huge number in the SBTALKER.EXE text-to-speech program, which came with my Ueber-31337 Sound Blaster 2.0. Now that's a long time ago.

  208. IOS 12.3 is out by Styx · · Score: 1

    And it supports IPv6. Too bad it's much more bloated than 12.2(x)T.

    --
    /Styx
  209. Can you memorize this? by Styx · · Score: 1

    2002:50a5:c5a1:2::10
    That's the IPv6 address of one of my machines.
    Oh, and besides: that's what the DNS is for anyway.

    --
    /Styx
  210. The cost of all this? by anonymous+leprechaun · · Score: 1

    I wanted to post a story the other day ... it didnt go through ... anyway ... i was wondering about the total costs of switching over to ipv6 ... i assume IANA works in a supply and demand basis ... v6 will provide such supply that if they do indeed work with sup/dem. ... the prices would reach rock bottom. thus ... the cost of having lines would drop ... but ... will home consumers see some of those savings?

    or is the whole switch complicated enough to actually cost what they save on IP's?

    or, yet again, will they totally ignore the possibility of lowering their prices?

    yet another possibility, could they even boast prices because the switch was _that_ complicated.
    ("for administrative reasons blah blah blah ...")

    anyway ... im just wondering.

    cheers

  211. check out alexlightman.com by Anonymous Coward · · Score: 0

    and then "ask me to dress up and do the dirty 4g dance for you". what a twit. Professional experience .... "coming soon". bout time bucko - you don't look like you're getting any younger. sooooo 1999.

  212. yer kidding right? by RouterSlayer · · Score: 1

    not this lame crapola again?
    can we get the main posting modded down?
    I mean, come on, we keep hearing this BS...

    and BTW, ipv6 is obsolete, I thought /.ers would at least have *some* technical sense and have known about ipv8 by now...

    I mean, ipv16 is already out...

    ipv6 is beyond ancient. get with the program already!

    PS- I "own" a class-b, so whatcha gonna do about it? ;)

  213. News: IPV6 not enough... by Anonymous Coward · · Score: 1

    ...surprise, surprise. 35 trillion ipv6 addresses are not enough.

    That's certainly a loaded statement. Now allow me to explain.

    Most slashdot readers are aware of the application of IPV6 addresses having to do with computing. Getting more information on military applications of IPV6 helps to fill in a bit of the knowledge gaps on the issue. But you need more information to understand the full breadth of the issue, and the problems that will crop up with even IPV6.

    About 15 years ago, I joined the UPC council, and registered my small business so that I could receive a manufacturer upc 5 digit number, allowing me to place upc numbers and bar codes on my company's products. That gave me a unique 5 digit number for my company, a single digit at the beginning that was either pre-determined for the industry, or was calculated (I forget which), plus the full selection of 5 digit numbers after my unique 5 digit number for product, which gave me 100,000 unique product numbers, plus a single check digit, which the scanners used to make sure the full number was scanned correctly, the check digit being calculated from the other digits.

    Why did I do this? Simple. The upc number (actually the bar code) was mandatory for me to get the product into the supermarkets. Previous to this, I was limited to selling my product in grocery stores that were individually owned. To get the product into chain-owned, or co-op owned grocery stores, and supermarkets, all of whom where already using scanners 15 years ago, I had to have bar code scanning ability on my product. Why did the chain stores and supermarkets want this? Back then, the single biggest argument, or selling point, of the scannners wasn't theft. It was the mistakes that the cashiers made. And not just in price. My product went into the produce section of supermarkets. Produce is the cash cow of supermarkets. The profit margins on produce are double and better in some of the supermarkets in my area. And the gross sales from produce is substantial. And the additional sales tied to customers who come in just for the produce is also substantial. I've sat in meetings where the Director of Operations, the Produce Supervisor, and other titles have told me that they actually (15 years ago) have tracked, both by upc scanning, and by actually physically following customers around, and watched while some customers purchased only the loss leaders from their sales flyers, and at the same time left the store to go shopping at other supermarkets across the street and down the block, to do the same at other supermarkets.

    At these same meetings, with one or two of the better producing stores' produce managers present, I've seen the produce managers jumping up and down in their seats insisting on the upc bar codes, because the cashiers input the sale as "grocery dept" instead of "produce dept" for a product that they don't know which department it belongs to (like mine might be mistaken for, especially since some of the chains actually put it into the grocery department). And what happens when the cashiers put the sales of produce into the grocery deparment? It inflates the profit margin of the grocery department, and deflates the profit margin and sales of produce. They have weekly and monthly meetings on these figures, and compensation is tied to these stats.

    Now let's get off the apples and oranges. Let's go back to the military for a second. Any guess that they will be issuing individual ipv6 numbers to tanks? Other large tranport vehicles? Ok. So there aren't that many tanks. You are aware that all the network devices will be getting them, including printers, routers, switches, and everything related. I'm sure keyboards, mice, and more will be thrown in as well. How about washers and dryers? They already have processors on board. Tie it to the network, screen popup on your pda (and later dick tracy watch) while you are next door getting a pizza, your wash is done.

    How about coffee machines? Coffee is re

    1. Re:News: IPV6 not enough... by InvaderXimian · · Score: 1
      Worst....Post....Ever....

      Actually, I don't know. I didn't read the whole thing. Plus, no single person will need 100,000 IP addresses, or more. Ever. One is enough for most.

  214. I TOLD them by Cat_Byte · · Score: 1

    "we're going to need something like 100 IP addresses for each human being."

    Sheesh and it was like an act of congress explaining to my isp that our .com needed 255 ip's.

    --
    Two roads diverged in a wood, and I - I took the one the bus load of girls just went down.
  215. more than 35 Trillion by HeartOfGold · · Score: 1

    I must be stupid:

    "IPv6 will increase the supply of addresses from 4 billion today to a number in excess of 35 trillion that is "so big that there's not a word for the number,""

    Isn't the word for that number "more than 35 Trillion"?

  216. Wow, I could have had a V8! by rs79 · · Score: 1

    He may be one of my better friends and a bit starkers but his V8 shit does work well and without the V6 hassles.

    IP addresses are the least of my concerns.

    --
    Need Mercedes parts ?
  217. Jeeesus christ people. . . Theres more to this. by Anonymous Coward · · Score: 0

    once there are enough domains for every man woman and child in the net. those domains will be plentiful enough to be REGISTERED making your toaster, your washing machine, you, your cellphone pager fax etc everything trackable by its own IP. Not a good plan if you ask me. How long before I'll be forced to REGISTER my very own IP before I can use it on the net. The system is there. It just takes one disaster and a few stupid senators to bring it ALLLLL down. No more anonymity. It may sound like a conspiracy, but it CAN HAPPEN NOW. Your whole life tied into your personal registered IP address. Say wasn't that in the bible somewhere? :)

  218. Maybe in the US? by agent+dero · · Score: 1

    This doesn't seem at all like a CRISIS!

    While I was in Germany last year, we had one PC in the house on the internet, and some of the people I know didn't even have computers on the internet.

    The world isn't all like the US, where every middle-class family has an XBox, PS2, P2P Server, 2 Windows computers, and a laptop.

    Some people in this world don't even have running water, in fact a great percentage. IPv4 is no crisis unless you need to have everything that uses electricity with an IP in your house

    --
    Error 407 - No creative sig found
  219. Killer App by stephenbooth · · Score: 2, Funny

    How about an IP address for the RFID chips in your clothing?

    That way your socks can tell your washing machine to ask the fridge to remind you to wash them whilst also emailing the NSA about you attending a meeting of [insert-fringe-organisation-currently-in-policial- disfavour-here] and your partner about the visit to the strip club afterwards. And obviously every CD (and CDplayer) will need it's own IP address so the embedded device (running WinCE) can connect back to the RIAA over the secret pervasive wireless network to tell them who's playing what as an antipiracy measure (the customer profiling use to allow them to send you even more junk mail is purely a side effect).

    Anything I missed?

    Stephen

    --
    "Don't write down to your readers, the only people less intelligent than you can't read" - Sign on Newspaper Office Wall
  220. me retard by wanderers_id · · Score: 1

    yeah, im a retard. I did notice it and thought I correcdted it... but as I said, im retarted.

    Correct URL

  221. I will ask for 1 MILLION dollars, heh heh by Anonymous Coward · · Score: 0

    more than 35 trillion per square meter of Earth

    Are you kidding? That's more than 665,000 IPV6 addresses per square NANOMETER of the Earth's surface.

  222. Not really by fnj · · Score: 1

    Even with a DNS over the internet site names will run out far before addresses do.

    Sure they would - if it was a simple flat namespace. Maybe that's why the internet is hierarchical. Right now you usually have machine.domain.com. But there's no reason you can't use more levels, like dmv.state.ma.us.

    So for your refrigerator, maybe it would be refrigerator.17312.main-street.mytown.mystate.us.

  223. Woops by Anonymous Coward · · Score: 0

    3.4^38 is not the same as 3.4*10^38 - not even close.

  224. And you can quote me on this one... by nicke999 · · Score: 1

    35 trillion address should be enough for everyone!

    --
    Thanks for browsing at -1
    Please vistit my blog: www.framtiden.nu
  225. Ok great how do i start by LocalHero · · Score: 1

    I have been reading a couple of pages of this article. Beeing quite good at ipv4 i see the problem with it. Doing nat will only save ipv4 for some time. That is not a solution.

    Today ipv6 is not used because nobody uses is. So its time to start using it! :-)

    So the real question how do i start using it. Today im on a student ipv4 network in sweden. Can i run ipv6 on it? How do i configure it etc etc. Anyone has any idees? Im runnig Linux and Windows

  226. Spammers IPs by heybo · · Score: 1
    Take away the IPs being used by Spammers this would free up a bunch. I see whole blocks of address being used by these a_sholes to cover their tracks when blocking them from our mail server. Right now over 22,000 addresses are block on our server. These could be used by someone else for real use, and even with 22,000 addresses block the sh_t keeps coming so there is still more that that for the asking.

    I agree with the others too. Why does a house hold need public IPs. NAT does work very well and does give some secutiry to the local network.

  227. Next Best Thing to Free by handy_vandal · · Score: 1

    IP Addesses too cheap to meter!

    --
    -kgj
  228. There is NO imminent crisis! by dmehus · · Score: 1

    This whole FUD thing over an IPv4 crisis is unwarranted. A quick check of the IANA website shows that there are dozens of unallocated, IANA reserved A class of IP addresses remaining. We will not run out anything soon, and should be good for another 15 to 20 years. Plus, IPv6 has serious privacy implications that can trace every packet (essentially, every footprint) back to you. Until those privacy concerns are addressed and that Internet tracking mechanism is removed, we're fine with IPv4.

    Slashdot needs to quit approving these scare stories. And that's all I have to say about that. Thanks.

    Doug

  229. Asymetric Internet by Anonymous Coward · · Score: 0

    A shortage of IP addresses, even if partially solved by NATing, still creates an asymmetric internet. The big players with money will get an IP that anyone can connect to, and the smaller guys won't.

    CmdrTaco started slashdot in his dormroom. The next slashdot will require a bigger initial investment (i.e., hosting or "business class" service); the $50 to $250 a month will stop people from experimenting with stuff like that.

    The big ISPs are trying to feudalize the internet, and IPv6 could route around that.

    1. Re:Asymetric Internet by ivanmarsh · · Score: 1

      No one, no company needs or for that matter, should want, all of the IPs inside their network to be routeable/visible to the outside world.

      ex: There's is no reason Susan in accounting, who is running no services on her Windows '95 box, should have a routeable IP. Which applies to 99% of the employees of any company.

      Of course routeable IPs should be available but if the people using them that don't need them didn't have them there would be no IP shortage.