Migration to the new Internet Protocol version 6 (IPv6) standard is virtually non-existent, according to a year-long study released this week by network security firm Arbor Networks. Experts and governments have been encouraging organisations to migrate to the new protocol because the current 20 year-old IPv4 is fast running out of available addresses.IPv4 addresses could in fact run out as early as 2010, according to Scott Iekel-Johnson, principle software engineer at Arbor Networks. The firm used data from over 80 of its ISP partners and customers to determine the amount of IPv6 traffic on the internet. Arbor Networks found that the proportions of IPv6 and IPv4 traffic has stayed roughly the same over the past year. The report also found that IPv6 traffic is still a tiny percentage of overall internet traffic. There were 6Mbps of IPv6 traffic by the end of July compared to 4Tbps of IPv4 traffic.
View: The full story @ vnunet
However I realise it will be a necessary evil. Perhaps better PR is necessary. Maybe even some "the sky is falling!!" type TV adverts.
However I realise it will be a necessary evil. Perhaps better PR is necessary. Maybe even some "the sky is falling!!" type TV adverts.
IPv4 addresses were never intended to be "easy to remember", this is just a bit of a side-effect. But to be honest, do you really NEED to remember many IPv4 addresses? Perhaps for an internal LAN, maybe, but even then most routers have a page listing all connected clients and their corresponding IP's.
However I realise it will be a necessary evil. Perhaps better PR is necessary. Maybe even some "the sky is falling!!" type TV adverts.
Well, I don't think it is terribly difficult to remember when you have 0's in certain places.
0000:0000:0000:0000:0000:0000:0000:0001 = ::1 (loopback; correponds to IPv4 127.0.0.1)
834f:047d:0000:0000:bc91:0000:0000:5662 = 834f:47d:0000:0000:bc91::5662
There shouldn't be any reason to memorize the IPv6 addresses anyway. Write them down and keep them in a safe spot! ^_^
However I realise it will be a necessary evil. Perhaps better PR is necessary. Maybe even some "the sky is falling!!" type TV adverts.
I've had the local university's public DNS server's IP address memorized for years now. In retrospect, because of cell phones and contact lists, i don't have any phone numbers memorized.
However I realise it will be a necessary evil. Perhaps better PR is necessary. Maybe even some "the sky is falling!!" type TV adverts.
Well, I don't think it is terribly difficult to remember when you have 0's in certain places.
0000:0000:0000:0000:0000:0000:0000:0001 = ::1 (loopback; correponds to IPv4 127.0.0.1)
834f:047d:0000:0000:bc91:0000:0000:5662 = 834f:47d:0000:0000:bc91::5662
There shouldn't be any reason to memorize the IPv6 addresses anyway. Write them down and keep them in a safe spot! ^_^
That's only the case where the IPv4 and 1Pv6 numbers are equatable. Remember, IPv6 has a larger total maximum address space than IPv4, and so there are IP number (very many IP numbers) that can only be correctly expressed in the IPv6 format. It's like the difference between a 64-bit bus and a 32-bit bus: You could still run 64-bit bus in 32-bit mode (well, theoretically) but there's just no way to run a 32-bit bus in 64-bits.
Right now, for the sake of full bi-directional interoperability between IPv6 and IPv4, the IPv6 hardware is mostly limited to those address ranges that are backwards-compatible with the IPv4 system. However, you are going to see more and more IPv6-only sites.. and sooner than you might think. China and the asia-pacific region are way ahead of the rest of the world when it comes to IPv6. We really need to get the infrastructure in place if we're going to catch up and not be left behind.
What I want to know is, out of those ISPs that only run IPv4, how many have the IPv6-capable hardware in. I'm hoping that it's the majority, because if it's not there is going to be an unpleasant crunch-time coming up. It's not that I'm afraid of IPv6, it's just that I'm afraid that some of our corporate CEOs are eithier ignoring the issue or are just ignorant about it.
I did setup my main system as a router -- now I don't need an external router/firewall box to connect all my other computers to the Web.
I am currently using PNRP to connect to my system from a remote location (instead of using any DNS providers like dyndns etc). However, I cannot access my system using an ipv6 address from a remote location.
Can you detail what you did for tunneling?
I got an IPv6 from a tunnel broker (www.tunnelbroker.net). I'm also allowed to allocate a /64 address range (most tunnel brokers do this too).
The Ipv6 over Ipv4 tunneling protocol IS built-in in vista, BSD variants (including mac os
Both ends of the ipv6 tunnel are an address from the /64 address range I was given. I used an "ping me from the outside" tool, and I discovered that ALL traffic to any of the /64 address was directed to MY end of the tunnel (obviously discarding those packets that are not destined to me). So what I did was configure vista (or linu
So I had two interfaces: the tunnel one (a "non-physical" interface), and the local one (giving an IPv6 address to the ethernet interface). I had to alter window's routing table so that packages going to the local interface are sent out through that interface (otherwise the way it was configured it would have probably sent them out to the other end of the tunnel where they would be discarded). But this wasn't enough, I had to tell windows to FORWARD ip packets (this was a bit tricy, I couldn't find the damn option in the command line, hehe). On linux this bit was MUCH easier.
And then configure all the other computers from my local network, giving them an ipv6 address from my range, and set
The way it works, the other end of the tunnel forwards all traffict to that range of addresses to me. If the destination is my local network, it forwards the traffict through the local ethernet. Traffic generated from the local ethernet to the outer ipv6 world will be sent to my end of the tunnel, then the other end will route it as normal.
Oh, and you have to tell windows to respond to pings too, to check from the outside if the local network is "external" now. hehe
1. Has to be mandated, such as OMB is doing in the United States government
OR
2. It has to be something that can be done without it becoming a capex monster (corporate boards do NOT want big capex expenses, even if there are large bennies down the road; they don't want to take the chance of being lynched by their bondholders)
Right now, converting to IPv6 is not mandated, and is largely still monstrously expensive to do. Natually, corporate world is avoiding doing so as long as is feasible.
I know; nobody likes a mandate (I like the idea about as much as root-canal surgery). However, how do you get over not just antipathy, but *understandable antipathy* towards spending a major pile of money where none of the benefits are obvious, short-term or long-term, without it?
Talk about insignificant...
http://www.arbornetworks.com/en/arbor-netw...e-internet.html
Still a small figure percentage wise.
Vunet (still) failing to spell correctly.
You can also get a WRT54GL for $50 and throw openwrt/dd-wrt/etc. on it.
You can also get a WRT54GL for $50 and throw openwrt/dd-wrt/etc. on it.
That's for support via the tunnel-broker method (the most common way to deploy end-user IPv6 today). Both DD-WRT and OpenWRT support this method (however, Tomato, the most common non-Linksys/non-Cisco firmware for WRT-type routers, does not). IPv6 support via tunnel-broker in routers is a lot less than $100, as most WRT-type routers (all the way back to the version 2.x WRT-54G/GL/GS, which is still found on a lot of retail shelves) support it via firmware swap. The issue I was referring to is support via other means than the tunnel-broker method. Native IPv6 support in the US (in fact, in North America) severely trails that of Asia (however, in Asia, the government-mandate method is responsible for forcing a lot of IPv6 deployment). I'm not saying that the mandate-method is either right or wrong; however, that's the way the data reads.
Plus most companies do hardware replacements every 3-5 years. Just brought a new Juniper firewall and a new SSL VPN device as well as replacing our Cisco router. All come with IPv6 support by default.
This would solve the problem of the "easy to remember" thing...
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.