Slashdot Mirror


Millions of Internet Addresses Are Lying Idle

An anonymous reader writes "The most comprehensive scan of the entire internet for several decades shows that millions of allocated addresses simply aren't being used. Professor John Heidemann from the University of Southern California (USC) used ICMP and TCP to scan the internet. Even though the last IPv4 addresses will be handed out in a couple of years, his survey reveals that many of the addresses allocated to big companies and institutions are lying idle. Heidemann says: 'People are very concerned that the IPv4 address space is very close to being exhausted. Our data suggests that maybe there are better things we should be doing in managing the IPv4 address space.' So, is it time to reclaim those unused addresses before the IPv6 crunch?"

500 comments

  1. screw ipv4 by k3v0 · · Score: 5, Insightful

    lets just switch to IPv6, it's more functional and future proof

    1. Re:screw ipv4 by Anonymous Coward · · Score: 5, Funny

      Hello. I am Hunvi Maguay, premier of Swaziland. If you have an unused IP address we will buy it from you for $6,000,000 right now. In order for us to send you the money, please send us your bank account number along with proof of identity. Your Social Security number would be good. Please tell us your mother's maiden name too. Hurry, our offer will not last long.

    2. Re:screw ipv4 by Finallyjoined!!! · · Score: 2, Interesting

      Right....

      So you've configured all of your network equipment to use IPv6 then.

      Tell me: What is your IPv6 address, what's the address of your router/gateway and what's the size of block you are using?

      --
      If I had an Ass, I'd call it Fanny Bottom, then I could slap my Ass; Fanny Bottom, on the Arse.
    3. Re:screw ipv4 by Spazztastic · · Score: 1

      Have you?

      Because I sure as hell haven't.

      --
      Posts not to be taken literally. Almost everything is sarcasm.
    4. Re:screw ipv4 by Synn · · Score: 4, Interesting

      Nobody has configured for IPv6 because there's been no forced set date to switch over so everyone is still just using IPv4 which is working just fine.

      But when the date comes it'll be a long weekend for a lot of admins, but I'm guessing the switch will happen just fine.

    5. Re:screw ipv4 by madhurms · · Score: 1

      Yeah. If you have to spend time and money, why not spend it completely on IPV6; instead of a combination of IPV6 + IPV4.

      After all you will eventually run out of IPV4 addresses and HAVE to use IPV6. So start now and finish IPV6 implementation faster.

    6. Re:screw ipv4 by Finallyjoined!!! · · Score: 5, Insightful

      Internally yes. Externally no. However my point was; everyone who stands up and says "Screw IPv4 let's move to IPv6" should be sat in front of a border router & told to get on with it.

      Everyone can eat salami, precious few can make it.

      --
      If I had an Ass, I'd call it Fanny Bottom, then I could slap my Ass; Fanny Bottom, on the Arse.
    7. Re:screw ipv4 by Anonymous Coward · · Score: 0

      Bank account number: 16777216
      Social Security Number: 1048576
      Mother's Maiden Name: Fookyu

    8. Re:screw ipv4 by Anonymous Coward · · Score: 2, Informative

      Indeed.

      So why isn't IPv6 widely adopted yet?

      Because

      1> IPv4 still works fine AND
      2> It costs money to implement IPv6 AND
      3> Implementation cost of IPv6 is more likely to drop than to raise over time.

      The implementation cost is most likely to drop, hardware prices have nothing but dropped ever since there was hardware for sale. Another couple of years from now the price of those routers will probably be cut in half again.

      So there's nothing strange going on, it's just business as usual. If someone somehow finds more IPv4 address space to use they'll probably claim they've saved the entire internet from collapsing but in my opinion it'll just postpone the switch to IPv6 and save everybody a couple of bucks.

    9. Re:screw ipv4 by vux984 · · Score: 4, Insightful

      Nobody has configured for IPv6 because there's been no forced set date to switch over so everyone is still just using IPv4 which is working just fine.

      Sure my PCs can all switch without too much trouble; just configuration issues.

      Will an xbox, xbox360, PS3, Wii, PSP or DS do ipv6? Will my ipod touch? What about my cell phone? Does my dlink nat/router do it? What about my dlink voip box? My network printer? My cable/adsl modem?

      Seriously.

      I can't abandon v4 at home (Wii doesn't do ipv6 afaik, nor does my router). Nor can I do it at work... the LaserJet 4050s don't do it unless I upgrade the jetdirect module (which is stupid expensive). I also doubt my cell phone supports ipv6. My parent's have a Wii and a usb-print server that don't d ipv6. My brother in-law has a PS3 and a Wii that doesn't appear to support ipv6. My parents in-law have an xbox and a wifi router that doesn't do ipv6... my cousin has a DS... she's stuck on WEP because it doesn't do WPA... I highly doubt its going to do ipv6.

    10. Re:screw ipv4 by goofyspouse · · Score: 4, Funny

      Get it on with a border router? That is wrong on so many levels.

    11. Re:screw ipv4 by mikael_j · · Score: 1

      My subnet is 2001:16d8:ff70::/48. Of course, I currently only have three machines that are configured to use IPv6, and I use an internal DNS server to keep track of them at the moment...

      /Mikael

      --
      Greylisting is to SMTP as NAT is to IPv4
    12. Re:screw ipv4 by hedwards · · Score: 5, Insightful

      What you'd do is upgrade the router. That's it.

      Basically new routers would do a 1:1 version of NAT going from IPV6 externally to IPV4 internally. You'd likely still be using the set aside non-connected blocks without problems. As things evolve you'd probably be able to do IPV6 easily internally and ditch that as the network devices support it.

      The difficulty of upgrading to IPV6 has never been on that end it's the other infrastructure and the ISP services which were where the actual work, challenge and money were located.

      I'm sure that there are other ways of doing it, but that's really the simplest and it allows people to transition on the less important end as they care to or not. It wouldn't make a difference for anybody else.

    13. Re:screw ipv4 by Anpheus · · Score: 2, Interesting

      All of those things can add IPv6 functionality in firmware, I'd put money on it. Just because the companies are too lazy to do so doesn't mean it's unpossible.

      The FCC should just mandate a switch to IPv6, if the US leads, the rest of the world tends to follow. Ridiculous foreign policy demands aside.

    14. Re:screw ipv4 by Chris+Pimlott · · Score: 4, Informative

      If you're like most of us, all your devices at home are living behind NAT. There's no reason they can't keep living in an ipv4 private network behind an ipv6 router.

    15. Re:screw ipv4 by __aamnbm3774 · · Score: 5, Funny

      I love all meat references.

      Screw the car-analogy people. Explain how this situation affects me in terms of meats!

    16. Re:screw ipv4 by Pincus · · Score: 1

      Future proof? I know we're talking astronomically big numbers, but despite the IPv6 marketing spin, nobody can say with certainty there won't be a reason 50 years from now for each fiber on your super-electro-shirt to have its own address. Suddenly a trillion, trillion, trillion might not be so unattainable.

      IPv4 is, what, 30 years old? Who anticipated this explosion back then?

    17. Re:screw ipv4 by morgauo · · Score: 1

      Wrong focus... IPV6 has to happen with the companies which produce those items. Very few home users are going to install ipv6 themselves.

    18. Re:screw ipv4 by Anonymous Coward · · Score: 0

      Not everyone can eat salami.

      • people who observe moral prohibitions on eating salami
      • the dead
      • people born without faces
      • people who can't afford to eat salami
      • people with irrational fear of sausages

      You really ought to do more research before making such wild claims.

      Perhaps you should do some research before making such wild claims:

      • people who observe moral prohibitions on eating salami -- they can eat salami, they just choose not to
      • the dead -- fair enough
      • people born without faces -- unless they were born with a mouth somewhere else on their body
      • people who can't afford to eat salami -- they can if it's given to them
      • people with irrational fear of sausages -- if it's chopped up and thrown in a stew without their knowledge, they can eat it
    19. Re:screw ipv4 by mini+me · · Score: 2, Interesting

      Will my ipod touch

      I don't see why it wouldn't. It runs pretty much the same operating systems that Macs do.

    20. Re:screw ipv4 by catxk · · Score: 3, Interesting

      Everyone who says we still need IPv4 and should focus on reusing the millions of idle addresses, should be sat in front of the internets and told to get on with it. I for one wouldn't have a clue.

      --
      Don't be crazy anymore!
    21. Re:screw ipv4 by OrangeTide · · Score: 1

      I ought to make you in salami.

      --
      “Common sense is not so common.” — Voltaire
    22. Re:screw ipv4 by Grimbleton · · Score: 1, Funny

      You're gonna take a big old sausage up the beef hole.

    23. Re:screw ipv4 by Finallyjoined!!! · · Score: 1

      Research done.

      Everyone can eat salami.

      Not everyone wants or can afford to.

      --
      If I had an Ass, I'd call it Fanny Bottom, then I could slap my Ass; Fanny Bottom, on the Arse.
    24. Re:screw ipv4 by Anpheus · · Score: 4, Insightful

      Future proof? Everyone says IPv6 is future proof. No one will ever need more than 2^64 addresses.

      That's ridiculous. If we have the addresses, we'll find some way to use them. Instead, it should be IPvX. We should have an extensible standard that the IANA or -someone- can flip a switch on and the routers will add another 8 bits to the address automatically. Need more IPs? Done, 256 times more. This scales well, means we'd never have to go through this again and in thirty years no one will be mocking our generation for this silly attitude of "2^X IPs is enough for the whole world."

    25. Re:screw ipv4 by __aamnbm3774 · · Score: 1

      LOL, I guess I had that coming.
      Now I find the idea even more hilarious.

    26. Re:screw ipv4 by silent_artichoke · · Score: 1

      +1, Insightful Seriously, would you take my boss's job from him? I beg you!!

    27. Re:screw ipv4 by Anonymous Coward · · Score: 0

      Name: Anonymous Coward
      Account numer: 666 666
      SSN: 666 66 6666
      mother's maiden name: Coward (never married)
      I'll send you the IP number as soon as the deposit clears.

    28. Re:screw ipv4 by omgitsthr33 · · Score: 2, Informative

      DD-WRT has been working on the implementation of IPv6 within their firmware. http://www.dd-wrt.com/wiki/index.php/IPv6

    29. Re:screw ipv4 by Anonymous Coward · · Score: 0

      You forgot:

      In Soviet Russia, salami eats you!

    30. Re:screw ipv4 by Anonymous Coward · · Score: 0

      What about people with rational fear of sausages?

    31. Re:screw ipv4 by xSauronx · · Score: 0

      or should: my brother avoids products with chocolate, caffeine, and pork because he has kidney stones and these cause them to be worse and more frequent.

      --
      By and large, language is a tool for concealing the truth. -- George Carlin
    32. Re:screw ipv4 by Sechr+Nibw · · Score: 5, Funny

      Only if you stick it in the Outgoing jack.

    33. Re:screw ipv4 by Cajal · · Score: 2, Interesting

      The FCC has no authority to dictate IPv6 usage in the US.

    34. Re:screw ipv4 by coolsnowmen · · Score: 2, Insightful

      We should have an extensible standard that the IANA or -someone- can flip a switch on and the routers will add another 8 bits

      IANA? You are not a ____? A computer engineer.

      Anyway, we should not have such a thing. Yes it would be easy in software to make such a conditional, but the high performance backbone needs to be just that. And when you add that "option" the hardware engineer needs to decide whether that condition should be done in serial (costs you in transient lag), or do all options in parallel (costs you in $$).

      But it really comes down to keep.it.simple.stupid engineering. Why add complicate a standard when you can't justify it?! Your attempt at future proofing ipv# is short sighted because ipv6 will easily last 20 years, and after that noone knows. They don't know because it is impossible to predict how technology will evolve, people will adopt it, and politics will allow it in 30 years. So as an engineer you pick a point, and you say with 99.999% probability this will be good enough for X years. At which point you change it.

    35. Re:screw ipv4 by RazzleDazzle · · Score: 1

      Come on I can actually follow your sentences' grammar and your spelling is spot on, you are obviously a fake.

      Now if you had said something more like this I might have believed your offer

      Greetings,

      I am requesting for your assistance in a business transaction. I work as a director of projects in the department of minerals and energy here Pretoria,South Africa. I represent a four member committee vested with the responsibility of contracts evaluation.

      We will require you to fill an application form that we shall submit to our country's justice department for the transfer of right and privilege of the former contractor to your name.The actual contract cost has been paid to the original contractor,leaving the balance of the inflated ($27,000,000.00 ) mentioned above which we want to legally obtain approval from the appropriate government authorities and our apex bank for disbursement.

      I will give the details of how we intend to proceed, this is a legitimate transaction. You will be paid 15% for your management fees; if I am able to reach terms with you.

      If you are interested, please write me back and provide me with your full names, tel/cell numbers and I will provide details. Keep this close to you we are still serving the government.

      Regards,

      Mr. Ramsey Nkosi.

      --
      ZERO ZERO ONE ZERO ONE ZERO ONE ONE! Just brushing up for my next big invention: Ethernet over Voice (EoV)
    36. Re:screw ipv4 by Anonymous Coward · · Score: 0

      The dead can eat salami? So what you are saying is that there are salami zombies out there!? RUN!

    37. Re:screw ipv4 by Cajal · · Score: 1

      IPv6 provides 79 trillion billion times more space and IPv4. Is that enough for you?

      Most of the guidelines on IPv6 programming focus on using IP-version-agnostic interfaces, rather than writing IPv6-specific code. Take a look at getaddrinfo() and getnameinfo().

      But, extending IP is non-trivial. You need to define a way to propogate the routes, to represent the addresses in DNS, and how to bind it to a variety of layer 2 protocols.

    38. Re:screw ipv4 by TheRaven64 · · Score: 4, Insightful

      Do you have any idea how big a number 2^64 is? There are currently just under 2^33 people in the world. This means that 2^64 is almost enough for every person to have as many IP addresses as there are currently people. It is enough for 2^35 IPs per square kilometre of the Earth - including the sea - or, to put it another way, enough for every 0.29cm^2 of the Earth's surface to have a unique IP. It is enough not just for every computer you own to have an IP address, but for every item of clothing, every item of furniture, and every object in your fridge to have a unique, public, IP, and still have a lot left over. IPv6 will last until nanotech becomes widespread and you want to have networks of nanoscopic devices online - and possibly even then since it would make sense to treat personal area networks as a single public device.

      --
      I am TheRaven on Soylent News
    39. Re:screw ipv4 by berashith · · Score: 1

      the precious few salami makers are putting brains in there now ?

    40. Re:screw ipv4 by gnick · · Score: 5, Funny

      The FCC should just mandate a switch to IPv6, if the US leads, the rest of the world tends to follow.

      Exactly.

      Listen up world! We've decided that you all should be using miles, feet, inches, Fahrenheit, and gallons. Please upgrade your silly metric system.

      --
      He's getting rather old, but he's a good mouse.
    41. Re:screw ipv4 by rossdee · · Score: 1

      I plan ti skip IPv6 and wait for IPv7 :)

      But seriously wouldnt it be more logical to have the next vesion be IPv8
      since IPv4 uses 4 bytes (32bits) per address and IPv6 is 6 bytes (48 bits)
      and all recently made computers have 64 bit CPU - so storing and manupulation the address would be the same overhead whether it is IPv6 or IPv8

      And its good promotion for the upgrade (put a V* in your computer, or

      It could be sponsored by the vegetable juice company (could of had a V8)

      ????
      Profit

    42. Re:screw ipv4 by Cramer · · Score: 3, Insightful

      Actually, it is far more complicated than current generation IPv4 NAT/PAT. IPv4/IPv6 requires a protocol bridge. I guess you are too young (and I'm really not that old) to remember when IPv4 ("IP") was new. Everybody had networks built with Appletalk, IPX, etc. A company that wanted to "get on the internet" either had to replace equipment and completely restructure their network into a "dual stack" rig -- while you could install a TCP/IP package in windows and Mac System 6, none of the services commonly in use (i.e. the reason for the network in the first place) would use IP. It took many more years for IP to finally become the backbone. For example, a decade (+) ago game makers were still using IPX for network play. And even as recent as 2003, the telco I was working for still had, and used, a large IPX network. (luckily, they had fazed out all the token ring hardware in the mid/late '90s.)

      It's not as simple as rewriting the source or destination in a packet. Both have to be changed and the entire packet rebuilt. Plus, there has to be logic to dynamically turn the IPv6 world into an IPv4 world -- because a legacy device has zero understanding of v6, it cannot understand a v6 address at all.

    43. Re:screw ipv4 by k3v0 · · Score: 1

      i haven't yet since my ISP doesn't yet support IPv6. but since i work at my ISP, i know we will support it soon. however, once the switchover happens i know my routers and home computers will support IPv6.

    44. Re:screw ipv4 by Chirs · · Score: 1

      If the router is handling the conversion and talking ipv4 internally, why would the devices need to support ipv6 again?

    45. Re:screw ipv4 by gbutler69 · · Score: 1

      I'm pretty sure IPv6 is 2^128 (a much, much, much, much larger number)

      --
      Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
    46. Re:screw ipv4 by NatasRevol · · Score: 4, Informative

      You forgot the real reason.

      IPv6 numbers are damn hard to remember.

      Seriously, what's easier?

      192.168.0.1 or
      2001:0db8:85a3:0000:0000:8a2e:0370:7334

      --
      There are two types of people in the world: Those who crave closure
    47. Re:screw ipv4 by hvm2hvm · · Score: 1

      Isn't ipv4 capable to hold a few billion addresses? I know you can't divide them very easy since they come in groups of at least 256 but still how the hell did so many addresses get used up? There can't be a billion computers connected to the Internet. Yes, ipv6 is better but the number of possible ipv4 addresses shouldn't be a problem at least for another decade or two.

      --
      ics
    48. Re:screw ipv4 by OolimPhon · · Score: 1

      Fail. IPv6 is 128 bits.

    49. Re:screw ipv4 by Cajal · · Score: 1

      As I said, it's highly unlikely that the router will NAT between IPv6 and IPv4 since no one can agree one a good way to do it. I'm certainly not aware of any routers that support it out-of-the-box.

    50. Re:screw ipv4 by BrowserCapsGuy · · Score: 1

      Can't you just get one of those government subsidized converter boxes like the ones being used for television and be done with it?

      --
      Alright! I know I'm in there! If I don't come out, I'll have to come in after me!
    51. Re:screw ipv4 by Cramer · · Score: 2

      You are underestimating the amount of work necessary as well as the amount of "legacy" equipment still in use today. Just look around your home/office and count up the number of devices for which the manufacturer has gone out of business (bought out, etc.) or has been declared "end-of-life" and is no longer supported. All of those devices are obviously working and providing some utility or they wouldn't be there.

      Bottom line: it's going to cost people/companies a lot of money and time to replace equipment and software, and reconfigure systems in order to support IPv6. Right now, no one is willing to spend that much money for something that Is Not Necessary.

    52. Re:screw ipv4 by Sancho · · Score: 1

      3> Implementation cost of IPv6 is more likely to drop than to raise over time.

      That's only true to a point. The faster you need something done, the more it tends to cost. If we get into a big crunch, the move will cost more. Also, some organizations are poo-pooing IPv6 even as they're revamping their infrastructure (a major ISP in Britain is a recent example). If they get into a crunch and need to deploy IPv6, they'll have to replace a great deal of their infrastructure. Depending upon when they need to, it could be much sooner than their next planned refresh cycle.

      So there's a lot to consider, honestly. Probably one of the good things to do is to buy IPv6-capable equipment as you replace existing equipment. That way, hopefully the bulk of your infrastructure will be in place and ready when you need it, and it's going to be relatively small additional costs per piece of equipment.

    53. Re:screw ipv4 by petermgreen · · Score: 1

      The number of organisations with more than the 16 million devices that can be addressed by 10.* is probablly pretty small and most large organisations preffer to keep the number of machines exposed to the open internet to a minimum anyway.

      Most public internet services are likely to be availible on IPV4 addresses for a long time, there are a lot of domestic users who can be forced behind nat if the ISP needs the addresses for higher paying histing customers.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    54. Re:screw ipv4 by alxkit · · Score: 0

      you forgot the salami allergies

    55. Re:screw ipv4 by supernova_hq · · Score: 1

      Sure, if you only want your devices to talk to each other. But as soon as your computer tries to access the ipv6 internet using an ipv4 address, you have some serious work to do. On the simplest scale, your router would need to convert all ipv6 dns addresses to "virtual" ipv4 addresses, then work as a translator. That however does not ever TOUCH protocol changes, encryption schemes, etc, only the address itself.

      In theory, you could hook up a token ring server behind a nat firewall with ipv4 on the other side (i believe banks still do this), but good luck having the two sides of the firewall talk to each other!

    56. Re:screw ipv4 by evanbd · · Score: 1

      IPv6 has a 128 bit address, not 64. It's faster for specialized routers to work with fixed with fields, so they just made it *really* big. No one thinks we'll ever need 2^128 addresses -- this lets us "waste" lots of bits on organizing things conveniently.

    57. Re:screw ipv4 by Kadin2048 · · Score: 1

      Well, it starts out with a maximum that's equal to 2^32, which is 4.2B, but you'd never be able to actually get there.

      Even if you set aside the old legacy allocations that are probably pretty impractical to get back, you lose quite a few addresses in routing overhead. This was really bad back before CIDR, but it's still a problem now. Addresses need to be handed out in blocks and then the blocks get cut down, smaller and smaller, as you go down the chain. But because it's such a PITA to request new blocks, everybody grabs a few more than they need at every level. The net effect is significant waste.

      I'm sure now, even with CIDR, there's probably a relationship between address-space utilization and routing table size, where as you start to approach full utilization (and have to start handing out addresses in smaller and smaller blocks, and networks end up with noncontiguous blocks acquired at different times, etc.) the routing tables start to get more and more complex.

      It's been a while since I've heard anyone particularly concerned about routing table size -- I assume because routers have been getting so much more powerful that they've kept ahead of the curve -- but it could turn into an issue again if we started to really saturate the address space. Particularly if gains in processing power and memory density started to taper off, you might get squeezed there instead of the raw lack-of-numbers issue.

      So even under the best circumstances where we recovered all the old IPv4 allocations, we wouldn't necessarily be buying ourselves as much time it might appear (by dividing the burn rate by the total available pool). There are a lot of factors that make it impractical to get to, or even near, 100% utilization. At some point it would just become painful to deal with, and in the process a lot of development probably would get stymied and a lot of money wasted on buying increasingly expensive addresses that could have been used more productively.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    58. Re:screw ipv4 by modecx · · Score: 1

      The Internet is not something that you just dump something on. It's not a big truck. It's a series of tubes. Sausage tubes. And if you don't understand, those tubes can be filled with unidentifiable meats like SPAM and if they are filled, when you put your delicious meat in, it gets in line and it's going to be mixed up by anyone that puts into that sausage tube enormous amounts of pork rectums, enormous amounts of other animal byproducts!

      --
      Constitutional rights may be respected, repealed, or modified; but they must never be ignored.
    59. Re:screw ipv4 by Sancho · · Score: 2, Informative

      Some perspective:
      Right now, there are over 6 billion people on Earth. IPv4 has a theoretical maximum of 2^32 (4.3 billion) IP addresses. IPv6 has a theoretical maximum of 2^128 IP addresses, which works out to more than 2^90 addresses per person currently on the planet. Yeah. Each person could have a whole bunch of IPv4-sized address spaces. A bunch of a bunch. Our planet probably isn't capable of holding so many people that each person would only get 2^32 addresses (size of the IPv4 address space.)

      I'd bet a couple of bucks that the human race will never ever need anything more than IPv6.

    60. Re:screw ipv4 by pbrooks100 · · Score: 1

      Absolutely, any in can be run with ~ 13kilobytes http://tech.slashdot.org/article.pl?sid=08/10/15/1839209&from=rss

    61. Re:screw ipv4 by Intron · · Score: 1

      It's just what we need to get the economy moving. In 1999 we had the Y2K Problem. Now we can have the YnotV6 Problem!

      --
      Intron: the portion of DNA which expresses nothing useful.
    62. Re:screw ipv4 by fm6 · · Score: 4, Funny

      The good grammar tells you he's a fake, but what kind? Obviously, a fake scam artist. In other words, a fake fake.

      But if he's not a real fake, what is he really? The only possibility that makes sense is that he really is the premier of Swaziland. I suggest you send him the information he requested. Or better yet, send it to me, and I'll handle the transaction for you.

    63. Re:screw ipv4 by Anonymous Coward · · Score: 0

      Is that like a fuck hole?

      If you're lucky, it's just a Arby's sandwich on the other side....

    64. Re:screw ipv4 by mattbee · · Score: 1

      That's fine and dandy in software land where you can just change your software to support an wibbly wobbly extensible standard. When you are investing in building routers for an ISP or other internet backbone, you need guaranteed performance, and not have to worry about whether fundamental parts of your addressing structures are changing size. That means very expensive Content-Addressable Memory (i.e. hardware hash tables, among other things) to guarantee that packets will go in and out at a particular rate. Those extra bytes in your packets can make a big difference to the price of a router which is trying to guarantee performance.

      At some point you have to say, screw it, this is the biggest most ambitious standard we can possibly conceive of, and it's safe for hardware vendors to start investing huge amounts of money in supporting it. And you can't do that with a "completely" futureproof packet.

      --
      Matthew @ Bytemark Hosting
    65. Re:screw ipv4 by cycler · · Score: 0, Redundant

      And this was modded Informative???

      Wouldn't it be easier if you strange guys upgrade your silly system to metric??

      At least the metric is easier to count. 10 of one thing is 1 of the same thing. /C

    66. Re:screw ipv4 by BitZtream · · Score: 4, Informative

      Its already well defined, there is no need for anyone to 'agree' on it, it was agreed on years ago.

      You are confusing NAT and PAT. I seriously doubt you use NAT anywhere. You are likely refering to PAT, NAT just translates addresses from one to another, a one to one mapping, one address external is used by one address internal. What you are used to using is PAT, with is Port and Address translation, which allows for one external address and many internal addresses.

      NATing between IPv6 and IPv4 is well defined and not difficult to do, there are already plenty of cheapy boxes for home use that do it. Hell mine will even setup an IPv6 Tunnel to someplace like he.net.

      PAT on the other hand is something no one cares about because the ridiculous amount of IPv6 addresses means we can just give EVERYONE a /64 and they can use REAL NAT rather than PAT to get the job done.

      Finally, part of the IPv6 protocol requires support for making IPv4 address space available over IPv6. Practically any router on the planet which supports both IPv4 and IPv6 will have the support to deal with both and bridge between them.

      So your statement is incorrect in that NAT is supported by pretty much every router that supports IPv6, what you are thinking of is not NAT, its PAT which no one in the IPv6 world cares about since its an old hack that doesn't need to exist in the new world of IPv6. Because of that, no routers are going to bother supporting it.

      For reference, since the defacto standard at the moment appears to be giving individual users a /64 block, From: http://en.linuxreviews.org/Why_you_want_IPv6

      Number of IP Addresses in a IPv6 /64 prefix, the typical space a home user gets: 18,446,744,073,709,551,616

      IPv6 gives citizens the opportunity to become real Internet participants. IPv4 makes citizens into passive consumers who are only able to connect to compartmentalized networks run by companies or governments. This is why the establishment does not want IPv6.

      There is a total of 2^128, or 340,282,366,920,938,463,463,374,607,431,768,211,456 unique IPv6 adresses. That's roughly 667 quadrillion addresses per square millimeter of the Earth's surface!

      Basically, we can not possibly exhaust this address space on the planet earth, there simply isn't enough matter on the planet to do so, and adding the matter required to do so would result in a gravitaional singularity forming as the matter collapsed onto itself. So ... there is no actual NEED to do it with IPv6.

      If you wanted to pick something to worry about, it would probably be the lack of stateful firewalling in those home/cheapie routers which the NATs of today effectively provide a outbound only initiation of connections, with IPv6 and the fact that cheapie routers aren't firewalling by default, we'll end up with a lot more machines fully exposed to the Internet by default.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    67. Re:screw ipv4 by joeman3429 · · Score: 2

      oh god, I'd never thought of that.

      I guess routers will have to have names now. 192.168.0.1 was easy to remember, but jesus christ. How will we locate our routers (among other things of course)? I'm honestly asking lol

    68. Re:screw ipv4 by joeman3429 · · Score: 1

      I propose we sit around and pretend that nothing's wrong, and then when crunch time happens, the government institute a internet bailout program at outrageous cost to the public.

    69. Re:screw ipv4 by Fastolfe · · Score: 2, Funny

      IPv6 will last until nanotech becomes widespread and you want to have networks of nanoscopic devices online - and possibly even then since it would make sense to treat personal area networks as a single public device.

      So your solution to running out of IPv6 addresses is.. NAT?

    70. Re:screw ipv4 by BitZtream · · Score: 1

      IPv6 already has system defined for translating IPv4 addresses to IPv6 and back again, and it can be used by any IPv6 enabled software to talk to IPv4 software. The serious work was done ... in the 90s. Its no more difficult than the PAT software already found on every cheapie router on the planet.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    71. Re:screw ipv4 by vonart · · Score: 1

      Just FYI: The IANA is the Internet Assigned Numbers Authority, which maintains the IP address allotments and can be found at http://www.iana.org/ .

      --
      The American Dream has too much grinding and the leveling makes no sense. -GameboyRMH (1153867)
    72. Re:screw ipv4 by juanillodgn · · Score: 1
      > It is enough for 2^35 IPs per square kilometre of the Earth - including the sea

      Yeah, but... What about the rest of the universe?

      We would have to redo it when our colonies surpass certain numbers... ;)

    73. Re:screw ipv4 by TheThiefMaster · · Score: 1

      I also doubt my cell phone supports ipv6.

      Most do, but the internet gateways they use often only support v4 on the internet side.

    74. Re:screw ipv4 by operagost · · Score: 1

      Seriously, what's easier?

      192.168.0.1 or
      2001:0db8:85a3:0000:0000:8a2e:0370:7334

      3.88

      DECNET FTW.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    75. Re:screw ipv4 by BitZtream · · Score: 1

      Please see: http://en.linuxreviews.org/Why_you_want_IPv6

      I'll paste the important part, but the main point is, the amount of matter required to even store all of the addresses available in the IPv6 address space doesn't exist on Earth with current technology. Adding the matter to Earth to just be able to store a list of all the addresses would result in our planet collapsing into a black hole long before we finished creating the list, let alone actually using it for anything.

      A /48 alone has enough address space to literally IPv6 enable every single device on the planet, and there are
      roughly 2^48 of them available in the IPv6 address space! So we've got support for untold billions of planets like ours with everything having its own unique address.

      That, to me, qualifies as future proof.

      Some Very Huge numbers
      Compare the numbers.. ..and realize why IPv6 is great:

      Total number of IPv4 IP Addresses: 4,294,967,296
      Number of IP Addresses in a IPv6 /64 prefix, the typical space a home user gets: 18,446,744,073,709,551,616
      IPv6 gives citizens the opportunity to become real Internet participants. IPv4 makes citizens into passive consumers who are only able to connect to compartmentalized networks run by companies or governments. This is why the establishment does not want IPv6.

      There is a total of 2^128, or 340,282,366,920,938,463,463,374,607,431,768,211,456 unique IPv6 adresses. That's roughly 667 quadrillion addresses per square millimeter of the Earth's surface!

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    76. Re:screw ipv4 by joeman3429 · · Score: 2, Funny

      I'm not going to let your ignorance keep my children from having their fridge/microwave/cellphone/shirt/hat/dog/cat/fishtank/monitor/3 dozen computers/swarm of spy-bot bees/printer/coffee mug/mouse/keyboard/envelope stamps/individual pages in their books/speakers/light bulbs/doors from having their own IP address.

      Insensitive bastard...

    77. Re:screw ipv4 by Sancho · · Score: 1

      You joke, but I'm pretty sure I don't have 4 billion pages combined in all of the books I own :)

    78. Re:screw ipv4 by BitZtream · · Score: 5, Informative

      You're missing the fact that an IPv6 /64 is what a home user gets, not the total address space. The IPv6 address space is 128 bits, meaning you get 2^64 blocks of 2^64 addresses.

      Meaning every square millimeter of the earths surface can be assigned approximately 667 quadrillion unique addresses. With your math, I personally can assign every 0.29cm^2 of the Earth an address out of my block alone.
      Please see:
      http://en.linuxreviews.org/Why_you_want_IPv6

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    79. Re:screw ipv4 by fm6 · · Score: 1

      Future proof? Everyone says IPv6 is future proof. No one will ever need more than 2^64 addresses.

      You're regurgitating the old "nobody will ever need more than 640K of RAM" myth. And it is a myth. It comes from the design assumption of MS-DOS that it would only ever run on early processors with a 1-megabyte address space. That assumption made sense when IBM and Microsoft's joint plan was to migrate everybody to OS/2 once 80286s became available. It only fell apart when the IBM/Microsoft partnership fell apart, and MS decided that MS-DOS could be kept going with various kludges to work around the 640K barrier.

      Every system for counting things makes some kind of assumption about how big the count can get. If you design a counting system so that it's infinitely extendable, you add a lot of complexity, which raises cost and lowers reliability. It always makes more sense to make some kind of assumption about the biggest number you plan to deal with and work from there. All information systems are designed that way.

      You get in trouble when you make the assumed biggest number too small, as frequently happens. But I think 2^128 (not 2^64) is a big enough number for IP addresses. Consider that there would have to be 2^52 IP addresses allocated for every star in the observable universe for us to use up that many addresses. That's going to take a long time. I think it's safe to say that by the time we do, the Internet, in anything like its present form, will be obsolete. I wouldn't even count on the human race surviving that long.

    80. Re:screw ipv4 by Bishop+Rook · · Score: 3, Interesting

      Or 2001:0db8:85a3::8a2e:0370:7334? You can shorthand out those all-0 octets.

    81. Re:screw ipv4 by joeman3429 · · Score: 1

      Yeah, and they certainly wouldn't be publicly accessible. I guess ipv6 *will* last for a while.

      Until we spread to other planets and the Empire's trillions of trillions of people communicate through some kind of faster than light internet. Ah, those'll be the days

    82. Re:screw ipv4 by MadnessASAP · · Score: 1

      Yep, all the notepad manufactuers can't wait for the release of IPv6. There sales are going to go through the roof.

      --
      I may agree with what you say, but I will defend to the death your right to face the consequences of saying it.
    83. Re:screw ipv4 by BitterOak · · Score: 4, Insightful

      If the router is handling the conversion and talking ipv4 internally, why would the devices need to support ipv6 again?

      Ok, so let's say you have your router converting packets from IPv6 and IPv4, and translating your internal IPv4 addresses to external IPv6 addresses. Now, let's say you're sitting at your IPv4 computer connected to this magic router. You launch Firefox and type type the Slashdot URL. (More likely, you'd have it bookmarked.) So, what does your computer do? It sends a DNS request to get Slashdot's IP address. Now, in an IPv6 world, this IP address would have 128 bits instead of 32. How is your IPv4 operating system going to make sense of this?

      So you might suggest a fancier router that is DNS aware, and translates those addresses back and forth, effectively acting as a DNS proxy. But there is a problem. How do you translate all IPv6 addresses to IPv4 addresses? Considering that the address space for IPv6 has 4 times as many bits, I don't see how this is even possible: you can't assign a unique 32 bit number to each 128 bit number.

      So the problem is much more complicated than it first appears.

      --
      If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
    84. Re:screw ipv4 by Cajal · · Score: 4, Informative

      I'm not confusing NAT and PAT. There was a nice writeup at ars technica recently about the IETF's efforts to define a v6/v4 NAT - http://arstechnica.com/news.ars/post/20081006-ietf-working-on-making-ipv6-and-ipv4-talk-to-each-other.html

    85. Re:screw ipv4 by BitterOak · · Score: 1

      The FCC should just mandate a switch to IPv6, if the US leads, the rest of the world tends to follow. Ridiculous foreign policy demands aside.

      Yikes! The FCC has never regulated internet protocols before. Do you really want them to start? Internet RFCs, which essentially define Internet protocols are not government regulations, but have been submitted by private individuals, and those that were useful caught on; others didn't. One could make the case that the Internet and its protocols evolved as rapidly and usefully as it did precisely because it didn't have government oversight.

      --
      If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
    86. Re:screw ipv4 by empaler · · Score: 1

      or should: my brother avoids products with chocolate, caffeine, and pork because he has kidney stones and these cause them to be worse and more frequent.

      You just made me more happy that I avoid pork. (Bacon is a vegetable, everyone knows that)

    87. Re:screw ipv4 by Golddess · · Score: 1

      Everyone can eat salami.

      The people born without faces can eat salami? Where will they stick it? Wait, I don't want to know....

      --
      "I'm not sure I like the fugnutish tone you used in your post!" -RogL (608926)-
    88. Re:screw ipv4 by es330td · · Score: 1

      You spelled entirely too many words correctly and your sentences in general display correct subject/verb/number/tense agreement to have been written by any scammer.

    89. Re:screw ipv4 by Anonymous Coward · · Score: 0

      What if we change from longitude and latitude for coordinates to IP addresses?

    90. Re:screw ipv4 by Loki_1929 · · Score: 1

      Does my dlink nat/router do it? What about my dlink voip box?

      D-link? Seriously? Why - because tapping out morse code 1s and 0s with a telegraph was too reliable?

      Get out.

      Seriously, anyone on Slashdot should be of a technical level to know that even in the worst of times, purchasing complete and utter garbage equipment just isn't worth it. If you're strapped for cash, go with Zyxel or US Robotics. Heck, even Belkin or Netgear is better off than the useless crap shipped en masse from the likes of D-link and Linksys. If you have a little money in hand, do yourself a favor and invest in a Sonicwall or cheap Cisco device. At the lower end, they're roughly the same price these days: around $300.

      --
      -- "Government is the great fiction through which everybody endeavors to live at the expense of everybody else."
    91. Re:screw ipv4 by John+Hasler · · Score: 1

      Exactly. IPV6 will probably need replacing in 20 or 30 years, but it probably won't be for lack of address space. It will be due to some irreparable failing that we cannot now anticipate.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    92. Re:screw ipv4 by MythoBeast · · Score: 1

      Ok, here's an education in IPv6. If you were to distribute all of the IPv6 addresses evenly across the people of the world, every human CELL would be able to have 55 million complete IPv4 address sets.

      There's so many available addresses that they don't even expect to make use of 1% of the address range in the foreseeable future.

      --
      Wake up - the future is arriving faster than you think.
    93. Re:screw ipv4 by POTSandPANS · · Score: 1
      I agree, but I don't think this is a case of there being a few /8s that somebody forgot about. This seems like changing a /22 into a few /24s to try to free up some unused subnets. Anybody that thinks this is a good idea should not be allowed to touch a border router.

      I think the way it'll happen is this: A country such as China or India will run out of addresses. They will be the first to change over and start using NAT to reach the rest of the world. They'll finance the change by selling the ipv4 blocks to anybody that refuses to change. Finally there will be no ipv4 shortage because north america will be the only place using it.

    94. Re:screw ipv4 by Architect_sasyr · · Score: 1

      Internal addressing is a lot easier to remember than external (thankfully external address' should be few and far between).

      I don't remember the exact numbers but I know a guy who uses IPv6 exclusivly at his education facility, and the address range is split up based on campus number, building number (prefixed with a 0), floor number, room number. Admittedly they look scary as hell, but the scheme is actually quite intelligent and easy to remember (at least it was when I was training there).

      If I can remember TY=!01!h&CxCKoW^F;iHPKCk5lg1;ps#0p>vT for my routers internal ssh password (obviously fudged a little bit) then I'm sure I'll be able to remember IPv6 passwords later on.

      --
      Me failed English...
      FreeBSD over Linux. If my comments seem odd, this may explain...
    95. Re:screw ipv4 by jcrousedotcom · · Score: 1

      Or even for much less you could get an old PC (I actually use a Celeron 400 w/ about 256 mb of ram - way over the top for what I need) and use something like IPCop. That's a lot less than $300 and a lot more capable than a D-link or most other "home" routers.

      --
      Illiterate? Write for free help!
    96. Re:screw ipv4 by Anonymous Coward · · Score: 0

      No. It's modded Funny.

      Please turn the sensitivity up on your sarcasm detector.

      Thanks.

    97. Re:screw ipv4 by LarsG · · Score: 1

      We have the same kind of problems with ipv4 Internet and ipv4 clients sitting behind pat/napt/snat/masquerade.

      Just like the current net where ipv4 services out there have to take into account ipv4 clients sitting behind pat, the early ipv6 net will have to take into account ipv4 clients sitting behind 6to4 translators.

      However, when the cloud is finally moved over to ipv6 the clients will start to move over too and we will finally have a fully ipv6 net.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    98. Re:screw ipv4 by Anonymous Coward · · Score: 0

      Oh, I've only got one IP address and 4 computers at home. Oh my, I don't know how I'll handle assigning 4 unique machines to 1 address. Boo hoo, woe is me, if only my router could somehow keep track of which address on the internet each computer is talking to and vice versa.

    99. Re:screw ipv4 by drmerope · · Score: 1

      And this is exactly the problem. Using 128b addresses was a big mistake. It just does not mesh well with hardware accelerated routing. The capacity of a router declines by 1/4 using IPv6. That makes IPv6 unsuitable for deployment.

      Sure in 4 years, technology will scale, but so will demand.

    100. Re:screw ipv4 by CAIMLAS · · Score: 1

      The point is that, short of complex management suites for IPv6, IPv6 will be, and is, almost completely impossible to effectively administrate at the human level. Even for a simple office network on IPv6, you'll need full DNS services in order to be able to effectively keep track of what is where.

      The days of being able to write down an IP address on a pad of paper for reference are (close to) being gone due to the inconvenience of doing so, I think.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    101. Re:screw ipv4 by Anonymous Coward · · Score: 0

      I prefer to refer to it as the WANhole.

    102. Re:screw ipv4 by kayditty · · Score: 0

      ..as well as the "octets" (these are technically uh.. double octets? hexadecoctets??) beginning with zero.

    103. Re:screw ipv4 by Anonymous Coward · · Score: 0

      And do all your applications support IPv6?
      I'm convinced that most OS's support it, but I'm pretty sure most applications don't.

    104. Re:screw ipv4 by hvm2hvm · · Score: 1

      True, I didn't think about the routing problems. Now I'm OK with changing to ipv6 :D

      --
      ics
    105. Re:screw ipv4 by rtb61 · · Score: 1

      More importantly

      1) Allocate all the IPv4 addresses.
      2) Create a scarcity.
      3) PROFIT

      The biggest delay in the transition from IPv4 to IPv6 is the profit that ISP's generate by renting access to them and of course IPv6 will be the big free internet address give away, even for the oft abused end users. So for them it really sucks, they have to spend money to switch from IPv4 to IPv6 so that they wont be able to make money by charging for IPv4 addresses. For the end users it is great.

      --
      Chaos - everything, everywhere, everywhen
    106. Re:screw ipv4 by Anonymous Coward · · Score: 0

      Last time I configured a border router for IPv6 it took a total of 30 seconds more than IPv4...

      Both Cisco and Juniper have mature, stable IPv6 implementations. I don't understand what you are whining about. It's trivial to do the switch.

    107. Re:screw ipv4 by LarsG · · Score: 1

      It's not as simple as rewriting the source or destination in a packet

      Neither is ipv4 PAT/SNAT/whatever-you-call-it. While simple address rewrite is sufficient for some protocols, other things break in interesting ways unless you do special handling on a protocol by protocol basis (FTP being the obvious example).

      Anyway, one is going to have to move to ipv6 some time and I don't really see how ipv4/ipv6 translators would cause much more pain than ipv4 PAT does today.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    108. Re:screw ipv4 by Anonymous Coward · · Score: 0

      Internet RFCs, which essentially define Internet protocols are not government regulations, but have been submitted by private individuals, and those that were useful caught on; others didn't. One could make the case that the Internet and its protocols evolved as rapidly and usefully as it did precisely because it didn't have government oversight.

      WTF are you talking about? Look up the RFCs for IPv4 and you'll see "DARPA" written all over them. You believe that's the name of a private individual??

    109. Re:screw ipv4 by porpnorber · · Score: 1

      Fortunately it's 2^128, not 2^64. If it were only 2^64, it wouldn't be future proof at all. You are right, we have to take 34 bits off the top just to index all the users. Actually, we probably have to take 40 bits off the top, if that's what we're doing, because of the administrative haggling problem—different countries always want pre-allocated blocks. Then, of course, people are born and die, form companies with separate identities, and want multiple address spaces for reasons of privacy.

      But leaving all that aside, I now have 24 "personal" bits. In reality, I'm not going to assign 2^24 addresses manually; they're going to be allocated by various address allocation mechanisms, and we're going to need a registry of those mechanisms. That's going to take 4, maybe 8 bits to figure out. Ok, so we've got 16 bits left to play with. Now, my plan for the future is to make every single interconnect in every single device with electronics in it serialised, packet-structured and IP-like. Let's give them all addresses. We'll start with macroscopic objects: the light switches in your house, the light bulbs in your car, the sensors in your appliances and burglar alarms, (in an ideal world, an address for each book you own to help you find it, but perhaps that's science fiction), the speakers in your sneakers, the subdevices in your phones and games and music players and so on. Now of course, for your computers. Each of them can soon be expected to have around 1024 processors for graphics and physics, an array of, I don't know, let's call it 8 storage devices at each of 3-8 levels of a storage hierarchy, each composed (for packaging reasons) of 16-64 subdevices. Now we need to take all of that and double it twice because there are logical devices as well as physical devices to contend with. Oh, and we want multicast and anycast addresses for talking to classes of devices. And there are networks! Thousands, perhaps millions, of microscopic routers and switches are gluing this together. They need management addresses at the very least. And, of course, hardware vendors want statically pre-assigned blocks of addresses so they don't have to connect manufacturing directly to a global bureaucracy—and most of them get to around serial number 3 before they go belly up, but they don't give the addresses back because they're still technically an asset in some financial limbo.

      And I said that books were science fiction, but maybe not. There's this nice convenient 'large' address space there for the allocating, let's use it with RFID and give a separate address to every can of beans. But we ran out of bits long before doing the beans, if you go back and count.

      I didn't even get to the route consolidation problem, and (for mathematical reasons) that would like to eat half the bits off the top. In IPv6, roughly speaking, it does.

      See, it was by asking the question 'how many computers can there possibly be?' that we got the fiasco that is IPv4 addressing. The questions we need to ask, are (a) by what processes can address be allocated, and (b) what things are potentially addressable.

      Fortunately these questions were asked this time, and 128 bit IPv6 addresses result. I do worry (see above) that it might not be enough—not because we are going to manufacture 2^128 physical objects (though 2^64 network addressable logical objects will happen in my lifetime), but because addresses, in reality, are not serial numbers but little packed data structures.

      One final thing I should point out: when I say this, people tend to respond, well, but you're assuming that everywhere is like America. No, I'm not. America is 'developed'—it's given up on deploying infrastructure, its corporate interests are allergic to new ways of doing things. The developing world is still adopting new ideas. The 'developing' world will be studded with cities that make Shanghai and Seoul look old-fashioned within the lifetime of IPv6, and there's some reasonable probability that they will have network addressable buttons, disposable paper T-shirts, balloons (fingers crossed for these being recyclable...). They likely won't be in America, though, because America has already been told what can't be done.

    110. Re:screw ipv4 by Cramer · · Score: 1

      yes, applications/protocols that make bad assumptions about network setup have issues. (i.e. those things that think they are smarter than the network stack to know what their external address is. Those protocols had issues before NAT was ever thought of. If you bind INADDR_ANY, you don't know what your address is. No protocol designed in the last decade should ever make any assumption about what addresses the other end sees. yes, I'm bashing SIP.)

      FTP in passive mode works perfectly without a protocol helper. The original standard for FTP (port mode) was written about 30 years. The internet is very different today. You cannot trust the client to tell you were to connect; it's too easily abused, and in the era of NAT the address of the socket you've setup for the connection isn't necessarily what the far end sees.

      And in todays networks with firewalls (which everyone should be using), you need specific protocol handlers anyway so secondary communications channels we be allowed through.

      People have been preaching IPv6 (IPng) for over a decade. Just like they've been screaming the sky is falling w.r.t. IPv4 address exhaustion pretty much since the first /8 was assigned.

    111. Re:screw ipv4 by Ant+P. · · Score: 1

      I don't see how this is even possible: you can't assign a unique 32 bit number to each 128 bit number.

      Just assign a unique 16 bit number to each 128 bit number. You know, using the same method your IPv4 router's been doing for years to make 32 bit numbers accessible to your (effectively) 8 bit internal IP.

    112. Re:screw ipv4 by BitterOak · · Score: 1

      WTF are you talking about? Look up the RFCs for IPv4 and you'll see "DARPA" written all over them. You believe that's the name of a private individual??

      I'm not saying that there was no government involvement in developing these protocols, just that there was no regulatory oversight. Sure, many (but not all) of the individuals who've written RFCs were government employees or government funded at the time, but that hasn't stopped non-governmental entities from submitting RFCs, and essentially the marketplace has decided which have caught on and which haven't. If a regulatory agency such as the FCC started mandating which RFCs to follow and which are not to be followed, that would represent a huge change in direction for the Internet.

      --
      If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
    113. Re:screw ipv4 by BitZtream · · Score: 1

      No, the article is just as confused as you are. They are refering to PAT as NAT-PT. The article is also clearly not written by someone who understands IPv6 at the core and why my original statement stands. There isn't a need for these services, just stupid people who keep trying to come up with ways to solve problems that don't actually exist so things appear to 'work the same as before'. They aren't going to work the same as before, nor do they need to, and the way the will work in the future was defined years ago. Its just a bunch of people saying 'I want to keep using PAT with IPv6 from my IPv4 network and I have a really good reason.' Except no one actually has a good reason, unless you count 'because I said so'

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    114. Re:screw ipv4 by totally+bogus+dude · · Score: 1

      Reading comprehension problems? This thread is suggesting that all you have to do is update your router to support IPv6 and all your problems are over. You can keep using IPv4 internally and the router will do everything needed to talk to the IPv6 world and everything will be peachy.

      The post you're responding to is suggesting that maybe, just maybe, that idea is complete bollocks for pretty obvious reasons. Your condescending post seems to be about something else entirely.

    115. Re:screw ipv4 by Anonymous Coward · · Score: 0

      you all should be using miles, feet, inches, Fahrenheit, and gallons. Please upgrade your silly metric system.

      For the love of god NOOOOOOO!!! KhaaaaaaAAN!!!

      *weeps like a little girl*

    116. Re:screw ipv4 by Cajal · · Score: 1

      And so which standard is it that allows you to translate between IPv6 and IPv4? You keep saying that it exists, but you've never pointed to an RFC.

    117. Re:screw ipv4 by ikeman32 · · Score: 1

      "The good grammar tells you he's a fake, but what kind? Obviously, a fake scam artist. In other words, a fake fake."

      "But if he's not a real fake, what is he really? The only possibility that makes sense is that he really is the premier of Swaziland. I suggest you send him the information he requested. Or better yet, send it to me, and I'll handle the transaction for you."

      No problem, I will have everything ready on the second Tuesday of next week.

  2. Credit crunch by Harmonious+Botch · · Score: 5, Insightful

    This is curiously similar to the current credit crunch. When a fix is not guaranteed to happen soon, people start hoarding.

    1. Re:Credit crunch by toleraen · · Score: 4, Interesting

      I was going to use the oil analogy. It's going to run out eventually, so why not switch to something better now before we run out?

    2. Re:Credit crunch by Samantha+Wright · · Score: 4, Interesting

      That's a little silly. These allocations were made in the 70s and 80s, before the Internet really existed outside of the US. At the time, the recipients of the addresses were those who were most likely to use them. No hoarding is going on.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    3. Re:Credit crunch by Harmonious+Botch · · Score: 1, Interesting

      That's a little silly. These allocations were made in the 70s and 80s, before the Internet really existed outside of the US. At the time, the recipients of the addresses were those who were most likely to use them. No hoarding is going on.

      Really? There are potential buyers - people who would pay for the IPs. But the owners are not selling - at any price. That is hoarding.

    4. Re:Credit crunch by Bill,+Shooter+of+Bul · · Score: 1

      Because everyone will have to buy new hardware that will properly handle ip6. Those that might be volume buyers of Ip6 enabled hardware are the same ones that have excess ip 4 addresses. So, they have little motivation to switch, and the demand for Ip6 hardware remains low while price remains high.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    5. Re:Credit crunch by gbjbaanb · · Score: 1

      because, to continue your oil analogy, no-one will change until the cost of this increasingly-scare resource rises to a point where its cheaper to migrate to IPv6.

      So - when your ISP says, you can have 1 shared IP, but if you want a static one it'll cost you $10 a month.. you'll start thinking about how you can get IPv6 and moving to a competitor who provides it, assuming you can get a home router that supports it... and then other ISPs will see the migration and start offering IPv6 as features, and then we'll be there.

      It'll just take those market forces, so if you want to help things along, grab as many static IPs as you can.

    6. Re:Credit crunch by Chaos+Incarnate · · Score: 4, Insightful

      That is hoarding.

      No, that's life outside a police state.

      --
      Benford's Corollary to Clarke's Law: "Any technology distinguishable from magic is insufficiently advanced."
    7. Re:Credit crunch by Klaus_1250 · · Score: 1

      [quote]Because everyone will have to buy new hardware that will properly handle ip6[/quote] For the bulk of consumer hardware, ipv6 is a software thing. Updating software, installing a new driver and updating firmware is all it takes.

      --
      It only takes one man to change the Wisdom of the Crowd to Tyranny of the Masses.
    8. Re:Credit crunch by Anonymous Coward · · Score: 0

      Car analogies only please.

    9. Re:Credit crunch by Anonymous Coward · · Score: 0

      no, it's still hoarding. It's just that outside of a police state there's no reason why they shouldn't hoard if they want to.

    10. Re:Credit crunch by Anonymous Coward · · Score: 0

      That's a little silly. These allocations were made in the 70s and 80s, before the Internet really existed outside of the US. At the time, the recipients of the addresses were those who were most likely to use them.

      They may have been most likely to use them AT THE TIME, but that is no longer the case. More importantly, THEY STILL AREN'T USING THEM.

      No hoarding is going on.

      Bullshit. I have 3 class C netblocks. Even if they weren't half-used, I wouldn't sell them unless it was for a large amount of money.

    11. Re:Credit crunch by Anonymous Coward · · Score: 0

      Really? There are potential buyers - people who would pay for the IPs. But the owners are not selling - at any price. That is hoarding.

      No, that is *owning*

    12. Re:Credit crunch by Big+Nothing · · Score: 1

      Your car analogy seems to be flawed.

      --
      SIG: TAKE OFF EVERY 'CAPTAIN'!!
    13. Re:Credit crunch by Minwee · · Score: 1

      There are potential buyers - people who would pay for the IPs. But the owners are not selling - at any price. That is hoarding.

      That's an interesting way to define it.

      How about this? You have two kidneys. People wish to pay for them, but you are not selling at any price. Is that hoarding?

    14. Re:Credit crunch by Mesa+MIke · · Score: 1

      You're assuming that the ISP will then give you a static IPv6.
      Well, maybe they will -- for $10 / month.

    15. Re:Credit crunch by PitaBred · · Score: 1

      Not quite. IP space is "common" space, just like the roads, parks and so on. Doing nothing with the chunk of public, limited resources you reserved for yourself most certainly IS hoarding. If there were a way to make more IP addresses, you would be correct.

    16. Re:Credit crunch by Just+Some+Guy · · Score: 1

      IP space is "common" space, just like the roads, parks and so on.

      IP space is "common" space, just like my living room.

      --
      Dewey, what part of this looks like authorities should be involved?
    17. Re:Credit crunch by Lord+Jester · · Score: 1

      Not necessarily.

      In some cases, they are hoarded. There are many large scale organizations that have switched to NAT based networks. As such, there is little (or no) reason to keep more than a very small subset. Even a single class C block. However, they choose not to relinquish these addresses for any reason.

      Some may hope to sell them, or more appropriately be paid a ransom for them as they do not truely own them. While others seem to do it out of a force of habit. If they relinquish them and then later need them, some fear they will not be able to reattain the same contiguous addresses.

      If we were to truly reallocate and more efficiently use the IPv4 address space, it would last us longer, but we do need to invest in a better solution. IPv6 has more address space and that is what we ultimately need.

    18. Re:Credit crunch by Bill,+Shooter+of+Bul · · Score: 1

      Should have been more specific. I meant non-consumer hardware, Switches routers and the like. A lot of them don't have the resources to handle their current load under the more intensive ipv6, even if you can get a software upgrade from the hardware vendor.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    19. Re:Credit crunch by Anonymous Coward · · Score: 0

      Not necessarily. If you scanned my home IP address, there would be no response on any port and it would look like an unused address. Maybe the ISPs for these addresses are "stealthing" the ports to prevent worms/trojans/etc.

    20. Re:Credit crunch by Zadaz · · Score: 1

      Why? Because, it's cheaper and more readily available than the alternative, and there's a large infrastructure to support it. The correct question is "why switch?"

      Go on and hoard the IPv4's. Buy them all up and stick them in your safe deposit vault where no one can get to them. It'll help us move to IPv6 that much faster.

      (Or to use hippy analogy, it's like carbon offsets.)

    21. Re:Credit crunch by azgard · · Score: 1

      No, because you also use them. Those people who have lots of IP addresses are not using them.

    22. Re:Credit crunch by Anonymous Coward · · Score: 0

      Car analogies only please.

      Ok. It's like owning a car you know is going to completely die soon. Why not invest in a new car now that will last you long into the future and save you some major headaches?

    23. Re:Credit crunch by Kadin2048 · · Score: 2, Interesting

      Actually this is exactly why nobody wants to change.

      Or rather, everyone knows they'll have to change eventually, but nobody wants to be first. Optimally, everyone wants to be last. There's no benefit to being an early adopter -- you spend a lot of money figuring out how to do everything right, upgrading stuff, maybe rewriting software; the Johnny-come-latelies just ride in on the coattails of everyone else. They hire a couple of consultants to do the worst of the work, who've gotten their experience on the early adopters, buy COTS software, cheap hardware, etc.

      Right now we're in a sort of 'Mexican standoff' where nobody wants to move first, because there's a risk by using up all that capital being first, your competitors will sit, and watch, and learn, and then leapfrog you when they get around to doing it later.

      (Similarly, both the U.S. and China need to move away from oil, but neither want to go first; both would prefer to let the other guy go first, and take the big economic hit from switching over to something else, and burn out the rest of the fossil fuels themselves, and then buy the alternative technology once it's cheap and being mass-produced, with all the R&D subsidized by the other guy.)

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    24. Re:Credit crunch by PitaBred · · Score: 1

      Just because you say it doesn't make it so. IP space is a limited resource used by everyone. Or do you not like your municipal water, sewer and road system?

      You would cry foul if a company "reserved" the road in front of your house (didn't have to pay for it, though), and didn't do anything with it, but made damn sure you couldn't use it. Why is IP space different?

    25. Re:Credit crunch by Just+Some+Guy · · Score: 1

      Real estate is finite, yet owned. Some of us paid (and continue to pay) quite a bit of money for ARIN assignments. How's that different?

      --
      Dewey, what part of this looks like authorities should be involved?
    26. Re:Credit crunch by Cajal · · Score: 1

      They aren't selling because the current RIR policies prohibit them from doing so. ARIN, APNIC and RIPE NCC are actively developing policies to allow address markets to form. There was an excellent video on this at the last APNIC meeting: http://www.apnic.net/meetings/26/program/ipv4/

    27. Re:Credit crunch by TheRaven64 · · Score: 1

      Everybody will start switching once sites they need to access go v6-only. If you could get, say, bbc.co.uk, to go v6 then you'd give people a big incentive to upgrade.

      --
      I am TheRaven on Soylent News
    28. Re:Credit crunch by smoker2 · · Score: 1

      Crap.
      No-one owns an IP, they are assigned. If you want a fixed IP, you pay to have it assigned to you, you don't buy it. If you don't buy it, you don't OWN it. So give them back.

    29. Re:Credit crunch by ckedge · · Score: 1

      > Some of us paid (and continue to pay) quite a bit of money for ARIN assignments.

      And you're using all of them?
      You have a reasonable expectation of using them within 10 years?
      Because, you know, we can give you a refund.

      Otherwise we're going to squat your ass down in front of a tribunal, just like the ones that decide whether a domain squatters is a domain squatter, or someone who's using said public resource in a valid just manner.

      Funny thing about the internet, it eventually treats things like you* as damage and routes around them. Your "ARIN assignments" are going to be worthless if everyone else's routes for "YOUR" ip addresses don't route to or from you.

      What!? What my network does with packets crossing MY NETWORK is none of your f'ing business.

      Funny how associative organizations work :)

      (*) (censorship is just one example)

    30. Re:Credit crunch by ericlondaits · · Score: 1

      I really don't know much about IPv6, but as I heard it should mean the end to NAT schemes... so, I'm worried by the possibility that I'll need an IP address asigned by my ISP for every device. Is that so? Because I then can easily see the "10 IPv6 addresses", "20 IPv6 addresses", and "100 IPv6 addresses" plans as the ultimate money making scheme.

      --
      As a Slashdot discussion grows longer, the probability of an analogy involving cars approaches one.
    31. Re:Credit crunch by ckedge · · Score: 1

      Hmm, actually, I should explicitly address your specific comparison.

      We need to build a superhighway here.

      It's currently your land. ...

      Can you guess what comes next?

    32. Re:Credit crunch by Just+Some+Guy · · Score: 1

      So, what "superhighway" runs through our netblock? Why are you advocating the hostile takeover of our address space - which you can't even verify is unused - and redistributing it to other commercial entities?

      --
      Dewey, what part of this looks like authorities should be involved?
    33. Re:Credit crunch by Fred_A · · Score: 1

      That's a little silly. These allocations were made in the 70s and 80s, before the Internet really existed outside of the US. At the time, the recipients of the addresses were those who were most likely to use them. No hoarding is going on.

      While the fact that A classes were given away like balloons at one point is now a bit of a problem, it didn't stop there.
      Even later, back when, here in Paris, I sed to regularly ask for addresses. There used to e that form that you sent upriver in the network "attn" the IANA (or whoever it was at the time) where all you had to say was "I have a few machines to hook up, there might be more later on" and you'd basically get as many class C nets as you requested (they had stopped handing out As and Bs by then). I know we (and most other orgs I knew of) only requested what we actually used. But I wouldn't be surprised if there had been a bit of abuse at the time.

      The young' uns might also want to remember that for quite some time, we were stuck with HTTP 1.0 where there was no "host" request. A server serving Web pages often had tens of addresses. One per hosted site.

      Of course, back then, it wasn't entirely clear how people would access the network, or even if they would want to. So presumably there was no real need to save addresses. Then IPv6 came along, as well as NATs. The latter being IMO the main reason we're still with 32 bit addresses.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    34. Re:Credit crunch by Nevyn · · Score: 1

      So - when your ISP says, you can have 1 shared IP, but if you want a static one it'll cost you $10 a month.. you'll start

      hahaha, $10 a month I laugh at you! I pay abou $80 a month, so I can get a /29 ... I used to pay that to get a /26 a few years ago (although at much lower speeds). I'd happily move to all IPv6 with a shared IPv4 to get rid of that cost. But noone is offering it, my ISP has had zero requests for it (apart from me) and it would cost them more to offer IPv6 than it does to offer IPv4.

      Realistically I hold out no hope at all that we won't hit peak IPv4, and have to suffer through the chaos for a few years while everyone scrambles to move. But then it'll be a lot less painful than peak Oil, and I see only slimmers of hope that'll go well.

      --
      ustr: Managed string API with ave. 44% overhead over strdup(), for 0-20B
    35. Re:Credit crunch by petermgreen · · Score: 1

      Everybody will start switching once sites they need to access go v6-only.
      But the site operators are by and large trying to get as many visitors as possible. So they are unlikely to go V6 only for a VERY long time.

      Websites will stay hosted on IPV4 even if it means forcing end users behind ISP level NAT to recover thier IPs.

      If I was an ISP right now my aim would be to get as many IPV4 IPs as I possiblly could and have contingency plans in place to force end users behind nat and recover thier IPs when they did run out.

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

      SOME real-estate is owned. The road in front of your house, as per my example, is NOT owned, as it's a public resource.

      Really, get your head around it. And as for your later comments as to whether or not you're using them, if you can prove you're using them, there's not a problem. Resources are meant to be utilized, otherwise they wouldn't be called resources. But if you AREN'T using them, they should be redistributed to someone who will, simply because of their limited nature.

      Eminent domain exists for a reason... sometimes there are douchebags like you who will buy up land just to fuck things up for everyone else.

    37. Re:Credit crunch by TheRaven64 · · Score: 1

      By and large is the operative term. If the DoD sites went 6-only then anyone tendering a bid for a DoD contract would need a working 6 stack. The same with other government sites.

      --
      I am TheRaven on Soylent News
    38. Re:Credit crunch by Just+Some+Guy · · Score: 1

      First off, son, I don't work there anymore, and I'm not even sure if they're still in business (or if they still own the assignments). You really need to quit making your disagreements into personal issues.

      Second, please explain to me why IP space is more of a "public good" than real estate? Some parts of the world are horrifically overcrowded but they use the real estate market to distribute limited resources. How is your way of confiscation and redistribution any more fair than what you (incorrectly) accused me of?

      --
      Dewey, what part of this looks like authorities should be involved?
    39. Re:Credit crunch by petermgreen · · Score: 1

      A few people may get bullied into V6 by thier customers or supplies but I don't think it will be a significant affect on the net as a whole.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    40. Re:Credit crunch by hob42 · · Score: 2, Insightful

      Nah, you have two, but can get by with one. Just let us buy the other, and if you really do need it in the future, you can always buy another one.

      (That sounded funnier in my head.)

    41. Re:Credit crunch by MadnessASAP · · Score: 1

      Unless your a Carrier and therefore part of the Common Carrier agreements. At which point it does become everyones buisness what you do with packets crossing your network.

      --
      I may agree with what you say, but I will defend to the death your right to face the consequences of saying it.
    42. Re:Credit crunch by gbjbaanb · · Score: 1

      no, instead of being allocated an IP address, they will give you a block (a /64 IIRC) which will give you enough IPs to address every electronic item you'll ever own.

      Its more likely they'll set it up so your devices auto-configure using your ISPs block.

    43. Re:Credit crunch by MadnessASAP · · Score: 1

      They used to be assigned, now they're bought. Back in the day when IPv4 came out they were effectively worthless since there were so damn many of them and all you had to do was ask nicely and you could get a whole /16 to yourself. Large coporations were handed out /8 like they were candy. Now of course IPv4 isn't nearly as big as it used to be and we seem to be running out of them.

      --
      I may agree with what you say, but I will defend to the death your right to face the consequences of saying it.
    44. Re:Credit crunch by PitaBred · · Score: 1

      Your statement implied that you DID still work there and continued to pay "quite a bit of money", so I responded in kind. Don't get mad at me for your incapacity to write clearly.

      And even though real-estate is "owned" by someone, it actually is a concession from the government. You don't own it if you don't pay your tithe to the government, and it can be taken from you if your ownership of it gets in the way of the public good. Or someone can make an argument that it does. And either way, not all real estate is privately owned, either. I explained that in my previous post, about parks and roads and such.

      Yes, some places ARE horrifically crowded. But imagine if someone owned an apartment building in, say, Manhattan. They would be stupid to not rent it out... they'd have astronomical taxes to pay and no money coming in from it. The same forces don't affect the IP space, since it's a "virtual" good, and even though you pay a lot for your ARIN allocations, a /8 costs just as much as a /14, and that's only $18K a year at max. There's no incentive to change or relinquish addresses if you're a big enough company (which, coincidentally, are the ones who own the majority of the "dark" addresses.) After any employer insurance contributions and so on, I'd doubt that $18K is even a minimum wage worker's salary, so it would scarcely affect many medium companies or some small ones. So no, a "real estate" style market will NOT work.

      Basically, the only solution to this (and it's only short-term, as more and more machines come online) is to redistribute the IP allocation, by mandate if necessary. Confiscation could quite easily be done under an "eminent domain" type clause, where you wouldn't be out money, you'd just be out of resources you weren't using anyway, and everyone would be better off by having more IP's available in general.

    45. Re:Credit crunch by TClevenger · · Score: 1

      I doubt that Xerox, Apple, IBM, HP, MIT, CSC, GE, Halliburton and Ford Motor Company paid for those Class A blocks they received back then and are still holding on to. A former co-worker of mine has his own Class C, which he didn't pay anything for and doesn't pay anything to maintain, but certainly won't give it back.

    46. Re:Credit crunch by Anonymous Coward · · Score: 0

      I was going to use the oil analogy. It's going to run out eventually, so why not switch to something better now before we run out?

      Same reason you don't change away from oil right now. Nothing else is as economical and reliable.

    47. Re:Credit crunch by POTSandPANS · · Score: 1

      I think most carrier grade routers should support ip6 already, or at least have a firmware update that will. Yes, IP6 addresses are 4 times longer but IP6 would allow us to use much better summary routes. The routing table might end up being not much bigger than it is now.

    48. Re:Credit crunch by Anonymous Coward · · Score: 0

      Why do you hate the Horde so much?

    49. Re:Credit crunch by Adam+Hazzlebank · · Score: 1

      Pah, the Internet is just a fad it'll never last.

  3. Give back class As by Neil+Watson · · Score: 5, Insightful

    Perhaps some of the institutions that still have class A networks reserved from the old days, with no reasonable need for them, should give them back.

    1. Re:Give back class As by Anonymous Coward · · Score: 5, Informative

      Yup, I work for one of them, GE - the entire "3.x" class-A network, 16million addresses - most of our internal network is those 3.x addresses, behind firewalls so basically useless - and even better, I pinged a few external GE sites I know of, and none of them even use 3.x addresses!!

      maybe 500K employee's & contractors, even add 500K more for servers and unallocated IP's in the ranges, that's still 15*million* unused. Besides which, we could easily run on 10.x internal networking and NAT/Proxy to outside.

      Don't be in a hurry to get them back though... its not a priority! (haha)

    2. Re:Give back class As by Anonymous Coward · · Score: 0

      Many companies also have multiple /16 and shorter in active use as isolated intranets, and there's more than a few universities that don't need all of their /16 either (and yes, I've personally seen both).

    3. Re:Give back class As by t0rkm3 · · Score: 4, Insightful

      As a network security guy in a company with 9 Class B's that are used within the company. (1 is Internet facing) The internal usage of public IP address space is justified by one thing, acquisitions. Every time a company is bought up by our company we have to integrate them into our network. We are already using some RFC1918 space at stub networks(plants/refineries) and for VoIP applications. However, the challenge of integrating 25,000 new IP devices with a conflicting address scope per merger is painful and wasteful.

    4. Re:Give back class As by mordred99 · · Score: 3, Interesting

      Hell .. some of the companies have all their stuff on public IPs. Once in particular (I won't say who) I can get to the manufacturing PLCs since they use public IPs on everything. I can shut off their machines if I wanted to. Yes I used to do security for them, but I was let go because I brought up too many things that would cost them money. Their security manager said "If I don't know about it, and something goes wrong, we can pay to fix it then. However it is cheaper to not tell upper management about it, as they will be forced to act and the last thing we need to do is spend money." Yeah .. I left.

    5. Re:Give back class As by Bill+Barth · · Score: 2, Informative

      Isn't this what DHCP is for? I'm a little surprised you have 25k boxes come in via a merger with static addresses.

      --
      Yes...I am a rocket scientist.
    6. Re:Give back class As by WMIF · · Score: 1

      The ISP's aren't helping much either. At my old company, I was looking to provide some ingress redundancy in the event of failure to the main pipe. We only had a /28 block of addresses so our ISP was not interested in BGP route exchanges. Our sales engineer suggested that we move to a /24 block for no extra cost, which would then allow what I wanted to do. I thought about it, but decided not to because I wasn't even using all of my /28.

    7. Re:Give back class As by rgviza · · Score: 1

      hehe I've walked GE's whois records. Their IP space is MASSIVE.

      -Viz

      --
      Don't kid yourself. It's the size of the regexp AND how you use it that counts.
    8. Re:Give back class As by eht · · Score: 1

      I'm working at CBS (not for them) and it is the same story, they allocate their block internally and firewall the heck out of it. They also use 10.x.x.x addresses internally.

    9. Re:Give back class As by Anonymous Coward · · Score: 0

      Even on the small biz side. Technically we are large, because we have over 1000 trucks drivers, but the office staff is small. In fact my office, a satellite, has roughly 24 computers in use. We have that I know of, about 15 to 20 IP's assigend to our T-1 connection. We are using 3. The rest is on a 192.168 behind NAT/Firewall.
      That's 12 to 17 IPs we could easily give back.

      The IP crunch was something I really haven't understood because of NAT and private addresses.

    10. Re:Give back class As by Spazztastic · · Score: 1

      I'd assume they use static addressing internally via a DHCP server that assigns the addresses based off their MAC address. This would be an added security feature to keep your average user from plugging in their laptop.

      Of course, your advanced user would just learn how to spoof a MAC address.

      --
      Posts not to be taken literally. Almost everything is sarcasm.
    11. Re:Give back class As by Spazztastic · · Score: 1

      Everything on public IPs?

      According to the IANA*, 19.0.0.0/8 is allocated to Ford. If my calculations are correct, which they rarely are, Ford has a total of 16,777,214 available addresses. This also applied to anybody else who uses a Class A /8 subnet. I don't see any reason for a company to need that many, of course I'm just using Ford as an example, there's many others including Halliburton, AT&T, Level 3, Xerox, etc.

      * http://www.iana.org/assignments/ipv4-address-space/

      --
      Posts not to be taken literally. Almost everything is sarcasm.
    12. Re:Give back class As by morgan_greywolf · · Score: 1

      What if I guess it correctly? What if I happened to have worked at the same place? ;) Okay, just tell me, do they have a /8 that begins with 19? ;)

    13. Re:Give back class As by nine-times · · Score: 1

      most of our internal network is those 3.x addresses, behind firewalls so basically useless

      Out of curiosity, can anyone give any reason for why you would want to do that? I can't think of anything off the top of my head. Even if there's no difference, I think I'd probably prefer to give people non-routable addresses, but maybe that's neurotic on my part.

    14. Re:Give back class As by TeraBill · · Score: 1

      This reminds me of a story from Network World a few years ago (maybe 9 or 10) which talked about how Stanford University had a Class A and several class B networks and re-addressed themselves into the B's and gave the A back. In the same article the network administrator for MIT (I believe it was) said that they didn't see there was being an IP shortage and was not considering giving any of the class A network that they have back to ARIN. I worked for a place at one point that had three Class B networks and some class C networks and we could have very easily existed in on class B since we were using under 20,000 IPs, but nobody was interested in trying to rework things to give any back. At the end of the day, I think more emphasis should have been given to migration planning for IPV6 and we wouldn't even be having this discussion.

    15. Re:Give back class As by Nimey · · Score: 1

      No reason to use static IPs with DHCP on a MAC whitelist. Dynamic IPs work just fine with that system.

      To prevent a random computer from being plugged into a network jack, you could implement 802.1x authentication. No worries about MAC spoofing.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    16. Re:Give back class As by bendodge · · Score: 1

      Big networks don't like DHCP. I makes managing the network much harder, as everything is floating around. Static IPs also make for better security.

      --
      The government can't save you.
    17. Re:Give back class As by qwertphobia · · Score: 2, Insightful

      Core routers don't get DHCP addresses. Servers don't get DHCP addresses. Infrastructure, for the most part, should not be dynamic, and should never rely on other infrastructure unnecessary.

      It can take years to transition between addressing policies.

      --
      Never ask for directions from a two-headed tourist! -Big Bird
    18. Re:Give back class As by mini+me · · Score: 1

      I'd rather give them a routable address if they were freely available. Let the firewall, not the router, do it's job.

    19. Re:Give back class As by Anonymous Coward · · Score: 0

      HP owns the entire 15.x and 16.x Class-A net. Seems like thats a bit more than they need ...

    20. Re:Give back class As by nine-times · · Score: 1

      That's fine, but why? If you're not going to be routing anything in to those machines anyway, what's the benefit?

      If there is a difference, I'd generally rather not let anyone get to the point of expecting a routable IP for any particular machine, except for servers where it's actually necessary. Then you should be able to reassign IPs arbitrarily and just update your NAT for your couple servers without anything breaking. But then, I also prefer to use DHCP and rely on name resolution, only making exceptions where necessary, so maybe it's just an issue of what problems you want to deal with?

    21. Re:Give back class As by Just+Some+Guy · · Score: 1

      As a network security guy in a company with 9 Class B's that are used within the company.

      You can get blocks that small now? When I worked at an ISP / web host, I was told to get an assignment from ARIN. At that time, the smallest block they'd hand out was /19 (32 /24s).

      --
      Dewey, what part of this looks like authorities should be involved?
    22. Re:Give back class As by Anonymous Coward · · Score: 0

      Same deal here. My company, Nortel, has the entire 47.X Class-A range. And like GE apparently, only a handful of addresses are outward facing, with internal assignments (ie my workstation) hidden behind firewalls. I also tried your ping test, and yep, our main web servers are not even using this range.

      It's a complete waste. Given Nortel's financial situation, this would be a great time to auction these off and get them back to serving a useful purpose.

      (Note: The 47 network is listed in older documents as Bell-Northern Research (BNR) - this is the old R&D unit for Nortel, which unfortunately, was completed absorbed several years back)

    23. Re:Give back class As by Sique · · Score: 4, Interesting

      NAT is a hassle, when it comes to more complex protocols than simple TCP. I've worked at a customer site which had a slightly... lets put it like this... unorthodox allocation of internal IP addresses. They just gave every site a 10.X.0.0/16, and then they had more than 256 sites (it's a large retailer, that's why). So they started expanding (yes I know, shame on them) into the 9.0.0.0/8 and 8.0.0.0/8 space.

      When they bought a company in another country, the sysadmins there absolutely refused to route those nets into the VPN (right they were). So now the customer starts heavily to NAT, so the new company never sees any internal 9.0.0.0/8 and 8.0.0.0/8 addresses.

      And now lots of things break. Videoconferencing and VoIP are among the worst offenders, but some complex logistics software they use is playing silly buggers too. And with more than 256 sites it's just not feasible to start readdressing all the IPs. They just don't have the people to do it, and they don't have the time to do it (it has to happen all at once, otherwise just more applications break during the transition period), and they don't have the money to hire enough external people to do it.

      It's a lesson why violating RFC1918 never was a good idea, but it is also a lesson that NAT gets you only so far.

      --
      .sig: Sique *sigh*
    24. Re:Give back class As by mordred99 · · Score: 1

      Nope .. but another manufacturing firm (thus the PLCs).

    25. Re:Give back class As by berashith · · Score: 1

      very true.

      I worked at a managed colocation facility that would purchase other data centers full of managed and colocated servers. The subnetting in both locations would be in the 10.x.x.x range, and it would take years to sort out how to integrate all of the new customers.

    26. Re:Give back class As by Anonymous Coward · · Score: 0

      "Don't be in a hurry to get them back though... its not a priority! (haha)"

      Yeah. I work for another one of those enterprises, i.e. the one that has 17/8. You want those addresses back? Go ahead. Try to get IANA to reclaim them. I dare you.

      Otherwise, make us an offer. I'm guessing the bidding would have to start somewhere upwards of US$100M before corporate officers here would even notice. Failing that, the rest of you losers can all eat RFC 1918 addresses and shut the hell up.

    27. Re:Give back class As by Kadin2048 · · Score: 1

      Because then you can have firewalls that are actually just firewalls, and don't perform NAT. There isn't necessarily anything that you can't do with NAT, but IMO it's much more elegant to not have it in there, if you don't need it.

      And if you have a Class A block, you don't need it.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    28. Re:Give back class As by Anonymous Coward · · Score: 0

      Umm... Class B is /16. You're thinking of Class C.

    29. Re:Give back class As by Just+Some+Guy · · Score: 1

      D'oh! I'll be running along now.

      --
      Dewey, what part of this looks like authorities should be involved?
    30. Re:Give back class As by petermgreen · · Score: 1

      NAT requires more CPU power than just firewalling. It also makes it very hard to trace the source machine when your ISP sends you a complaint. Finally some protocols just plain don't get on with NAT.

      Also there are mergers. Generally when companies merge they want to allow cross connections between thier networks as they merge services. If the two networks have IP conflicts with each other that can be a big problem.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    31. Re:Give back class As by houghi · · Score: 1

      So basicay we do not have enough adresses, so you have an easier job.

      --
      Don't fight for your country, if your country does not fight for you.
    32. Re:Give back class As by afabbro · · Score: 1

      Umm... Class B is /16. You're thinking of Class C.

      Yeah, it's the opposite of bra sizes. Very confusing.

      They say that "more than a Class B-ful is wasted..."

      --
      Advice: on VPS providers
    33. Re:Give back class As by Anonymous Coward · · Score: 0

      However, the challenge of integrating 25,000 new IP devices with a conflicting address scope per merger is painful and wasteful.

      Painful, yes, which should have been considered as part of the cost of merging ahead of time.

      Wasteful, no- or at least only wasteful to the company in question. To everyone else, not wasteful.

      Having said that, I estimate about 99% (yes it came from my ass, but my ass is making an educated estimate) of small businesses (home offices, retail stores, etc.) who use static IP's could get by with a simple stickey/persistant IP by DHCP because they aren't even announcing routes.
      Most of the non-ISP type companies I see like to simply add new IP's instead of properly setting up their network, because it is often quicker and simpler.
      At the ISP I work for, we recently turned up a hotel with a /21 bloc because they demanded a static for every room.

      Most of the wasted IP's are due to network admins & IT people who simply don't know what the fuck they are doing.

    34. Re:Give back class As by QuietLagoon · · Score: 1
      Yup, I work for one of them, GE - the entire "3.x" class-A network, 16million addresses
      .

      HP has two class A's, one from way back when, and one when they acquired Compaq who previously got DEC's class A.

      HP can't need that many IP4 addresses.

    35. Re:Give back class As by j+h+woodyatt · · Score: 1

      A similar issue arises with providers who place their subscribers behind twice-NAT on addresses they aren't stealing from somebody else. The free Wi-Fi service on the commuter shuttles provided by my employer is operated by an ISP that does this. It mostly works, except when it falls over and dies.

      Why would you do this? So that you can conserve your own IP address space without having to worry about address realm conflicts between your subscribers and the services you are providing to them. Why does this suck? As you know, Bob, it's because applications quite naturally assume that any IPv4 address outside the RFC 1918 ranges are global scope. (That's because— you know— they are.)

      So these applications assume they can stop attempting their NAT traversal strategy because they think they've fixed the public address properly when they really haven't.

      I do so dearly love people who refuse to learn the lessons of RFC 3424.

      --
      jhw
    36. Re:Give back class As by t0rkm3 · · Score: 1

      Yeah... My selfish ass is the one that doesn't want a multi-billion dollar company to go through the pain of transitioning IP addresses and two-way NATs and all that jazz.

      There's this funny thing called money. You go ahead and tell some that X million will be lost this year so we can donate address space back to the community. In addition, X million will be a recurring cost after every acquisition due to that donation. After they fire you and your children unto fifteen generations... and anyone that dares to utter a word that rhymes with your name..

    37. Re:Give back class As by t0rkm3 · · Score: 1

      Not my job... but I can empathize with the network team. I'm security dude... firewalls, VPNs, IDS/IPS, and NAC.

      Routing is soooo boring.

    38. Re:Give back class As by Anonymous Coward · · Score: 0

      Poppycock. Granted I would never use DHCP for servers and 99.99% of network devices, but for clients it's 100% necessary.

      Also, if you think static IPs make for better security, you're doing it wrong.

    39. Re:Give back class As by totally+bogus+dude · · Score: 1

      Yep, that's a problem. We'll be in a similar situation shortly. Funnily enough, we just moved to a new datacentre and asked the new one if they could give us around 64 IP addresses (which would be more than enough for the foreseeable future). We ended up being given 3 class Cs that they had just lying around. So now one of these ranges has 3 IPs in use for corporate services, and another has maybe 14 in use for websites we're hosting.

  4. And for just 10 dollars a month... by lobiusmoop · · Score: 4, Funny

    you can give one of these poor unwanted IP's a home.

    --
    "I bless every day that I continue to live, for every day is pure profit."
    1. Re:And for just 10 dollars a month... by The+Moof · · Score: 1

      Funny you mention that. I asked AT&T about getting a static IP address.

      They told me only business class accounts can get static addresses.

    2. Re:And for just 10 dollars a month... by NeverVotedBush · · Score: 3, Funny

      Do I get a picture of it and a thank-you letter?

    3. Re:And for just 10 dollars a month... by Bryansix · · Score: 1

      So get business class. It's not like they check to see if you are a legitimate company or anything. Any bum on the street could sign up for a business class account. I should know.

    4. Re:And for just 10 dollars a month... by pcgabe · · Score: 1

      Just 10 dollars a month? Wow, who is your ISP?

      --
      Don't put advice in your sig.
    5. Re:And for just 10 dollars a month... by Anonymous Coward · · Score: 0

      Sure, but the thank you is a letter for Viagra and the picture is tubgirl.

    6. Re:And for just 10 dollars a month... by Anonymous Coward · · Score: 0

      that may be AT&T's policy, but its definately not like that for all ISP's. My own, Eclipse Internet (UK), has free static ip addresses - one is simply a toggle on the online control panel, you can get two by filling in a form and more can be provisioned if you have a genuine need for them.

  5. Leftovers from before NAT? by LeotheQuick · · Score: 2, Interesting

    Maybe these addresses are simply leftovers from before people started to make wide use of NAT, which cut down a whole lot on the # of addresses in circulation

    1. Re:Leftovers from before NAT? by Anonymous Coward · · Score: 0

      No, these are addresses assigned to the few companies who registered addresses in the early days of the internet. Who'd imagine every hot dog stand would want an IP in those days.

      Even without NAT they could assign an IP to every router, server, desktop and coffee machine they have and still not use even 10% of their address space. They were stuck-up greedy bastards.

      Look I've got a Class A! Mine's bigger than yours!

  6. Millions of Internet Addresses Are Lying Vacant by mcgrew · · Score: 1

    Sounds like Detroit or East Saint Louis.

  7. Why bother? by Timothy+Brownawell · · Score: 4, Insightful

    Would giving them back do anything other than encourage network providers to procrastinate on IPv6 for another couple years?

    1. Re:Why bother? by watice · · Score: 1

      Isn't that a good thing? I imagine there are going to be serious security issues when ipv6 is implemented and EVERYTHING is routable. The average joe who has no idea what a firewall is will suffer the most. I definetly think we should stick out with ipv4 a while longer, I don't know about the accuracy of this guy's "icmp probe of the internet" though.

    2. Re:Why bother? by FeepingCreature · · Score: 1

      This is eerily similar to the "bailout" VS "let them fail" discussion.

    3. Re:Why bother? by hedwards · · Score: 2, Insightful

      I doubt that will be a bigger problem than what we currently have. The most likely thing will be for the IPV6 stuff to end at the modem and be IPV4 internally. At least until the security and configuration utilities are easy enough for people to use. I'd be surprised if it weren't opt out in some fashion.

      The big thing is for the ISPs and the rest of the net to be ready for IPV6, the home user is sort of the last part that needs to be changed. And they aren't the ones that are pushing for more time.

    4. Re:Why bother? by Just+Some+Guy · · Score: 2, Insightful

      Isn't that a good thing? I imagine there are going to be serious security issues when ipv6 is implemented and EVERYTHING is routable.

      So we move back the crisis another 18 months. What then? We find some ultra-short-term "fix" to put it off another 18 months for "security issues"? At some point, you've gotta do what you've gotta do.

      --
      Dewey, what part of this looks like authorities should be involved?
    5. Re:Why bother? by kabocox · · Score: 1

      Would giving them back do anything other than encourage network providers to procrastinate on IPv6 for another couple years?

      Maybe, just maybe because there is no real reason pushing for IPv6 if the IPv4 address space were properly managed.

      Heck, how do we know IPv6 won't be all assigned out in 5-10 years? Yes, it's an ungodly massive number of addresses, but that won't stop folks that don't need that many addresses from being assigned address ranges in the trillions or more to start of with. How will IPv6 stop one guy/company/organization from being assigned like 5% of the address space right off? That's the real problem with IPv4. If that were fixed, there most likely wouldn't be a real reason to push for IPv6 for most people for a few more decades.

    6. Re:Why bother? by kasperd · · Score: 1

      Exactly my thought. I think giving back addresses might actually be bad for the internet as a whole. Giving back addresses means more fragmentation in allocations, which means more headaches for routing. Giving back addresses also means, that by the time we really have to convert, there will be more systems to convert, hence the cost will be higher.

      --

      Do you care about the security of your wireless mouse?
  8. IBM, Ford, Microsoft, etc. by Spazztastic · · Score: 3, Insightful

    If the big fortune 100 companies would dump their IP blocks that they don't use more then 10% of the whole sensationalist scare of "OH MY GOD WE'RE RUNNING OUT OF ADDRESSES" wouldn't even be relevant.

    Also, to quote someone from the last three articles related to IPv4 running out, it seems like one of these articles shows up on the main page at least once per month and nothing has changed.

    I don't see why any company, even in the expandable future, would use every address in a /8 subnet... unless they have everything open to the internet, which is moronic.

    --
    Posts not to be taken literally. Almost everything is sarcasm.
    1. Re:IBM, Ford, Microsoft, etc. by Spazztastic · · Score: 1

      Before some grammar Nazi pounces me, I meant "Foreseeable future." Not expandable.

      --
      Posts not to be taken literally. Almost everything is sarcasm.
    2. Re:IBM, Ford, Microsoft, etc. by Anonymous Coward · · Score: 0

      I work for a big company that spends a lot of time buying or selling off bits and pieces of the company. We use our Class B for infrastructure stuff and private 10.x.x.x space for clients. That way if we get bought again, there's no chance of our WAN links, server ip's, etc. overlapping with the company we have to merge with... even though we only have a couple hundred of our registered addresses facing the public internet.

    3. Re:IBM, Ford, Microsoft, etc. by Anonymous Coward · · Score: 0

      [quote]
      which is moronic
      [/quote]

      Yes, it is. It is also all-too-common.

    4. Re:IBM, Ford, Microsoft, etc. by Bryansix · · Score: 1

      The reason these articles appear monthly is so that when IPv4 addresses really do become scarce and the price for them shoots up then the people who saw it coming can say "I told you so. I jumped up and down and screamed about it and you did nothing. NOTHING!".

    5. Re:IBM, Ford, Microsoft, etc. by Dekortage · · Score: 1

      Shucks, I kinda liked "expandable future"...

      --
      $nice = $webHosting + $domainNames + $sslCerts
  9. Wow... by Anonymous Coward · · Score: 0

    ICMP _and_ TCP. That's really high-tech.

  10. Why is anyone surprised? by gstoddart · · Score: 4, Insightful

    People setting up networks aren't trying to use every single address in their space.

    It's far easier to use an entire a.b.c.* as a logical sub-domain than fiddling with netmasks and all that stuff so that a.b.c.1 and a.b.c.200 are on different subnets.

    The amount of work people would need to invest to use every single IP address with no holes would be cumbersome. (I'm not saying you can't do it, it's just tedious.) And, you never know when you're going to need to allocate more machines -- I remember getting blocks of IP addresses for static machines in case I needed another machine in the future.

    Now, why most people aren't using 10.*.*.* as their internal stuff I'll never know. Since the overwhelming majority of machines on the internet aren't (and shouldn't) be directly routable, it's an awful waste to not have organizations behind NAT-ed firewalls and not drawing from the common pool of route-able IP addresses.

    Cheers

    --
    Lost at C:>. Found at C.
    1. Re:Why is anyone surprised? by Finallyjoined!!! · · Score: 4, Informative

      Quite right, there's no reason whatsoever why 98% of users shouldn't be behind NAT gateways. I've seen stupid situations where bloody printers are assigned a public IP - so people can print to them over the internet - Whaaat??? Furthermore pretty much all VPN client software (excluding Microsoft shite, of course) is NAT-T aware.

      One other point, not related to the above, TFA states they are using icmp to determine if a host is alive. Really? What is the margin for error here? Pretty much every device I configure with a public IP & connected to the net, will not respond to icmp (except from designated hosts/host blocks) Guess we can take their figures with a pinch of salt then.

      --
      If I had an Ass, I'd call it Fanny Bottom, then I could slap my Ass; Fanny Bottom, on the Arse.
    2. Re:Why is anyone surprised? by spaceyhackerlady · · Score: 2, Insightful

      Now, why most people aren't using 10.*.*.* as their internal stuff I'll never know. Since the overwhelming majority of machines on the internet aren't (and shouldn't) be directly routable, it's an awful waste to not have organizations behind NAT-ed firewalls and not drawing from the common pool of route-able IP addresses.

      This is exactly how the company I work for does it. We use one public IP address, and our computers (all private IPs, as they should be) are NATted behind our router. I do the same thing at home, partly to circumvent how many computers my ADSL provider will let me plug in to their connection without giving them more money. :-)

      If everybody did things like this we would need a lot fewer IP addresses.

      ...laura

    3. Re:Why is anyone surprised? by mce · · Score: 1

      Now, why most people aren't using 10.*.*.* as their internal stuff I'll never know. Since the overwhelming majority of machines on the internet aren't (and shouldn't) be directly routable, it's an awful waste to not have organizations behind NAT-ed firewalls and not drawing from the common pool of route-able IP addresses.

      Mainly for historical reasons. My previous employer managed to get a B block back in the 1980s. After all, they planned on needing more than 256 addresses, so they would need it... At some point in the early 1990s, they finally managed to clean up the entire network to have logical and consistent addressing (it was a truly horrible mess before that), and since they had the B range, they used it. A few people already understood back then that this was a waste, but IT didn't listen. By now, they have many thousands of machines. All of them nicely firewalled and DMZ-ed, of course but, from an effort point of view, I can fully understand that they're not interested in changing the whole setup all over again.

    4. Re:Why is anyone surprised? by Anonymous Coward · · Score: 0

      My former company is now sitting on two IP blocks (at least) of 64K addresses each, with no earthly reason why they're still allocating public addresses internally. The good news is that they're moving towards using 10.* addresses. The bad news is that I doubt they're going to return those blocks to ARIN any time soon.

      -- Bill

    5. Re:Why is anyone surprised? by camperdave · · Score: 2, Interesting

      The amount of work people would need to invest to use every single IP address with no holes would be cumbersome. (I'm not saying you can't do it, it's just tedious.)

      It's not so much about the little holes, but the ones so big that you could drive a tank through and still have enough room on either side to comfortably fit an aircraft carier through sideways: like the class A block owned by Digital Equipment Corporation, which went belly-up in 1998; or the Computer Sciences Corporation which employs 98 thousand people, but has 16 million IP addresses (for 17 computers apiece, I guess); or the class A loopback adresses, there because somone occasionally pings 127.0.0.2 just for variety.

      And speaking of waste, why blow a 10.0.0.0/8 on a LAN when 192.168.x.0/24 will do just fine? It's this mindset that has lead us to where we are now. I'm switching to IPv6 as soon as my ISP can provide it. ping ::1 is so much easier to type.

      --
      When our name is on the back of your car, we're behind you all the way!
    6. Re:Why is anyone surprised? by Kenshin · · Score: 1

      Now, why most people aren't using 10.*.*.* as their internal stuff I'll never know.

      I'm using 10.*.*.* addresses for my home and business networks. Overkill? Sure. But, pretty much every home and small business I've inspected the network of is using 192.168.1.*, and that's ridiculous and boring.

      --

      Does it make you happy you're so strange?

    7. Re:Why is anyone surprised? by grumbel · · Score: 1

      Quite right, there's no reason whatsoever why 98% of users shouldn't be behind NAT gateways.

      Users should be behind a firewall, not behind NAT, beside breaking the Internet, not really doesn't help much.

    8. Re:Why is anyone surprised? by gstoddart · · Score: 1

      I'm using 10.*.*.* addresses for my home and business networks. Overkill? Sure. But, pretty much every home and small business I've inspected the network of is using 192.168.1.*, and that's ridiculous and boring.

      True story. A couple of years ago someone with not enough network drops in their office brought in an el-cheap-o router/firewall that did it's own DHCP and NAT.

      It turns out the default 192.168.1.* was actually used internally as out finance servers. The newly confusing looking machine with the conflicting IP caused all sorts of badness as all of a sudden multiple machines showed up.

      The solution, was to ban those routers. :-P

      Cheers

      --
      Lost at C:>. Found at C.
    9. Re:Why is anyone surprised? by Fulcrum+of+Evil · · Score: 1

      What's the problem? Random joes shouldn't be handing out IP addresses in an office; I'd ban those things too.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    10. Re:Why is anyone surprised? by bendodge · · Score: 4, Informative

      NAT is a hack, not a firewall.

      --
      The government can't save you.
    11. Re:Why is anyone surprised? by gstoddart · · Score: 1

      What's the problem? Random joes shouldn't be handing out IP addresses in an office; I'd ban those things too.

      I mostly agree with you.

      It was more of a comedy of errors. I agree that people shouldn't be handing out IP addresses. However, in this case, the router wasn't on a 192.168.* address, and *should* have been doing NAT so that when it went past the guys office drop, the packets would be handled like anything else and look like they were coming from a machine correctly.

      Unfortunately, whatever strange combination of mis-configured stuff meant that machines in two completely different cities and on completely different subnets were getting conflicts on the same IP address. It actually took IT hours to find out why the finance machines had dropped off the network.

      At the time, we just didn't think it would have been possible given the sheer number of different networks involved.

      I was merely pointing out that the default 192.168.1.* probably isn't the best, since it's everyone's default. At the very least, if I'm going to use 192.168 I set it to a different one than .1.*.

      Cheers

      --
      Lost at C:>. Found at C.
    12. Re:Why is anyone surprised? by PitaBred · · Score: 1

      There's no reason why 98% of users SHOULD be behind NAT gateways. The Internet was designed peer to peer. It should stay that way, unless you don't like actually being able to, you know, communicate, and would rather have the Internet just evolve into another broadcast medium where a limited cartel of media companies control access to information.

    13. Re:Why is anyone surprised? by sl3xd · · Score: 2, Insightful

      It's a useful hack, but it also causes as many problems as it creates.

      People who worry about IPv6 being routable everywhere on the internet really need to get their heads examined. It's quite simple to set up a packet filter that acts more or less identical to a NAT packet filter. It's quite simple to keep packets from getting where you don't want them to go - no more difficult than IPv4 with the NAT hack.

      --
      -- Sometimes you have to turn the lights off in order to see.
    14. Re:Why is anyone surprised? by PitaBred · · Score: 1

      NAT is not a solution unless you're a fan of getting rid of the peer-to-peer nature of the Internet. The whole point of it was to put every IP on more or less equal ground as far as communication... NAT prevents that. Hell, there are already a lot of ISP's that NAT their customers, so they have to give out fewer "real" IP's. That will happen even more often if "everybody did things like this". That does not bode well for the 'net as a communications platform, because it puts users into different classes.

    15. Re:Why is anyone surprised? by Finallyjoined!!! · · Score: 1

      Well, yes there is...... the limited number of IPv4 addresses :-)

      --
      If I had an Ass, I'd call it Fanny Bottom, then I could slap my Ass; Fanny Bottom, on the Arse.
    16. Re:Why is anyone surprised? by recoiledsnake · · Score: 1

      Furthermore pretty much all VPN client software (excluding Microsoft shite, of course) is NAT-T aware.

      Uhh? I thought XP SP2 enabled NAT-T and updates have been available for Windows 2000 and plain vanilla XP to enable NAT-T.

      --
      This space for rent.
    17. Re:Why is anyone surprised? by Anonymous Coward · · Score: 0

      "NAT is not a firewall"

      Did parent say it was? Enlighten me, why should a home printer have a public IP(6) address? Companies and smart people using internal networks are always gonna be using NAT, so dream all you want if you think IPv6 will make it go away.

    18. Re:Why is anyone surprised? by GNU(slash)Nickname · · Score: 1

      Now, why most people aren't using 10.*.*.* as their internal stuff I'll never know. Since the overwhelming majority of machines on the internet aren't (and shouldn't) be directly routable, it's an awful waste to not have organizations behind NAT-ed firewalls and not drawing from the common pool of route-able IP addresses.

      Well, for one reason, different organizations frequently have a need to connect their networks together.

      I did some work awhile ago for a group of 6 hospitals that needed to join their networks together to facilitate some resource sharing. 4 of those used overlapping space in 10.0.x.x.

      Since nobody would bite the bullet to renumber their network, we wound up having to use NAT on the client side of each connection to translate the server addresses of the "central" hospital. Then they wanted the central servers to be able to print to local printers, so we had to NAT those backwards from the server side of the connection as well.

      All in all, it created a highly unmaintainable mess that would have been avoided if they had all been using centrally allocated addresses. Yes, one could argue that the regional hospital authority should have centrally managed the 10-space, but then what happens when the regions want to share resources?

    19. Re:Why is anyone surprised? by entrigant · · Score: 1

      I really never understood the complete ICMP block mentality. You break all sorts of diagnostic tools and you obliterate any meaningful error reporting. I'm personally sick of trying to connect to things that refuse to send me a proper connection refused icmp packet. Instead they make me sit there for a few minutes while the connection attempt just times out on my end.

      Just block echos on your broadcast address and stop being so paranoid.

    20. Re:Why is anyone surprised? by wastedlife · · Score: 1

      or the Computer Sciences Corporation which employs 98 thousand people, but has 16 million IP addresses (for 17 computers apiece, I guess);

      Your math is either wrong or you made a typo. That would be 170 computers a piece. Just pointing out that it is even more ridiculous than your post states.

      Anyway, I believe CIDR was meant to take care of this, but it was never really utilized and there was too much cruft like the examples you posted.

      --
      Said, "It's just like dice but it's got more sides And it tells me who lives and who dies"
    21. Re:Why is anyone surprised? by pacman+on+prozac · · Score: 1

      It's probably a good idea to block the ICMP redirect messages too.

      Personally I lock it right down to just echo, echo reply, time exceeded and destination unreachable. PMTU still works, you still get invalid connections dropped properly and you can monitor connectivity.

      Does anyone know of any situation where ICMP redirects are valid any more? Seems to me that dynamic routing protocols and IP-redundancy protocols like VRRP have removed any use for them....other than doing MITM attacks on people not filtering ICMP that is ;-)

    22. Re:Why is anyone surprised? by MadMidnightBomber · · Score: 1

      It's far easier to use an entire a.b.c.* as a logical sub-domain than fiddling with netmasks and all that stuff so that a.b.c.1 and a.b.c.200 are on different subnets.

      It's also easier to have a flat /16 where everyone's just plugged into nested switches and served off one DHCP server. But it doesn't bloody scale.

      --
      "It doesn't cost enough, and it makes too much sense."
    23. Re:Why is anyone surprised? by petermgreen · · Score: 1

      Hell, there are already a lot of ISP's that NAT their customers, so they have to give out fewer "real" IP's
      That behaviour has always struck me as a little strange. It would seem to make more sense to me to get as many IP addresses as possible now so they can be reallocated to more lucrative customers later when the new allocations run out.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    24. Re:Why is anyone surprised? by mishehu · · Score: 1

      Uhm. Just because something has an IP address that is publicly routable doesn't mean that you CAN'T FIREWALL IT. NAT is just a bandaid on a wound requiring stitches. It in of itself only adds in a very small layer of protection.

      If you think NAT is so great, tell me what happens when you have a user whose home network is in 10.0.0.0/24 and they try to connect to their office VPN, which provides them with... wait... an IP in 10.0.0.0/24? I do believe that IPv6 has mechanisms for these types of situations built in (the 3 scopes).

    25. Re:Why is anyone surprised? by greed · · Score: 1

      CIDR takes care of it from the technology side.

      It doesn't mean that allocations were suddenly changed. It meant that IBM now owns 9/8 instead of Network 9.

      That's the human side. Technology can't fix that [in acceptable ways].

    26. Re:Why is anyone surprised? by greed · · Score: 1

      Ummmm... I work in a company that has used up a significant chunk of 10/8. There's issues with the allocation to be sure, but if you need more than 254 hosts, it's your best bet.

      In fact, RFC 1918 suggests use of 10/8 in any situation where your routers support the necessary subnetting to do this sort of thing. Using the Class C for a LAN is a throwback to class-based routing (that is, when the address class implied the netmask). I haven't seen a stack where that was necessary since MacTCP... and even then, if you could do the hex-to-decimal conversions, you could work out how to set things up.

      I know of no reasonable explanation for loopback being 127/8, though. Other than Legacy Poirposes or Hysterical Raisins.

    27. Re:Why is anyone surprised? by Eil · · Score: 1

      NAT is a hack, not a firewall.

      NAT allows outbound connections from an internal network to the Internet while making the reverse impossible without deliberately adding some special forwarding rules. Explain to me how that isn't one implementation of a firewall.

      Yeah, I know you pedantic network security types draw a distinction between the concept of "NAT" and "firewall" and that's fine because in theory they're not really the same thing. But if you want to get really technical and snooty about it, I counter that the term "firewall" can mean anything from a single iptables rule on some bloke's laptop all the way up to a rack full of sophisticated servers and networking equipment that perform complex routing, filtering, QoS, traffic shaping, authentication, access control, etc. At the end of the day, "firewall" just means something that blocks or allows traffic based on a static or dynamic configuration.

      Signed,
      A Pedantic Network Security Type

    28. Re:Why is anyone surprised? by Finallyjoined!!! · · Score: 1

      I mentioned neither firewall nor protection, the discussion was the usual /. "We're running out of IPv4 addys" :-(

      --
      If I had an Ass, I'd call it Fanny Bottom, then I could slap my Ass; Fanny Bottom, on the Arse.
    29. Re:Why is anyone surprised? by dbIII · · Score: 1
      NAT is a huge pain in the backside as soon as people use things a common as ftp (still used a lot), half a dozen different types of filesharing software, networked games, VoIP and a few other things that are screwed up by NAT.

      The above coward may know that firewalls are a completely different thing but many people reading this would be assuming that because you get NAT and a firewall in the same black box that they are even the same thing. It would be handy for each PC to have a unique IP address and you just have a firewall between there and the route to the net. The cost of IPv4 addresses makes that unlikely.

      The only reason people think NAT gives you some sort of security is because the average malware can't deal with it properly yet.

    30. Re:Why is anyone surprised? by kybred · · Score: 1

      I was merely pointing out that the default 192.168.1.* probably isn't the best, since it's everyone's default. At the very least, if I'm going to use 192.168 I set it to a different one than .1.*.

      I prefer the 172.16/12 addresses for my home network. They're rarely used. I was using 192.168/16 addresses at home and couldn't connect with the VPN at my office, since it was using the same address range.

    31. Re:Why is anyone surprised? by Anonymous Coward · · Score: 0

      That's because NAT wasn't designed until _after_ people realized maybe the IPv4 address space wasn't enough. It wasn't until the mid 90's that NAT became popular.

      And gstoddart, "people setting up networks aren't trying to use every single address in their space" - it's clear that you don't belong the that group of people...

    32. Re:Why is anyone surprised? by bendodge · · Score: 1

      Perhaps I should state it this way: NAT is a hack and no excuse for a real firewall.

      Yes, NAT is like a one-way funnel, and you can make a real firewall do that too, but one cannot say that NAT is needed because can perform some functions of a real firewall. Car analogy: 'we should keep making old cars because they go slow, and new cars can go slow too.'

      --
      The government can't save you.
    33. Re:Why is anyone surprised? by BitZtream · · Score: 1

      Yes, idiots like you that break protocol (blanket ICMP blocking) make it more difficult to actually get useful reports out of the network, thank you so much for being a part of the problem due to your own ignorance rather than actually being helpful. Please never touch another network device again cluebie.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    34. Re:Why is anyone surprised? by Finallyjoined!!! · · Score: 1

      You really have no idea do you?

      Suggest you go away and research, before lurking & waiting 2 days to add your two-pennyworth of un-informed tripe.

      --
      If I had an Ass, I'd call it Fanny Bottom, then I could slap my Ass; Fanny Bottom, on the Arse.
    35. Re:Why is anyone surprised? by totally+bogus+dude · · Score: 1

      Yeah, NAT is fantastic until you have to set up a VPN with another company who is using the same reserved IP space as you.

      Maybe you should enlighten us as to why a home printer shouldn't have a public IP address, assuming there's no scarcity of IP addresses? What harm does it do? The answer is absolutely none, because NAT is not a firewall. Blocking access to IPs unless you've explicitly configured exceptions is just a side-effect of NAT, and the same can be achieved by a "default deny" firewall.

      So what harm does putting devices on non-routable addresses do? In most cases, none. In some cases -- e.g. if you really do want to access that printer over the internet, or you want to set up a VPN with someone who just happens to be using the same private IP range as you -- then it causes lots of complications.

      Therefore there's two options: let everything use public IP space and have no problems; or use private IP space and possibly have problems. I'm not sure why so many people are so eager to choose the option that may cause them problems down the road. Possibly it's because their only exposure to packet filtering is in the form of NAT, and have no idea that it's quite possible to filter traffic to public addresses at a central device without using NAT.

    36. Re:Why is anyone surprised? by totally+bogus+dude · · Score: 1

      or the class A loopback addresses, there because someone occasionally pings 127.0.0.2 just for variety.

      Well, I do use different loopback addresses for different services. e.g. if I have several mail filters running on a single box, I'll often have them bound to different loopback IP addresses so I can have slightly more informative Received: lines in the headers. For example, inbound mail has headers like these:

      Received: from a.mx.***** (clamsmtp.*-mx-01 [127.0.0.5])
      by relay.*-mx-01 (Postfix) with ESMTP id 136BF93B69;
      Fri, 17 Oct 2008 07:55:25 +0800 (WST)

      Which is slightly more informative than all the internal handling being from "localhost" 127.0.0.1.

      A whole /8 for it does seem a teeny bit excessive though; I think 127.0/16 would have been more reasonable.

    37. Re:Why is anyone surprised? by BitZtream · · Score: 1

      Yes, I'm the one that needs to do research.

      Let me help you:
      http://tech.slashdot.org/comments.pl?sid=996699&cid=25385889

      or more specifically:
      http://www.freelabs.com/~whitis/isp_mistakes.html

      That'll cost you a cluepon.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    38. Re:Why is anyone surprised? by Finallyjoined!!! · · Score: 1

      That's not research, suggest you buy and read this: http://www.ciscopress.com/bookstore/product.asp?isbn=158705115X

      Here's an extract, because I'm not lending you my copy, to get you started: http://www.ciscopress.com/articles/article.asp?p=174313&seqNum=4

      Also, if you're configuring Cisco kit, as I do, consider adapting Rob's access-list, found here: http://www.cymru.com/Documents/icmp-messages.html

      Now refund my cluepon please.

      --
      If I had an Ass, I'd call it Fanny Bottom, then I could slap my Ass; Fanny Bottom, on the Arse.
  11. Many addr's may be behind firewalls... by Anonymous Coward · · Score: 5, Informative

    We get this all the time from our ISP's. "Our scans reveal that you're not using much of the space we've allocated to you." In reality, those IP's are behind firewalls that only permit certain customers to reach them. Otherwise they don't respond - even to pings. The IP's appear dead to everyone except authorized users, and our ISP's aren't authorized.

    1. Re:Many addr's may be behind firewalls... by Timothy+Brownawell · · Score: 3, Funny

      I wonder what the opposite strategy would do... have the firewall intercept pings, but instead of just dropping them, pretend to be the target and answer them itself.

    2. Re:Many addr's may be behind firewalls... by Volante3192 · · Score: 1

      Heh, the following companies should get alerts like that: GE, IBM, Xerox, HP, Apple, Ford, Halliburton...each of those have a full Class A block, HP has two even. (What, they want each printer of theirs sold to have a unique public IP?...)

      I don't think those /29 and /30 blocks are the problem. it's all these unsaturated class As.

    3. Re:Many addr's may be behind firewalls... by jabuzz · · Score: 1

      Perhaps the best solution is to create a market in IP address spaces. If there is a monetary incentive for HP to take one if it's class A blocks break it into a bunch of class B blocks and sell them on the open market I am quite sure they would.

    4. Re:Many addr's may be behind firewalls... by qwertphobia · · Score: 1

      Yeah... because I want everyone to be able to print to my printer!

      --
      Never ask for directions from a two-headed tourist! -Big Bird
    5. Re:Many addr's may be behind firewalls... by Anonymous Coward · · Score: 0

      It can be done with Honeyd

    6. Re:Many addr's may be behind firewalls... by sl3xd · · Score: 2, Insightful

      You gotta love the assumption they're making that "not pingable means not in use."

      In reality, it can quite easily mean that most of the IP addresses on the internet are firewalled off, because they're not serving anything to the rest of the internet. If anything, I like to think of it as a good sign that at least rudimentary security measures are being taken by consumers.

      Grandma doesn't need her own web server, mail server, etc. Neither do most consumers - heck, I only have a couple of ports open - SSH and a gaming VoIP server.

      Guess what ping does? Yup. Nothing.

      --
      -- Sometimes you have to turn the lights off in order to see.
    7. Re:Many addr's may be behind firewalls... by sl3xd · · Score: 1

      Why even bother?

      The companies are the rightful and legal owners of the block A addresses - they bought and paid for them. To get them from them will require a lengthy court battle and billions of dollars in legal fees. By the time that's done, IP address exhaustion will have happened.

      Even then, the amount of additional IP addresses offered is miniscule compared to the need.

      NAT isn't a solution, it's a convenient hack that is already causing more problems than it's worth - all kinds of peer to peer apps from Skype to torrents have no end of troble because of NAT. Our networks are deliberately left vulerable so that apps can "punch through" NAT. NAT is a security blanket that doesn't really offer the protection many have been brainwashed into believing.

      Frankly, I don't see why there's so much hate towards IPv6. It's not that much more complicated than IPv4. It's that people don't want to spend any time learning it. So while people seem happy to spend months learning the ins and outs of IPv4, they are completely unwilling to touch IPv6.

      Anybody who blindly repeats the mantra "IPv6 is routable everywhere, I can't 'protect' my network!" needs to quiet down and stop spreading FUD. Just because you're scared you'll actually have to learn something new does not make IPv6 something to avoid. If you thought you were done going to school when you entered this industry, you picked the wrong profession.

      The simple fact is IPv6 can be firewalled and packet filtered like an IPv4 network. It's quite simple to setup an IPv6 firewall that will keep those nasty, evil packets from ever being routed to the final destination, and in fact, acts much like a connection-tracking NAT firewall. It doesn't require a firewall running on every system, just the main one that faces the rest of the interenet -- just like we already do with IPv4.

      --
      -- Sometimes you have to turn the lights off in order to see.
    8. Re:Many addr's may be behind firewalls... by houghi · · Score: 1

      In reality, it can quite easily mean that most of the IP addresses on the internet are firewalled off, because they're not serving anything to the rest of the internet.

      That would mean they are not in use for the desired purpose and should be given back.

      --
      Don't fight for your country, if your country does not fight for you.
    9. Re:Many addr's may be behind firewalls... by sl3xd · · Score: 1

      ... you seem to have missed my point entirely, but I'll address yours below.

      My original point there are hundreds of millions single addresses given to home and corporate users, and that address uses a firewall which doesn't responding to the pings used in the study. I think that's a good sign - that individual users have a firewall on the IP address assigned to them by their ISP.

      But for your point...

      This comes down to an allocation of resources - the same old argument of a few rich people controlling more wealth than the other 90% of the population. What "should" happen and what does happen aren't the same thing.

      Those addresses were bought and paid for; they are legally considered property. In a very real sense, they are "real estate" on the internet. To quote a recent movie: "Land is the one thing they're not making any more of." So the companies with large blocks of addresses are virtual landowners.

      One thing is certain: The address blocks are not going to be simply given back as a goodwill gesture. They're either going to be sold or fought over in court. Given the price will keep going up, the likelihood they'll be sold is small, because there's a huge incentive to not sell.

      They can be taken using imminent domain law, but that requires a fair market value to be paid - and that's assuming it isn't defended vigorously by the companies, a process that takes years.

      Keep in mind also, that these companies also have an interest in seeing IPv6 put into use, which is yet another reason for them to hang onto the addresses. First and foremost, holding onto the addresses to force adoption of IPv6 may be "the right thing to do" for them. Second, they can make money selling consulting and services.

      --
      -- Sometimes you have to turn the lights off in order to see.
    10. Re:Many addr's may be behind firewalls... by Eunuchswear · · Score: 1

      The companies are the rightful and legal owners of the block A addresses - they bought and paid for them.

      Wrong! They paid nothing, and they don't own them either(*), that's why they can't sell 'em. This is the big problem preventing the obvious "economic" solutions to the IPV4 address space problem.

      ((*) if anyone does own IPV4 addresses it's the RIR's and the IANA).

      --
      Watch this Heartland Institute video
  12. Re:Pedantic Correction for the Headline by Surt · · Score: 1

    I'm sure the headline just means that they are actually in use, falsifying their idleness.

    --
    "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
  13. Reliable? by Anonymous Coward · · Score: 1, Insightful

    I, for one, question the reliability of this data since the machines that are occupying those addresses are probably firewalled.

  14. Fallow-Field Legislation by VE3OGG · · Score: 2, Interesting

    In the oil-business (and in many other fixed-resource industries, more then likely) there is a particular kind of legislation that would likely work very well in such a situation. It is known as 'fallow field legislation'.

    It works like this:

    If a company finds (or buys) rights to an oil field, they are given five years to start producing from it. If they do not, cannot, or are otherwise unwilling after those 5 years, the rights are revoked and the government (or governing body) will find someone who will and can.

    Fast forward to IPv4 -- any address that isn't being used (and by used I mean that there is no web presence, to use of e-mail, etc.) after a certain time period (perhaps 1-2 year(s)) then the address is revoked and put back into the public pool.

    Obviously, the easiest way to get around this little regulation would be to put up a place holder page, or redirect it to the main site. This would be much trickier. Likewise, it would not stop the name squatters (and increasingly the registrars) from putting up those SPAM pages, but like I said, it would fix the problem of people just sitting on a resource without using it.

    My $0.02

    1. Re:Fallow-Field Legislation by mcelrath · · Score: 1

      This sounds like a great idea for IP=Intellectual Property.

      If you do not, or cannot make money from your IP "rights" within the last 5 years, then that IP enters the public domain.

      --
      1^2=1; (-1)^2=1; 1^2=(-1)^2; 1=-1; 1=0.
    2. Re:Fallow-Field Legislation by Anonymous Coward · · Score: 0

      Fast forward to IPv4 -- any address that isn't being used (and by used I mean that there is no web presence, to use of e-mail, etc.) after a certain time period (perhaps 1-2 year(s)) then the address is revoked and put back into the public pool.

      yeah lets just start assigning single-ip blocks revoked from large corporations, that wont completely kill routers by causing excessively complex routing tables.

      It's also pretty hard to define 'web presence'. If I have a quake server running every friday night, do I get to keep the ip? What about a vpn service that only allows the IPs I authorize to connect to it? That would appear entirely dead to the rest of the internet but is certainly in use.

    3. Re:Fallow-Field Legislation by Anonymous Coward · · Score: 0

      Sig error:

      Ignoring the amusing abuse of exponents that leads to (1=-1), how do you get from that to (1=0)? You can get to (2=0), or (-1=0)....

    4. Re:Fallow-Field Legislation by Obfuscant · · Score: 1
      Fast forward to IPv4 -- any address that isn't being used (and by used I mean that there is no web presence, to use of e-mail, etc.) after a certain time period (perhaps 1-2 year(s)) then the address is revoked and put back into the public pool.

      Not every use of an IP address is for a web server. I run two systems with web servers on them. All of the rest have no need and will not run web services, and yes, I need to be able to get into them from outside.

      Further, many of them are firewalled so only specific outside places can get in. Yeah, run a web server to make them "legal", but YOU won't be able to get to the server to detect it.

      Obviously, the easiest way to get around this little regulation would be to put up a place holder page,

      Yes, obviously, the answer to this problem is to run useless servers where they aren't needed, opening up security holes as the bugs are uncovered, increasing the administrative workload for everyone and making a field day for crackers. Sure.

      My $0.02

      Right.

    5. Re:Fallow-Field Legislation by mcelrath · · Score: 1

      I know how to divide by 2. And -1 for that matter.

      --
      1^2=1; (-1)^2=1; 1^2=(-1)^2; 1=-1; 1=0.
    6. Re:Fallow-Field Legislation by Anonymous Coward · · Score: 0

      The difference between the IPv4 address space and other fixed-resource industries is that IPv4 is an artificial resource! IPv6 works, and is deployable, even amidst many naysayers. IPv6 is basically the opposite of a "fixed" resource. It's like snapping your fingers and having a ball of oil bigger than the entire earth, ready to drill. But, nah, we've still got some pockets off shore that can be drilled! Screw this entire planet of oil (IPv6)!

    7. Re:Fallow-Field Legislation by SQLGuru · · Score: 1

      Simple....if 1=0 ("proven" in the sig) and -1=0 ("derived" by you), then 1 + -1 is the same as 1 + 0. Anything + 0 has the answer of Anything. So, 1 + 0 = 0.

      Layne

    8. Re:Fallow-Field Legislation by Cowmonaut · · Score: 1

      Yeah! It's a great idea!

      That's why it was originally made that way, just with a slightly longer time frame.

      Kudos to Disney and other "big media" corps for making it indefinitely rather than within a set time frame.

    9. Re:Fallow-Field Legislation by qwertphobia · · Score: 1

      Are you suggesting that I lose my entire Class B, or just parts of it? How do we negotiate which parts, and who takes the responsibility of notifying my upstream providers that someone else can advertise parts of my registered space?

      --
      Never ask for directions from a two-headed tourist! -Big Bird
    10. Re:Fallow-Field Legislation by VE3OGG · · Score: 1

      Just to clarify:

      To those who runs servers periodically, or to those who run servers that are not attached to a web server, what I am suggesting is not aimed at your uses. They are indeed legitimate, and can be used however you want.

      However, those that *do* buy out these addresses, and leave them fallow, simply to horde (and let us face it -- many companies do this) they would be the specific target of this.

  15. His research is invalid!! by Anonymous Coward · · Score: 1, Informative

    I have 2 class C ranges, and if he scanned mine he would have only got a handful of ICMP replys. I intentionally block ICMP on the majority of my IP's because it's nobody's business if I have anything on it.
    I'm willing to bet that I'm not the only one blocking ICMP! Not by a LONG SHOT!

  16. TCP and ICMP by IceCreamGuy · · Score: 4, Insightful

    I drop ICMP entirely, and besides our website and mailservers, we don't have any standard tcp ports open on any of our other external IPs. I really can't imagine it's that much different for other medium and large businesses; am I to believe they nmapped the entire Internet? (It's clear FTA that they did not) To me, these findings are not that surprising in the security-oriented world we live in today.

    1. Re:TCP and ICMP by Anonymous Coward · · Score: 1, Informative

      Do you realize that dropping all ICMP breaks PMTUD among other things?
      Don't block all ICMP just block the ICMP you don't want.

    2. Re:TCP and ICMP by Anonymous Coward · · Score: 2, Insightful

      If none of the ports are open on any of your external IPs, then why do you need to have more than one external IP?

    3. Re:TCP and ICMP by Anonymous Coward · · Score: 5, Informative

      I drop ICMP entirely

      Then you're an idiot who has no business managing a firewall.

    4. Re:TCP and ICMP by afidel · · Score: 1

      They are probably just not open to YOU, most of us sane people use ACL's to limit who can talk to equipment. Just because it's not open to the public doesn't mean it doesn't need to be uniquely identified on the routable internet.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    5. Re:TCP and ICMP by Phroggy · · Score: 1

      If none of the ports are open on any of your external IPs, then why do you need to have more than one external IP?

      He didn't say there are no ports open, he said there were no standard ports open.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    6. Re:TCP and ICMP by Nimey · · Score: 1

      Indeed. ICMP is in the RFC for a reason.

      'Course, I block a bit of ICMP as well, but just the incoming stuff that tells details about the network, i.e. incoming timestamp, incoming netmask, incoming router. Pings I allow through, and all the outbound stuff.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    7. Re:TCP and ICMP by IceCreamGuy · · Score: 1
      I may be an idiot and not have any business managing a firewall, but apparently judging from the article you linked to, a lot of people make the same mistake. I went in and checked though, and I was thankfully mistaken, we do have 3-0, 3-1, 3-2, 3-3, 3-4, and 11 turned on, but 8 definitely off on the outside.

      So now I'm not sure if we really would be invisible, are there other scanning methods besides echo?

    8. Re:TCP and ICMP by ObsessiveMathsFreak · · Score: 1

      The institution where I work has blocked ICMP for years. It's not the only thing they restrict.

      Ping (obviously) does not work. SSH does not work. NTP does not work.
      But. Browsing still works. Outlook still works. Windows shares still work.

      They have no intention of changing this state of affairs, and as infuriating as it is for people like myself who use these services, most users are totally and utterly oblivious to the effects of the change.

      Say what you will about defective or broken networks. Blocking ICMP continues to be a viable practice whose use only increases as time goes by. The internet of the future will have no pings if people remain complacent about the viability of these lobotomised networks.

      --
      May the Maths Be with you!
    9. Re:TCP and ICMP by ChuBie · · Score: 1

      I drop ICMP entirely

      So your one of the "network admins" that is causing my PMTU discovery to fail. Thanks idiot!

      Google "blocking icmp" to see the numerous reasons why blocking all ICMP types is braindead.

      Just block the ones that can be abused.

    10. Re:TCP and ICMP by Anonymous Coward · · Score: 0

      The link you provided focuses on ISPs, and the person you responded to classified himself as smaller than a medium or large business and didn't sound like they were in the ISP business. While it is true that ISPs are discouraged from blocking ICMP through their network, it is good practice to disallow ICMP directed at hosts that need limited Internet access or that should be partially or completely hidden from the Internet. Why give hackers additional targets if it isn't necessary? For any host on the Internet, the more traffic allowed to the device the more chance their would be for DoS and/or exploitation. In other words, if ICMP or any other access isn't necessary for running a given service, it should be blocked. That's Security 101.

      In your attempt to play the expert, you have exposed yourself as nothing more than an amateur. Let me give you some advice, unless you genuinely know what you are talking about, keep your comments and insults to yourself. Who's the idiot now?

    11. Re:TCP and ICMP by IceCreamGuy · · Score: 1

      Holy shit, calm down, I'll turn it on. I already said above that I meant echo and let a decent amount of ICMP through. The only reason I block echo is because the previous admin had it off and I didn't really have an informed opinion on it one way or the other. But you've convinced me in the most assholish, unconstructive way to turn it on, so sorry for breaking your PMTU, I hope it frustrated you at one point or another.

    12. Re:TCP and ICMP by Anonymous Coward · · Score: 0

      Read the title of the article you ref!!!!!!
      Common ISP Mistakes - not end user mistakes for crying out loud!

    13. Re:TCP and ICMP by Anonymous Coward · · Score: 0

      That was a really useful link, thanks. I think that explains a problem I had a place I used to work when the monkeys running the network started playing around with the routers.

    14. Re:TCP and ICMP by Anonymous Coward · · Score: 0

      Um, apparently you are the idiot, because if he's running a web server he's Providing a Service on the Internet.

    15. Re:TCP and ICMP by Anonymous Coward · · Score: 0

      Browsing still works. Outlook still works. Windows shares still work.

      No, they don't. They work sometimes, for some people and some sites.

      But by blocking ICMP, *EVERY* other protocol is being degraded.

      Most likely someone tries to visit a web site, or email someone else, it doesn't work, you just say "oh,it doesn't work, I don't know why" and move on, never attributing it to the bad policies.

      Blocking ICMP continues to be a viable practice whose use only increases as time goes by.

      No, it absolutely does not. There is *NO* value in it, at all. Why don't you just block UDP as well?

      The internet of the future will have no pings

      The problem is not about "ping", it's about ICMP. (And morons like you who think that they are the same thing.)

    16. Re:TCP and ICMP by Anonymous Coward · · Score: 0

      This is only at 5: Informative? This should be at at least 12.

    17. Re:TCP and ICMP by Anonymous Coward · · Score: 0

      I may be an idiot and not have any business managing a firewall

      OK, from your other posts here, it appears that idiot was too strong a word. Please accept my apologies.

      apparently judging from the article you linked to, a lot of people make the same mistake

      Yes, but that doesn't make them not idiots. They're idiots who are told that they're doing it wrong, but continue to do it anyway.

      I went in and checked though, and I was thankfully mistaken, we do have 3-0, 3-1, 3-2, 3-3, 3-4, and 11 turned on, but 8 definitely off on the outside.

      That looks good - you're blocking ping, but allowing necessary stuff.

      In another post you said you were going to enable it - don't, unless you know why it was disabled in the first place. (If it's being done for "security", then go ahead and enable it. If it's being done for some other reason, then evaluate that reason.

      On my border firewalls, I block ICMP-echo-request from untrusted hosts (basically I allow ping from my ISP's NOC/routers, in case they need to troubleshoot something.) Note that I don't block them as a security measure, it's done to eliminate noise in my logs. (If you're using it as a security measure, don't - it doesn't provide any security at all.)

    18. Re:TCP and ICMP by Anonymous Coward · · Score: 0

      That information seems pretty outdated - I run a /19 and block ICMP just about everywhere. I'm running mail, DNS and web servers in very busy production environments and have _never_ had problems with bad MTU discovery.

      The first stage of an attack is network enumeration - disabling ICMP makes it just that little bit more difficult, particularly as attackers won't be able to perform traceroutes through your network.

    19. Re:TCP and ICMP by Anonymous Coward · · Score: 0

      The link you provided focuses on ISPs

      Which is entirely irrelevant. It contains important information that anyone managing a firewall needs to know, whether they're an ISP or not.

      it is good practice to disallow ICMP directed at hosts that need limited Internet access

      No. It is never good practice to disallow ICMP. EVER . If you believe it is, then you don't understand what ICMP is used for.

      Why give hackers additional targets if it isn't necessary?

      Sorry, but do you really believe that a hacker could exploit a hole in PMTU discovery?!?!

      if ICMP or any other access isn't necessary for running a given service, it should be blocked.

      The thing is - IT IS NECESSARY . BY DEFINITION. If you believe its not necessary, then you don't understand what it's for, and you're a moron.

      In your attempt to play the expert, you have exposed yourself as nothing more than an amateur.

      No, that would be you. You've proven that you know absolutely *nothing* about IP, ICMP, or security.

      Let me give you some advice, unless you genuinely know what you are talking about, keep your comments and insults to yourself.

      Instead of trying to give me advice, you should honestly examine your own post. You obviously know nothing about what you're talking about.

      Who's the idiot now?

      That would be you.

    20. Re:TCP and ICMP by Anonymous Coward · · Score: 0

      I drop ICMP entirely

      Then you're an idiot who has no business managing a firewall.

      amen.

    21. Re:TCP and ICMP by BitZtream · · Score: 1

      This stuff always makes me laugh.

      Why block timestamp? Do you run on some time other than what the rest of the world does? I mean you should probably be keep in sync using NTP or something like that, in which case the timestamp packet isn't going to tell anyone much more than they can already make a pretty accurate guess on.

      Why block incoming router? Again, with a traceroute and a guess or two you can figure this out pretty easy without ICMP.

      Netmask? Really? Who cares? What are you afraid of them knowing? You have 2 web servers on the same subnet? Oh Gnoes!

      I'm a paranoid SOB and have a pretty strict set of firewall rules, all normal tcp/udp/unknown protocols are blocked inbound, and there is a strict set of whats allowed outbound, but blocking these things is just silly and pointless. But ICMP? It goes whatever it wants outside of directed broadcasts pretty much. If I have to deal with some weird OS exploit based on ICMP I'll block it until I can get patched, but I don't see a reason why you'd really want to continue blocking it, its probative value really just isn't that great and you're potentially making some other poor admin who has to debug a problem work that much harder to find information you've done very little to actually protect, just makes him/her do more work for pretty much zero gain on your side as any person trying to exploit you is just going to automate all of it.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    22. Re:TCP and ICMP by IceCreamGuy · · Score: 1

      Thanks, I believe it was done in the name of security, and since it actually frustrates me sometimes, I think I will go ahead and enable it. I really appreciate your response, (even though you're AC) this kind of discussion where I can actually learn something from peers is why I love slashdot.

  17. Re:Pedantic Correction for the Headline by Anonymous Coward · · Score: 0

    Oh dear, I think you should lie down and think about that a bit harder.

  18. Re:Pedantic Correction for the Headline by Anonymous Coward · · Score: 0

    No, it shouldnt. Lay is when you're doing it to something else. "I lie down." "I lay down my arms."

  19. No! by Anonymous Coward · · Score: 0

    Or yes if you want to watch sysadmins scramble to save the day in the final hour.
    Hmm, wait thats how we solve all tasks that donÂt generate imediate revenue.

  20. Bankrupt companies by sunderland56 · · Score: 2, Interesting

    What happens to the IP addresses allocated to companies that are now (a) bankrupt, or (b) bought out by larger companies, or (c) allocated to companies now significantly smaller in size? There must be a significant pool of addresses that could be reclaimed there.

    e.g. dec.com, compaq.com, sco.com, sgi.com....

    1. Re:Bankrupt companies by stereoroid · · Score: 1

      There's a fuller list here. Whole blocks are unallocated, held by IANA. I know that, in the case of Compaq, it didn't have its own range originally, but acquired 16.x.x.x with DEC. That was absorbed by HP (15.x.x.x) and is still used internally.

      --
      (this is not a .sig)
    2. Re:Bankrupt companies by Anonymous Coward · · Score: 0

      You'll have to ask HP about DEC and Compaq's IP allocations, since it owns both.

  21. The simplest solution is to... by Jodka · · Score: 1, Insightful

    Raise prices.

    Raising the price of an IP address increases the incentive to not to waste the IP address.

    --
    Ceci n'est pas une signature.
    1. Re:The simplest solution is to... by azgard · · Score: 1

      That's also the most idiotic solution. Sure, yes, reward those who got lucky and got large blocks in early days, and make pay those who actually use them.

    2. Re:The simplest solution is to... by dword · · Score: 1

      And how would this fix things? It would only make the companies that own A.*.*.* keep those addresses instead of releasing them to the public.
      The problem: we're out of ipv4 ips
      The cause: many of them are allocated but unused
      The short-term solution: release unused addresses
      Long-term solution: ipv6
      How would raising prices help?

    3. Re:The simplest solution is to... by Jodka · · Score: 1

      assguard wrote:

      Sure, yes, reward those who got lucky and got large blocks in early days, and make pay those who actually use them.

      Raising prices means that those who hold an IP addresses in the future would pay more to hold that IP address than they pay now.

      Your objective reveals that you do not understand the concept of an increased price.

      --
      Ceci n'est pas une signature.
    4. Re:The simplest solution is to... by Jodka · · Score: 1

      fword wrote:

      And how would this fix things? It would only make the companies that own A.*.*.* keep those addresses instead of releasing them to the public.

      Raising prices means that those who hold an IP addresses in the future would pay more to hold that IP address than they pay now.

      Your objection reveals that you do not understand the concept of an increased price.

      --
      Ceci n'est pas une signature.
    5. Re:The simplest solution is to... by dword · · Score: 1

      Cool! I didn't know that, it's great when you make mistakes like this and someone corrects you. I've just checked it out and you were right. Thanks :)

  22. Panic is good. by Jack9 · · Score: 1

    How long did it take for the world to believe that the moon was a hunk of desolate rock as opposed to a god or made out of cheese? World perception is important and there's a lot of people who understand the IPv4 is running out. Not needed or advised to try and slow down adoption by yelling "wait wait wait we can still cheat to tread water longer" when the ocean is getting bigger by the day.*

    //*on the spot metaphor

    --

    Often wrong but never in doubt.
    I am Jack9.
    Everyone knows me.
    1. Re:Panic is good. by eihab · · Score: 1

      I thought the whole point of their research is to say "Wait, we can squeeze more IPs that are allocated and not used before moving to IPv6".

      --
      If you can't mod them join them.
    2. Re:Panic is good. by Jack9 · · Score: 1

      And why is THAT a good idea?

      --

      Often wrong but never in doubt.
      I am Jack9.
      Everyone knows me.
  23. ICMP and TCP? by Anonymous Coward · · Score: 1, Interesting

    What about firewalls set to drop this traffic from unknown sources instead of rejecting?

  24. Millions more have been hijacked by Arrogant-Bastard · · Score: 5, Interesting

    In addition to all those lying idle because of excessive address space allocation, there are huge swaths of space which have been hijacked. Recent discussion on the NANOG list has highlighted some of these; the Spamhaus DROP list features others. And other researchers have found still more that are obviously no longer under the control of their putative owners, and are being use for spam, spyware, phishing, and worse. Attempts to get network operators, registrars, ICANN, ARIN, and others to effectively disable these resources -- and eventually to reclaim them -- have been largely unsuccessful. Yes, in some isolated cases, limited action eventualy takes place, but it's far too little far too late to be considered anything close to "effective". We need a concerted, worldwide effort to not only reclaim this space, but to blacklist for life those found currently possessing that -- because (as we've seen repeatedly) they won't be deterred by anything else.

    1. Re:Millions more have been hijacked by Anonymous Coward · · Score: 0

      The people who run spam networks today are going to be the voice of the people in the future you're looking forward to, where world-wide crackdowns on rogue network operators results in a neat, controlled Internet(tm).

    2. Re:Millions more have been hijacked by n4djs · · Score: 1
      the question is - why do routers simple not drop connections from these hijacked address blocks as a default policy? Is it because the process of activating a new block is not working well due to router configurations internet wide, or is there rogue routers that are enabling this? Or something else?

      Also, why do merged companies get to keep multiple class A's (HP/Compaq/Digital/Tandem comes immediately to mind, but I am certain that there are others)? Perhaps it is time to pass a $1 per allocated address annual fee or tax to 'encourage' people to release unused addresses. This is particularly true of organizations that are NAT'ed or proxied with very few machines that are internet facing...

      The reality is that the IPv4 -> IPv6 transition is extremely costly, and may face some huge problems with the current economic crisis.

  25. MIT is 18.*.*.* by Dogun · · Score: 2, Informative

    Last I checked, MIT had all of 18.*.*.*...

  26. Wrong! Lying is the correct form. by DigitalReverend · · Score: 4, Informative

    http://www.grammarmudge.cityslide.com/articles/article/992333/8992.htm

    http://www.askoxford.com/betterwriting/classicerrors/grammartips/lyingandlaying

    If you are in the process of putting something down, you are laying it down, but that object once it is there, it is lying. The verb lay has a direct object that the action is performed on. He is laying the book credenza. She is laying her purse on the counter. Once it has been laid, it is now lying. The book is lying on the credenza. The purse is lying on the counter. IP addresses are lying unused.

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

    --
    I read Slashdot for the headlines, because the headlines, unlike the articles, are usually original and never duplicated
  27. Need a Class C to do BGP by WisePug · · Score: 2, Informative

    I just setup redundant internet connectivity, and needed to get a class C address space, even though I only use a dozen or so addresses. I guess this is to limit the size of routing tables. Seems like a waste.

    1. Re:Need a Class C to do BGP by afidel · · Score: 1

      Depends on your provider, AT&T will do BGP between sites for us with just a /26 though I believe you do need a full C to get an ASN to do BGP between providers.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    2. Re:Need a Class C to do BGP by ChuBie · · Score: 1

      I guess this is to limit the size of routing tables. Seems like a waste.

      Yes on both. Almost all ISPs will filter out any routing advertisements from their customers that are smaller than a /24 prefix.

    3. Re:Need a Class C to do BGP by chrisj_0 · · Score: 1

      I had this same problem. I already have a /24 from my ISP. when we went to our DR site to turn up the network I was told that they wouldn't accept the /26 for BGP and I had to get yet another /24 from them just to advertise both networks. so now I have 4 /24 address ranges. 2x at the corp office and one each at our Colo sites. I need a total of about 35 public addresses but I've been assigned over 1,000.

  28. Re:Pedantic Correction for the Headline by Tack · · Score: 1

    The general problem with being a Grammar Nazi is that you had better be sure you're right. (And you're not.)

  29. Re:Pedantic Correction for the Headline by Anonymous Coward · · Score: 0

    No, "lying" is correct.

    Lay has an object. Lie does not.

    You lay bricks, but you lie on your couch.

  30. Interactive map by citking · · Score: 2, Informative

    There is an interactive map on their site that allows you to zoom into the IP space pretty nicely. Our uni has a B range of addresses and we use only two Cs of that right now. When we split off from the main building and got onto city fiber, they decided that, rather than give us a private IP range like the other campuses, we would be allocated one of the C ranges.

    Of course, no one knew what they were doing so getting the ASA and default routes set-up properly was a nightmare, but hey, we're using more of our IP space now! (sarcasm intended)

    --
    "This food is problematic."
  31. They used ping! by eihab · · Score: 5, Interesting

    From the article:

    The USC research group used the most innocuous type of network packet to probe the farthest reaches of the Internet. Known as the Internet Control Message Protocol, or ICMP, this packet is typically used to send error messages between servers and other network hardware.

    My home network is in complete stealth mode, and to them that's another "idle IP" address.

    I also love how they arrived to their conclusion:

    the team probed a million random Internet addresses using both ICMP and TCP, finding a total of 54,297 active hosts ...
    In total, the researchers estimate that there are 112 million responsive addresses ...
    but the overall conclusion--that the Internet has room to grow--is spot on

    How did this ghetto-science experiment end up on Slashdot again?

    --
    If you can't mod them join them.
    1. Re:They used ping! by Anonymous Coward · · Score: 0

      How did this ghetto-science experiment end up on Slashdot again?

      perhaps timothy has been taking "editor" lessons from kdawson?

    2. Re:They used ping! by value_added · · Score: 1

      My home network is in complete stealth mode

      Mine, too!

      My own approach is a bit unusual (I use a /31), but it offers similar advantages without the need for complex firewall rulesets.

    3. Re:They used ping! by ObsessiveMathsFreak · · Score: 1

      How did this ghetto-science experiment end up on Slashdot again?

      I'm not sure I understand the question... .

      --
      May the Maths Be with you!
    4. Re:They used ping! by mapleneckblues · · Score: 1

      The researchers do address your points:
      http://www.isi.edu/ant/address/

      Internet Census Taking,
      We believe we have taken the first census contacting each address of the visible Internet since 1982 (RFC-832). A census is an enumeration of all allocated addresses. We probed all 2.7 billion allocated addresses (compared to 315 in 1982). We are able to probe only the visible Internet: all addresses that use public addresses and choose to respond.
      Accuracy,
      No census of billions of addresses will be perfect; we underestimate occupancy for three reasons: A few percent of probes and replies are lost due to congestion. Addresses such as those behind firewalls choose not to receive or reply to our requests. Other computers use private addresses. We evaluate loss in our technical report; evaluation of the other cases, the invisible Internet, is future work.

    5. Re:They used ping! by Anonymous Coward · · Score: 0

      My understanding of the 1 million addresses was they ran a comparison on those million addresses of icmp and tcp. Of the two methods icmp came back 3/4 of the time where tcp came back just under 2/3 of the time. Hence the reason they used icmp.

    6. Re:They used ping! by wertigon · · Score: 1

      What the... You, sir, have just made the impossible. The smallest subnet one can have is /30. That leaves two bits or four addresses, one for router, one for broadcast, one for network name and one for your computer. Would you kindly explain how that would fit in two addresses?

      --
      systemd is not an init system. It's a GNU replacement.
  32. IPv4 addresses running out: by circletimessquare · · Score: 4, Funny

    the IT hysteria of the early century. just as juicy a media hit as the Y2K panic and fear from last century, but not as much consulting opportunities

    personally i'm waiting for 2012, when the elder gods of the mayan calendar awaken and in their rage at not being greeted by chocolate, peppers, and virgins, they reroute all null pointers in all code to the apocalypse. plenty of IT hysteria, plenty of consulting opportunities

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:IPv4 addresses running out: by sl3xd · · Score: 1

      Well, you're partly correct - there are a lot of consulting opportunities.

      In both cases, the "fear and panic" was because there is a real problem that needs to be solved. Fear and panic is a good way to get resources allocated to fix the problem - that way, you're the hero instead of a villan. IPv4 exhaustion is coming. The only debate is on the timeframe.

      You can try to mitigate the problem with years of legal battles and billions of dollars in legal fees... ie. try to fix the problem legislatively... And even then, it's at best a temporary solution.

      Or you can actually fix the problem by using the protocol designed over a decade ago in anticipation of the problem. IPv6 is apparently so good that many of its features were 'backported' for use in IPv4.

      IPv6 solves the problem nicely, and there's a lot of money (and jobs, homes bought, children fed, divorces filed, alimonies paid, and kids sent to college) that can be made from it. It's not a magic bullet, but it does solve a number of routing issues and the big one - address space.

      So the question remains: Do we want to enhance our skills, solve the problem, and make money solving the problem, or do we want to whine and pout about "the good old days" when gas only costed $0.99 a gallon?

      --
      -- Sometimes you have to turn the lights off in order to see.
  33. Underused Subnets by prestomation · · Score: 1

    I had always heard similar. In the early days, lots of people where given A subnets on the assumption "We'll never need all those addresses so take a whole block!", so now large parts of Class A's are being unused, but the logistics of sorting all that out would be a pain

  34. Re:Pedantic Correction for the Headline by Vortran · · Score: 1

    How could an IP address be laying? How does an IP address lay anything? Do they lay bricks? Are they hoping to GET layed? Did one of these lying addresses lay you upside the head?

    If you're going to wax pedantic, first try being right.

    --
    Knowledge is like ignorance.. too much can be just as bad as not enough.
  35. The problem isn't the addresses... by nsayer · · Score: 1

    it's the size and complexity of the non-default routing table. The principle reason to switch to IPv6 is that it gives us the opportunity to throw away the old legacy routing table and insist on sticking with hierarchical address allocation to keep the routing table small.

  36. Re:Pedantic Correction for the Headline by geminidomino · · Score: 1

    Informative? No. Wrong, actually.

    "To Lay" is an transitive verb. You lay down arms, lay down the law, lay that cute blond from accounting.

    "To lie", in the sense of adopting a prone or supine position, is an intransitive verb. You lie down and put your hands behind your head, or lie under said cute blond.

  37. Re:Pedantic Correction for the Headline by geminidomino · · Score: 1

    and like all grammar corrections (I don't think it was a flame), mine contains one of its own. It should be "is a transitive verb."

  38. lots of waste by Anonymous Coward · · Score: 0

    I used to work at a university that had several thousand workstations in the campus. Each one is required to have a public IP address. It was nice to remote desktop in, but very wasteful.

    1. Re:lots of waste by Anonymous Coward · · Score: 0

      You've been brainwashed into thinking NAT is a good thing. It breaks shit. It is terrible. Every workstation having a public IP is how thing are supposed to be done! This doesn't mean you shouldn't firewall, though.

  39. everybody just calm down by dieselpawn · · Score: 1

    Here's an idea.. Why not just slap another octet to the end of IPv4?? I think I am capable of remembering 3 lousy numbers rather than eight groups of four hexadecimal digits.

  40. just a few examples by marvinglenn · · Score: 2, Informative

    See http://www.iana.org/assignments/ipv4-address-space/

    019/8 Ford Motor Company 1995-05 LEGACY
    marvin@tribble:~$ host www.ford.com
    www.ford.com is an alias for
    www.ford.com.edgesuite.net.
    www.ford.com.edgesuite.net is an alias for a1200.g.akamai.net.
    a1200.g.akamai.net has address 96.17.109.74
    a1200.g.akamai.net has address 96.17.109.18

    013/8 Xerox Corporation 1991-09 LEGACY
    marvin@tribble:~$ host www.xerox.com
    www.xerox.com is an alias for www.xerox.com.edgekey.net.
    www.xerox.com.edgekey.net is an alias for
    e82.c.akamaiedge.net.
    e82.c.akamaiedge.net has address 72.246.128.108

    009/8 IBM 1992-08 LEGACY
    marvin@tribble:~$ host www.ibm.com
    www.ibm.com is an alias for www.ibm.com.cs186.net.
    www.ibm.com.cs186.net has address 129.42.58.216

    003/8 General Electric Company 1994-05 LEGACY
    marvin@tribble:~$ host www.ge.com
    www.ge.com has address 192.131.227.156

    048/8 Prudential Securities Inc. 1995-05 LEGACY
    marvin@tribble:~$ host www.prudential.com
    www.prudential.com is an alias for web.prudential.com.
    web.prudential.com has address 12.34.100.148

    Apple (17) and HP (15) have their public website within their allocation. Eli Lil(l)y (40) appears also has their public website within their allocation, but I have a hard time believing that they could ever need that many public IP addresses.

    So there... I just found an extra quarter million addresses. (5 x 2^16) Y'all can pay me by giving me my own /24.

    --
    The whores get mad when the sluts give it away for free.
    1. Re:just a few examples by deets101 · · Score: 1

      What is wrong with the E (I think) class addresses? They are, after all "reserved for future use".

      --

      --
      My parents went to Slashdot and all I got was this lousy sig.
    2. Re:just a few examples by totally+bogus+dude · · Score: 1

      Well, Ford and Xerox use Akamai for hosting their website; so their actual web front-end(s) live on different IP addresses than those returned by "www". We use "origin.ourdomain.com" as suggested by Akamai, but none of the big players seem to.

      129.42/16 is allocated to IBM as well, so they do in fact host their website within their own address space. They just have multiple address spaces.

      Then of course there's the issue that the internet is useful for things other than hosting websites, and there's no particular reason why any of these companies would want to physically host their own public websites anyway. They're not web design or hosting companies, so it's perfectly reasonable for them to have a professional hosting company host their sites. Not saying they all do, just that it's pretty naive to say "their website isn't within their allocated block, therefore they're not using their block".

  41. My Class C use... by HeyBob! · · Score: 1

    ... or /24 if you prefer

    I only use about 15 of the possible 253 ip addresses - the rest is wasted - I used to need them way back when there was no web multihoming though.

    This would make a good poll:
    Q: What percentage of your allotted IP space do you actually use?

  42. Decades? by Hikaru79 · · Score: 5, Funny

    The most comprehensive scan of the entire internet for several decades

    As opposed to the great Internet scans of the 30s?

  43. Unused addresses don't mean anything by FliesLikeABrick · · Score: 1

    Just because addresses are lying idle doesn't mean we don't have a problem coming up. There is no sane way to use these idle addresses without having the large networks (read: owners of /8s) renumber their networks in such a way that they can be sanely subnetted and routed somewhere else.

    Say a company has a /22. They may not be using more than half of their actual addresses, yet they may have assigned and be currently using every possible /24 in their allocation. Even if they are only using some of the addresses in a /24, it makes sense so that they can add machines to a subnet in the future without having to renumber everything to make certain subnets larger when they could/should have been that way from the start.

    That last sentence pretty much describes what would have to be done to make use of these "idle" addresses. Renumbering everything to make these addresses available in routable subnets doesn't solve anything, it just shifts the problem onto the network owners who would have to give up theses addresses now, as they'll find themselves running out of address space at some point.

    Then again, we could just move the whole world to one flat address space where any address can be used anywhere... (kidding).

    The fact that there is an end of site and a "finite" number of addresses means that IPv6 adoption is important and is going to happen. Keep in mind that this article also completely ignores the fact that NAT is hiding millions of computers that otherwise would have needed publicly-routable IPv4 addresses. With IPv6, this hack of a solution isn't needed anymore.

    We outgrew IPv4 a while ago, we just haven't hit the absolute limit of what we can do with it because of aids like NAT and hopefully we'll never have our backs up against that wall.

    1. Re:Unused addresses don't mean anything by FliesLikeABrick · · Score: 1

      And I didn't even mention the insanity that will arise in global routing when a whole bunch of MIT's /22s are taken from MIT and assigned to some companies in Europe. Route aggregation will go out the window unless (for example) MIT moved all of their stuff into the lower or upper half of 18/8 (or otherwise made room for it to be split off "properly). Even then, you're still splitting one route into two or more (granted it isn't as bad as pulling a bunch of /22s right from the middle of it)

    2. Re:Unused addresses don't mean anything by Toll_Free · · Score: 1

      I agree with you 100 percent, coming from the engineering side of networking back in the 90s and early part of Y2K (I left IT the day EnRon came apart, literally).

      What is the big deal about having not enough IP addresses (intentionally written with Engrish as my (secondary) primary langrij lol)?

      I mean, it is no big deal to have a complete web server farm pretty much have no more than 3 or 4 IPs, right? We figured out a LONG time ago how to have more than one domain parked on the same IP address.

      With NAT (And I'm NOT a fan of NAT, just proposing the other side, and asking for sane arguments against what I'm proposing (more to figure out if people agree with my decisions)), you can have 65 thousand HOW many services running on the same IP. And with HTTP redirects and being able to host more than one domain per IP, that sure does seem like a workaround to me....

      Again, this is more a Q for a bunch of different A's, as I wondered WHY NAT doesn't work. Yup, it's a pain in the ass, and I know for a fact that there are a few things that it DOESN'T work for, but for the rest, why? Just because it creates a bit more work for us (as the IT people that are making it work, not the programmers / etc... The actual guys who are never thanked, but always make the servers and such work) in setting up NAT tables?

      I've had to make the decision to apply for more addresses before, and had to talk my CIO OUT of going with NAT, but in the end, I ended up doing both.... That was in 97, company is still set up the same way, although the IPs (backbone) changed since I left.

      Let the flamings begin......

      --Toll_Free

    3. Re:Unused addresses don't mean anything by totally+bogus+dude · · Score: 1

      The main issue with running 65 thousand services on single IP is that we like having services listening on their customary ports. Both for aesthetic reasons -- most people don't want to advertise their site is www.example.com:3403, for example -- and for technical ones. For better or worse, most people restrict access to services based on well-known port numbers. If you run your website on anything but port 80 (or 443 for HTTPS) then quite a few people won't be able to access it.

      So you do virtual hosting. But that either requires all your clients use the same basic server software, or you run yet another service in front to proxy the request to the appropriate server. All of this works and works well, and can provide a lot of flexibility. But if you don't need that flexibility, why do it?

      I agree with those who say NAT is just a hack to work around the arbitrary shortage of IP addresses. I don't particularly dislike NAT -- although it does cause complications for some protocols -- but I see absolutely no reason to use it where it's not necessary. And it's only necessary to conserve IP addresses, which are an imaginary made-up resource to begin with. If we just imagined a bigger number to begin with, there'd be no reason to use NAT in the first place.

  44. I have 11 Class C's with lots of empty numbers by mschuyler · · Score: 2, Interesting

    and you can have them when you pry them from my cold, dead fingers. I would never be able to get them today, but way back in the early nineties they just gave them away. I had ten sites and wanted to start a Frame Relay network, so 'they' gave me a Class C for every site and one to knit them together. A couple of my sites had less than a dozen computers. Of course, these days even the copy machines have an IP address, so those sites are up around two dozen or so. One of them is doubling in space, so we'll be up to fifty or so. One of our sites closed, so that freed up an entire Class C, but our largest site is pushing the limits, so we moved the empty Class C to the large site. The numbers are scattered all over the place. .1 is always the router. Of course, the hubs have their own IP address. Public access stations started at .100 to be easily recognizable, but then the staff machines got up to .99 so we had to hop scotch over the public numbers and keep going with .200. The numbers are static because it's easy to track, and when we first started it seemed a reasonable path to take.

    Could we do this differently. OF COURSE!! There are lots of ways to free up a ton of space. Please don't lecture me on how to do it. I know how to do it. It's just that the system is working now. The system just kinda grew on us. When we started we had no idea copy machines would have IP addresses. Even the damn VoIP phones have IP addresses! That was a big hit on our numbers. Are refrigerators next? We had no idea we'd have fifty servers instead of three or four. Life has changed and because we are realtively 'wealthy' in terns of addresses, we had the flexibility to change with it.

    I look at our Class C's kinda like a fixed field database. There's a lot of air in there. It compresses really nicely if you need to, but disk space is cheap, so there's no real reason to conserve it.

    The thing is, even though we have a bunch of empty addresses, our experience shows that we're going to grow into them. We've already encountered congestion a couple of places. As soon as those new fridges show up we'll need some more numbers. My guess is before too long we're going to have to do some subnetting and consolidate a couple of our small sites into one Class C to free up the other one to use in a large site. That should work fine. I don't see any problems pulling that off. Of course, if we build another big site, we'll have to think through what to do very carefully. e'll probably do the new site like y'all want us to. We may not have any choice.

    But those Class C's are mine. I own them, and you can't have them back.

    --
    How about a moderation of -1 pedantic.
    1. Re:I have 11 Class C's with lots of empty numbers by Cajal · · Score: 1

      Under current RIR policy, you do not own IP addresses. You simply lease the right to use them.

    2. Re:I have 11 Class C's with lots of empty numbers by mschuyler · · Score: 1

      Policy be damned. How, exactly, are they going to take them back? Can you imagine an 'edict' that 'demands' a company give back an allocation they've had for 20 years and is entwined into their IT system like a tumor into a brain? Let's just say that the reaction to such a move would be met with an overwhelming response. I could see voluntarily giving back a totally empty Class C (or half a B, for that matter) if a company simply were not using it and had no realistic plans for using it in the future, but a Class C half full with numbers over the entire range? I don't think so. Prepare to go to court and spend a long time there.

      --
      How about a moderation of -1 pedantic.
    3. Re:I have 11 Class C's with lots of empty numbers by Anonymous Coward · · Score: 0

      Nothing stops you from continuing to use those numbers internally...however the rest of the Internet will no longer route traffic for those numbers towards you. Works fine so long as you do not need to access the Internet from those machines. But then if you wanted to access the Internet, you would conform to Internet standards...which would include returning numbers when the lease expires.

      It probably won't come to anything as harsh as that, eg just telling you that you are no longer to use those numbers as from a certain date. But I suspect that if it did, you would find that suing wouldn't help much. If it were me, I would be positioning myself to avoid any problems down the track. The mobile data networks I work with have been IPV6 capable for users since they went in, although to the best of my knowledge nobody has used the capability.

  45. Return the 10.0.x.x range!!! by Anonymous Coward · · Score: 0

    'cos I'm sure they aren't being used!

    1. Re:Return the 10.0.x.x range!!! by hob42 · · Score: 1

      Just don't touch the 10.1.x.x range, that's what I use at my house, and I don't want to share. ;)

  46. Won't SOMEBODY think of the appliances? by SoundGuyNoise · · Score: 2, Funny

    But my refrigerator, it needs, nay, craves an IP address, so it automatically orders my eggs and ravioli and orange creme soda, and orangutans, and breakfast cereals.....

    --
    You never expect irony, do you?
    Want to be a professional wrestler? Visit www.iyfwrestling.com
    @iyfwrestling
    1. Re:Won't SOMEBODY think of the appliances? by Anonymous Coward · · Score: 0

      Don't be so quick to write that off. ..wait, you eat monkeys?!

  47. This is news? by overshoot · · Score: 1
    Considering how many Class A netblocks there are (each with 2^^24 globally-routable addresses) how is this a surprise?

    Does anyone really believe that IBM has 16 million globally-addressable systems? Hell, no. IBM, like any sensible company, has a good firewalls. Likewise AT&T, the USDOD, etc.

    At a rough guess, more than half of the IPv4 address space is unreachable and doing absolutely no good for the assigned owners.

    --
    Lacking <sarcasm> tags, /. substitutes moderation as "Troll."
  48. Class-B unused for sale $500k by Anonymous Coward · · Score: 0

    I have a Class-B, totally unused for 8 years,
    for sale to the highest bidder,
    lowest offer I'll take is $500k, cash only, sorry
    yes, I really do own a totally unused class-B

  49. My experience with RIPE by Richard+W.M.+Jones · · Score: 3, Informative

    This story rings true. I worked for a company during the dot-com boom and just after which requested an allocation from RIPE (the European equivalent of ARIN). I was the designated & trained "LIR" (I think that was the term?).

    We received 8,192 IP addresses. We actually had them authorized to us in blocks of 256 addresses, and each time we needed another 256 we had to go back to RIPE and justify the expansion. However it is my understanding that the full 8,192 addresses were reserved for us.

    We ended up using 3 x 256 addresses, but after a later downturn in the fortunes of the company, even many of those went unused.

    I left the company many many years ago. However I notice the company that acquired it is still using those 3 x 256 addresses, and the original 8,192 are still reserved at RIPE. The IP addresses are even registered to the name of a director who was ousted when the company was taken over, at a street address that the company hasn't occupied for many years.

    Rich.

    1. Re:My experience with RIPE by Richard+W.M.+Jones · · Score: 1

      Ah who cares ... 212.57.32.0 - 212.57.63.255.

      Rich.

  50. Re:Pedantic Correction for the Headline by Anonymous Coward · · Score: 0

    Wrong. Lay/laying is a transitive verb, i.e., "lay down arms".

    Lie/lying has multiple meanings, including:

    5. to speak falsely or utter untruth knowingly, as with intent to deceive.

    3. to be or remain in a position or state of inactivity, subjection, restraint, concealment, etc.: to lie in ambush.

    http://dictionary.reference.com/browse/lie

  51. Simpler Politics by Midnight+Thunder · · Score: 4, Insightful

    lets just switch to IPv6, it's more functional and future proof

    Yup and it is probably much simpler. Trying to reclaim addresses involves political issues, finding out who to talk to, bureaucracy and some technical issues. Switching to IPv6 is about technical stuff and just getting going. You are going to have to switch to IPv6 at some point, so why spend energy twice?

    --
    Jumpstart the tartan drive.
    1. Re:Simpler Politics by lawn.ninja · · Score: 1

      Because only so much money exists? And there are these things in the real world called budgets... Just a guess though.

    2. Re:Simpler Politics by joeman3429 · · Score: 1

      We in america don't actually believe in budgets...
      National Debt Clock

    3. Re:Simpler Politics by Anonymous Coward · · Score: 0

      Because when push comes to shove, I can sell my individual ip addresses for 10s of thousands each for no actual work on my part.

  52. Good Luck by Anonymous Coward · · Score: 0

    I work for one of those companies. You try telling the 4th largest company in the WORLD that allocating an entire public /8 (that they paid for) on their internal network (and not using it externally) is bad juju and that they need to allocate money to readdress their entire global business and see how far that goes.

    Let's see, I can not spend any money and keep my existing setup or I float additional expense in this economey in order to make some geeks on the internet happy. Hmmmm.....

    1. Re:Good Luck by Garabito · · Score: 1

      Yes, because your company is the sole owner of its IPv4 address space; it's not that it was leased from an Internet authority like IANA or something; nor they can ask for your company to give them those addresses back... That would be communism, you know?

  53. NAT is a hack. by SanityInAnarchy · · Score: 2, Interesting

    Granted, it may be cheaper, in the short term, to use NAT than to upgrade to ipv6.

    But imagine if no one was using NAT anywhere. This would have two effects:

    First, techniques like Skype's UDP hole-punching would be completely unnecessary. You wouldn't even need a central server -- you could just use protocols like SIP the way they were meant to be used.

    Port forwarding would be a thing of the past. Far more peer-to-peer technologies would just work.

    Second, we'd run out of IPv4 a lot faster.

    --
    Don't thank God, thank a doctor!
    1. Re:NAT is a hack. by Spazztastic · · Score: 1

      You'd also be exposed to far more vulnerabilities if you didn't apply firewalls or system hardening.

      Would you really want your mission-critical servers to be open to the world? Sure, you may be the most qualified person to secure a network, but I still wouldn't want someone to have the ability to poke at my servers.

      Since you mention skype, which is what I use at home, I would never have my IP Phone open to the world or outside of a firewall. I want to know what goes in and out through my pfSense box. Even if IPv6 was deployed, I'd still rather have IPv4 internally.

      --
      Posts not to be taken literally. Almost everything is sarcasm.
    2. Re:NAT is a hack. by brunascle · · Score: 1

      First, techniques like Skype's UDP hole-punching would be completely unnecessary.

      Not completely. It would still be needed for firewalls that only allow outbound connections.

    3. Re:NAT is a hack. by entrigant · · Score: 2, Informative

      You might want to sit down for this...

      NAT is not a firewall.

      Try this:

      iptables -P INPUT Drop

      Suddenly you have the same false sense of safety using a public IP.

    4. Re:NAT is a hack. by Spazztastic · · Score: 1

      I agree, I don't look at it as one but I also have the firewall configured on my pfSense box.

      I apologize if my post gave the idea that I looked at it as one.

      --
      Posts not to be taken literally. Almost everything is sarcasm.
    5. Re:NAT is a hack. by TheRaven64 · · Score: 2, Insightful
      Rubbish. Which is more secure, of the following two options:
      1. A public IP address, which you use to run a published protocol, on well-defined ports, through a firewall that blocks everything except the authorised ports.
      2. A NAT'd IP, which requires you to do lots of tricks to bypass, preventing the firewall from being able to tell the difference between malware and VoIP traffic.

      This is exactly the option people have now. If you want something like VoIP, and both endpoints are behind a NAT (they usually are these days) you need to rely on something like Skype, which is a security nightmare (see the paper 'Silver Needle in the Skype' for more details).

      --
      I am TheRaven on Soylent News
  54. Re:Pedantic Correction for the Headline by NeverVotedBush · · Score: 3, Informative

    It's best, however, when you are laying someone else -- as in "I'm laying your girlfriend." "I got laid by your wife."

  55. Re:Wrong! Lying is the correct form. by nameendingwith · · Score: 2, Funny

    Once it has been laid, it is now lying.

    So in other words, there are no Slashdot users that are lying. If they say they are lying, then they are lying.

  56. Re:Wrong! Lying is the correct form. by Anonymous Coward · · Score: 0

    I believe many people get confused because the past tense of "lie" is "lay".

  57. Comment removed by account_deleted · · Score: 5, Funny

    Comment removed based on user account deletion

  58. I used to have a class C just for my cube. by sirwired · · Score: 1

    I work for one of those companies with a Class A address and we hand them out like candy internally. One of my previous jobs was doing network equipment support so my cube had a big 'ol stack of routers and switches that did nothing but talk to each other. Instead of me having to go through obtaining a new address every time I needed to add a new piece of equipment or test something, the powers-that-be just assigned me my own Class C.

    Ah, the joys of more IP's than we knew what to do with...

    The likelihood of any of those places giving up addresses (at least without some form of compensation) is probably pretty low.

    SirWired

  59. Why do we need so many ? by daveime · · Score: 1

    I don't get it ... I thought everyone was sharing 127.0.0.1 ?

  60. Rearranging Deck Chairs on the Titanic by Detritus · · Score: 2, Insightful

    This whole discussion is a waste of time. You aren't going to get any of these address blocks without an expensive and prolonged fight. Wasting valuable resources that could be used to advance a real solution, IPV6.

    Even if you "liberated" all of these address blocks, they would be quickly consumed by the natural growth of the Internet.

    NAT is not a solution, it is a malignant blight that must be destroyed. If you want a firewall, get a real firewall.

    --
    Mea navis aericumbens anguillis abundat
  61. Expansion expansion expansion. by goodmanj · · Score: 1

    TFA is moronic. Why? Here's an analogy: you're a librarian at a big university library. You notice there's lots of gaps and empty space on the shelves, so you "condense" things by packing all the books up with no gaps. Hooray, now they all fit in two rooms and you've got a whole room full of empty shelves!

    The next day in the mail, a new shipment of 200 new books arrives. You suddenly realize that you're going to either have to put all the new books together in the empty third room, breaking Library of Congress order and making them impossible to find, or reshelve every single book in the library.

    Oops.

    And *that*, my friends, is why MIT needs a Class A internet address (18.*.*.*).

  62. TCP/ICMP not a good way to do this by jimmyhat3939 · · Score: 2, Insightful

    TCP and ICMP is not a good way to test this. Plenty of IPs won't respond to a ping and don't have any TCP ports open for inbound connections (SYN flag set).

    --
    Free Conference Call -- No Spam, High Quality
    1. Re:TCP/ICMP not a good way to do this by Toll_Free · · Score: 1

      Yes, that's why professor has tenure.

      Because he HASN'T SEEN REAL LIFE IN > 18 YEARS (back when we all discovered turning ICMP reply off).

      --Toll_Free

  63. B2B: IPs meant to be unique, not just public by An+anonymous+Frank · · Score: 1

    Public IP addresses (ISP?) are needed to go from A to B on the Internet and back, private ranges get you around internally, and purchased address blocks ensure that business to business routes (private links between two partners) don't cause oddities in anyone else's networks.

  64. Re:Wrong! Lying is the correct form. by Thunder+BoB · · Score: 1

    > Please don't make fun. Yes, I perhaps have told a tall tales like most others here.

  65. Re:Wrong! Lying is the correct form. by Anonymous Coward · · Score: 0

    liar

  66. Re:Wrong! Lying is the correct form. by Phroggy · · Score: 1

    I remember it this way: "Now I lay me down to sleep" has a direct object ("me"). If there's an object it's lay, if not it's lie.

    Unless, as the AC pointed out, it happened in the past, in which case it's lay again. Bleh.

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  67. Here is the actual article and interactive map. by GlobalColding · · Score: 1

    If you want to see the original pop-up free article on the census is here - http://www.isi.edu/ant/address/ and there is a pretty cool interactive map here http://www.isi.edu/ant/address/browse/index.html . Enjoy.

    1. Re:Here is the actual article and interactive map. by tehIvyn · · Score: 1

      Very Cool! Thanks.

  68. Question their methodology by Locke2005 · · Score: 1

    Are these addresses lying idle, or merely configured to not respond to ICMP echo (ping) packets? 'Cause, you know, I'm pretty sure their test can't tell the difference...

    --
    I've abandoned my search for truth; now I'm just looking for some useful delusions.
    1. Re:Question their methodology by mysidia · · Score: 1

      Professor John Heidemann from the University of Southern California (USC) used ICMP and TCP to scan the internet.

      MILLIONS of IP addresses that are in use are behind a firewall, and don't necessarily want to communicate with you.

      In fact, thousands of big bad firewall admin may be sending complaints to the ISP providing connectivity to the server performing the tests about "hacking attempts" (Even though they were only port 80 probes).

      Just because an IP isn't publicly probable without knowing exactly the service that host provides (if any), does not mean it is unused.

      Workstations are the most prevalent type of host on the internet and may be closed off entirely from remotely-initiated probes for "security" reasons.

  69. Where the IPs are by Renderer+of+Evil · · Score: 1

    I've learned everything I know from xkcd

  70. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  71. The old purposely inflicted scarcity. by Yaa+101 · · Score: 1

    I think we first have to start forcing all owners of class A networks to move to class B networks and NAT (likewise for class B owners to move to class C networks). This should free up a lot of new to be used public IP addresses.
    There is no reason why internal networks should have direct external exposure through a public IP number, the internet is a collection of separate networks.

    1. Re:The old purposely inflicted scarcity. by mshannon78660 · · Score: 1

      Actually, as someone else pointed out, there are lots of good reasons. One in particular is B2B communications. Now, if both companies are using 10/8, you have to do NAT (and probably on both sides). This has a tendancy to break lots of protocols that you might want to use with a trusted partner. Having assigned address space on at least one side makes this easier (that way you only NAT the clients), but it works better if both sides are globally unique. Those addresses may not be publicly accessible (and so wouldn't show up in a scan like in the TFA), but they are really being used for their intended purpose. I think the people who wrote the article are confusing the Internet with the World-wide web - although related, they are NOT the same thing.

    2. Re:The old purposely inflicted scarcity. by sl3xd · · Score: 1

      Sure. YOU spend the billions of dollars to do that. How do you force them do to it? The only way is legally - and they know those IP addresses are worth billions of dollars. You'll pry the addresses from their cold, dead hands. And for what? A few years delay in the inevitable? It'll take longer than that to wrest the IP addresses from the companies.

      NAT is not a solution to the problem - it's taking one problem and adding another on top of it. IM/Chat programs, VoIP, P2P, and many other things are given no end of trouble due to NAT. NAT is already causing more problems than it's worth.

      There are really only two things NAT does:
      The first is letting a home user have more than one machine for her IP address, letting him get around ISPs that only allocate a customer with one IP address (so they can charge for additional addresses).
      The second is in deluding people into believing it makes a network secure.

      Here's a clue: Skype, bittorrent, and any of a host of other protocols BREAK THROUGH NAT, trivially. NAT does nothing to secure a network from attack; the methods to punch NAT are well known and frankly, have to be left open (or else users would complain that their apps won't work).

      There is only one solution to the problem of address exhaustion: Migrate to a protocol that has a larger address space. IPv6 is the obvious choice. Forcing people with blocks of "unused" IPv4 addresses only prolongs the inevitable - and only by a couple of years at that.

      --
      -- Sometimes you have to turn the lights off in order to see.
    3. Re:The old purposely inflicted scarcity. by mysidia · · Score: 1

      Just say no to NAT. The first problem is it is a non-standard bastardization of IP.

      NAT with overloaded addressing breaks any protocol your equipment doesn't know how to NAT properly.

      Many protocols such as HTTP are easy to translate, and it will seem to work seamlessly. Many are not.

      Secondly, NAT breaks communications where the NAT'ed host needs to be contacted first, before a connection has been built.

      These are ample reasons that NAT is not acceptable on real networks with diverse usage.

      And definitely not acceptable on research networks where new protocols are being run by some users.

      The internet is an open medium, and new protocols are being developed every day, that your equipment does not know how to NAT.

      Some protocols contain embedded IPs and cryptographically verified checksums. They cannot be NAT'ed.

  72. Isn't there a better way to do this? by damn_registrars · · Score: 2, Insightful

    It appears that all they did was ping every address they could, and then track which addresses responded and which ones did not. Consdiering how many systems are either configured to not respond to ping, or sit behind firewalls that stop the ping from getting through, this seems like a method of marginal value.

    Wouldn't there be a better way to query the addresses than this? In some areas, I suspect checking DNS records might be more informative if what you are looking for is which addresses are unused (though of course DNS isn't mandatory either).

    --
    Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
  73. How about class B's as well? by Anonymous Coward · · Score: 0

    Bank of America owns something like 26 class B subnets, most of which are used internally. There was a decision made in the mid 90's to use the public class B's internally as well as externally so that when BofA bought a company that was using a "private" subnet there would be no issues of overlap taking place when it came time to make the purchased company part of the Borg. However, BofA doesn't come close to using all of those address blocks. How about they pony up some of those spaces as well (and other big org's like BofA, you can bet, have done the same thing). Running out of addresses? Bah! It's pure and simple greed on the parts of the owners of these spaces and network and security folks who aren't smart enough to figure out how to deal with acquisitions.

    1. Re:How about class B's as well? by FlyingBishop · · Score: 1

      I go to a university with 3000 students that got a Class B to itself back in the 80's. No way we're using a significant number of those (and just about everything's behind a firewall.)

      Just the same, I don't think they should go into the pool, at least not until everyone's good and ready to switch to ipv6.

  74. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  75. You'd still need NAT anyway by Anonymous Coward · · Score: 0

    Even if the whole world went to IPv6 tomorrow, do you think ISPs like Comcast will stop charging people $7/month for each additional IP address?

    NAT is here to stay.

    1. Re:You'd still need NAT anyway by Cajal · · Score: 1

      Under the current proposals, each customer will get at least one /64. Is 4 billion billion IPv6 addresses enough for you?

    2. Re:You'd still need NAT anyway by j+h+woodyatt · · Score: 1

      Right now, they charge an additional fee for each DHCP lease you consume. Since DHCP6 has an IPv6 prefix delegation option, you can expect that your home gateway will get at least a /64, and probably a /56 or better (depending on the outcome of discussions in IETF around this active Internet Draft currently in the RFC Editor Queue.

      --
      jhw
  76. More oversight? by edmazur · · Score: 1

    Isn't one of the requirements of obtaining something like a class A network that the 16 million address space be mostly utilized either immediately or in the near future? Maybe tighten these restrictions and/or check up on these organizations more often to help prolong the IPv4 doomsday?

  77. Re:Wrong! Lying is the correct form. by Anonymous Coward · · Score: 0

    Once it has been laid, it is now lying.

    [insert relationship joke here]

  78. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  79. Re:Wrong! Lying is the correct form. by Anonymous Coward · · Score: 0

    Getting Layed is what happens when you have sex.

    Lying is what happens when slashdot readers are asked if they've had sex....

  80. DHCP Server Redundancy by qwertphobia · · Score: 1

    Assuming an organization uses DHCP to hand out public addresses... many DHCP installations have several banks of dynamic addresses so that if one DHCP server goes out to lunch there is enough address space to handle the maximum expected requirements of that network.

    --
    Never ask for directions from a two-headed tourist! -Big Bird
  81. Re:Wrong! Lying is the correct form. by Anonymous Coward · · Score: 0

    Hey, do you think you can educate people about the correct use of obsess?

    It should be used exactly like 'possess', but people don't get this.

    The correct usage:
    * I'm obsessed with trying to convert people back to the correct usage.
    * Getting people to use the verb correctly obsesses me.
    * If that person is obsessing me, he is in *my* thoughts and not the other way around.

  82. Futurama response by uberjack · · Score: 1

    Silence! I concur.

  83. Charge them for the unused ones by PineHall · · Score: 1

    We need to charge the companies for the unused or unseen IP addresses. If the addresses are unused or internal to the company then charge them $100 an address. Or let them put the unused ones back in circulation. We need to make it worth their while.

  84. !Suprising at all by kellyb9 · · Score: 1

    How is this the least bit suprising? I imagine many companies only use 10% of their address space.

  85. And then you have... by Anonymous Coward · · Score: 0

    ...idiots like the IT group on my campus that thinks every machine on the internal network for some reason needs a public IP address instead of using this 'new' technology called "NAT".

  86. This is a peer review paper. by kilocomp · · Score: 2, Informative

    Yes I am sure the researchers have no idea what a firewall is. And everyone is a network admin with their home routers...

    Of course these researches used logic to determine when a firewall is in place. One possible way would be to look at a subnet as a whole, if neighboring IPs are responding you can make a reasonable guess that other IPs should respond if binded to another node. This is a sampling of 4 billion, so no, individual circumstances where this doesn't hold up won't make a difference.

    Wait for the actual paper to come out during the conference. If your research with your home router shows this is an incorrect paper, you can call them out. After all this is what peer review is all about.

    1. Re:This is a peer review paper. by john_heidemann · · Score: 1

      A preprint of the paper is available
      at http://www.isi.edu/~johnh/PAPERS/Heidemann08c.html

      I encourage folks to review the actual, peer-reviewed paper before commenting on the methodology.

  87. That's a great idea.. by tjstork · · Score: 1

    I think they should pay me for them, to be honest.

    --
    This is my sig.
  88. Fail! by jimpop · · Score: 1

    Fail! How did this (video?) professor manage to use icmp/tcp to determine hosts, or the lack thereof, of IP space behind corporate firewalls? Curious minds may want to know...I for one call bullshit!

  89. Re: Lying by mordred99 · · Score: 1

    Contract was up, I was let go, I left the firm I was with to be with the firm I am at now because they were incompetent. It all happened within 2 days of one another, not lying .. just not giving all the facts.

  90. Severely Flawed by Anonymous Coward · · Score: 0

    As anyone who knows anything, Professor John Heidemann should fully well know that most big buisnesses BLOCK inbound ICMP TRAFFIC. Why? Because botnets use that to see if machines are alive, and will attack them if they respond.

    Face the facts, simply because a ip address doesn't respond to ICMP 'ping', doesn't mean it isn't being used.

  91. drill for more by Anonymous Coward · · Score: 0

    I was going to use the oil analogy. It's going to run out eventually, so why not switch to something better now before we run out?

    If we drill off the coast we'll be sure to find more IPv4 addresses.

  92. Re:Pedantic Correction for the Headline by Dekortage · · Score: 1

    True. If you're going to "GET layed" (as opposed to "PUT layed", I guess), then you are probably not "getting laid."

    --
    $nice = $webHosting + $domainNames + $sslCerts
  93. Re:Wrong! Lying is the correct form. by Anonymous Coward · · Score: 0

    The other day I lay down with a woman. I got laid, woohOO! As we were lying there, I told her I loved her. That was a lie.

  94. Re:Wrong! Lying is the correct form. by g1zmo · · Score: 1

    Just to add further pedantic detail to this conversation, these are properly known as transitive verbs (takes an object, i.e. lay) and intransitive verbs (takes no object, i.e. lie).

    I remember once telling my father I was "going to lay down", and he responded with something like "where exactly are you going to place these goose feathers?". That cemented it in my head forever.

    I know -- very dorky.

    --
    I have found there are just two ways to go.
    It all comes down to livin' fast or dyin' slow.
    -REK, Jr.
  95. the only way IPv6 is happening by circletimessquare · · Score: 1

    is if the government mandates it, like forcing television stations to go digital in february 2009

    even if all of the ipv4 namespace was exhausted, and people were shooting each other in the street for ipv4 addresses, still no one would go to ipv6

    the reason is: there is no audience there. and there is no audience there because there are no sites there. and there are no sites there because it costs so much money to upgrade your infrastructure... for the sake of a protocol no one is using

    its the same problem as: no job without experience, no experience without a job. the only solution is for the government to force us to ipv6 in a given timeframe. no other solution will work

    no one is going to voluntarily migrate, because there is no reward for doing so. you can reply there is a reward: solve address exhaustion. but you are not looking at the problem in the right perspective: individual versus community. this is a problem we all have, not an individual problem. therefore, there is no individual incentive to solve the problem. we either all go at the same time, or we don't go at all. no one is going to trickle over to ipv6, since its such a hassle and there is no reward for doing so, on an individual basis

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:the only way IPv6 is happening by sl3xd · · Score: 1

      You can already get to all of the internet on straight IPv6. IPv6 is surprisingly backwards-compatible, and everything gets to its destination - even if the destination doesn't talk IPv6, things like 6to4 allow everything to work seamlessly. Traffic stays IPv6 as long as it can, and then falls back to IPv4.

      Believe it or not, the guys developing IPv6 did their homework, and they did their job well. There is nothing to fear in IPv6 except ignorance.

      Incidentally, government did mandate the switch to IPv6. It more or less all became official when The US Government (which still controls the internet) mandated that DNS had to be fully available in IPv6 in early 2008.

      In the US, there's currently both the new ATSC and the old NTSC for TV. NTSC gets turned off in most areas in Feb 2009. But both are in use right now. But one is going away.

      IPv6 is pretty much the same story. Pretty much all the hardware (including the stuff used by ISPs and telephone companies) that uses TCP/IP can do IPv6. The same is true of the software - Linux, Windows, OS X, *BSD. Apache, SSH, IIS, NFS, kerberos, and many, many others.

      The hardware is in place, the software is in place. Anybody who wants to use IPv6 can do so if they're willing to crack a book. My ISP provides pure IPv6 service to those that want it - they don't advertise the fact, but it's there and they're grateful for the people who use it.

      --
      -- Sometimes you have to turn the lights off in order to see.
    2. Re:the only way IPv6 is happening by dwye · · Score: 1

      > even if all of the ipv4 namespace was exhausted,

      Neither IPv4 nor IPv6 have any namespace. They are numberspaces.

      Even if you know, other readers might not, so here goes the boring explanation:

      192.7.6.x is a numberspace (of Class C width, and I know that it is not supposed to be routed, it was just a demo), vs. bandit.netdestroyers.evilmasterminds.ORG, which is a namespace (well, a point in one).

      Namespaces are not yet much of a problem, except when someone else has your preferred name, like hp.com being owned by a printer company, rather than Henry Purcell, who wants it but hasn't enough money to make the company give it up, the evil domain squatters! Or hp-sucks.com being owned by HP (it may be, for all I know) rather than Hypobaric Products, Makers of Fine Vacuums (not cleaners, the really empty spaces) Since 1992. Or when someone wants to use an umlaut in the domain name, or any other character that is not in [A-Z0-9_\-], but cannot (at least from most browsers, DNSs, etc.).

    3. Re:the only way IPv6 is happening by totally+bogus+dude · · Score: 1

      I think you're mistaken. My ISP has recently set up an IPv6 broker for all their customers to use, and are in the process of working out how to neatly provide IPv6 along with v4 to their end-users. I think last I heard they can pretty much do this, but are waiting for router vendors to catch up and support it so it's just easy as IPv4 is today. Early adopters pave the way, and having to solve the problems they encounter makes it easier for those that follow.

      It doesn't just rely on ISPs to be that forward-thinking or interested enough in the technology to implement it just for the fun of it all, though. Eventually lucrative customers of big ISPs will start saying they want native IPv6 connectivity, so there's a good business case even for large publicly-listed ISPs to make sure they can support it when their customers want it. Because if they don't, their customers will go to other ISPs that can.

      You're right in that it won't happen overnight; it's an incremental process. That process is already underway though, and as more and more people start to prepare the barrier to entry will be reduced, and eventually most of the internet will be ready for IPv6, or even actively using it. It will take a long time before people are willing to set up IPv6-only websites, but it will eventually happen when the costs of reclaiming unused IPv4 addresses exceeds the potential cost of being unreachable to the ever decreasing IPv4-only internet.

      I expect we'll be operating dual-stack nodes for a long, long time though.

  96. My IP isnt idle, and Im working on keeping it busy by killmofasta · · Score: 1

    for at least the next 10+ years.

    torrents, emules, bears, and crusty limeys!

    ftp, atp, stp and just raw blast feed!

    Gimmie a D!

  97. Force IPV6 adoption by nrozema · · Score: 1

    If the US government gave out $40 coupons for IPV6 "converter boxes", we could get this thing done by the end of the year.

  98. not a good one to scan by jriding · · Score: 1

    OrgName: DoD Network Information Center
    OrgID: DNIC
    Address: 3990 E. Broad Street
    City: Columbus
    StateProv: OH
    PostalCode: 43218
    Country: US

    NetRange: 7.0.0.0 - 7.255.255.255

    --
    love the taste, hate the texture
    1. Re:not a good one to scan by mschuyler · · Score: 1

      That's 'cause every smart bomb has its own IP.

      --
      How about a moderation of -1 pedantic.
  99. Re:Wrong! Lying is the correct form. by Anonymous Coward · · Score: 0

    This is /. If you're saying you've been laid, then you're lying...

  100. Address space by wfstanle · · Score: 1

    First of all, its not 2^64 addresses, it's 2^128 addresses. To the layman, that is not very much of a difference.

    Do you have ANY idea how large 2^128 is? I have heard estimates that it is larger than the number of atoms on earth! I haven't done the math but it does not seem impossible.

    1. Re:Address space by afabbro · · Score: 1

      First of all, its not 2^64 addresses, it's 2^128 addresses. To the layman, that is not very much of a difference.

      Do you have ANY idea how large 2^128 is? I have heard estimates that it is larger than the number of atoms on earth! I haven't done the math but it does not seem impossible.

      For comparison, the number of atoms in the universe is estimated to be 10^80.

      --
      Advice: on VPS providers
    2. Re:Address space by Anonymous Coward · · Score: 0

      Roughly 3.4*10^38 or approx 340,282,366,920,938,463,374,607,431,770,000,000,000 addresses compared to 4,294,967,296 addresses. Just slightly larger....

  101. 2 things: by circletimessquare · · Score: 1

    1. you've contradicted your initial assertion that's plenty of consulting dollars in the migration to ipv6. you now say all the infrastructure in place. obviously, there's a lot more work to be done, and obviously, its not completely straightforward and easy. even for end users (calls from mom: "you open network properties and click what again? this is too complicated, why can't i just use the site like i always do?")

    2. finally, with ipv6, just as you will notice in february 2009, no one is going to use ipv6 or digital tv unless they HAVE to. and even then there will tons of complaints, even though its obviously better. you completely discount the inertia and comfort level and "good enough" mentality involved here

    ipv6 will never get out of the single digits on percentage of users, until it is mandated. if you refute that, you don't know much about human psychology

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:2 things: by sl3xd · · Score: 1

      I've already said - it is mandated, at least for all government sites (and possibly anything that gets federal dollars). The conversion is already underway.

      And in spite of the fact the there is a _lot_ of infrastructure in place for IPv6, there's still a lot of money to be made, because of one simple fact: The infrastructure can handle IPv6. It doesn't mean that the bulk of the minesweeper consultants who administer the networks know how to turn it on.

      In my experience, the vast bulk of that crowd isn't interested in learning any more than they have to - if they were, they would have gone on to a University, as the 2-year tech schools often cost more. "We cost more because we get you into the workforce faster."

      Being IPv6 ready is a lot like saying your car can burn E85 ethanol. It doesn't mean your car is burning E85, just that it can.

      So the money to be made is in knowing how to turn IPv6 on. It's not particularly difficult, but frankly, neither is IPv4, which people are more than happy to take months to learn to use. But just like IPv4, IPv6 requires somebody who knows how to do it - which eliminates most of the entire IT profession, who didn't learn it at their tech school, and aren't interested in learning it now.

      From a consumer's standpoint, IPv6 no worse than IPv4. Vista comes with IPv6 enabled, as does OS X. Most linux distros have IPv6 turned on by default as well. I'd argue it's even easier to configure a user's computer to use IPv6 than IPv4-- you don't need DHCP, and static addresses are the rare exception rather than the rule.

      If you plug a computer into a working IPv6 network, it's going to work. The only thing I had to do to get every computer in my house working with IPv6 is to set up my router so it would use IPv6. After that, they all received IPv6 addresses automatically - I didn't have to do a thing. They all automatically get addresses, DNS "just works", and all of the user programs "just work".

      The simple fact is that the only thing keeping IPv6 from being adopted is FUD and laziness - with one being used to prop up the other.

      I'd say that government mandates would help, but it won't actually be necessary - address exhaustion is a fact, and even with the best management, IPv4 won't last another decade.

      We don't have good network management for the Internet - that's been established already; heck, it's considered a virtue by many.

      Nevertheless, the lawful owners of these large chunks of IP addresses aren't going to let them go for free; they'll hold on to them to drive the price up. The longer they hold on to them, the higher the cost will be.

      I'd argue the only way they'll give up the addresses is one of two ways:
      1.) They're forced to, in court - it'll take longer for that to work its way through than SCO's various lawsuits (which are still ongoing). We'll be out of addresses by then, and will be forced to IPv6 out of necessity.
      2.) People deploy IPv6, driving down the cost of the block of addresses.

      --
      -- Sometimes you have to turn the lights off in order to see.
  102. This project proves what they don't understand by cdogg4ya · · Score: 1

    As someone else pointed out, there are numerous reasons out there that there is a lot of PUBLIC IP space that will not be reachable from the Inernet. Business to Business (B2B) where multiple companies networks need to talk to each other is the perfect example of this. B2B is becoming much more relevant in the days of outsourcing services and for service providers. Additionally there is a lot of infrastructure that is out there that uses Public IP space that will not respond to scans because they have been hardened not to do so. As someone pointed out, blocking ICMP THROUGH a router or firewall is a no-no, but blocking it destined to the device is just fine and is actually good practice. Now I totally agree where companies that were assigned a /8 and assigned every device a Public IP whether it needed it or not needs to be read the riot act and return it.

    START RANT ^^
    Those who just spout move to IPv6 have no clue. The world is not ready for IPv6 and my money is that we will not end up with mainstream adoption (and I mean every new consumer device and piece of software that comes out is IPv6 aware) for at least another decade. There is way too much to do and companies have just over the last few years really started networking everything.
    Nobody wants to go back and learn a brand new protocol for which you basically need to throw away 80% of what you thought you know. Finally, IPv6 only truly solves one problem that we have in IP networking today and that is the number of available addresses. We know for a fact in Ethernet that your not going to have several million devices in the same broadcast domain (VLAN) (and yes, I know some of IPv6 uses multicast) so we are going to be orders of magnitude more wasteful than we can possibly be with IPv4. The only way around it is to subnet which past a /80 you lose the ability to do autoconfiguration which basically renders IPv6 useless.

    END RANT ^^

  103. Gulity as charged by pseudorand · · Score: 1

    I work at a university and we (my department) give everyone public IPs simply because that's the way they've always done it. I've pointed out that maybe we could switch to 10.'s for all but a select few and even get some added security from the effort (you can't hack it if you can't address it), but my boss is firmly on the leave-well-enough-alone page. And he's probably right. Unless we grow quite a bit unexpectedly, we've got plenty of IPs (/23) for our needs and our firewall has served us well so far. It would just be unnecessary work to fix something that ain't broken.

    You may hate me now.

  104. So what? by rabtech · · Score: 1

    First, the obvious as everyone has already pointed out: lots of firewalls and routers drop ICMP or don't respond to pings, so this survey is useless.

    Second, so what? Even if it were a valid survey, a few million more addresses aren't going to help the situation. Every proposed stopgap just extends the exhaustion date a year or less into the future.

    To me, the failure of IPv6 is that it is really an entirely different protocol sharing a similar name. If IPv6 had simply extended the 32-bit address space it would be a much more straightforward upgrade from IPv4.

    --
    Natural != (nontoxic || beneficial)
  105. Microsoft doesn't have a Class A by Anonymous Coward · · Score: 0

    Those were sold to forward-looking companies like IBM, HP, DEC, and Apple.

    Microsoft didn't "get" the Internet at the time.

  106. Methodology in full by MadMidnightBomber · · Score: 1

    sudo nmap -T insane -O 0-255.0-255.0-255.0-255

    --
    "It doesn't cost enough, and it makes too much sense."
  107. BULLSHIT!!! (look up ""STEALTHed" ports) by Anonymous Coward · · Score: 0

    This is BULLSHIT!!! Everyone with decent security (e.g., they set all ports to stealth) will appear as a vacant IP address to these morons.

    Andy Out!

  108. Maybe some of them are hiding by John+Jorsett · · Score: 2

    My address is behind a firewall that doesn't respond to unsolicited incoming packets. It's in use, but you'd never know it from the outside.

  109. apologies, i meant numberspace, i wrote namespace

    however, as you have explicated, the namespace issue is out there as well, although less to do with exhaustion and more to do with collision

    i would add to your explication that countires such as china whose "solution" to nonascii domain names is to extend the name space into other character systems, do so at the peril of cleaving the internet. of course, for governments who wish to keep their citizens uninformed and insular, this is not a "problem." and even if chinese ideograms were acccepted part sof the namespace, western users would be less likely to visit, simply out of a lack of familiarity, which breeds exclusion. and of crouse it doesn't do anything really about name collisions, as hp is not going to solve its problem by buying the han ideogram for hp

    as it is, the chinese have no problem adding 26 more characters to their collection of thousands of han characters they need to remember, so no real exclusion is happening the other way when you keep it the ascii character set as a hard limit

    you could of course say that even if you preserve an ascii character set for the internet namespace, you've won a hollow victory since the website might be in a foreign language and so the exclusionary walls are still in place. but you have at least preserved the common framework across which future exchanges of ideas might still take place. less walls is always better

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  110. "millions" is a drop in the bucket. by ChrisA90278 · · Score: 1

    Let's see now. There are on order of a few billion IP addresses and on order of a few million of them unused. That works out to abut 0.1 percent un-used. In other words 99.9 percent are in use.

    "millions" is not enough when you need billions. In fact it is thousands of times not enough

  111. Here's a true story by Anonymous Coward · · Score: 0

    A billion years ago - or so it seems - there was a company that was able to finagle a class B internet address.

    There were about 50 people in that company.

    Yours truly was the network administrator.

    However, as things go, that company split apart into two groups: company A and company B.

    Company A went off to do stuff, while yours truly went with company B. The class B address was supposed to go with company A. However, company A went kaput, and never really put their name on it.

    Fast forward: I get bored at work, and decide to look at who got my old address space. Surprisingly, I still have it.

    So, I talk with the legal representative of company A, and he claims it to be an asset of the company. If we can sell it, I get a percentage.

    Here's the thing - if I let IANA know, and legal representative finds out, I fear that my little tushy might get sued. I really, really don't want to get sued.

    As a result - class B address sits idle. And I am ashamed.

  112. IPs are wasted frequently by Eil · · Score: 1

    I've worked for two companies now (one an ISP, one a web host) where every server, desktop, laptop, printer, and wireless client in the building was given an "Internet" IP and then firewalled off from the Internet rather than being given a "private" IP (10.x.x.x or 192.168.x.x) and placed behind a NAT. Why? Apparently, no other reason than for the fact that they can. I've tried explaining to managers at both companies what a poor idea this was but they didn't care.

    The web host I worked at also wastes IPs like no tomorrow. They'll put 1024 IPs in a VLAN and then stop assigning IPs to new servers once it's 75% full so that they don't run out of IPs to assign to existing customers. Which is fine, except that the vast majority of customers never request anywhere near that amount.

    There have got to be many other companies that just throw away IPs like this. If we really are going to run out of IPs in the next few years, then ARIN really needs to start charging more for the use of IPs or make it harder for companies like the above to keep grabbing large chunks of IPs and just sit on them.

  113. lol "minesweeper consultant" by circletimessquare · · Score: 1

    i'm going to borrow that phrase from you, that's hilarious, thanks ;-)

    however right or wrong you comments are (and i agree with most of what you said) it just makes resistance to mandating the change to ipv6 even less potent: its not so hard, you insist. well then good! lets bank your assertions

    because in reality, my pointing out that ipv6 has to be mandated (or, rather, to qualify your comments, that the death of ipv4 has to be mandated) has less to do with technical truths than with human psychological truths

    so i concede all of your technical points, regardless of their truthfulness or not. for one, because you are mostly right, but mostly because my point about human psychology is the real meat of my observation

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:lol "minesweeper consultant" by sl3xd · · Score: 1

      my point about human psychology is the real meat of my observation

      I mostly agree with the human psychology factor: People in general resist change with vigor; more accurately, they go with what works until it doesn't work anymore. It seems to come down to running out of options. A government mandate does exactly that - it eliminates options in a way people permit.

      Running out of addresses is another way to exhaust options in this case - and is much more chaotic than a government mandate.

      In something in a different vein: the thought occured to me - how likely is it that the companies that have large blocks of IPv4 addresses actually want to hold on to the addresses, and not for their own gain?

      Think of it - large tech companies, many of which helped invent both IPv4 and IPv6, may want to force IPv6 adoption, simply because they may feel it's the right thing to do. What if they see giving back those block addresses as hurting their customers in the long run?

      Yeah, I didn't think so either... they'll probably just want to hold on to them to try to make a buck...

      --
      -- Sometimes you have to turn the lights off in order to see.
  114. Lieing idle. by Anonymous Coward · · Score: 0

    Perhaps they are lieing idle. Not every IP device will respond to unsolicited IP traffic.

  115. Re:Pounce! by MadnessASAP · · Score: 1

    Sure it is, it's a subnet of the /0 network.

    --
    I may agree with what you say, but I will defend to the death your right to face the consequences of saying it.
  116. IPv6 and the developing world by cenc · · Score: 0

    I have been working in developing countries on the fringe of the internet for about 10 years now. You would be surprised at what problems this would cause. Places where very old computers are new, windows 98 is still around, network admins can hardly do much more than configure dhcp, a lot of things will break if IPv6 is suddenly forced. Among other things I know hospitals, stores, government servers that will not be able to make the switch because they can not afford to and the "computer guy" does not know how to make the switch.

  117. Here's why: by 3vi1 · · Score: 1

    Companies buy and merge with companies.

    Even though 99% of your company is behind a firewall, are you going to number your headquarters, plants, and sales offices using 10.0.0.0 - 10.2.255.255? Or... use those three Class B's you have registered to make them truly unique?

    Which way is more likely to be mergeable *immediately* with your new 4 billion dollar acquisition?

  118. IPv4 sucks but it could be extended to last long by Herby+Sagues · · Score: 1

    It would be fairly easy to implement some extensions that could make IPV4 last much, much longer. Basically, we have DHCP to make address usage within a range more efficient. With fixed IP we frequently had low usage of IPs within a range, often well below 50%. With DHCP we have reached nearly 100% allocation rates. What we need is a new protocol, which I would call Dynamic Subnet Configuration Protocol (DSCP) that would assign subnets on demand to DHCP servers. Once implemented a DHCP server would not be configured for a fixed range, but would be configured to ask for a subnet of a specific size (which could be adjusted dynamically depending on the allocated addresses) to it's (ISP provided) DSCP server. The DSCP server would in turn negotiate ranges with upstream DSCP servers. That way, companies would only use ranges as large as needed, and no addresses would be wasted. With over three billion addresses to use, even not counting private addresses (which should cover the vast majority of PC addresses) we should have enough for a long time even without IPV6. Now, DSCP alone (and the adaptation of DHCP servers) would not be enough. We would need also some autoconfiguration tools to insure connectivity during IP range reassignation (including the necessary tools to insure proper routing between the two addresses, maybe temporary routing capabilities could be incorporated into the DHCP service, or autoconfiguration of routers and network equipment could be integrated). Easy? Definitely not. Doable, hell, yes, a few orders of magnitude easier than deploying IPV6 worldwide. And while it wouldn't have the other advantages of IPV6, compatibility would be a given and no clients would need to be modified. So who's writing the RFC?

  119. Nortel Networks (aka BNR) using 47.0.0.0/8 by Anonymous Coward · · Score: 0

    16 million IP addresses for just 32,000 employees ???

  120. Big Corps have WAY more than they need or use... by dublin · · Score: 1

    There are a LOT of unused and unneeded V4 addresses out there. I think a reasonable effort at ectracting them could easily free up enough V4 addrs to last for another decade or two at current use rates.

    Here's how I know: Back in the early 90's, I managed Chevron's transition to TCP/IP. Unfortuantely, it wasn't long before the Chevron Telecommunications Division folks got into the act, and working with Cisco, they managed to get TWENTY-THREE Class B networks assigned. (To be fair, the clueless Cisco SE's had told them they needed that many, so CTD wrote up a long, and presumably persuasive, application explaining how the world would end if they didn't get this completely ridiculous block of IP addresses. When I left the company in 1994, they were using no more than about a dozen Class-C equivalent subnets even at the largest sites, and many had an entire class B to handle only a few dozen nodes. The clueful among us all felt embarrassed and guilty about using that many addresses, but we used them anyway - heck they were assigned, so why not?

    Although Chevron's glut of IP addresses isn't the norm, I'd also bet it's not unique - that clueless Cisco engineer designed similar networks for lots of other big companies during that time, too...

    --
    "The future's good and the present is nothing to sneeze at." - Roblimo's last ./ post
  121. Re:Pounce! by Anonymous Coward · · Score: 0

    With CIDR nothing is a subnet -just a "net".

  122. in the 70s by Anonymous Coward · · Score: 0

    Just have to mention that Norway and Britain got connected to the net (it was Arpanet then) in 1973.

  123. Blame ISPs... by frank_adrian314159 · · Score: 1

    My ISP only lets me buy static addresses in blocks of five. I would be happy to have a single static address, but there seems to be some sort of problem with that. As such, four of my addresses are lying fallow.

    --
    That is all.
  124. ICMP? by Toll_Free · · Score: 1

    I, like most of my network engineers, turned off ICMP reply back in, what, the 90s?

    Sure this guy knows what He's talking about? I mean, if an address doesn't respond to ping, it must be dormant.

    What a FUCKING moron. My only guess is anus #1 has tenure, therefore can't be fired for not knowing what the FUCK He's talking about.

    --Toll_Free

  125. Re:Wrong! Lying is the correct form. by lumenistan · · Score: 1

    Agreed. Example: Hi, I'm Chef. I want to lay you down by the fire...

    Actually, that's altogether another use of lay, nevermind.

  126. please update your statistics by Anonymous Coward · · Score: 0

    I have pretty paranoid firewall, so I bet he was not able to scan my IP. So, please change your statistics -1, because my IP is used, you just have no way to see that.

  127. Maybe the reason its not implemented is that it is by Anonymous Coward · · Score: 0

    abundantly available.

    I mean, how can the greedy masters of the people make any profit out of a resource in almost infinite free supply?

    So maybe this is one reason why it's not exactly pushed.

  128. Routing by marcovje · · Score: 1

    IPV6 is not just more addresses, but also simplification of routing.

    Attempts to reuse will possibly break compatibility (which breaks the use of not switching in the first place), and further increase routing by fragmenting the IPV4 space (and thus routing tables) even more

  129. The same old question... by Douglas+Goodall · · Score: 1

    Back in the day, large companies wanted every desktop to have a visible routable address. That was before we considered whether that was even a good idea. Since then NAT has saved our butts and management has come to see that all computers don't have to have visible addresses. Moving to IP6 just puts us back in the old place where we can all have visible addresses again, and we can consider whether that is a good idea. IMHO, most companies don't need more than a few visible addresses for visible servers. Client machines can all sit inside NAT'ed subnets and do just fine.

  130. Flawed study... by bwcbwc · · Score: 1

    Considering the number of firewalls that block internet traffic and silently drop ICMP requests into internal corporate networks, how the heck can he conclude that addresses are unused when he performs a scan from the internet?

    WAFI

    --
    We are the 198 proof..
  131. Heres the flawed car analogy! by Dan541 · · Score: 1

    So if some kid nicks your motor you should just forget it and buy a new car. Your probably going to buy a new car at a later stage anyway, so why spend the energy twice?

    --
    An SQL query goes to a bar, walks up to a table and asks, "Mind if I join you?"
  132. Pointless by Anonymous Coward · · Score: 0

    Even if we reclaimed every single IPv4 address that is known to be idle/abandoned (by much better surveys than this one, which is seriously flawed), it would buy us only 6-12 months at the current consumption rate -- and would cost a ridiculous amount of money, mostly in legal fees. It won't save us from having to move to IPv6, just change when we have to pay that cost, too.

  133. I must admit, that the survey probably found... by DaveHowe · · Score: 1

    That none of the hosts I admin responded to ping. Personally, I think blocking ping at the firewall a useless security technique if I am responding to http or IKE packets, but the expensive security firm we hired to audit us pointed proudly *every single time* to that response as being a security issue, so I got sick of having to argue it out and just blocked inbound icmp that wasn't a response to an outgoing query.

    Even if it didn't, which host would they expect to reply? most of my IP space is overloaded - if I have http and smtp open on the same IP, you can bet a bundle they aren't going to the same internal host, and the ASA isn't going to be responding to ping on behalf of the NATs it hosts.

    If that wasn't bad enough, back when I had service from Demon Internet's business DSL service, they blocked all icmp even if you wanted it - that made monitoring line uptime a pain for our monitoring software back at head office, and led to us changing provider.

    What it comes down to is that a pingsweep of the internet will tell you how many IP addresses respond to pings - no more, no less.

    --
    -=DaveHowe=-
  134. Minor Correction by Kadin2048 · · Score: 1

    I said:

    So even under the best circumstances where we recovered all the old IPv4 allocations, we wouldn't necessarily be buying ourselves as much time it might appear (by dividing the burn rate by the total available pool)...

    What I meant was:

    So even under the best circumstances where we recovered all the old IPv4 allocations, we wouldn't necessarily be buying ourselves as much time it might appear (by dividing the burn rate into the total available pool)...

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  135. Re:IPv4 sucks but it could be extended to last lon by catxk · · Score: 1

    Sorry, I didn't read your entire post, I just want to thank you for proving my point.

    --
    Don't be crazy anymore!