Follow Slashdot stories on Twitter


Forgot your password?
Microsoft Networking The Internet IT

Microsoft Runs Out of US Address Space For Azure, Taps Its Global IPv4 Stock 250

alphadogg (971356) writes "Microsoft has been forced to start using its global stock of IPv4 addresses to keep its Azure cloud service afloat in the U.S., highlighting the growing importance of making the shift to IP version 6. The newer version of the Internet Protocol adds an almost inexhaustible number of addresses thanks to a 128-bit long address field, compared to the 32 bits used by version 4. The IPv4 address space has been fully assigned in the U.S., meaning there are no additional addresses available, Microsoft said in a blog post earlier this week. This requires the company to use the IPv4 address space available to it globally for new services, it said."
This discussion has been archived. No new comments can be posted.

Microsoft Runs Out of US Address Space For Azure, Taps Its Global IPv4 Stock

Comments Filter:
  • by The New Guy 2.0 ( 3497907 ) on Saturday June 14, 2014 @02:59PM (#47237317)

    IP blocks are meant to be a drill-down system. For example, 128.230.x.x is indicates it's on the Syracuse University campus.... with the 16 bits worth of addresses being spread out so that a specific x in the third position would indicate what building to send the packet to.

    Microsoft's problem here is that their Azure service has used every one of the IP addresses allocated to it... and Microsoft doesn't have any subnets remaining in the "USA Block" of their IP addresses... so they have to move IPs that would have been used overseas back into the Azure datacenter. As IPv4 continues to be used we're going to start to see more of these "we're running out!" stories.

  • Re:OR (Score:5, Informative)

    by petermgreen ( 876956 ) <> on Saturday June 14, 2014 @04:27PM (#47237711) Homepage

    At the top level the major transit networks support IPv6 and most of them have for years.
    At the bottom level the end devices mostly support IPv6 though XP systems (which are still scarilly common) have it disabled by default

    The problem comes in the middle, access providers and corporate network operators need to do the work to give the IPv6 capable devices they and their customers own access to the IPv6 internet. Many of them don't see doing so as a priority.

    MS implemented a protocol called teredo to work arround this but it's fragile because it fights nat rather than working with it. It's also disabled by default on networks where a domain controller is detected (presumablly because MS didn't want to be accused of subverting corporate firewalls).

    Most operating systems will preffer IPv6 when a native v6 connection is available and yet the ipv6 traffic as reported by the likes of google is in the single digit percentages.

    Unfortunately I'm struggling to find good stats on how many users can access v6 only resources even though they preffer v4. Test-ipv6 has some stats but I don't consider them representitive of normal users. I remember seeing some stats a while back that said it was about half but I don't remember where

  • by statemachine ( 840641 ) on Saturday June 14, 2014 @05:56PM (#47238005)

    Yes, having 2^128 addresses will make routing so much simpler.

    Indeed, it will. All IPv6 addresses are regional. There won't be any subnets split across continents.

  • Don't Panic! (Score:4, Informative)

    by jbgeek ( 952457 ) on Sunday June 15, 2014 @07:02PM (#47242615)

    Don't Panic, or be afraid of IPv6.

    People often talk of "switching" to IPv6. One does not "switch". You simply deploy it alongside IPv4. Right now my home network is happily running IPv4 and IPv6 at the same time, called a "dual-stack" environment. This sort of set up will be common for decades until IPv4 use dwindles to nothing, and people start turning it off.

    Nearly all operating systems and devices supporting IPv6 have it turned on by default, so you're already running IPv6. You just don't have globally routable addresses assigned (most likely). You could actually use ping (windows) and ping6 (*nix) to ping other hosts on your LAN using link local addresses, which have automatically been assigned (see those addresses starting with fe80 on all of your interfaces?), if you knew how, right now. :-)

    If you know IPv4 routing and subnetting, you already know most of what you need to know about IPv6. Except that IPv6 is simpler since there's no need to NAT. Just set up your firewall exactly as you would under IPv4 (same security policy), minus the NAT. Subnetting is also simpler, with no need to fret over "right sizing" your subnets so they're "just big enough" and don't use too much of your precious IPv4 space. Just assign a /64 out of your /48 (businesses will be easily be able to request multiple /48s) and you're done. Never run out of host numbers, or subnets.

    Some folks are frightened by the use of hexadecimal for IPv6 addresses. No need to fret. It makes sense, and would have made sense for IPv4 also. Hex for IPv6 not only makes the IPv6 addresses more compact., it's also far easier to translate hex into binary, and work with prefix-lengths than decimal IPv4 address are. I can do it in my head all day with no issue. All you have to do is memorize 16 bin patterns from 0000 to 1111, each represents a hex digit from 0 - F. Piece of cake. No more annoying math and base conversion to try to figure out which subnet some IPv6 address belongs to like with IPv4. No more subnet masks either (which are also decimal), instead, just prefix lengths (although this is also true of IPv4 with CIDR, adopted long ago, many user interfaces still require a netmask for IPv4 instead of just a /prefix-length, sigh).

    Anyway. Go play with IPv6. It will be an essential skill to add to your Resume/CV, and will only take a short time to figure out. Go set up an tunnel with Hurricane Electric or some other tunnel broker to get some globally routable IPv6s. It's simple and you'll learn a lot and quickly! And best of all, you'll stop being afraid of IPv6! :-)

    (apologies to those who already have adopted IPv6 and know all this already ... this isn't addressed to you!)

"Oh my! An `inflammatory attitude' in alt.flame? Never heard of such a thing..." -- Allen Gwinn, allen@sulaco.Sigma.COM