Following an unfortunate sequence of events, my mail server is currently reachable only via IPv6. It took me a few days to even notice the lack of IPv4.
IPv4 connectivity should be back in a day or two. We fixed the root problem last night.
What I learned from this involuntary experiment: Lack of IPv4 access for a mail server is real problem in 2024, it's something that has to be fixed, but it's a surprisingly small problem.
Googlebot started crawling v6-only web sites in August. The pages it visits still do not appear in search results.
This is only the fifth crawler to visit my v6-only site.
I have an IPv6-only web site. It's a draft, full of broken links and I'm not making much progress, so I thought I'd make it v6-only to limit its audience.
Googlebot still doesn't see v6-only sites, but two other web crawlers have found the site in the past month.
People keep saying blah about how IPv4 can go on even if there are no free addresses, they'll just be traded on a free market.
So. I don't think so.
Either, the blocks to be traded will primarily be large (the kind commonly routed today), or primarily be small (the kind commonly handed to end-users). I'll argue each separately. […More…]
I enable IPv4. Temporarily at least. […More…]
If you can read this sentence, you have IPv6 support, either directly or via a web proxy. (Update: no, I added IPv4 access to the blog.) […More…]
Bad news: Opera lost IPv6 ability in version 10.10. Opera cannot connect to this site, even if it's running on a host with IPv6 ability.
No news: The search engines still don't support IPv6. The (other) browsers still support IPv6.
Good news: Today I saw a torrent swarm with more than 20% IPv6 peers. Not a special swarm in any way: I download my old LPs whenever I play them, so I'll be able to play them in the kitchen or office too next time. It was the torrent swarm for one of them.
Googlebot, msnbot and Yahoo Slurp have all seen links to rant.gulbrandsen; none of them followed the links.
On one hand, a blog which can't be indexed by the major search engines is pointless. On the other, this particular blog is really a CMS/publishing tool for my writings and ramblings about udoc and literate programming, and until I'm done with that subject, it doesn't matter much whether anyone can read the site, oops, the blog. So I'll leave it 6-only until that writing is more or less done, then reconsider the matter.
Mikrotik makes a series of small, neat routers. I have a 433UAH (with indoor case), which has a VPN tunnel to OpenVPN running on a rented server at vollmar.net. This describes how to build an IPv4 and IPv6 VPN tunnel between a Mikrotik router with a dynamic IP address and a Linux server running OpenVPN with fixed IP addresses. […More…]
New IPv4 addresses are being allocated at a rate of 6-7 per second and there aren't very many left. In a while, we're going to run out. What then?
I think that when it happens, some people will try to buy other people's IPv4 addresses, but frankly I doubt that there'll be enough willing sellers to supply 6-7 addresses per second, so at least some people will have to make do with only IPv6 addresses. That's going to be painful.
That period will be less painful if a few people put web sites and other services on only IPv6 now, so that the transition starts sooner, with fewer victims, and ramps up later.
I'm not willing to do all that much. But this blog is unimportant, so I put that on IPv6. I could have used a name-based virtual host or used one of my free IPv4 addresses, but someone has to make a start.
Later, maybe I can put something other than a web site on IPv6.
