After much discussion and debate we have decided that giving the MetaNet IPv6 addresses isn't such a trivial task. Basically the only types of addresses that work with the structure of MetaNet are Global Unicast Addresses (defined in RFC:2373 and RFC:2374) ie. (Real-World) IP addresses. The RFC:1918 equivalent IPv6 addreses are designed for "site" use only and previous experience (OSPF) has taught us that treating the MetaNet as a single site does not work very well. The problem now becomes how to obtain Global Unicast Addresses that we can use on MetaNet. For now the solution that we have come up with is that each MetaNet user who wants to participate in MetaNetIPv6 testing needs to obtain for themselves a /48 allocation from www.freenet6.net. This will then be routed using bgp+ over the MetaNet. 

  

 These instructions are currently very Debian orientated. Sorry, perhaps you should migrate to debian is you are not already using it. Or you could update this page with info for your distro of choice. 

  

 * IPv6 Capable Linux Box see [IPv6Setup] 

 * Working Knowledge of IPv6 

  

 Visit http://www.freenet6.net/cgi-bin/new_account.pl and create an account for yourself. It is recommended that you use your metanet site name as your userid for freenet6 as they use it to setup your AAAA record.%%% 

  

  apt-get install freenet6 

  /etc/init.d/freenet6 stop 

  

 Check your inbox. Hopefuly you have received an email containing your Freenet6 username and password. Remeber them, you'll need them in a second.%%% 

 Edit the file /etc/freenet6/tspc.conf so that it looks the this example [tspc.conf] Substitute your username and password from above in the appropriate places and fill in the correct value for the if_prefix line (i'll use eth0 for the rest of the documentation).%%% 

 Save the file and exit 

  

  /etc/init.d/freenet6 start 

 You should see something similar to the following 

  victor:/etc/freenet6# /etc/init.d/freenet6 start 

  Setting up freenet6 IPv6 tunnel (wan1): 3ffe:b80:3:935d::2/128 

  inet6 addr: fe80::205:1cff:fe10:41c8/10 Scope:Link 

  inet6 addr: 3ffe:b80:1f16:1::1/64 Scope:Global 

 First are your standard IPv4 address(es) followed by your IPv6 addresses. Ignore the first address (it is a special link-local address used for configuration) the second address is what we are concerned with. It has global scope and is routable from anywhere on the 6bone! This address has been allocated from your /48 and you can see that the freenet scripts have been clever and have placed your internal network on a further subnet inside this to give an IP address with a /64 netmask. So for example the /48 shown in the example is 3ffe:b80:1f16 and the subnet is 1. 

  

  ping6 2001:458:20:100::1 

  traceroute6 2001:458:20:100::1 

  

 ''note you need iputils-tracepath for traceroute6 under debian -- PerryLorier'' 

  

 Now you need to give your internal machines IPv6 addresses, this can be easily accomplised using zebra add the lines to your zebra.conf 

  interface eth0 

  ipv6 nd send-ra 

  ipv6 nd prefix-advertisement ''your allocation from above'' 

 This will cause zebra to do router announcements on eth0 for your internal ranges. Any machine on that network will hear the router announcements and will automatically assign itself an IP address out of that range. 

  

 Make sure your client machines have ipv6 enabled see [IPv6Setup] for more information on this. 

  

 * The IP addresses that you now have on your gateway and client machines ARE world-routable. You may want to firewall them. See [IP6Tables]. 

 * The IP address of your wan1 interface is not in your /48 it is your tunnel endpoint 

 * You will have very high latency (~600ms) talking to any real-world or 6bone hosts as your packets traverse the tunnel. 

  

  

 * First, upgrade Etud, the old version has a bug where you can't assign IPv6 addresses to the wan0 interface. Oops.[1] 

 * Establish your link-local IP address for your wan0(or whichever) interface. 

 * talk to JamesSpooner or PerryLorier about organising ipv6 [BGP] peering. 

  

 Note: We are now using LinkLocal addresses rather than an allocation from someones range. If these don't ping right have a look at their Wiki Entry. 

  

 [1]: Etud was echoing packets that the kernel sent back to itself. This had the problem that the kernel would say "Is anyone using this address" and then would hear that yes, someone is using it (itself!) so it would stop using it. Doh. 

  

 * A top priority for you should be to configure DNS so that we can ping you without using those nasty hexadecimal IPv6 addresses. 

 * More coming later.. http://www.isi.edu/~bmanning/v6DNS.html may be usefull 

 * You can get reverse DNS delegated for your /48... See http://www.freenet6.net/reverse-dns.shtml for more info.