...
| Entire host IPv6 only (removed IPv4 address and A record) | | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="14ff55fc851a94fb-e02c7341-4f2a4607-999fa60b-954ac326731ddc7377df9e2f"><ac:plain-text-body><![CDATA[ | | Nagios runs only on IPv6 | Configure | ]]></ac:plain-text-body></ac:structured-macro> |
| Entire host IPv6 only (removed IPv4 address and A record) | | ||
| All linux servers run Postfix on IPv6 only (except listed MXs) | Remove IPv4 addresses from | ||
| All linux managed by SSH via IPv6 only | Configure " | ||
| All linux servers use only IPv6 resolvers | Only statically configured IPv6 addresses in | ||
| 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
:
...
status | description |
| |||
---|---|---|---|---|---|
| NAT64 | ||||
| DNS64 | ||||
| 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. | |||
| 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... |
Some tests indicate the Ecdysis works well.
Also, they presented at our own conference last year
Take into consideration!
...
| 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 |
| 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 |
| Remote Desktop client ( | A An RDP (Remote Desktop) connection to a Windows 7 computer using a hostname that only has a AAAA record takes 11 seconds. |
...
| Autoconfiguring name servers does not work for Mac OS X | Macs need manually configured name servers, boo! |
| 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.") |
| CyberDuck does not work with IPv6 hostnames | Use either literal IPv6 address, or IPv6-only host name |
Misc
To Do
| ||||
| Axis Q1755 web cam | Can be configured to do IPv6, but only PING works | ||
| VMware ESXi, Vcenter, VCB. These SHOULD work on IPv6. Curious if it really works | |||
| HP and Sharp printers, but we need IPv6 ACLs first | |||
they really work on IPv6 only | ||||
| | Cisco AnyConnect | Client get IPv4 + IPv6 address from the office, so remote user can access all IPv6 services |