...

nameserver 2001:610:148:dead::4
nameserver 2001:610:158:98d::42
domain terena.org

Tinyproxy

Some of our systems have extra "security needs", and they are not allowed to initiate outgoing connections by default. This means that IP ACLs are used so that they can only reach neccessary services (SMTP gateway, DNS resolvers, NTP etc).

Because those hosts do need access to some web sites (mostly for software updates), we use a proxy server to allow them access to those domains.

If you have an IPv6-only host that only needs access to some outside HTTP resources, then this approach kills two birds with one stone:

• Many services are run on CDNs such as Akamai, which renders IP ACLs into a nightmare. A proxy solves this by allowing domains/URLs.
• Some services are only accessible via IPv4 (Microsoft Update, hostupdate.vmware.com, Secunia.com). A dual stack proxy does the protocol translation. If those web sites were the only problems on the IPv6-only system, this is just what you need, and you can avoid using additional complex systems such as NAT64/DNS64.

Because we do not need any caching, but only the access restriction part, I choose tinyproxy because it is very light weight and simple.

The only downside is that the tinyproxy that sits in Ubuntu 12.04 does not listen on both IPv4 and IPv6 at the same time

2013-01-04 Shame on me... I didn't test properly , but tinyproxy does work on both protocols 

I assumed that this result:

netstat -tlnpvw | grep tinyproxy
tcp6 0 0 :::8888 :::* LISTEN 3946/tinyproxy

meant that it didn't listen on v4... but I was wrong.

Listen ::
#This will accept connections on IPv6, but also on IPv4: IPv4-mapped IPv6 addresses are used:
#CONNECT Jan 04 15:29:13 [23566]: Connect (file descriptor 6): host.terena.org [::ffff:192.87.30.2]

Listen 0.0.0.0
# This will listen on IPv4 only

Listen 2001:610:148:dead::666
# This will listen only on the specified IPv6 address. Not nice, but workable.

Coda 2 drops support for IPv6

...

Hopefully they add back IPv6 support, perhaps with a configuration switch. Until that time we won't upgrade.

As of December 2012, Coda is at version 2.0.7, and still no IPv6 support.

Remote support with IPv6-only VNC

...

By default it listens on both IPv4 and IPv6 but it can be easily configured to listen only on IPv6:

Image RemovedImage Added

I use this to remotely support people. One important issue: you do have to know the network address before you can connect to it . There are two ways, users are eitherpossibilties:

• In the office. All our computers autoconfigure themselves with the modified EUI64 interface identifier, which is based on the interface's MAC address. This works out of the box for Mac OSX 10.7/10.8, but on Windows you have to manually configure this (once). Note that this does not have to clash with privacy extensions; those can (and should, IMHO) still be disabled. This means that computers will have a(n extra) predictable address in the office, so you can assign easy to remember hostname to them, such as 'laptop-alice-wifi', 'laptop-alice-wired', etc. Note that this does not have to interfere with.
• Out of the office. People working from remote need to set up their Cisco AnyConnect VPN connection. Once that is done, they have IPv6 connectivity, bypassing any NAT boxes they might be behind. They either need to tell me their network address, or I can look it up on our VPN server.

...

MySQL at this moment does not support IPv6 connections, but the development versions seem to support it (sort of). There are tools to make it work, such as https://twiki.cern.ch/twiki/bin/view/EGEE/IPv6CARE.
Not A Problem Here: we have only one host running MySQL, and that will be phased out in the future any way..
Not A Problem Here: we have only one host running MySQL, and that will be phased out in the future any way.

Update 2013-03-22: We were forced to use MySQL for some stuff, but the version in Ubuntu 12.04 appears to have IPv6 support . I configured it to listen to IPv6 only:

bind-address            = '::'

apt-get

security.ubuntu.com does not work, so no security updates. Workaround: use local mirror nl.archive.ubuntu.com for security updates.

Update 2013-03-12: This has been fixed : https://lists.ubuntu.com/archives/foundations-bugs/2013-March/140037.html

Pear Net_Socket

Does not like IPv6 addresses, wrote patch.

...