You only need a /48 if you have multiple subnets behind your tunnel. If you do not have separate subnets for eg your wifi and wired, you can use a single /64 just fine. And that single /64 comes per default with a tunnel. Note that you per tunnel receive two /64's: one for the tunnel (where the <tunnelprefix>::2 is your side of the tunnel and <tunnelprefix>::1 is the PoP), and a second /64 which is routed toward <tunnelprefix>::2 that you can use for your local network. See your home for a easy overview as there they are listed. You do not need to request a /48 unless you have a need for multiple /64s. You do not need IPv6 DNS servers, as one can resolve IPv6 DNS records (AAAA) over IPv4 or IPv6 transport. Most very likely and that is how it is supposed to work too ;) Why do you think it is unreliable just for IPv6? Please note that IPv4 and IPv6 addresses are stored in the same DNS system. Unless you are going to do millions of DNS queries, the DNS traffic will really not be noticed. What one typically does when one has a home server (be that a Windows or Linux box or anything else), is to install a so-called caching DNS proxy. Typically that is unbound, pdns-recursor or even a full BIND so that one can also configure some local zones (which is handy if you want to server local IPv6 addresses from a local domain for instance, unless you do that from a server on the Internet). This way that local caching server can do all your DNS resolution and one can even avoid using the ISP resolvers. On Debian/Ubuntu it is indeed really that easy. Thanks to Gary Coady's work several years ago one even gets easy to use debconf questions for the configuration which makes it much easier than Windows setup actually... aiccu is the first step, then your server has the connectivity. The second step is to setup radvd and fill in the subnet prefix into radvd.conf, enable IPv6 forwarding on the server, start up radvd and presto, all should work.

A quick progress update. I didn't get around to doing anything until this evening. I installed aiccu on ubuntu, that part was very easy, and it seems to be working just fine. Then I thought I better then remove it from my Windows 7 Laptop. I wasn't sure exactly how to do this so I just went into the device manager, and disabled the itap driver, and the teredo driver. I've now been trying to get ubuntu share my IPv6 connectivity with the rest of my network, but right now I'm coming up against a problem. When I type sudo /etc/init.d/radvd restart I get: Stopping radvd: No /usr/sbin/radvd found running; none killed. radvd. Starting radvd: * IPv6 forwarding seems to be disabled. * See /usr/share/doc/radvd/README.Debian * radvd will *not* be started. I think I may have to do some Googling to try and figure out what the problem is, but I don't have any more time tonight.

OK things are making a bit more sense but it's still not working. Andreas you are right about the network prefix. This is the problem of being a newbie, when I started I didn't notice that the prefix of my subnet was slightly different from my IPv6 address. I realised and changed this a while ago. One point that is still a little confusing is that when I go to Test your ipv6 on my ubuntu machine it says my ip address is 2a00:14f0:e000:9d::2 So does this mean that the address ubuntu machine uses to access the IPv6 internet is slightly different from the one I should be sharing to the rest of my subnet? Jeroen. Thanks for the commands to disable the tunnel adapters on my Windws 7 Laptop. Windows 7 now says it's ipconfig is Windows IP Configuration Wireless LAN adapter Wireless Network Connection 10: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Wireless LAN adapter Wireless Network Connection 9: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Wireless LAN adapter Wireless Network Connection 2: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2a00:14f0:e000:809d:b8a5:9fca:6a51:dadd Temporary IPv6 Address. . . . . . : 2a00:14f0:e000:809d:a0df:a8d7:8421:fdec Link-local IPv6 Address . . . . . : fe80::b8a5:9fca:6a51:dadd%23 IPv4 Address. . . . . . . . . . . : 192.168.1.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : fe80::21c:c0ff:fec8:45a3%23 192.168.1.251 Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : (wireless adapters 9 and 10 seem to be some type of virtual adapters that Windows 7 keeps installing, and I keep deleting Grrr....). Another part I'm confused about is whether my /etc/radvd.conf should use eth0, the same as my ipv4 interface, or whether an ipv6 tunnel uses some other interface such as eth1. Perhaps I'd better quite my current configuration files. /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.1.202 netmask 255.255.255.0 gateway 192.168.1.251 dns-nameservers 192.168.1.251 # Trying to configure Ipv6 tunnel, apparently I need to define a # local IPv6 address as well # iface eth1 inet6 static # address 2a00:14f0:e000:809d::2 # netmask 64 (the commented out lines at the bottom are something I tried that I saw on a web page, but they caused all my internet access to stop working, so I decided they must be wrong and commented them out). /etc/radvd.conf interface eth0 { AdvSendAdvert on; MinRtrAdvInterval 3; MaxRtrAdvInterval 10; prefix 2a00:14f0:e000:809d::/64 { AdvOnLink on; AdvAutonomous on; AdvRouterAddr on; }; }; Another question. I tried to ping my ubuntu machine from my laptop using ipv6. To be honest, I really didn't know what ipv6 address I should be trying to ping, and so I just tried every combination I could think of, and none of them got any response. Is Ubuntu supposed to respond to ping in this way, and what address should I be trying to ping? If I can't even ping my routing machine then that might indicate ipv6 being blocked in some way. Any more ideas. I'm a but stuck at the moment. Thanks. Richard.

A quick update. I tried pinging the ipv6 gateway as returned by ipconfig, and that worked. So my Ubuntu machine is accepting incoming IPv6 packets using the link local address.

