IPv6-ready client program (contoh) - Revision history

Onnowpurbo: /* URL testing */

2013-06-26T02:29:45Z

URL testing

Onnowpurbo: /* Browser yang siap IPv6 */

2013-06-26T02:16:21Z

Browser yang siap IPv6

Onnowpurbo: /* Browser yang siap IPv6 */

2013-06-26T02:15:05Z

Browser yang siap IPv6

Onnowpurbo at 02:04, 26 June 2013

2013-06-26T02:04:11Z

Onnowpurbo at 02:02, 26 June 2013

2013-06-26T02:02:30Z

Onnowpurbo at 01:50, 26 June 2013

2013-06-26T01:50:26Z

Onnowpurbo at 01:09, 26 June 2013

2013-06-26T01:09:38Z

Onnowpurbo: New page: 4.5. IPv6-ready client programs (selection) To run the following shown tests, it's required that your system is IPv6 enabled, and some examples show addresses which only can be reached if...

2013-05-22T02:39:58Z

New page: 4.5. IPv6-ready client programs (selection) To run the following shown tests, it's required that your system is IPv6 enabled, and some examples show addresses which only can be reached if...

New page

4.5. IPv6-ready client programs (selection)

To run the following shown tests, it's required that your system is IPv6 enabled, and some examples show addresses which only can be reached if a connection to the 6bone is available.
4.5.1. Checking DNS for resolving IPv6 addresses

Because of security updates in the last years every Domain Name System (DNS) server should run newer software which already understands the (intermediate) IPv6 address-type AAAA (the newer one named A6 isn't still common at the moment because only supported using BIND9 and newer and also the non-existent support of root domain IP6.ARPA). A simple test whether the used system can resolve IPv6 addresses is

# host -t AAAA www.join.uni-muenster.de

and should show something like following:

www.join.uni-muenster.de. is an alias for tolot.join.uni-muenster.de.
tolot.join.uni-muenster.de. has AAAA address
¬ 2001:638:500:101:2e0:81ff:fe24:37c6

4.5.2. IPv6-ready telnet clients

IPv6-ready telnet clients are available. A simple test can be done with

$ telnet 3ffe:400:100::1 80
Trying 3ffe:400:100::1...
Connected to 3ffe:400:100::1.
Escape character is '^]'.
HEAD / HTTP/1.0

HTTP/1.1 200 OK
Date: Sun, 16 Dec 2001 16:07:21
GMT Server: Apache/2.0.28 (Unix)
Last-Modified: Wed, 01 Aug 2001 21:34:42 GMT
ETag: "3f02-a4d-b1b3e080"
Accept-Ranges: bytes
Content-Length: 2637
Connection: close
Content-Type: text/html; charset=ISO-8859-1

Connection closed by foreign host.

If the telnet client don't understand the IPv6 address and says something like “cannot resolve hostname”, then it's not IPv6-enabled.
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.

@@ Line 82: / Line 82: @@
 ===URL testing===
-.5.4.1. URLs for testing
+Ada beberapa URL yang baik untuk testing IPv6, seperti:
-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.
+* http://www.kame.net - animasi kura-kura harus bergerak kalau di akses menggunakan IPv6

@@ Line 75: / Line 75: @@
 * Proxy setting automatic (*.pac) tidak dapat di exten untuk menangani request IPv6 secara terpisah (misalnya jangan menggunakan proxy untuk IPv6) karena pola mereka (biasanya ditulis menggunakan java dan hard coded ke dalam source seperti dalam Maxilla source code).
-* Pada versi yang lama tidak akan mengerti URL dengan IPv6 seperti http://[2001:a60:9002:1::186:6]/ (this given URL only works with an IPv6-enabled browser!).
+* Pada versi yang lama tidak akan mengerti URL dengan IPv6 seperti http://[2404:6800:4003:803::1014]/ (URL tersebut hanya akan bisa di akses menggunakan browser yang siap IPv6).
 Cara test paling sederhana adalah cobe nge-web dengan URL di atas tanpa proxy.

@@ Line 67: / Line 67: @@
 ==Browser yang siap IPv6==
-A current status of IPv6 enabled web browsers is available at IPv6+Linux-status-apps.html#HTTP.
+Kebanyakan masih mempunyai masalah,
-Most of them have unresolved problems at the moment
+* Jika menggunakan proxy yang hanya untuk IPv4, maka request IPv6 yang dikirim ke proxy akan tidak di mengerti. Solusinya: update proxy software.
-    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).
+* Proxy setting automatic (*.pac) tidak dapat di exten untuk menangani request IPv6 secara terpisah (misalnya jangan menggunakan proxy untuk IPv6) karena pola mereka (biasanya ditulis menggunakan java dan hard coded ke dalam source seperti dalam Maxilla source code).
-    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).
+* Pada versi yang lama tidak akan mengerti URL dengan IPv6 seperti http://[2001:a60:9002:1::186:6]/ (this given URL only works with an IPv6-enabled browser!).
-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!).
+Cara test paling sederhana adalah cobe nge-web dengan URL di atas tanpa proxy.

