You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 61 Next »

Our office has a /24 IPv4 and a /48 IPv6 network.
Test to see if it would be possible to run parts of the TERENA Secretariat office network on IPv6 only.
This page keeps track of progress, bugs, and issues with this transition.
I will start with all systems and services that are used only internally.

Milestones

(tick) 2011-02-28

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

ldap.terena.org

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4a5d6c8f-99d5-4bf7-9587-21ed3836747a"><ac:plain-text-body><![CDATA[

(tick) 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>

(tick) 2011-02-07

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

svn.terena.org

(tick) 2011-02-01

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

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

(tick) 2011-01-31

All linux managed by SSH via IPv6 only

Configure "ListenAddress ::" in sshd_config

(tick) 2011-01-30

All linux servers use only IPv6 resolvers

Only IPv6 addresses in /etc/resolv.conf

(tick) 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

To avoid name resolution problems, it was necessary to copy to the legacy 127.0.1.1 entries to ::1:

127.0.0.1       localhost
127.0.1.1       ldap.terena.org ldap

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback ldap.terena.org ldap

Misc issues

status

description

 

(question)

NAT64

TAYGA?, Ecdysis?

(question)

DNS64

Ecdysis?

(error)

Cisco 3750 does not support IPv6 access lists on VLANs

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

(error)

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.

(error)

HP Laserjet 4250

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

(error)

Google Mini does not support IPv6

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

(error)

Axis Q1755 web cam

Can be configured to do IPv6, but only PING works (sad)

(question)

Sharp MX-2600N printer

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

Some tests indicate the Ecdysis works well.
Also, they presented at our own conference last year (wink)
Take into consideration!

Linux issues

(error)

PECL radius

IPv6 doesn't work. Needed for TERENA web site. Considering rewriting code to use LDAP.

(tick)

apt-get

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

(tick)

Pear Net_Socket

Does not like IPv6 addresses, wrote patch.

(tick)

ntp

ntp.ubuntu.com does not work. Use our own NTP server graham.terena.org, or one of the many SURFnet chimes.

(tick)

ntp

dumps core without IPv4 loopback address. Keep legacy 127.0.0.1 address

(tick)

Confluence and JIRA LDAP auth via IPv6 = b0rked

Workaround: use IPv6 only hostname: ldap.ipv6.terena.org

(tick)

Radiator

Cannot use IPv6 LDAP server. Filed support ticket at Open.com.au. Fixed as of 2011-02-12. Also make sure to add flags to any custom perl hooks:
my $ldap = Net::LDAP->new('ldap://ldap.terena.org',inet6=>1);

(tick)

Listmanager

Custom email list manager, running on Erasmus. 2 lists were doing queries to ldap.terena.org. Unfortunately the Net::LDAP in Ubuntu Hardy (libnet-ldap-perl) is too old and does not recognise the inet6 paramater. Hacked Fixed by copying /usr/share/perl5/Net/LDAP.pm from a Lucid box.

Windows issues

(tick)

WinSCP

Upgrade to 4.2.8 or later to get IPv6 going

(error)

EMS PostgresQL manager

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

(tick)

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.

(info)

Remote Desktop client (mstsc.exe)

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.

Mac OS X issues

(error)

Autoconfiguring name servers does not work for Mac OS X

Macs need manually configured name servers, boo!

(error)

CIFS client on Mac OS X does not support IPv6

Unable to file bug report due to lame web site ("An error has occurred. Please report the error to Apple Inc. by emailing the error detail to devbugs@apple.com.")

(tick)

CyberDuck does not work with IPv6 hostnames

Use either literal IPv6 address, or IPv6-only host name godzilla.ipv6.terena.org.
Fixed in 4.0

To Do

(question)

VMware ESXi, Vcenter, VCB. These SHOULD work on IPv6. Curious if they really work on IPv6 only

(question)

Google
  • No labels