comparison doc/www.anonet2.org/public_pod/faq.pod @ 498:7ad8b0d24cd1 draft

Updating faq.pod for a2.o with new IPv6 info
author lex <lex@lynx.ano>
date Mon, 09 May 2011 23:49:39 +0000
parents bf59001028f4
children 9f6446024c18
comparison
equal deleted inserted replaced
497:dddace3d21ef 498:7ad8b0d24cd1
291 anarchy is IPv6: SRN has made no secret of his strong opposition to IPv6, 291 anarchy is IPv6: SRN has made no secret of his strong opposition to IPv6,
292 but that didn't stop an enterprising new AnoNet2 user from deploying 292 but that didn't stop an enterprising new AnoNet2 user from deploying
293 it himself and connecting with others, even after "the management" 293 it himself and connecting with others, even after "the management"
294 (both UFO and SRN) flatly refused to participate. 294 (both UFO and SRN) flatly refused to participate.
295 295
296 Update: The IPv6 version of AnoNet2 now has 4 members, and lex is 296 Update: The IPv6 version of AnoNet2 now has 6 members over roughly 11
297 providing data to feed SRN's new IPv6 graphs, which are only reachable 297 IPv6-capable hosts, and lex is providing data to feed SRN's new IPv6
298 over IPv4. (After lex grew the network to 3, UFO joined.) 298 graphs, which are only reachable over IPv4. (After lex grew the network to
299 3, UFO joined.) lex also provides transit between IPv6 Anonet and dn42,
300 carrying traffic inside ULA ranges between the two darknets. Services are
301 starting to become available over IPv6.
299 302
300 =item Why don't AnoNet1 and AnoNet2 merge again? 303 =item Why don't AnoNet1 and AnoNet2 merge again?
301 304
302 The short answer is that a number of people have tried to do just that, 305 The short answer is that a number of people have tried to do just that,
303 but AnoNet1 has adopted an exclusionary policy towards AnoNet2, for some 306 but AnoNet1 has adopted an exclusionary policy towards AnoNet2, for some