Wednesday, December 8, 2010

Methods of mitigation of IPv4 address exhaustion

Is the appearance of log entries of the form:
crawl-66-249-65-10.googlebot.com - - [08/Dec/2010:12:43:59 -0500] "GET /techwatch.ca/....

an indication of mitigation effort for the address exhaustion of IPv4 or is this a general change for the migration to IPv6?

Previously crawls from Googlebot were of the form: 66.249.65.10

I still have entries in my logs that are of the IPv4 quads of 00-FF (000-255)

Update: May 2012

The server log entries when I last looked were pretty much spilt between IPv4 addresses and host names for the originating servers. It is my theory that the Host Server Name will be the identifier when IPv6 is fully inplemented. This is because the new breed of Router/Gateway is capable of addressing the host assocaited with the MAC address of the device connected to the Internet.

I addition the Residential Gateway and the Terado Tunneling adapter, if used by your ISP, can determine the local LAN address of the devices connected to that device. When IPv6 is fully implemented the individual device will be addressed - NOT the router or Gateway.

1 comment:

Anonymous said...

Was wondering what the security implications of the move from IPv4 addressing to IPv6.

I had heard that it would be possible for an APO to determine individual devices that are connected behind a NAT firewall.

I see that you have a few posts on this matter. Also you seem to have observed that your server logs have fundamentally changed over the last while.

I agree that this is probably more than coincidental and it is likely to be related to the way that Internet accesses are routed going forward.

I am surprised that others have not picked up on this and feel that there are many that will be surprised when their download activity is found out.