101–110 of 149 posts
Earlier quoted context omitted.
Those can all be changed. A determined spammer could make a bot that automatically changes them.
I assume a browser fingerprint of the right granularity is hard to change for someone who would vandalize Wikipedia without a proxy.
Earlier quoted context omitted.
I can assure you the US is feeling the brunt of the IPv4 crunch. I'm building something that needs massive amounts of public address space and I simply can't get IPv4 addresses for it. I've asked multiple providers. You are LUCKY if you can get a /28 at this point. Hoarding. Rolling with IPv6 instead. I get you have an interest in the Qatar/Wikipedia situation, but it seems to be unlikely due to IP address resource m…
> I'm building something that needs massive amounts of public address space // You piqued my interest, what?
Doing it solo now, but I need help.
Here's a report you can see the current projects with a bit of history: http://www.potaroo.net/tools/ipv4/index.html The potaroo site by Geoff Huston has been running for over a decade tracking address consumption. Some history for ARIN consumption predictions: Feb 2014 predicts Mar 2015. Oct 2013 predicts Jan 2015 [0]. Apr 2013 predicts Apr 2014 [1]. Nov 2012 predicts Sept 2013 [2]. Sep 2012 - RIPE out of addresses.…
These aren't brick walls but the shortage is already being felt. I know that at Efficito, one of the reasons we switched hosting providers was that we couldn't get ipv6 connections working flawlessly to our backup connections before (meaning more ipv4 space required). I don't think we will ever hit exhaustion per se.
Earlier quoted context omitted.
I can assure you the US is feeling the brunt of the IPv4 crunch. I'm building something that needs massive amounts of public address space and I simply can't get IPv4 addresses for it. I've asked multiple providers. You are LUCKY if you can get a /28 at this point. Hoarding. Rolling with IPv6 instead. I get you have an interest in the Qatar/Wikipedia situation, but it seems to be unlikely due to IP address resource m…
Then there are guys like me. I have a /24 routed to my home (pre-ARIN legacy space registered in the early 90's!)
Earlier quoted context omitted.
I can assure you the US is feeling the brunt of the IPv4 crunch. I'm building something that needs massive amounts of public address space and I simply can't get IPv4 addresses for it. I've asked multiple providers. You are LUCKY if you can get a /28 at this point. Hoarding. Rolling with IPv6 instead. I get you have an interest in the Qatar/Wikipedia situation, but it seems to be unlikely due to IP address resource m…
I know of multiple providers who have gotten allocations in the last month (up to /19) and will be requesting another one myself in the near future. ARIN has plenty of IPs.
I have noticed a change in approach, even if unconscious. Instead of predicting doom, they have started to celebrate small victories (like Google IPv6 traffic passing 3%). I think that's natural when the size of this undertaking is so great. Unfortunately IPv6 adoption is not a matter of just providing access lanes to this wonderful new technology. IP permeates too much of the infrastructure, tooling, etc. How could…
still wonder how much of the internet is not IPV6 compatible.
We previously had backups located in Denver and production servers located in Europe, both through the same hosting provider (FDC). We never could get IPv6 working flawlessly (high packet loss, etc) intercontinentally and the problems weren't on our side.
We moved to Hetzner and have our systems spread throughout their datacenters (backups, and some backend systems on one side, customer data on the other) and have had absolutely no problems with ipv6.
What this tells me is that somewhere between the Czech Republic and Colorado there are routers which although they sort of support ipv6 don't do so in a usable way.
Doesn't the US defence department hold a ridiculous amount of the address space? What would it take for them to give some of that up?
The growth in internet-connected devices is exponential. By the time the last blocks were issued they were going out at 1 class A (i.e. 1/256 of the entire IPv4 address space) every month . So it's not worth the effort to recover existing addresses.
The real problem is routing table size with BGP. As we continue to divide the internet into smaller routable blocks, this is requiring an exponential amount of memory in BGP routers. Currently, the global BGP table requires around 256mb of RAM. IPv6 makes this problem 4 times worse.
IPv6 is a failure, we don't actually _need_ everything to have a publicly routable address. There were only two real problems with IPv4: wasted space on legacy headers nobody uses, and NAT traversal. IETF thumbed their noses as NAT (not-invented-here syndrome) and instead of solving real problems using a pave-the-cowpaths-approach, they opted to design something that nobody has a real use for.
Anyway, I'm hoping a set of brilliant engineers comes forward to invent IPv5, where we still use 32 bit public address to be backward compatible with today's routing equipment, but uses some brilliant hack re-using unused IPv4 headers to allow direct address through a NAT.
Flame away.
Truth is NAT works just fine for the vast majority of cases, and makes a layered (IE not-eggs-all-in-one-basket) approach to security much simpler. The real problem is routing table size with BGP. As we continue to divide the internet into smaller routable blocks, this is requiring an exponential amount of memory in BGP routers. Currently, the global BGP table requires around 256mb of RAM. IPv6 makes this problem 4 t…