| 7:27 pm on Feb 3, 2011 (gmt 0)|
Some where there's an old explanation on Webmaster World on how to block the IPV6 ranges.
Don't recall if it was this forum or one of the others.
Nor do I recall who provided the explanation
| 8:34 pm on Feb 3, 2011 (gmt 0)|
Well I definately started thinking about this a few month ago. We currently get the IPV4 Data from a paid source and I also have an old script of mine that parces the data available(havent run the routine in a while) from the ARIN, RIPE etc ftp sites.
I think I will still go the route of the way we have it now, the IP data is in DB and then ....
It's on a back burner at this point.
| 11:03 pm on Feb 3, 2011 (gmt 0)|
I use MySQL to hold the blocklist. IPV6 will certainly increase the serving time of matches but I suppose I'll have to wait and see by how much.
Or I could just retire. The internet is rapidly going to hell on a handcart - actually, more like on a Formula 1 racer! :(
| 3:07 pm on Feb 4, 2011 (gmt 0)|
How imminent a problem is this? I hope we have a few more years or so before we have to seriously worry about this.
| 3:55 pm on Feb 4, 2011 (gmt 0)|
|How imminent a problem is this? |
I would think it depends on how much of a tech geek you are, and what type of environment you work in.
As for myself, I'm actively pursuing the issue inhouse currently. mail servers, website, user seats, etc.
| 11:07 pm on Feb 4, 2011 (gmt 0)|
Almost all the IPV4 ranges have now been allocated - there was a major allocation bout last year, mostly to US companies. It now depends, I suppose, on how many of those IPs get used up and how fast. With some companies allocating /15 and more to clouds, it could be soon. :(