@@ Line 46: / Line 46: @@
 Jika telnet client tidak mengerti IPv6 maka akan keluar error seperti “cannot resolve hostname”, maka kemungkinan besar telnet client tersebut tidak mengenal IPv6.
-Current versions of openssh are IPv6-ready. Depending on configuring before compiling it has two behavior.
+==Client SSH siap dengan OPv6==
-    --without-ipv4-default: the client tries an IPv6 connect first automatically and fall back to IPv4 if not working
+===openssh===
 .5.3.2. ssh.com

@@ Line 1: / Line 1: @@
-.5. IPv6-ready client programs (selection)
+Untuk menjalankan test ini, kita membutuhkan sistem yang siap dengan IPv6.
-To run the following shown tests, it's required that your system is IPv6 enabled, and some examples show addresses which only can be reached if a connection to the 6bone is available.
+==Cek DNS untuk me-resolve address IPv6==
-Because of security updates in the last years every Domain Name System (DNS) server should run newer software which already understands the (intermediate) IPv6 address-type AAAA (the newer one named A6 isn't still common at the moment because only supported using BIND9 and newer and also the non-existent support of root domain IP6.ARPA). A simple test whether the used system can resolve IPv6 addresses is
+Karena security update beberapa tahun belakangan ini, seharusnya semua DNS server menjalankan software terbaru yang harusnya mengerti tentang address IPv6 tipe AAAA.
   # host -t AAAA ipv6.google.com
@@ Line 15: / Line 15: @@
-.5.2. IPv6-ready telnet clients
+Telnet client harusnya siap IPv6, test sederhana dapat digunakan menggunakan perintah misalnya,
   $ telnet ipv6.google.com 80
@@ Line 26: / Line 24: @@
   Connected to ipv6.l.google.com.
   Escape character is '^]'.
   HEAD / HTTP/1.0
   HTTP/1.0 302 Found
@@ Line 33: / Line 35: @@
   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: 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
+ 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."
+  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
@@ Line 42: / Line 44: @@
   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.
 .5.3. IPv6-ready ssh clients
@@ Line 75: / Line 76: @@
 A short test is to try shown URL with a given browser and using no proxy.
 .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.

@@ Line 58: / Line 58: @@
   $ ssh -6 ::1
   user@::1's password: ******
@@ Line 66: / Line 65: @@
 A current status of IPv6 enabled web browsers is available at IPv6+Linux-status-apps.html#HTTP.
@@ Line 84: / Line 80: @@
 A short test is to try shown URL with a given browser and using no proxy.
 .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.

@@ Line 6: / Line 6: @@
 Because of security updates in the last years every Domain Name System (DNS) server should run newer software which already understands the (intermediate) IPv6 address-type AAAA (the newer one named A6 isn't still common at the moment because only supported using BIND9 and newer and also the non-existent support of root domain IP6.ARPA). A simple test whether the used system can resolve IPv6 addresses is
-and should show something like following:
+ # host -t AAAA ipv6.google.com
 .5.2. IPv6-ready telnet clients
@@ Line 18: / Line 20: @@
 IPv6-ready telnet clients are available. A simple test can be done with
-HTTP/1.1 200 OK
+ $ telnet ipv6.google.com 80
-Date: Sun, 16 Dec 2001 16:07:21
-GMT Server: Apache/2.0.28 (Unix)
+ Trying 2404:6800:4003:803::1013...
-Last-Modified: Wed, 01 Aug 2001 21:34:42 GMT
+ Connected to ipv6.l.google.com.
-ETag: "3f02-a4d-b1b3e080"
+ Escape character is '^]'.
-Accept-Ranges: bytes
-Content-Length: 2637
+ HEAD / HTTP/1.0
-Connection: close
-Content-Type: text/html; charset=ISO-8859-1
+ HTTP/1.0 302 Found
 If the telnet client don't understand the IPv6 address and says something like “cannot resolve hostname”, then it's not IPv6-enabled.
 .5.3. IPv6-ready ssh clients
 .5.3.1. openssh