Archive for June 30th, 2010
Test Your Network and ISP for IPv6 Readiness
Want to test your network for IPv6 readiness? Go to http://areyou.v6ready.info/ .
Also see the countdown clock. With all of the devices we have, tablets, laptops, desktops, servers, routers, phones and other devices, there are only so many left (IPv4 addresses)…
There are two types of IP addresses. Public and Private. Private numbers are NATed. They allowed us to have IP addresses that were 10.x.x.x, or 172.16.x.x or 192.168.x.x. NAT allows us to have multiple computers in our home and our home router would have one public number supplied by our ISP. May sound complicated to the novice but actually is pretty easy if you could see it drawn out. For example our school has four IP addresses that are public (we have four lines coming in) but behind it has hundreds of nodes (computers, Access Points, Bridges, Printers and other devices.)
Comment form ARIN’s president
And to add to this post – ARIN’s President and CEO
Very nice post. I’d add that you need to begin planning to have your public servers (web, email, DNS) reachable via IPv6. Talk to your ISP about getting IPv6 over your existing IPv4 service, plan how to add IPv6 addresses to your external servers, and make sure you review your security configuration for handling IPv6 traffic.
For additional information, you can look to ARIN’s wiki for IPv6 information:http://www.getipv6.info
/John
John Curran
President and CEO
American Registry for Internet Numbers (ARIN)
Everything you need to know about IPv6
Everything you need to know about IPv6.
Just read an article that an unpatched computer can be infected faster than it could download updates. That once IPv6 is in place if one billion infected computers each were scanning a billion IPv6 addresses per second, it could take up to a hundred million years to scan the IPv6 addresses that have been give out now.
Kame Project shows if you are IPv6 ready.
Testing Your Firewall for IPv6
Here’s a way to test your Firewall (hardware) for IPv6 compatibility Link (see how to interpret your results)
Preparing for IPv6 is very important at this time. Early implementation will be the key to successfully making this transition.
All you have to do according to the article is run the dig command (there is a dig program for Windows).
; <<>> DiG 9.5.0-P2 <<>> hk ns@203.119.2.18
;; global options: printcmd
;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 746
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:;hk. IN A
;; ANSWER SECTION:hk. 360000 IN CNAME hk.connectify.local.hk. 86400 IN A 203.119.2.28
;; Query time: 9 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Wed Jun 30 22:06:52 2010;; MSG SIZE rcvd: 73
;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 75
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION
:;ns\@203.119.2.18. IN A
;; AUTHORITY SECTION:. 10800 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2010063001 1800 900 604800 86400
;; Query time: 3240 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Wed Jun 30 22:06:55 2010
;; MSG SIZE rcvd: 108
Planning for IPv6
