Slashdot Mirror


China To Run Out of IPv4 Addresses In 830 Days

JagsLive writes "China is running out of IP addresses unless it makes the switch to IPv6. According to the China Internet Network Information Center, under the current allocation speed, China's IPv4 address resources can only meet the demand of 830 more days and if no proper measures are taken by then, new Chinese netizens will not be able to gain normal access to the Internet. Li Kai, director in charge of the IP business for CNNIC's international department, says that if a netizen wants to get access to the Internet, an IP address will be necessary to analyze the domain name and view the pages. At present, most of the networks in China use IPv4 addresses. As a basic resource for the Internet, the IPv4 addresses are limited and 80% of the final allocation IP addresses have been used."

69 of 619 comments (clear)

  1. 830 days? China? by suso · · Score: 5, Informative

    Try the whole world. According to this counter, the world will be out of IPv4 addresses in 768 days.

    1. Re:830 days? China? by ohxten · · Score: 5, Funny

      Really? I thought there was a separate internet in China...

      --
      Need an automatic screenshot taker? Try here.
    2. Re:830 days? China? by Van+Cutter+Romney · · Score: 4, Funny

      Try the whole world. According to this counter, the world will be out of IPv4 addresses in 768 days.

      So the world runs out of addresses before China runs out?

      Did the Chinese government move themselves to outer space?

      --
      Help a man when he is in trouble and he will remember you when he is in trouble again.
    3. Re:830 days? China? by morgan_greywolf · · Score: 5, Informative

      There would be a lot more available addresses if companies that were given entire /8 blocks in the 80s and 90s (Ford, IBM, AT&T, Halliburton, etc.) were to give back those blocks. Most of those companies aren't even really using their /8 blocks anymore, with most of the addresses going unadvertised.

    4. Re:830 days? China? by Anonymous Coward · · Score: 5, Funny

      Shame Lehman didn't have a /8 block.

    5. Re:830 days? China? by mollymoo · · Score: 5, Insightful

      If 25 companies (are there even that many with /8s?) gave back their entire allocation, that would still only add 10% to the pool. That might buy a little time (a year, if we're at 80% and have two years left), but it's hardly going to solve the problem.

      --
      Chernobyl 'not a wildlife haven' - BBC News
    6. Re:830 days? China? by Prof.Phreak · · Score: 5, Funny

      Did the Chinese government move themselves to outer space?

      Nop. They've enabled NAT on their national firewall.

      --

      "If anything can go wrong, it will." - Murphy

    7. Re:830 days? China? by Anonymous Coward · · Score: 3, Insightful

      A year is a lot of time. Think how much cheaper computers/routers get in a year. That's a lot of expense saved if they can delay switching over for a year.

    8. Re:830 days? China? by Midnight+Thunder · · Score: 4, Insightful

      A year is a lot of time. Think how much cheaper computers/routers get in a year. That's a lot of expense saved if they can delay switching over for a year.

      Its simpler if people just started accepting that IPv6 is going to happen and adjust accordingly. For me its like having to accept Y2K was going to happen and acting accordingly. Believe me its much simpler to code the applications than go through the politics, and possibly technical issues, of getting someone to give back a block they don't appear to be using.

      Get your ISP and your router manufacturer to provide you an IPv6 solution. That too is probably not easy, but if we all start making noise then they will start doing something - hopefully.

      --
      Jumpstart the tartan drive.
    9. Re:830 days? China? by philspear · · Score: 3, Funny

      So the world runs out of addresses before China runs out?

      Did the Chinese government move themselves to outer space?

      In communist china, IPv4 addresses run out of YOU.

  2. Uh Oh! by Smivs · · Score: 5, Funny

    Sounds like it will be easier than ever to ring the Wong number!

  3. Normal 'net access? by i.r.id10t · · Score: 5, Interesting

    Do any Chinese citizens even have "normal" 'net access now? Thought NAT was used heavily, not to mention the GFWOC

    --
    Don't blame me, I voted for Kodos
  4. Meet With Congress by mfh · · Score: 5, Funny

    To get a quick infusion of 700 billion IP4 addresses -- NOW!

    --
    The dangers of knowledge trigger emotional distress in human beings.
  5. What is the point in having a public IP address by jeffmeden · · Score: 5, Insightful

    When your WHOLE COUNTRY is behind a firewall? NAT the hell out of that! Flatten it to a /8 network in 10.0.0.0 and put it all behind one public IP. Problem solved!

    1. Re:What is the point in having a public IP address by Artraze · · Score: 5, Informative

      > When your WHOLE COUNTRY is behind a firewall? NAT the hell out of that!

      The firewall is more figurative than literal. My understanding is that it basically bans certain IPs/domains. That can be done with a stateless system, while a true NAT/firewall would need to track all packets of all connections of all users. Not impossible, but insanely expensive. Plus it would have the unpleasant side effect of actually firewalling China (i.e. no incoming connections), whereas now they just don't let you view certain things.

      The whole point is largely moot anyway. First, as was pointed out above, the entire world is estimated to run out in about 780 days, so they've apparently got more time then the rest of use. Second, the primary usage of IPs comes from blocks assigned to institutions and businesses, with the latter _requiring_ incoming connections. Could a business have one public IP and NAT/load balance their servers and whatnot? Sure, but they could always switch to IP6, which is gonna be a lot cheaper than all these NATs

  6. So will the Interweb Gods force IPv6... by Ortega-Starfire · · Score: 4, Interesting

    Or will they just open up reserved addresses or something stupid like that?

    --
    ---- Liquid was a patriot ----
  7. Netizen? by Anonymous Coward · · Score: 5, Insightful

    Netizen is really stupid word, we really don't need more buzzwords.

    1. Re:Netizen? by jbeaupre · · Score: 5, Funny

      Worse, they are using "netizen" to describe people who aren't on the internet. Kind of like calling someone a pilot if they would someday like to fly a plane.

      --
      The world is made by those who show up for the job.
    2. Re:Netizen? by Ritz_Just_Ritz · · Score: 4, Funny

      One World, Two Internets.

      It's got a nice ring to it. LOL

    3. Re:Netizen? by Ambiguous+Coward · · Score: 4, Funny

      Kind of like calling someone a pilot if they would someday like to fly a plane.

      Come now, this is Slashdot. It's actually more like calling someone a car mechanic, when they would some day like to work on cars.

      -G

      --
      Their may be a grammatical error, misspeling, or evn a typo in this post.
  8. Q: Why is starting in the Subject: line annoying? by DNS-and-BIND · · Score: 5, Funny

    A: Because it breaks the flow of a message.

    --
    Shutting down free speech with violence isn't fighting fascism. It IS fascism!
  9. HP by QuietLagoon · · Score: 5, Interesting
    When HP acquired Compaq, HP also got DEC's /8 block of IP4 addresses. Now HP has at least two /8 blocks of IP4 addresses.
    .

    C'mon HP, be a good netizen and give back the bulk of those IP addresses. Try using NAT instead of hoarding IP addresses that others so desperately need.

    1. Re:HP by fprintf · · Score: 5, Interesting

      Sorry, I should have previewed!

      If I were HP (or Ford or AT&T), I wouldn't be a good "netizen" before giving consideration to what the blocks of /8 addresses are worth. If they wait another 365 days or so, perhaps folks will start getting desperate enough to pay for them. Can you imagine the value those addresses will have to a rapidly expanding internet enabled population, like China, that also has the means to pay for it? It might be a whole lot cheaper for China to buy the blocks than implementing iPv6, even at an exorbitant, over-the-barrel rates HP might be able to get.

      On the other hand, what is being a good player in the internet enabled worth anyway? Is there some intrinsic value in being good, or using the Google philosophy "Don't be evil"?

      I say hold out for a while.

      --
      This post brought to you by your friendly neighborhood MBA.
    2. Re:HP by Amouth · · Score: 4, Interesting

      on top of that if they would redo ssl so thatyou can support host headers that would allow allot of consolidation of webservices/sites by farm hosters..

      personaly i think we are all just too lax about dealing with IP's..

      --
      '...if only "Jumping to a Conclusion" was an event in the Olympics.'
  10. China will be first to use IPv6 by QuoteMstr · · Score: 5, Insightful

    I predict that we'll see China begin to use IPv6 addresses before most other people. Why?

    • Extreme scarcity of IPv4 addresses: China gained internet access well after the era of enourmously wasteful address assignment ended.
    • The great firewall is always set up as a traffic relay. Not only does it provide a natural point to set up an IPv6->IPv4 NAT gateway, but running IPv6 internally makes it that much more difficult for dissidents to bypass the firewall.
    • China's strong central state would allow mandating of IPv6 and near-instantaneous implementation.
    • Chinese sites are accessed by relatively few non-Chinese. Therefore, the penalty for running an IPv6-only site inside China would not be very great.

    Granted, I'm no fan of China's human rights policies. But it definitely has an advantage in terms of adopting IPv6. Hopefully, when China switches protocols, it'll catalyze the rest of the world to do so as well.

  11. In other news by augustz · · Score: 5, Interesting

    Slashdot runs it's 15th story about IP addresses running out "real soon now". The first was something like 5 years ago :)

    These stats ignore the fact that there are huge available allocations that can go behind NAT's. An ISP can NAT big chunks of its user network. Charging even a modest amount per IP would free up huge numbers of IPs. There are abandoned blocks (companies out of business) and wildly oversized blocks (MIT etc).

    Plus, we've been hearing these stories for years. The idea that the internets resources are going to become ipv6 anytime soon is unlikly. So folks are going to figure out a way to manage the existing pool, where there is lots of room for improved efficiency.

    Fun to keep on reading these stories... they're always written as breaking news :)

    1. Re:In other news by fabs64 · · Score: 3, Insightful

      Not a week goes by where someone doesn't trot out a new statistic on how P2P uses the vast majority of bandwidth on the internet. And you suggest NAT will be the solution to limited IP addresses.
      *sigh*

  12. The worst part is-- by straponego · · Score: 4, Funny

    They're even running out of RFC 1918 addresses.

  13. Don't worry... by flowerp · · Score: 5, Funny

    the LHC will end it quicker than that. They estimate some 90 days until they've got their repairs done ;)

    --
    --- Eat my sig.
    1. Re:Don't worry... by Hal_Porter · · Score: 3, Funny

      Do they take PayPal? Would a donation speed things up?

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
  14. They'll just do what they always do by Centurix · · Score: 5, Funny

    Impose a one IP address per family rule...

    --
    Task Mangler
  15. Why would China want to fix this? by FireStormZ · · Score: 4, Interesting

    Seriously their government is hell bent on controlling what goes into and out of that nation and what better way to do that than by forcing people to use a proxy..

    --
    "Ahh! Arrogance and stupidity in the same package, how efficient of you!" --Londo Molari
  16. It's more annoying if subject and post don't... by clickety6 · · Score: 5, Funny

    Pease porridge hot
    Pease porride cold
    Pease porridge in the pot
    Nine days old!

    --
    ----------------------------------- My Other Sig Is Hilarious -----------------------------------
  17. And what does that buy us? by SmallFurryCreature · · Score: 4, Interesting

    IP4 doesn't have enough addresses, of course a managers solution is to put of the inevitable so that it happens on someone elses watch rather then taking the time we got now to develop and implement a solution.

    IF pushing IP6 doesn't work in the roughly 2 years remaining THEN we can use the buffer of under-used blocks as a last reserve. if we use the reserves now, and do nothing then we still have the same problem, just a bit further away but this time with no reserves remaining and no work chance of it being solves in time.

    You should run for president, you would do well with your solutions.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

  18. NAT is not a solution by QuoteMstr · · Score: 5, Insightful

    NAT is not a solution. It's a huge, gigantic clusterfuck of a problem. Some people only started their careers after NAT was widespread, so they can't imagine how wonderful the world is without it. The internet is much simpler when you can assume that all nodes can directly address all other nodes.

    Look: this is what we've done.

    In the beginning, each endpoint of a TCP (or UDP) connection looked like this:

    [octet][octet][octet][octet][16-bit port]
    [(------- host-------------)(--service--)

    Each octet was routed hierarchically, and the port acted as an additional level of routing within a single node.

    With CIDR, the model moved to this:

    [32-bit opaque address][16-bit port]
    (-------host----------)(--service--)

    This change didn't hurt anything, aside from an increase in router complexity. Allowed the 32-bit address space to be used much more efficiently.

    Now with the IP address shortage, the situation looks like this:

    [48-bit address]
    (----?---------)

    Note how we've lost the distinction between host and service and smushed them all together into one huge opaque number. We've caused ourself lots of problems with this:

    1. One can no longer tell which service is being used based on part of an endpoint address (i.e., the port.). Firewalls, proxies, and so on become much more complicated.
    2. Only part of the endpoint address is provided by DNS. (I'm ignoring SVR records, which nobody uses.) Thus, part of the address needs to be hardcoded:
      • Every damn piece of software has to have a knob to control what port to use.
      • When software is too much trouble to configure, we use hardcoded port-parts. Consider SMTP and HTTP. When the port-portion of the big smushed address is hardcoded, Herculean efforts have to be made to route these services through NAT. Good luck if you want to run more than one SMTP server behind a given NAT gateway.
    3. 48 bits still isn't enough to satisfy growing demand. What happens when you can't address the endpoint you want even if you use all the address bits and all the port bits? Do we start piling on in-band multiplexing? Should every protocol necessitate something like HTTP 1.1's host header?
    4. Getting a publicly-routable endpoint address involves talked to one or more routers, which may or may not allocate a port for you. And this portion of the endpoint address is highly dynamic.
    5. Because of the last reason, protocols that involve callbacks are complicated. FTP, for example, made perfect sense in the days before NAT. Now, it's viewed as a problematic pain in the ass that always needs special NAT rules and connection tracking to accommodate it.

    These days, instead of saying "connect to mydomain.foo.cx", for example, you have to say "connect to mydomain.foo.cx at port 12345". That's out of band address information, and should never be needed. Imagine if DNS only gave you the first three octets an IP address, and every application requires you type in the last one in manually. That's what the world is like today!

    1. Re:NAT is not a solution by QuoteMstr · · Score: 4, Insightful

      Let's ignore in-band multiplexing being messy a hack. Let's ignore the lack of consistency between multiplexing schemes. Let's ignore the immense complexity of making routers understand every stupid little application-level protocol. Let's ignore the latency introduced by waiting for a connection to open before knowing where the next hop goes.

      Even after all that ignoring, your proposal won't work. Not with anything resembling today's equipment anyway.

      I'm Bob, you're Alice. (We can switch; I'm flexible.) You want to initiate a call to me. Let's say we've registered with a central directory, and the directory tells you that I'm at address A.B.C.D:12345.

      But wait -- back up. What right do I have to use A.B.C.D:P? As far as I'm concerned, I'm at 192.168.1.1. So I connect to the directory and tell it I'm at 192.168.1.1, listening on port 12345.

      The directory replies "what the hell are you talking about? That's not a public IP. Your public IP is A.B.C.D.". If you, Alice, try to connect to me at 192.168.1.1, the connection will fail, or go to your annoying friend Carol, whom you really don't want to talk to. OTOH, if the directory replies with A.B.C.D, how are you supposed to connect to me? Remember, I'm listening at 192.168.1.1 at port 12345.

      Either I have to talk to my ISP and tell it "give me an external port and forward traffic on that port to 192.168.1.1 port 12345", or the directory server has to talk to A.B.C.D and tell it "Oh yeah. Your client 192.168.1.1. He's listening on port 12345. He told me so. Give me a port I can connect to you on that will have traffic go there."

      The second scheme is clearly a security problem. The first requires cooperation from ISPs. UPNP sort-of addresses the issue, but not really very well at all.

      Basically, you're reinventing an entire routing protocol. Poorly.

      You need to upgrade ISP equipment to allow this sort of chit-chat to go on whenever somebody wants to listen for a connection.

      What happens if your ISP is itself behind a NAT? What happens when you run out of ports?

      The way you propose, it's turtles all the way down. It'd still be cheaper to just adopt IPv6 in the first place.

  19. Re:NAT? by Shakrai · · Score: 4, Informative

    Heck, they already firewall everybody -- why not just break IPs up into NATted subnets? The 10.x.x.x range should give them enough room for awhile, right?

    Hmm.... 16,777,216 IP addresses divided by 1,300,000,000 citizens.....

    --
    I want peace on earth and goodwill toward man.
    We are the United States Government! We don't do that sort of thing.
  20. DEC's /8 block was assigned to ... by PolygamousRanchKid+ · · Score: 3, Funny

    Carly Fiorina's ego. It's so big that it was necessary to support all of her ego's operations. If it grows any more, the IPv6 address space will be screwed as well.

    --
    Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
  21. Blocks vs. sub-blocks. by DrYak · · Score: 5, Informative

    So the world runs out of addresses before China runs out?

    The world will run out of new blocks to allocate (as in "254.xxx.yyy.zzz"), before China gives out all addresses in the allocated blocks it has (as in "www.254.254.254").

    Nonetheless, IPv4 can only provide a little lower than 253^4 different addresses. What makes it worse is that it's allocated in chunks (some chunks are reserved like the 127.x.y.z family - other addresses may be free but land in a range which is allocated to some company and thus can't be used by your computer).

    Thus even if some providers use dynamic IP (only those machine which are connected have an IP address - thus an ISP needs a chunk only as big as the number of simultaneously connected users, not as the total number of subscriber), and lot of router use NAT (only 1 single IP address is visible on ther internet. all the machine are visible through this address and use a private address on the internal network),
    in a world where everything including your fridge is connected to teh interweb 24h a day, 7 days a week, we will quickly run into a situation where no more IPv4 address can be assigned to a new machine :
    - the ISP has ran out of addresses in its chunk because there are more simultaneous connection (because everyone stays perpetually connected) that there are free address in the chunk (china will reach this point in 2-3 years)
    - and there are no more new free chunk to allocate for the providers (all are already either reserved like the 10.*.*.* and 192.168.*.* range, or have already been allocated to others) thus now way to give more chunks with more IP to the ISPs (the world will reach that point too in about 2 years).

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Blocks vs. sub-blocks. by Darth_brooks · · Score: 4, Insightful

      in a world where everything including your fridge is connected to teh interweb 24h a day, 7 days a week, we will quickly run into a situation where no more IPv4 address can be assigned to a new machine

      And tell me again why my fridge will be on a public IP, rather than the 192.168.1.xxx address my Best Buy $49.99 Linksys router will give it?

      Even better, explain to me why I, as Joe Sixpack will *need* my fridge on a public IP where every flaw and exploit will be passed directly to it, rather than dropped at the NAT box?

      Or better still, explain why a small business with 60 users should have every last user on a public IP?

      Or why a college or university needs to put every last workstation, printer, AP, and toaster on a public IP address?

      NAT exists because NAT works. No, it is not the be all end all for any perceived IPv4 woes, but there is a metric assload of stuff out there with a public IP that either should be, or desperately NEEDS to be on a 10.xxx.xxx.xxx network.

      --
      There are some people that if they don't know, you can't tell 'em.
    2. Re:Blocks vs. sub-blocks. by TheRaven64 · · Score: 4, Insightful

      So you can connect to your fridge and see if your milk has gone off from outside your home? NAT does not give security. A firewall gives security, and most NAT devices also do firewalling. If you don't want your fridge to be accessible from anywhere outside your network, or only from a set of VPN locations, then you can easily configure your firewall to block inbound connections to it (which is likely the default anyway).

      Does your small business with 60 employees want to use IP telephony? In this case, each PC (or each telephone) needs a public IP. You can get away with routing this at the application layer, but why bother when it doesn't actually gain you anything?

      --
      I am TheRaven on Soylent News
    3. Re:Blocks vs. sub-blocks. by NFN_NLN · · Score: 4, Insightful

      Even better, explain to me why I, as Joe Sixpack will *need* my fridge on a public IP where every flaw and exploit will be passed directly to it, rather than dropped at the NAT box?

      What you want is a firewall not a NAT. A firewall will protect you just the same and allow people to initiate communication as YOU desire.

      Or better still, explain why a small business with 60 users should have every last user on a public IP?

      There are quite a few examples why this is important but here's one. Why can't all students / businesses have a public IP with an exposed port for VoIP? Why do VoIP products have to have complicated NAT traversal software that doesn't always work and at the very least just adds useless overhead.

      It's called a firewall. Set one up and stop spreading FUD.

    4. Re:Blocks vs. sub-blocks. by truthsearch · · Score: 5, Informative

      In our small business IP telephony is handled with DHCP. All calls get routed through an asterisk server. So we only need one static IP address for the whole phone system. We need asterisk as a PBX anyway, so it's no extra fuss.

    5. Re:Blocks vs. sub-blocks. by Bryansix · · Score: 5, Informative
      Actually NAT DOES provide some sort of security. That is because by default nobody can see which devices sit behind the NAT. They also can't directly address them. So you want to see if your milk expired at home while you are at work so you can buy more if you need to? That problem has been solved. Your fridge had NO problem making outbound connections. It CAN upload the latest stats to a website that either you host yourself or a service from your fridge manufacturer. Need a better solution? Map the Public IP of the NAT but with a high unused port number to your fridge. Then whenever you connect to your SINGLE IP address but on that specific port it will serve up the stats on the fridge.

      See there are two solutions already to your perceived problem.

      Does your small business with 60 employees want to use IP telephony? In this case, each PC (or each telephone) needs a public IP. You can get away with routing this at the application layer, but why bother when it doesn't actually gain you anything?

      Wrong! I deployed 100 Hosted VOIP phones in a NAT environment. My Router has 11 public IP addresses but the phones all use the same one. If I used SIP trunks instead it would be the same deal. Only the phone server would need a public IP for the SIP trunks; not each phone.

    6. Re:Blocks vs. sub-blocks. by gnick · · Score: 5, Funny

      So you can connect to your fridge and see if your milk has gone off from outside your home?

      No problem. Just forward port 6969 (the standard port for FAP or Fridge Access Protocol) to the 192.168.1.x internal IP assigned to your fridge. Then you can FAP anywhere you have Internet access.

      --
      He's getting rather old, but he's a good mouse.
    7. Re:Blocks vs. sub-blocks. by ydrol · · Score: 4, Informative

      "Actually NAT DOES provide some sort of security"

      I agree, though being pedantic it's PAT and not (just) NAT

    8. Re:Blocks vs. sub-blocks. by gnick · · Score: 5, Funny

      Doesn't matter - the IPv4 shortage is a myth.

      DeBeers actually has plenty, but they're being hoarded away in vaults in Antwerp to keep the price artificially high.

      --
      He's getting rather old, but he's a good mouse.
    9. Re:Blocks vs. sub-blocks. by QuoteMstr · · Score: 4, Insightful

      Actually NAT DOES provide some sort of security.

      Sure, in the same sense that crushing an airliner into a cube makes it useless for terrorists. NAT breaks the internet, and when you break something, it's useless because it's broken.

      You can filter packets with a firewall without doing any NAT at all. In fact, your life would be a lot easier without NAT. There would be no need for configuring ports. There would be no need for mapping and configuring and making and unmaking.

      You'd plug things in, and they'd just work. Globally. You can allow connections to your fridge from work, or from anywhere. A firewall could do that. The fridge itself could do it. But you'd still be connecting to your fridge, and not some random port on some arbitrary gateway machine somewhere.

      Going with your fridge analogy, why should it be a bad thing for a grocery store to connect to all the fridges it knows about in order to tell them about new products? Why this artificial distinction between "inbound" and "outbound" traffic?

    10. Re:Blocks vs. sub-blocks. by nutrock69 · · Score: 5, Funny

      Going with your fridge analogy, why should it be a bad thing for a grocery store to connect to all the fridges it knows about in order to tell them about new products?

      Dear Fridge,
      You're out of SPAM!
      - the grocery store

    11. Re:Blocks vs. sub-blocks. by raju1kabir · · Score: 3, Insightful

      For the average user, they're interchangeable.

      That's a consequence of the way things have evolved, not a characteristic of the essential nature of things.

      The only reason we have these NAT boxes is because ISPs didn't give each customer a whole bunch of IPs. If they had, then we'd have the same boxes, but call them firewalls.

      You are trying to justify something based on its existence. That's what we call a circular argument.

      Why can't everyone have one? Because not everyone NEEDS one.

      From such statements does infamy arise.

      How do you possibly know whether or not it might be useful to have independent addressability for orders of magnitude more devices than have it now? Have you already invented all the things that this might bring about, and pronounced them useless? What a remarkably shortsighted view.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    12. Re:Blocks vs. sub-blocks. by QuoteMstr · · Score: 4, Informative

      So why do you need NAT instead of a non-translating firewall?

    13. Re:Blocks vs. sub-blocks. by surgen · · Score: 3, Informative

      >Actually NAT DOES provide some sort of security. That is because by default nobody can see which devices sit behind the NAT.

      You could also use a firewall to block some ICMP traffic. That is what the college I attend does, and they do it specifically so that, among other things, people can't see what devices are sitting on the network. Granted IPv4 gives the outside user some idea because of how many IP addresses are allocated to us, but with IPv6 that won't happen either.

    14. Re:Blocks vs. sub-blocks. by LanMan04 · · Score: 4, Interesting

      Actually NAT DOES provide some sort of security. That is because by default nobody can see which devices sit behind the NAT.

      Well, kinda-sorta. If you look at the behavior of the IPid field of outbound TCP packets coming from a NAT/PAT router, which most of the time is untouched by the router, as well as the TTL field, you can make a pretty good guess as to how many devices are behind the router, and a rough guess as to their OSes.

      The IPid field is usually used as a packet counter for a given OS, so it will increase in value by 1 for every packet sent. So if you have a few machines, each counting, you can group the outbound packets by IPid value. Also, various OSes have different default values for the TTL field (64, 128), so you can make a guess as to what OS it is as well.

      See: "Passive Detection of NAT Routers and Client Counting," Straka, K., Manes, G., 2006 in International Federation For Information Processing, Volume 222, Advances in Digital Forensics, eds. Olivier, M., Shenoi, S., (Boston: Springer).

      --
      With the first link, the chain is forged.
    15. Re:Blocks vs. sub-blocks. by gnick · · Score: 3, Funny

      Usually people as enthusiastic about needing to FAP as you seem to be don't mind the option of "nonstandard ports". But, to each his own.

      --
      He's getting rather old, but he's a good mouse.
  22. Please by fahrbot-bot · · Score: 3, Insightful

    stop saying "netizens".

    --
    It must have been something you assimilated. . . .
    1. Re:Please by Spatial · · Score: 4, Funny

      Quite so. It's simply good netiquette.

  23. Re:Dynamic address from ISP = intermittent lock-ou by ServerIrv · · Score: 3, Interesting

    ISPs will not be able to oversell their DHCP pool. Back in the days of dial-up, yes, but now that every broadband ISP installs a router/modem that is on 24 hours a day not a chance. Most people will turn off or suspend a computer when it's not in use, but will never do the same for their router.

  24. Why is everyone talking about pushing back IPv6? by bugg · · Score: 4, Insightful

    Why is everyone in the comments talking about various steps (reallocating large blocks, more widespread NAT, etc.) that would allow us to push back IPv6?

    It seems that we very close to the point where every device supports IPv6 (Vista adoption is helping this) but just isn't using it. Let's start turning it on. What better way to help the adoption than by having users who are IPv6 only complaining?

    --
    -bugg
  25. There's plenty of addresses left by StoatBringer · · Score: 5, Funny

    We've only used half the available numbers.
    Just start using negative numbers: -248.100.-97.-201

    --
    Cress, cress, lovely lovely cress
  26. Return more /8 addresses? by HockeyPuck · · Score: 3, Insightful

    Why can't some of the owners of /8 address spaces return them back to be re-allocated?

    For example, HP owns 15.0.0.0 through 16.0.0.0 (~33m ip addresses) can't they get by on just ONE class A network?
    Apple owns 17/8
    MIT own 18/8
    US Postal Service 56/8.
    http://www.iana.org/assignments/ipv4-address-space/

    Do all these companies need to have ALL of their devices on publicly routable IP addresses? From a security standpoint, I would hope not. Odd since IBM, a company much larger than MIT and Apple can get by on just one /8, and I'm having trouble believing that HP requires 2 /8 networks.

    We talk about making our datacenters "green" by consuming less power, there's got to be an equivalent for consuming fewer public IP addresses.

    I've just finished re-IPing our datacenter (~5000 servers), not to 'release IP addresses back, but to undo the damage done by years of seemingly randomly assigning IP addresses to servers in our datacenter. Yes it's a pain, but so is any form of cleaning up your datacenter (cabling for example).

  27. Everyone should have two /64 subnets in IPv6 by gambolputty3 · · Score: 3, Interesting

    Ordinary users of the IPv6 Internet should be allocated as a minimum two /64 subnets. One /64 subnet would be for a private LAN network and the other /64 subnet would be for a public facing DMZ network. The DMZ network would be useful for any kind of reachability which only selected people can access content. IPv6 capable VoIP PBXs would be especially useful here like Asterisk and Freeswitch. Imagine the possibilities of assigning every phone call or user its own IPv6. This should elimiate VoIP spam. Other notes: Point to point links should be a /126, not a /64. Businesses of differing sizes don't need a full /48. This would be like giving out blocks of IPv4 Class A addresses all over again. The size of the allocated IPv6 for a business should match their real size and needs. Applications and operating systems need to be more IPv6 aware.

  28. Peak IP4 is a Myth by TimeTraveler1884 · · Score: 5, Funny

    Peak IP4 is a myth; there are still plenty of addresses buried in the Canadian tar sands. However, in the short term, the only solution is to lift the ban on coastal drilling for IP4 addresses.

  29. Re:Counting the wrong things by TheRaven64 · · Score: 3, Informative

    IPv6 allows addresses to be assigned very sparsely, which simplifies routing tables a lot. Back in the early days of IPv4, you could look at the first octet of an address and make a routing decision. The next router would look at the next octet, and so on, and so you only needed 256 routing table entries in each one. The network was conducted as a tree. You'd send a packet to the local router, which would say 'this isn't in my local network, send it up a tier' until it got to one that could start sending it down again.

    With CIDR, you stopped being able to do this. Addresses were allocated in blocks of 256, so you had to look at the first three octets to make a routing decision. This meant you need up to 16,777,216 routing table entries. With IPv6, this is no longer required, and you can go back to having the IP addresses roughly corresponding to the network topology.

    --
    I am TheRaven on Soylent News
  30. Re:More to the point by deraj123 · · Score: 4, Insightful

    I'll answer your question with another:
    Why not?

    Seriously. This whole "X doesn't NEED to be on the internet" is a ridiculous argument. It's simply saying "oh, having a PC and computer type equipment on the internet should be enough for anybody". The whole point of this internet thing is innovation. Sure, a fridge doesn't NEED to be on the internet. Unless I want it to have some functionality that requires internet connectivity. Same with my computer. It functions just fine, and doesn't NEED to be on the internet.

    And why is "fridge can reorder beer for you" drivel? Is there some reason that a fridge SHOULDN'T reorder your beer? Sure, it's not a vital function, but neither most of the stuff that our technology does. Again, this is what innovation and technology is all about - improving the standard of living, making this easier, etc.

  31. Energy costs. by Kadin2048 · · Score: 3, Interesting

    The refrigerator is a poor example, but other appliances and home HVAC systems could realize significant energy savings by communicating with each other, and by being controlled remotely over the internet (or some other means).

    There are a lot of interesting scenarios: if you had real-time, fluctuating power pricing, you might want to have appliances change their energy consumption or other settings in response to their cost. Only run some appliances when the spot price is below $0.15/kwh, for example.

    Or even simpler, if you have a peak-load factor as a component of your bill, devices could communicate with each other to ensure the total draw at any one time doesn't exceed some predetermined maximum. Different appliances would each have a priority, and would have to shut down to accommodate higher-priority draws. (E.g.: the clothes dryer would shut off if you turned on the electric stove or microwave, because it would have a lower priority -- unless you were really obsessive about not having wrinkled clothes, I suppose, in which case you could set it the other way around.)

    The two could be combined, as well: once you have the infrastructure in place, you could set up whatever rules you wanted, balancing preferences for certain services against costs, and prioritizing certain services at various times. It wouldn't be hard to produce detailed reports of what each appliance/service was costing to operate, and how new rules would affect costs based on past usage patterns. (There's the potential for a lot of complexity in the control system, but to a user it might seem very simple on the surface.)

    Also, there's a wide range of appliances that really only need to run when people are in the house (or just before they enter the house) but tend to run continuously because it's a PITA to run them based on inflexible timers: HVAC, lighting, water heaters, possibly even water pressure-pumps. Devices would only be turned on when necessary for another device, or a user need was anticipated. I could easily imagine a system that was plugged into an online calendar and controlled this in a way that hid it from the user as much as possible. Heck, if you had a PDA with GPS, you wouldn't have to do anything.

    The driving force behind "home automation" up until now has mostly been the geek factor of controlling all your lights/appliances/whatevers from a single point, but I think in the future, energy savings and integration will be the selling point. Since it seems unlikely that we'll really make significant inroads on alternative sources of energy before we start to run low on petroleum, there's a non-trivial chance that energy may become staggeringly expensive. I could easily see a future where the running costs of energy-intensive appliances greatly exceed -- even to the point of triviality -- their purchase price.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  32. Even if it wasn't hex codes, it would be a PITA by coryking · · Score: 3, Interesting

    What is IPv6, 128-bit address space? That is what, 16 bytes?

    Worse case in decimal (I added the dashes so *I* could make sure I typed it right :-)
    216:126:59:03-58:95:58:32-126:43:55:129-59:59:59:1

    Worse case in hex (same deal).
    FA:FA:FA:FA-12:55:43:BA-55:DA:CC:DB-89:A1:C1:01

    Basically, you are boned :-) Maybe we need a different number system that is like Base64 instead of Base16? Heck... why not just base64 encode the IP address. Base64 is what, A-Z, a-z, 0-9,+,=? A Base64 encoded IPv6 address is just:
    Az.

    Or make it Base32 instead so you can be case insensitive (A-Z, 0-9 and only drop a couple easy to mix up characters like i, l and o to get to 32 chars). A Base32 IPv6 is:
    A1Y2.

    You could even break out subnets with Base32:
    A1Y:2/96 (subnet mask ZZZ0)

    So yeah... why didn't they go Base64 or Base32 instead of Base16?

  33. Re:More to the point by Mister+Whirly · · Score: 5, Funny

    "Just how lazy are you?

    As much as technology will allow.

    --
    "But this one goes to 11!"
  34. Re:Wow, I suck by Srin+Tuar · · Score: 3, Informative

    your examples are wrong.

    HEX: 4 bits per byte, takes 32 chars to encode IPv6 Address

    Base32: 5 bits per byte, takes 26 char to encode an IPv6 address

    Base64: 6 bits per byte, takes 22 chars to encode an IPv6 address

    You can see the return on investment is pretty small for base32 and base64, since it costs you the transparency of the output.

    try again.

  35. Re:More to the point by OverZealous.com · · Score: 3, Insightful

    When discussing putting every device online with a distinct IP (especially IPv6), I've never seen anyone mention the ISP element. What happens when you all of the sudden need to add several dozen new devices to you internet connection?

    What I mean is, ISPs (at least, U.S. ISPs) right now are trying everything possible to charge money. They charge for every single static IP, small bumps in speed, etc. I remember when it they wouldn't even talk to you over the phone if you had a router in place.

    So, imagine that every device expects to be statically placed online. Now, all of the sudden, to use your Wii or PS3, access your fridge's web server, log into your coffee pot, or update your in-home automation and security system, you have to pay your ISP a small add-on monthly fee.

    My point here is that NAT or an equivalent cannot and will not go away. The overwhelming majority of devices just don't need open web access. Instead, these devices should be routed through some sort of obscuring and securing device. If a home-owner needs to access their fridge, they should first log into their home-portal, which provides access to their in-home network.

    Besides, someone else mentioned the store sending advertisements to my fridge. Thanks but no thanks. I'll just visit your website if I'm interested in the current ads.