Slashdot Mirror
The Night the IETF Shut Off IPv4
IP Freely writes "At this year's Internet Engineering Task Force meeting in Philadelphia, conference organizers shut off IPv4 for an hour. Surprisingly, chaos did not ensue. 'After everyone got his or her system up and running, many people started looking for IPv6-reachable web sites, reporting those over Jabber instant messaging — which posed its own challenges in the IPv6 department. I was surprised at the number of sites and wide range of content available over IPv6. Apart from — obviously — IPv6-related sites; they ranged from "the largest Gregorian music collection in Internet" to "hardcore torrents." Virtually none of the better known web destinations were reachable over IPv6. That changed when ipv6.google.com popped into existence.'"
I'm glad to know that the internet will still be able to fulfill its primary purpose as a porn distribution channel when we switch over to ipv6.
I like my beverages with warning labels!
More about the hardcore torrents, please.
Who else put ipv6.google.com in their address bar just to see what would happen?
Request your free CD of my piano music.
And really, only problems I saw were the fact that it's pain in the ass to get automatic DHCPv6 working. The idea is that IPv6 stateless autoconfig (router advertisement) has a bit that tells the client if they should get ALL config via DHCP or just additional (like DNS addresses). However, no easy way to make Linux kernel execute DHCPv6 client based on the received stateless autoconfig bit.
Anyway, after statically configuring DNS servers, things were very smooth. Google et al worked, I could access entire IPv4 web via sixxs.org (just go http://slashdot.org.sixxs.org/ to access Slashdot via IPv6), I could SSH to my home servers...only things that seemed a bit odd were failing reverse DNSes on some hops when running traceroute. Jabber worked, IRC worked.
Great experience and experiment.
'Apart from -- obviously -- IPv6-related sites; they ranged from "the largest Gregorian music collection in Internet" to "hardcore torrents."'
Once you can get porn on the medium, you know it is a winner.
Finding things in IPv6 Cyberspace...
"So what's the Gregorian music website?"
It's the little azure ball to the south of the stepped scarlet pyramid of the Eastern Seaboard Fission Authority burning beyond the green cubes of Mitsubishi Bank of America.
I highly recommend using an Ono-Sendai Cyberspace 7 computer deck.
Stay away from Sense/Net if you're a n00b, or you're likely to get iced.
-- Terry
The trouble with ipv6 is that ipv4 works so well for 90% of the population (in the same manner that 76% of statistics are made up on the spot) that nobody who doesn't really care about this won't put in an effort to make the switch. It looks like going 100% ipv6 is quite a few years off, foo.
I _really_ fail to understand the rationale for DHCPv6.
IPv6 was designed o that stateless autoconfig resulted in routable addresses.
Combine that with ZEROCONF, and you can discover everything that a DCHP server is going to be able to tell you, and more.
The only technical rationale I've ever heard is for reverse DNS, to prevent someone getting on the local net without authorization and relaying through your SMTP server, but that requires that you configure your DHCP server to only serve to "trusted" MAC addresses. It's also totally useless with DNSUPDAT, since anyone who gets an address can update the reverse in their home domain, and relay out that instead (which is more secure anyway).
So the only rationale I see is controlling access to network dialtone (a business rationale, based on the business model of selling packets rather than selling pipes - a model I happen to disagree with allowing to continue to exist).
So whose idea was it to turn on DHCPv6?
-- Terry
Sixxs.net lists some IPv6 web sites in its Wiki:
http://www.sixxs.net/wiki/Category:IPv6-specific_content
and there is also some other 'Cool IPv6 stuff' listed on the Sixxs web site:
http://www.sixxs.net/misc/coolstuff/
Jumpstart the tartan drive.
I did, though I expected it to work since I have had IPv6 access for awhile now. I just didn't know that Google had an IPv6 site. Google's homage to the dancing Kame is pretty nice.
All editorial writers ever do is come down from the hill after the battle is over and shoot the wounded.
You assume wrong. It's more like a hardcore TCP/IP packet. These are, in fact, torrents which use every possible function of the torrent protocol, and uses them all to absurd extremes. One or two seeds and trackers? Please. Thousands of seeds and hundreds of redundant trackers on each torrent file. Uses every single port on the machine. Got a webserver set up on 80? Too bad, it's hardcore torrent time, and that port's being taken over.
The content is actually just the string "HELLOWORLD" repeated one billion times, though.
Demanding constant attention will only lead to attention.
Someone should fix that and the traffic would have gone back up to normal load :-)
Here is my list of sites that I was able to reach using native IPv6
using IE worked:
ipv6.google.com
www.ripe.net
www.apnic.net
www.stupi.net
www.arin.net
www.icann.org
www.nlnetlabs.nl
Failed foillowing sites did not work
www.cisco.net/com
www.microsoft.com
www.speakeasy.net
slashdot.org
news.bbc.co.uk
www.mbl.is
www.cnn.com
www.comcast.com/net
news.com.com
www.ibm.com
slashdot was missing,too, and unlike google it still is.
dp@phoenix:~/Desktop$ ping6 ipv6.google.com
PING ipv6.google.com(2001:4860:0:1001::68) 56 data bytes
64 bytes from 2001:4860:0:1001::68: icmp_seq=1 ttl=53 time=221 ms
64 bytes from 2001:4860:0:1001::68: icmp_seq=2 ttl=53 time=214 ms
64 bytes from 2001:4860:0:1001::68: icmp_seq=3 ttl=53 time=221 ms
--- ipv6.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2026ms
rtt min/avg/max/mdev = 214.969/219.185/221.367/3.006 ms
dp@phoenix:~/Desktop$ ping6 ipv6.slashdot,org
unknown host
dig ipv6.google.com AAAA
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 7, ADDITIONAL: 0
;; QUESTION SECTION:
;ipv6.google.com. IN AAAA
;; ANSWER SECTION:
ipv6.google.com. 10455 IN CNAME ipv6.l.google.com.
ipv6.l.google.com. 5 IN AAAA 2001:4860:0:1001::68
ipv6.l.google.com. 5 IN AAAA 2001:4860:0:2001::68
dig slashdot.org AAAA
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
605413? Yes, it's a prime.
With blackjack, and hookers!
What I really want to know is, how many of the people who had computers at that conference were users who had no clue what IPv6 even was, much less how to configure their computer to use it.
It's one thing to say IPv6 is ready because a conference filled with engineers could download their pron with IPv4 turned off. It's entirely another thing to say that IPv6 is ready because it works without my mother even knowing the difference.
There is a theory which states that if ever anyone gets IPv6 working without any glitches, it will instantly disappear and be replaced by something even more bizarre and inexplicable.
We hope your rules and wisdom choke you / Now we are one in everlasting peace
(When it comes to Linux support for protocols, it's a popular platform for early developers, but maintenance can be an issue. enSKIP and SGI's STP code are abandonware, the real-time network driver for RTAI is infrequently updated, and the GAMMA Active Messages driver is seriously stalled in a number of areas. Many updates to Web100 have just been kernel increment updates, not bugfixes or added features. I don't recall seeing any support for VIA - which is fair enough, given it's dead - or iWarp. Linux' QoS supports RED, but neglected BLUE, GREEN, BLACK, WHITE and PURPLE the last time I looked.)
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
"Hardcore torrents"? Probably a pee fetish site.
SIERRA TANGO FOXTROT UNIFORM
IPv6 has around 10^23 addresses per square meter of Earth. The only reason I can think of that we would want to replace it would be if we found a superior replacement for the entire concept of packet switching.
Or you can just bite the bullet and put in the hours, acknowledging that it won't lead to extra revenue but is necessary for the internet to continue.
Well, you're right, I know the manufacturer's would love to sell you new routers. But I've often wondered why there is no market for 'premium firmware upgrades'. That is, let's say I've got a Linksys home router. The hardware is perfectly capable of handling IPv6 - if the firmware just supported it. Yes, I could upgrade to OpenWrt or some other 3rd-party firmware (I think I might, soon, because I've been having on-going issues that I think might be un-fixed bugs in the official firmware), potentially, but I don't see a lot of people ever doing that (voiding your warranty and risking 'bricking' your unit is pretty scary to most people).
Now, if I were Cisco/Linksys (I think Cisco bought Linksys awhile back, no?), I *think* I'd rather sell people a $15 firmware update which gives them cool new features, and which requires me to manufacture 0 new hardware (so the marginal profit is *extremely high*), than to sell them a $40-$60 piece of hardware which requires me to also pay for manufacturing, shipping, and give the retail outlets who are selling it a fat margin (so that, I bet, Cisco only gets $20-30 anyhow, with the rest going to Best Buy, Circuit City, Fry's, TigerDirect, etc).
But, maybe there's more margin in hardware than I realize. Granted, they have to sell hardware anyhow (e.g. for new users who don't have their hardware to begin with), but why not sell existing customers the new firmware without requiring new hardware? I suppose it comes down to there is no established precedent for people paying for firmware. . . they expect it to be free, so the market might not, at least initially, embrace buying firmware upgrades. There are also the technical support issues of having to deal with routers that got bricked because the power went out while the upgrade was in progress or something. But if the router was designed well to begin with, it should be fairly resistant to bricking during the upgrade process.
Still. . . with a marginal cost close to 0 for the 'product', and fewer other people in the chain to split the profits with (they might have to still pay some per-unit fees, like licenses if they use a proprietary 3rd-party embedded OS), it would seem like this could be a reasonably lucrative business model.
A lot of people think they need their ISP's help to get IPv6 connectivity. That's not the case. If you're running Windows Vista, or if you use an Apple Airport router, you should get connectivity to the IPv6 Internet out of the box. If you're running Linux, I've writtent a short HOWTO about IPv6 under Linux.