Page History

2011-02-28

Entire host IPv6 only (removed IPv4 address and A record)

ldap.terena.org

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="12dd2436de63483f-1da74c13-4bba4b98-a8cea1b1-0645f675f977428bf89aafe7"><ac:plain-text-body><![CDATA[

2011-02-07

Nagios runs only on IPv6

Configure Listen [2001:610:158:98d::42]:80 in /etc/apache/ports.conf.

]]></ac:plain-text-body></ac:structured-macro>

2011-02-07

Entire host IPv6 only (removed IPv4 address and A record)

svn.terena.org

2011-02-01

All linux servers run Postfix on IPv6 only (except listed MXs)

Remove IPv4 addresses from $mynetworks, and set "inet_protocols = ipv6"

2011-01-31

All linux managed by SSH via IPv6 only

Configure "ListenAddress ::" in sshd_config .

2011-01-30

All linux servers use only IPv6 resolvers

Only statically configured IPv6 addresses in /etc/resolv.conf

2010-10-26

VPN supports IPv6

A new VPN setup: Cisco AnyConnect. Clients get an IPv4 and an IPv6 address from the office pools, so they can access all services via IPv6

NAT64

TAYGA?, Ecdysis?

DNS64

Ecdysis?

Cisco 3750 does not support IPv6 access lists on VLANs

Needs replacing in 2011 anyway. New box might support NAT64?

Sharp AR-M276

This copier/printer does not support IPv6 at all.
Could not retrieve e-mail addresses for 'scan to email' after LDAP server went IPv6 only. Hack Work-around: manually put addresses in.
Our big Sharp MX2600n has full IPv6 support, so we should get rid of this clunker on the first occasion.

HP Laserjet 4250

Jetdirect J7949E does not support IPv6. Replace this with the JetDirect 635n.

Google Mini does not support IPv6

Needs replacing in 2011 anyway, but don't forget to check!!

Axis Q1755 web cam

Can be configured to do IPv6, but only PING works

Sharp MX-2600N printer

Does seem to do IPv6, but printing is not (yet) possible

Windows 2003 + MS SQL 2005 + Exact Globe 2003 != ??

Check if this works...

WinSCP

Upgrade to 4.2.8 or later to get IPv6 going

EMS PostgresQL manager

Tunneling via SSH does not work. Native Postgres connections work, so the bug must be in sshfwd.dll.

TurtoiseSVN

I had some repositories checked out with TurtoiseSVN, using my SSH keys from Putty/Pageant. Any actions on the repository started to have a really long delay after switching off IPv4 on the subversion server. Fixed after using the right repository URL format, in my case using the Putty session name instead of the host name. This session has everything set properly already. In my case the hostname is svn.terena.org, and the PuTTY session name is svn.

Remote Desktop client (mstsc.exe)

A An RDP (Remote Desktop) connection to a Windows 7 computer using a hostname that only has a AAAA record takes 11 seconds. mstsc.exe does an A query first, gets back a No such name, then wait 11 seconds, then asks for and receives the AAAA record, and then immediately connects.