What d’you want for nothing, a global, anonymized, link-encrypted wireless mesh ipv6 network? Yeah, me too.
Let’s build some of those and then hook em together, what say?
Using off-the shelf wifi hardware and cheap old computers (or fancy store-bought bespoke devices, your choice) it’s cheap to put together a local meshnet (where by “cheap” I mean “much cheaper than wiring up your neighborhood.”) It’s technically non-trivial, but pieces of it can be easily achieved.
Anonymization: Tor works over pretty much anything. It adds a bit of latency, which meshnets can ill afford, but there are ways to mitigate that.
Link encryption: CJDNS offers this and a lot more. IMO each hop of a route should be encrypted, in addition to end-to-end encryption. Cycles are cheap these days.
Wireless mesh: Wifi hardware is typically used in one of two modes: Infrastructure mode (like your wireless access point) and Managed mode (like your laptop or smartphone). Another one, Ad-Hoc mode, allows wireless interfaces to connect to each other on a “peer-to-peer” basis. Not all wifi hardware supports this mode, but most does. A “mesh” network is one in which every node in the network (that is, every device which is connected to it) participates in routing messages within the network and to other networks. Currently my personal favorite among the various mesh protocols is BATMAN-adv – largely because lots of devices already support it (it’s built-in to Linux (sort of.))
IPv6: At this point I think we can safely conclude that most ISP, at least in the US, won’t migrate to IPv6 until they are dragged there kicking and screaming. This means that IP addresses will continue to get rarer and more expensive, as the IPv4 address space has mostly run out.
What this means is that it will be more difficult for small operators to get a presence on the Web, and that home users of the Internet will continue to be second-class citizens.
What better way to force a migration to IPv6 than to build out the network ourselves? It’s cheaper to obtain a block of publicly routable IPv6 addresses larger than the entire internet than it is to get one routable IPv4 address. It’s possible that someone out there has already allocated a routable IPv6 prefix for public use. If not, I’ll probably do it- some day when I have a spare minute and an extra dollar.
Global: with these technologies, neighbors can implement a local and reasonably secure network on the cheap. These neighborhood networks (neighbornets?) won’t scale to very large size before latency and routing overhead become a problem. Therefore it makes sense to deploy such networks on a local basis, and provide gateways between them. Such networks are also not a replacement for the global Internet. What’s needed is to link the disparate networks into larger (say, municipal) internets with local gateways and local fiber; and to link these internets into larger (say, county-wide) internets, and so on until global reach is achieved. At this point, the current Internet would be just another internet.
I’ve been thinking about this stuff for a long time, but haven’t done much with it due to lack of funds, time, and patience. Right now other projects are prioritized ahead of it. If anyone reading this is interested in learning more about it, please feel free to PM me.