Perhaps I should also quote my sysctl and aiccu.conf (obviously I'll erase my SixXS passowrd) richard@Music-Server:/etc$ cat sysctl.conf # # /etc/sysctl.conf - Configuration file for setting system variables # See /etc/sysctl.d/ for additional system variables # See sysctl.conf (5) for information. # #kernel.domainname = example.com # Uncomment the following to stop low-level messages on console #kernel.printk = 3 4 1 3 ##############################################################3 # Functions previously found in netbase # # Uncomment the next two lines to enable Spoof protection (reverse-path filter) # Turn on Source Address Verification in all interfaces to # prevent some spoofing attacks #net.ipv4.conf.default.rp_filter=1 #net.ipv4.conf.all.rp_filter=1 # Uncomment the next line to enable TCP/IP SYN cookies # See http://lwn.net/Articles/277146/ # Note: This may impact IPv6 TCP sessions too #net.ipv4.tcp_syncookies=1 # Uncomment the next line to enable packet forwarding for IPv4 #net.ipv4.ip_forward=1 # Uncomment the next line to enable packet forwarding for IPv6 # Enabling this option disables Stateless Address Autoconfiguration # based on Router Advertisements for this host net.ipv6.conf.all.forwarding=1 # Line added following instructions in radvd README file net.ipv6.conf.default.forwarding=1 # Apparently the .all version is for existing interfaces # and the .default option is for new interfaces. # Hence it is best to have both lines. ################################################################### # Additional settings - these settings can improve the network # security of the host and prevent against some network attacks # including spoofing attacks and man in the middle attacks through # redirection. Some network environments, however, require that these # settings are disabled so review and enable them as needed. # # Do not accept ICMP redirects (prevent MITM attacks) #net.ipv4.conf.all.accept_redirects = 0 #net.ipv6.conf.all.accept_redirects = 0 # _or_ # Accept ICMP redirects only for gateways listed in our default # gateway list (enabled by default) # net.ipv4.conf.all.secure_redirects = 1 # # Do not send ICMP redirects (we are not a router) #net.ipv4.conf.all.send_redirects = 0 # # Do not accept IP source route packets (we are not a router) #net.ipv4.conf.all.accept_source_route = 0 #net.ipv6.conf.all.accept_source_route = 0 # # Log Martian Packets #net.ipv4.conf.all.log_martians = 1 # richard@Music-Server:/etc$ richard@Music-Server:/etc$ sudo cat aiccu.conf [sudo] password for richard: # Under control from debconf, please use 'dpkg-reconfigure aiccu' to reconfigure # AICCU Configuration # Login information (defaults: none) username REM6-SIXXS password ************(deleted) # Protocol and server to use for setting up the tunnel (defaults: none) protocol tic server tic.sixxs.net # Interface names to use (default: aiccu) # ipv6_interface is the name of the interface that will be used as a tunnel interface. # On *BSD the ipv6_interface should be set to gifX (eg gif0) for proto-41 tunnels # or tunX (eg tun0) for AYIYA tunnels. ipv6_interface sixxs # The tunnel_id to use (default: none) # (only required when there are multiple tunnels in the list) tunnel_id T93914 # Be verbose? (default: false) verbose false # Daemonize? (default: true) # Set to false if you want to see any output # When true output goes to syslog # # WARNING: never run AICCU from DaemonTools or a similar automated # 'restart' tool/script. When AICCU does not start, it has a reason # not to start which it gives on either the stdout or in the (sys)log # file. The TIC server *will* automatically disable accounts which # are detected to run in this mode. # daemonize true # Automatic Login and Tunnel activation? automatic true # Require TLS? # When set to true, if TLS is not supported on the server # the TIC transaction will fail. # When set to false, it will try a starttls, when that is # not supported it will continue. # In any case if AICCU is build with TLS support it will # try to do a 'starttls' to the TIC server to see if that # is supported. requiretls false # PID File #pidfile /var/run/aiccu.pid # Add a default route (default: true) #defaultroute true # Script to run after setting up the interfaces (default: none) #setupscript /usr/local/etc/aiccu-subnets.sh # Make heartbeats (default true) # In general you don't want to turn this off # Of course only applies to AYIYA and heartbeat tunnels not to static ones #makebeats true # Don't configure anything (default: false) #noconfigure true # Behind NAT (default: false) # Notify the user that a NAT-kind network is detected #behindnat true # Local IPv4 Override (default: none) # Overrides the IPv4 parameter received from TIC # This allows one to configure a NAT into "DMZ" mode and then # forwarding the proto-41 packets to an internal host. # # This is only needed for static proto-41 tunnels! # AYIYA and heartbeat tunnels don't require this. #local_ipv4_override richard@Music-Server:/etc$

I seem to have confirmed that my ubuntu is not routing anything. I discovered a utility called pingpath, and I entered pingpath -6 ipv6.google.com the result was not encouraging. Tracing route to ipv6.l.google.com [2a00:1450:400c:c00::67] over a maximum of 30 hops: 0 richard-VAIO [2a00:14f0:e000:809d:5d43:9032:28f0:65c3] 1 * * * Computing statistics for 0 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 richard-VAIO [2a00:14f0:e000:809d:5d43:9032:28f0:65c3] Trace complete. I've pretty much spent all day on this, and can't figure out why it wont work. :-(

Hurray, a result. All I did was add the lines you suggested to /etc/network/interfaces and edit /etc/radvd.conf changing eth0 into sixxs. Oh and then restart the machine. Then when I tried pinging ipv6.google.com, it worked. Now my windows machines have IPv6 connectivity. Windows 7 is still being awkward about Ipv6 DNS, which will be something I can look into later. The nice surprise is that DNS seems to work OK on my older Windows XP Laptop. I'm pretty sure I know why that it, I read that Windows Vista and Windows 7 prefer not to resolve Ipv6 addresses when the only IPv6 connection is a tunnel. Next however I probably better see if I can still get connectivity with UFW active. Although actually before that I have non computing things I need to get done today :-( Well now I can start experimenting with IPv6 on my laptops. Thanks very much for your help, without you I was going around in circles trying to work out what to do. Thanks. Richard.