IPv6-ready client program (contoh)

Untuk menjalankan test ini, kita membutuhkan sistem yang siap dengan IPv6.

Cek DNS untuk me-resolve address IPv6

Karena security update beberapa tahun belakangan ini, seharusnya semua DNS server menjalankan software terbaru yang harusnya mengerti tentang address IPv6 tipe AAAA.

Test sederhana tampak berikut ini,

# host -t AAAA ipv6.google.com

dan harusnya akan tampak sebagai berikut:

ipv6.google.com is an alias for ipv6.l.google.com.
ipv6.l.google.com has IPv6 address 2404:6800:4003:800::1011

Telnet client yang siap IPv6

Telnet client harusnya siap IPv6, test sederhana dapat digunakan menggunakan perintah misalnya,

$ telnet ipv6.google.com 80

Trying 2404:6800:4003:803::1013...
Connected to ipv6.l.google.com.
Escape character is '^]'.

masukan

HEAD / HTTP/1.0

hasilnya

HTTP/1.0 302 Found
Location: http://www.google.com.sg/
Cache-Control: private
Content-Type: text/html; charset=UTF-8
Set-Cookie: PREF=ID=fd105bce7948e981:FF=0:TM=1372208872:LM=1372208872:S=YTnn9vG9buRittEI; expires=Fri, 26-Jun-2015 01:07:52 GMT; path=/; domain=.google.co m
Set-Cookie: NID=67=MTceEcK4qnyL_NeUStqIpvHTtqvrG2FTxt4qdSN-zCbuYvrxlL37lZQe6TukGty6V9UWTLRpO3prQ8MJxciG5avgvfS6iYYyiWF7SnG39BQZ4WIRrF-uq_3XRHQK-Mwe; expires=Thu, 26-Dec-2013 01:07:52 GMT; path=/; domain=.google.com; HttpOnly
P3P: CP="This is not a P3P policy! See http://www.google.com/support/accounts/bin/answer.py?hl=en answer=151657 for more info."
Date: Wed, 26 Jun 2013 01:07:52 GMT
Server: gws
Content-Length: 222
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN

Jika telnet client tidak mengerti IPv6 maka akan keluar error seperti “cannot resolve hostname”, maka kemungkinan besar telnet client tersebut tidak mengenal IPv6.

4.5.3. IPv6-ready ssh clients 4.5.3.1. openssh

Current versions of openssh are IPv6-ready. Depending on configuring before compiling it has two behavior.

   --without-ipv4-default: the client tries an IPv6 connect first automatically and fall back to IPv4 if not working

   --with-ipv4-default: default connection is IPv4, IPv6 connection must be force like following example shows

$ ssh -6 ::1 user@::1's password: ****** [user@ipv6host user]$

If your ssh client doesn't understand the option “-6” then it's not IPv6-enabled, like most ssh version 1 packages. 4.5.3.2. ssh.com

SSH.com's SSH client and server is also IPv6 aware now and is free for all Linux and FreeBSD machine regardless if used for personal or commercial use. 4.5.4. IPv6-ready web browsers

A current status of IPv6 enabled web browsers is available at IPv6+Linux-status-apps.html#HTTP.

Most of them have unresolved problems at the moment

   If using an IPv4 only proxy in the settings, IPv6 requests will be sent to the proxy, but the proxy will fail to understand the request and the request fails. Solution: update proxy software (see later).

   Automatic proxy settings (*.pac) cannot be extended to handle IPv6 requests differently (e.g. don't use proxy) because of their nature (written in Java-script and well hard coded in source like to be seen in Maxilla source code).

Also older versions don't understand an URL with IPv6 encoded addresses like http://[2001:a60:9002:1::186:6]/ (this given URL only works with an IPv6-enabled browser!).

A short test is to try shown URL with a given browser and using no proxy.

4.5.4.1. URLs for testing

A good starting point for browsing using IPv6 is http://www.kame.net/. If the turtle on this page is animated, the connection is via IPv6, otherwise the turtle is static.