Little Interest In Next-Gen Internet
Ant wrote in to mention a Computerworld article that is reporting on the slow acceptance of the IPv6 version of the internet. From the article: "Information Technology (IT) decision-makers, in U.S. businesses and government agencies, want better Internet security and easier network management. However, few see the next-generation Internet Protocol called IPv6 as helping them achieve their goals, according to a survey released Tuesday by Juniper Networks Inc."
...untill they run out of addresses
just doesn't have the same ring to it.
Meh.
Translation: "There's a marketing job to be done"
I thought education was for important things which you need, and marketing was to convince you to use products and services?
My 3D Texturing Skinning work (under construction)
The reason why is there's not that much support or software for the protocol. As the summary said they want better security and easier management, but there's not even a good IPv6 firewall up and running, so why would they take it up?
Wait a while until there's the software backing then you'll see companies using it.
Which is why IPv6 isn't going to be in full effect until 2025. They figured that acceptance would be slow. The fact is, at this point, people don't need IPv6. But when the numbers start to run out, they'll be clamoring for it.
NAT is the reason why ipv6 has not really been needed. The idea of having an IP address for everyone on the planet and for his dog too was really not needed.
::1 ?) and over all lack of a need helped kill IPv6 from becoming too popular.
Once NAT+Firewalls became popular enough, the requirement for large IP chunks for offices and stuff disappeared.
No backward compatibility, ugly naming scheme (tell me , who like
Quidquid latine dictum sit, altum videtur
Learn to use and enjoy Zero compress in IPv6 :) ::1 would be the same as 0:0:0:0:0:0:0:1
/32 IPv6 block and the ISP replies that they don't retail out single IPs.
Did you hear about the guy who went to get a
Quidquid latine dictum sit, altum videtur
Thanks for clarifying what IT meant. I've been lost on this site for YEARS and now I finally know what that acronym means. Life is good.
Semes like someone could make a ton of money designing a IPv4 to IPv6 bridge, so you could run 2 network segments, expanding the IPv6 segment as you go.
I'm just here to regulate Funkyness
all the cyber people need to support teh AOL in their awesome efforts to make the internets better for everybody.
can't believe you peeps havent seen the cool AOL comercials!!!!111
"want a better internet?"
"you belong to america online!!!"
An Indian-American Hindu committed to non-violent thought/speech/action alarmed by the global explosion of radical Islam
How about providing static IP addresses to DSL and cable modem users, so we can actually use simple DNS (or even just memorized IP addresses) to host things with servers in our living rooms? Seems to me that would be a huge value proposition for any ISP to its customers.
There are 2 kinds of people in this world. Those that can keep their train of thought,
Developing countries dont have an option other than to move to IPv6 due the apparent shortage of IP numbers. And if that's the way, then the rest have to go for IPv6 because, they say v6 cannot inter-operate with v4.
Regardless, what's wrong with IPv4? I've been using it on my network for years and I haven't had any problems or extra requirements. They're gonna have to come up with damn good reasons to switch because, at the moment, it's just not worth the hassle.
I know i'm not the only one who thinks like this.. all of my colleagues are happy with the v4 system, and the (less high maintenance) users know what i'm talking about when I assign IPs or mention '127.0.0.1'. None of them have a clue about '::1', and it isn't worthwhile changing until IPv4 truly becomes defunct and obsolete.
What are you talking about?
/48 allocated to me so each machine has its own real ipv6 internet address and can talk directly to all other internet ipv6 addresses. (plus, I have over 281 trillion ip addresses spare for later)
I run ipv6 and ipv4 together on the same net all the time.
For ipv4 I have one static internet address on my router machine which provides NAT for all the other internal machines.
For ipv6, I have a
Also the applications don't need writing for one or the other. By using the ipv6 API you automatically get support for ipv4 at the same time.
There is an easy upgrade path. What will really get folks upgrading is when more and more sites become ipv6 only. For example I am setting up a nature webcam site which will be ipv6 only for exactly this reason.
-- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz
Of course it can run on the same network. Just need a v6 connectivity, just as you have a v4 one. You absolutly don't need multiple nics! Are you one of those who think an interface can only be configured with one ipv4 address ?
And Juniper Networks is pushing the idea that IPv6 is not on anybody's agenda because sell routers, NAT boxes and associated services. A severely restricted adress space is what they need to continue to do so. This is just an attempt on their part to establish/enforce a perception that IPv6 is not needed/wanted. It may have misfired, though.
Something bad is coming when people are suddenly anxious to tell the truth.
IPV6 will involve more digits/typing/remembering than IPV4. Of course sysadmins are reluctant.
---If you can't trust a nerd, who can you trust?
"If studies like this aren't acted on ... then instead of having a quarter of all the world's ISPs clustered here, around Reston, you'll have a quarter of the world's ISPs clustered around Tokyo or Beijing. I don't know if that's what the U.S. government really wants."
Hmm... moving AOL to Tokyo or Beijing might not be a bad idea. Would be much more expensive to send out all those CDs to people here...
-- If god wanted me to have a sig, he'd have given me a sense of humor.
Ehm, I'm currently surfing on Slashdot (IPv4), while my mail is sent using an IPv6 SMTP server. I only have *one* connection to my ISP, and only one NIC, and only one router.
IPv4 and IPv6 can easily coexist, and IPv6-only programs don't even have to be modified to accept IPv4 connections (keyword "IPv4-mapped addresses").
A miracle?
I have a minimal writeup on my blog here. It states where I got my 6to4 tunnel from, how to activate the tunnel (in FreeBSD), and the problem I faced when activating the tunnel! All in all, now my webserver answers requests on ipv6!! Check it out! Its very easy, I suggest all geeks at least try this at home. Later tomorrow, once I'm done testing, I will put an extensive writeup on how to make your home network a functioning IPV6 ONLY network (includes: Windows Boxes, Mac Boxes, Linux Boxes, FreeBSD boxes, and OpenBSD Boxes).
First, you need to make it cheap and easy to migrate, and make it part of the OS. Want a new Windows machine? Fine. It'll connect to the Internet and Ipv6 transparently, and you won't see the difference.
Second, move all the porn sites to IP v6.
Actually, screw step 1. If you can manage step 2, and keep any new upstarts from taking over the vacated IP v4 porn market, then IP v6 will become the standard within a year. We'll all have a laugh over the contorted and convoluted arguments PHBs with little to no technology understanding will come up with to justify switching their corporate networks to IP v6.
"Live Free or Die." Don't like it? Then keep out of the USA
it took me 15 minutes to set up 6to4 on mac os x...
I can access any ipv4 address or ipv6 address without any problems.
but I guess that doesn't count as an "easy way...to try it out"
much to the dismay of all my developers, my answer to just about every problem is "you can use an ssh tunnel for that"
when i bought my powerbook 15 months ago, reverse tunnels stopped working, and it took me awhile to figure out why.
normally you'd run something like:
ssh -R 8080:localhost:8080 user@remotedevbox.com
to let a remote server access tomcat running on your laptop.
i suspect OSX routes "localhost" to the ipv6 address by default in this case. the solution was to change the tunnel:
ssh -R 8080:127.0.0.1:8080 user@remotedevbox.com
point being... from the "what have you done for me lately" perspective, ipv6 has been nothing but a headscratcher. and we're supposed to run the internet on it?
For example I am setting up a nature webcam site which will be ipv6 only for exactly this reason.
Until the porn world goes IPv6 only there will be no major rush to upgrade. I really hope that your "nature webcam site" is really nude women running around in the forest or I just don't see it making a difference.
I first implemented IPv6 on a Cisco 7120 with a single FreeBSD 4.0 box as a host behind it - this would have been some time in late 2000. The IPv6 link came from Viagenie and this lasted a few months before I got bored with it.
I tried again last year with a couple of cable modem attached Cisco 17xx and some tunnels from Hurricane Electric. I was at a point where I wanted to do a lot more with IPv6 to get ready for my CCIE exam. HE was relentlessly useless in getting me more than what their tunnel broker system provided so I gave up again.
I tried later last year with BTexact's tunnel broker service and some other routers. Made it run, then started moving offices and lost interest.
I'm at it again - BTexact because they've got the best tunnel broker web interface and they'll give multiple tunnels, Cisco 28xx here, Cisco 17xx at a playful customer's site, and one FreeBSD 5.4 host. My CCIE gets closer and closer so this time its gotta go - web server, DNS, going to put up six total tunnels, then press for a block larger than the default
Looking at IPv6 from the outside it would appear that someone collected a bunch of people who got kicked out of IETF for mental instability, a number of disgruntled Novell employees who believed that IPX was a gift from an advanced space alien culture, and locked them all in a junior high gymnasium with a goodly supply of blotter acid and two boxes of twinkies. Its the only explanation we have for the results we see today
I am very easy to get along with, but I don't have time to waste being nice to people who are being stupid. -Theo
Few articles actually address real IPv6 benefits and instead pull out strawmen about a purported shortage of IP addresses. That's got to be the least significant and least relevant change between IPv4 and IPv6. Maybe that's all the 'journalists' can get their teeny minds around, or maybe it's mandated spin because certain key advertising accounts *cough*MS*cough* aren't looking to be IPv6 compliant any time soon.
Some of the main advantages of IPv6 over IPv4 are:
- quality of service
- simplified headers
- multicasting
- security (that's certainly buzzword compliant, why is it never brought up?)
- autoconfiguration
- improved routing
- authentication
Japan and China are already rolling out IPv6 networks. Since the article specifically points out the U.S., maybe it's time that U.S. businesses start getting technical news from sources other than their MS account representative.Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
I could set up my servers to do IPv6, but I don't have sufficient motivation to do so. It takes time and energy to get this set up, and I don't see any return for doing so. This is because the network effect is not yet strong enough. Someone has to work on getting IPv6 to "Cross the Chasm" or to "the Tipping Point".
Helping with organizational effectiveness is our job.
These guys have a good tunnel broker interface:
https://tb.ipv6.btexact.com/
I used these guys a couple of years ago and they made me very sad:
ipv6tb.he.net/
I am very easy to get along with, but I don't have time to waste being nice to people who are being stupid. -Theo
Other than larger address space?
- New header format (less overhead in routers)
- A new Efficient and hierarchical addressing and routing infrastructure (again....less overhead in routers)
- Stateless and stateful address configuration (You could theoretically dump your DHCP servers)
- Built in IPsec
- Better support for QOS (Quality of service) in the protocol fields
- It's extensible (more headers can be added..it's in the protocol)
and more...
Most users use a firewall to do NAT at the moment., they thus get some level of protection.
Take that away, have loads of IPV6 addresses and un-informed consumers, and your setting yourself up for your uC driven toaster, oven, refrigerator, entertainment center etc spamming people.
It just gives me the screaming heebie-jeebies -- does anyone else remember the feeling of walking into a PeeCee site that was 'internet connected'back in the 90's and asking what they were doing and finding out every un-patched PC had a distinct IP on the internet?
I read that Alexis de Toqueville Institute study as well.
Juniper has a horse in the race, selling network devices.
There's currently an IPv6 conference at which they're appearing as well. The conference ends today (2005-May-26).
There's a Washington Post article on the summit.
I'm posting from the summit, where they have a IPv6 802.11 network up for visitors use.
-- Improve Windows - Buy a Mac!
Actually it's small mammals running around somewhere in England.
Young, petite, teens?
Hey guys, how about you get a clue?
Try IPV8! its a hell of a lot better!
its backward compatible with IPv4 - not necessary to change all the internet hardware or BS
and it has a LOT more addresses than Ipv6 ever will.
Dont like it? then try IPV16 !!!
sheesh you guys are behind the times... really!
Off course once it's released, you'll start waiting for IPv8 (etc)...
It's just FUD. Probably from IPv6 fan-boys.
But don't take it from me. Take it from the guy who runs the organisation that gives out addresses to India and China.
While there are certainly cases where NAT isn't nearly good enough, for the vast majority of users it IS good enough.
That's what makes IPv6 acceptance so slow: your ISP isn't going to rebuild its infrastructure so that you can run a SMTP server. Certainly not for the measly (from their POV) $50 a month you and your friends are paying for that line. If you want a static IP, or a few, you can have it, but you'll start paying $150 a month or more for the service.
Some day, those necessary static IPs will be too rare, and you'll have to switch ISPs to get it. At that point your ISP will need to switch to IPv6 to keep your business. I have no idea when that day is. It may well be soon; I can't say. But as a major investment for your ISP they're going to put it off as long as possible.
So the answer to your question, "Why shouldn't people be able to have full IP connectivity?" is, "Because not enough people want it to make it worth their while, but if you really want it you can pay for it."
It's got built in equivalent of IPSEC. That alone would go a long way in improving most computing environments.
"Improved routing" refers to, among other things, route aggregation which reduces the size of routing tables which is helped by the simplified header which reduce router processing loads.
Someone with more networking knowledge can clarify why the IPv6 functions are much better than the IPv4 ones, where they may appear to overlap.
Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
Most ISPs don't want their users hosting ANYTHING out of their living-room. That would use up bandwith which is directly linked to the pocketbook of your ISP. What ISPs want is home users paying a regular rate and using a minimal amount of bandwith (e.g. surfing the web, checking email). Not serving up their home movies or getting slashdotted.
Not to mention that by making dynamic IPs the industry standard, they can treat "static IP" as an extra feature and charge through the nose for it. (Much like text-messaging & ring-tones on cell phones.)
All of which is to say, ISPs see no profit from giving all their users static IPs. IPv4 is a blessing because it makes static IPs precious. Moving to IPv6 would just cut apart that revenue stream (at least in the short-run, which is all most companies seem to be concerned with).
-tom
It breaks my pluginses, my precious!
You can run dhcp on ipv6. Your isp can choose how they set up things, just like with ipv4.
Autoconfiguration with MAC addresses might not be the answer for ISP networks, since an ISP might not have enough control about people's NICs or how they will use MAC numbers. I suspect they will offer two solutions: one DHCP-like with 1 ip for cheaper accounts, and one with
In 2000, I had an ISP that had native ipv6 support, and I was assigned one random ipv6 address through dhcp.
As I understand it, one of the main selling points of the whole ipv6 setup was that end-users would be alotted a
Well, that's no surprise; there's hardly any interest in today's internet.
Read up on IPv6 some time.
Dude, I've been working with IPv6 for 7 years or so.
It's got built in equivalent of IPSEC. That alone would go a long way in improving most computing environments.
"built in equivalent of IPSEC"?? Huh? Rather, you mean the IPv6 standard requires that IPv6 implementations must have IPSEC, I am guessing. IPv6 with IPSEC is no more secure than IPv4 with IPSEC.
"Improved routing" refers to, among other things, route aggregation which reduces the size of routing tables which is helped by the simplified header which reduce router processing loads.
You are confusing two things here. IIRC, IPv4 checksum includes the TTL count, which means it has to be recalculated at every hop. This was fixed in IPv6. It's been a few years, but I think that this is what people normally refer to by "simplified headers".
Route aggregation, OTOH, is directly a result of address allocation policies. The hope is that because we can give "enough" addresses to each ISP, that any given network will only have to advertise a single route, thus minimising the number of routes that routers must maintain. This is a beneficial (and as yet unproven) side-effect... of having lots of addresses!
Someone with more networking knowledge can clarify why the IPv6 functions are much better than the IPv4 ones, where they may appear to overlap.
If you're talking about the socket API, in my experience there is no real advantage to the IPv6 functions. They exist so that you can manipulate IPv6 addresses, nothing more, nothing less.
Given the quantity of addresses available for IPv6, I'm unsure as to why IPv4 couldn't / wasn't made a subset of IPv6?
Right now we've got a catch-22 it seems. Why would I offer an IPv6 ONLY service, if that means a ton of my users will be locked out? As long as I offer an IPv4 service, why would my users switch? They can just use IPv4 up the stack.
If IPv4 address were subsets of IPv6, couldn't an IPv4 users request an IPv4 address. Once it hits their ISP, check routing and prefix if possible with IPv6 prefix. This could happen anywhere along the line, including just the last hop. My server can just run an IPv6 stack, and know that the rest of the internet, IPv4 and 6, can reach it.
Instead, we've got a "fresh start" approach, which seems like a bit of a stretch.
Or am I missing something obvious here? It sure looks to me at this point that running an IPv6 only server is a bit complicated unless you set up a broker or something else manually.
But is like USB adoption, Microsoft won't do it until 'Apple's done it'.
Guess what? Apple's already done it, (with Airport Extreme and Express, with eight octet groups right on the hardware,) but they're not making a big deal out of it because Apple's customers are not tech savvy enough to know what the fuss is about anyway.
All Apple need to do is start making a noise and Microsoft will once again play 'catch up.'
I'm running IPv6 on my friggin LAN and the WAN is only running IPv4. Go figure?
MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
I posted about this a couple of years ago I think.
Everyone keeps talkign about NAT and its problems and support for apps and services. The real reason that IPv6 isn't being adopted is because core backbone providers aren't forcing it. No one has made a real commitment to IPv6, so it is not used at the enterprise level.
If you start with service providers, I don't believe that there is a lot of IPv6 even at that level. This is only really my conjecture, but as a consultant in the network management space, I don't hear customers begging for products that support IPv6. And until the backbone providers , and the IETF, decide that IPv6 must go forward, NAT is going to work for most people, and not much will change.
IPv6 is going to be a tough row to hoe, it will necessitate a lot of updates to libraries and software before it can be fully supported. A lot of companies spend a lot of money every year to monitor and manage their business systems with IPv4 based applications, and aren't going to risks the expense until IPv6 is necessary and vendors fully support it.
One problem is that the united states has a lot more IPs per population than most of the rest of the world (does anyone have exact numbers for this?), so we'll be one of the last to run out, and therefore one of the last to adopt ipv6, which puts us in a very bad position.
A similar problem on a smaller scale is that those who own a lot of IPv4 addresses now have a competetive advantage over those who don't, and these are exactly the people (large ISPs, telco companies) who need to adopt IPv6 in order for it to take off. Their control of a scarce resource gives them a relative advantage against those who don't, so why would they ever want to cooperate to make that resource become non-scarce? It just isn't in their best interests.