IPv6-ready kernel - Revision history

Onnowpurbo: /* Currently known “not supported IPv6 capable links” */

2013-06-22T02:53:13Z

Currently known “not supported IPv6 capable links”

← Older revision		Revision as of 02:53, 22 June 2013
Line 71:		Line 71:
	* ISDN dengan enkapsulasi rawip, nama device: isdnX		* ISDN dengan enkapsulasi rawip, nama device: isdnX

	==~~Currently known “not supported~~ IPv6 ~~capable links”~~==		==Link yang tidak mendukung IPv6==

	ISDN ~~with encapsulation~~ syncppp, device ~~names~~: ipppX (~~design issue of the~~ ipppd, ~~will be merged into more general~~ PPP ~~layer in~~ kernel ~~series~~ 2.5.x)		ISDN dengan enkapsulasi syncppp, nama device: ipppX (masalah disain dari ipppd, akan digabungkan dengan lapisan PPP di kernel seri 2.5.x)

Onnowpurbo: /* Currently known never “IPv6 capable links” */

2013-06-22T02:51:43Z

Currently known never “IPv6 capable links”

← Older revision		Revision as of 02:51, 22 June 2013
Line 65:		Line 65:
	Masalah utama yang ada karena struktur lapisan jaringan dari implementasi kernel yang ada. IPv6 paket tidak di kenali dengan nomor IP header (6 bukan 4). Tapi di kenali oleh nomor protokol di protokol lapisan ke 2. Oleh karenanya, protokol transport yang tidak mengggunakan nomor protokol tersebut tidak akan bisa melepaskan paket IPv6. Catatan: paket akan tetap dikirim melalui link, akan tetapi di bagian penerima, proses pengiriman / pelepasan paket tidak akan bekerja. Kita dapat melihat hal ini menggunakan tcpdump.		Masalah utama yang ada karena struktur lapisan jaringan dari implementasi kernel yang ada. IPv6 paket tidak di kenali dengan nomor IP header (6 bukan 4). Tapi di kenali oleh nomor protokol di protokol lapisan ke 2. Oleh karenanya, protokol transport yang tidak mengggunakan nomor protokol tersebut tidak akan bisa melepaskan paket IPv6. Catatan: paket akan tetap dikirim melalui link, akan tetapi di bagian penerima, proses pengiriman / pelepasan paket tidak akan bekerja. Kita dapat melihat hal ini menggunakan tcpdump.

	==~~Currently known never “IPv6 capable links”~~==		==Link yang tidak akan pernah mampu IPv6==

	* Serial Line IP (SLIP, RFC 1055 / SLIP), ~~should be better called now to~~ SLIPv4, device ~~named~~: slX		* Serial Line IP (SLIP, RFC 1055 / SLIP), sebaiknya di sebut SLIPv4, nama device: slX
	* Parallel Line IP (PLIP), ~~same like~~ SLIP, device ~~names~~: plipX		* Parallel Line IP (PLIP), sama dengan SLIP, nama device: plipX
	* ISDN ~~with encapsulation~~ rawip, device ~~names~~: isdnX		* ISDN dengan enkapsulasi rawip, nama device: isdnX

	==Currently known “not supported IPv6 capable links”==		==Currently known “not supported IPv6 capable links”==

	ISDN with encapsulation syncppp, device names: ipppX (design issue of the ipppd, will be merged into more general PPP layer in kernel series 2.5.x)		ISDN with encapsulation syncppp, device names: ipppX (design issue of the ipppd, will be merged into more general PPP layer in kernel series 2.5.x)

Onnowpurbo: /* Network Device yang Siap IPv6 */

2013-06-22T02:47:55Z

Network Device yang Siap IPv6

← Older revision		Revision as of 02:47, 22 June 2013
Line 63:		Line 63:
	Tidak semua network device yang ada mendukung (akan mendukung) kemampuan untuk membawa paket IPv6.		Tidak semua network device yang ada mendukung (akan mendukung) kemampuan untuk membawa paket IPv6.

	Masalah utama yang ada karena struktur lapisan jaringan dari implementasi kernel yang ada. IPv6 paket tidak di kenali dengan nomor IP header (6 bukan 4). Tapi di kenali oleh nomor protokol di protokol lapisan ke 2. Oleh karenanya,		Masalah utama yang ada karena struktur lapisan jaringan dari implementasi kernel yang ada. IPv6 paket tidak di kenali dengan nomor IP header (6 bukan 4). Tapi di kenali oleh nomor protokol di protokol lapisan ke 2. Oleh karenanya, protokol transport yang tidak mengggunakan nomor protokol tersebut tidak akan bisa melepaskan paket IPv6. Catatan: paket akan tetap dikirim melalui link, akan tetapi di bagian penerima, proses pengiriman / pelepasan paket tidak akan bekerja. Kita dapat melihat hal ini menggunakan tcpdump.

	A major issue is that because of the network layer structure of kernel implementation an IPv6 packet isn't really recognized by it's IP header number (6 instead of 4). It's recognized by the protocol number of the Layer 2 transport ~~protocol. Therefore any transport protocol which doesn't use such protocol number cannot dispatch~~ IPv6 ~~packets~~. ~~Note~~: ~~the packet is still transported over the~~ link, ~~but on receivers side~~, ~~the dispatching won't work (you can see this e.g~~. ~~using~~ tcpdump).

	==Currently known never “IPv6 capable links”==		==Currently known never “IPv6 capable links”==

Onnowpurbo: /* Network Device yang Siap IPv6 */

2013-06-22T02:42:56Z

Network Device yang Siap IPv6

← Older revision		Revision as of 02:42, 22 June 2013
Line 63:		Line 63:
	Tidak semua network device yang ada mendukung (akan mendukung) kemampuan untuk membawa paket IPv6.		Tidak semua network device yang ada mendukung (akan mendukung) kemampuan untuk membawa paket IPv6.

	Masalah utama yang ada karena struktur lapisan jaringan dari implementasi kernel yang ada.		Masalah utama yang ada karena struktur lapisan jaringan dari implementasi kernel yang ada. IPv6 paket tidak di kenali dengan nomor IP header (6 bukan 4). Tapi di kenali oleh nomor protokol di protokol lapisan ke 2. Oleh karenanya,

	A major issue is that because of the network layer structure of kernel implementation an IPv6 packet isn't really recognized by it's IP header number (6 instead of 4). It's recognized by the protocol number of the Layer 2 transport protocol. Therefore any transport protocol which doesn't use such protocol number cannot dispatch IPv6 packets. Note: the packet is still transported over the link, but on receivers side, the dispatching won't work (you can see this e.g. using tcpdump).		A major issue is that because of the network layer structure of kernel implementation an IPv6 packet isn't really recognized by it's IP header number (6 instead of 4). It's recognized by the protocol number of the Layer 2 transport protocol. Therefore any transport protocol which doesn't use such protocol number cannot dispatch IPv6 packets. Note: the packet is still transported over the link, but on receivers side, the dispatching won't work (you can see this e.g. using tcpdump).

Onnowpurbo: /* Network Device yang Siap IPv6 */

2013-06-22T01:42:47Z

Network Device yang Siap IPv6

← Older revision		Revision as of 01:42, 22 June 2013
Line 61:		Line 61:
	==Network Device yang Siap IPv6==		==Network Device yang Siap IPv6==

	~~Not all existing~~ network ~~devices have already~~ (~~or ever~~) ~~the capability to transport~~ IPv6 ~~packets~~. ~~A current status can be found at IPv6+Linux-status-~~kernel~~.html#transport~~.		Tidak semua network device yang ada mendukung (akan mendukung) kemampuan untuk membawa paket IPv6.

			Masalah utama yang ada karena struktur lapisan jaringan dari implementasi kernel yang ada.

	A major issue is that because of the network layer structure of kernel implementation an IPv6 packet isn't really recognized by it's IP header number (6 instead of 4). It's recognized by the protocol number of the Layer 2 transport protocol. Therefore any transport protocol which doesn't use such protocol number cannot dispatch IPv6 packets. Note: the packet is still transported over the link, but on receivers side, the dispatching won't work (you can see this e.g. using tcpdump).		A major issue is that because of the network layer structure of kernel implementation an IPv6 packet isn't really recognized by it's IP header number (6 instead of 4). It's recognized by the protocol number of the Layer 2 transport protocol. Therefore any transport protocol which doesn't use such protocol number cannot dispatch IPv6 packets. Note: the packet is still transported over the link, but on receivers side, the dispatching won't work (you can see this e.g. using tcpdump).

	~~4.1.4.1.~~ Currently known never “IPv6 capable links”		==Currently known never “IPv6 capable links”==

	* Serial Line IP (SLIP, RFC 1055 / SLIP), should be better called now to SLIPv4, device named: slX		* Serial Line IP (SLIP, RFC 1055 / SLIP), should be better called now to SLIPv4, device named: slX
Line 71:		Line 73:
	* ISDN with encapsulation rawip, device names: isdnX		* ISDN with encapsulation rawip, device names: isdnX

	~~4.1.4.2.~~ Currently known “not supported IPv6 capable links”		==Currently known “not supported IPv6 capable links”==

	ISDN with encapsulation syncppp, device names: ipppX (design issue of the ipppd, will be merged into more general PPP layer in kernel series 2.5.x)		ISDN with encapsulation syncppp, device names: ipppX (design issue of the ipppd, will be merged into more general PPP layer in kernel series 2.5.x)

Onnowpurbo at 01:35, 22 June 2013

2013-06-22T01:35:23Z

← Older revision		Revision as of 01:35, 22 June 2013
Line 47:		Line 47:
	==Compile kernel dengan kemampuan IPv6==		==Compile kernel dengan kemampuan IPv6==

	Jika langkah di atas memperlihatkan hasil yang negatif, dan kernel yang kita gunakan tidak mendukung IPv6, maka kita mempunyai pilihan berikut:		Pada saat ini sebagian besar kernel yang digunakan sudah mendukung IPv6.
			Jika langkah di atas memperlihatkan hasil yang negatif,
			dan kernel yang kita gunakan tidak mendukung IPv6, maka kita mempunyai pilihan berikut:

	* Update distribusi yang kita gunakan ke distribusi yang mendukung IPv6 (sangat di sarankan untuk pemula).		* Update distribusi yang kita gunakan ke distribusi yang mendukung IPv6 (sangat di sarankan untuk pemula).
Line 54:		Line 56:
	* Compile kernel dengan USAGI extension		* Compile kernel dengan USAGI extension

	Jika kita memutuskan untuk compile kernel, kita ada baiknya		Jika kita memutuskan untuk compile kernel, kita ada baiknya mempunyai pengalaman compile kernel sebelumnya.


	~~If you decide to compile a kernel, you should have previous experience in kernel compiling and read the Linux Kernel HOWTO.~~		==Network Device yang Siap IPv6==

	~~A comparison between vanilla and USAGI extended kernels is available on~~ IPv6~~+Linux-Status-Kernel.~~
	~~4.1.3.1. Compiling a vanilla kernel~~

	~~More detailed hints about compiling an IPv6-enabled kernel can be found e.g. on IPv6-HOWTO-2#kernel.~~

	Note: you should use whenever possible kernel series 2.6.x or above, because the IPv6 support in series 2.4.x only will no longer get backported features from 2.6.x and IPv6 support in series 2.2.x is hopeless outdated.
	~~4.1.3.2. Compiling a kernel with USAGI extensions~~

	Same as for vanilla kernel, only recommend for advanced users, which are already familiar with IPv6 and kernel compilation. See also USAGI project / FAQ and Obtaining the best IPv6 support with Linux (Article) (Mirror).
	~~4.1.4. IPv6-ready network devices~~

	Not all existing network devices have already (or ever) the capability to transport IPv6 packets. A current status can be found at IPv6+Linux-status-kernel.html#transport.		Not all existing network devices have already (or ever) the capability to transport IPv6 packets. A current status can be found at IPv6+Linux-status-kernel.html#transport.
Line 76:		Line 67:
	4.1.4.1. Currently known never “IPv6 capable links”		4.1.4.1. Currently known never “IPv6 capable links”

	Serial Line IP (SLIP, RFC 1055 / SLIP), should be better called now to SLIPv4, device named: slX		* Serial Line IP (SLIP, RFC 1055 / SLIP), should be better called now to SLIPv4, device named: slX
			* Parallel Line IP (PLIP), same like SLIP, device names: plipX
	Parallel Line IP (PLIP), same like SLIP, device names: plipX		* ISDN with encapsulation rawip, device names: isdnX

	ISDN with encapsulation rawip, device names: isdnX

	4.1.4.2. Currently known “not supported IPv6 capable links”		4.1.4.2. Currently known “not supported IPv6 capable links”

	ISDN with encapsulation syncppp, device names: ipppX (design issue of the ipppd, will be merged into more general PPP layer in kernel series 2.5.x)		ISDN with encapsulation syncppp, device names: ipppX (design issue of the ipppd, will be merged into more general PPP layer in kernel series 2.5.x)

Onnowpurbo at 01:28, 22 June 2013

2013-06-22T01:28:51Z

← Older revision		Revision as of 01:28, 22 June 2013
Line 47:		Line 47:
	==Compile kernel dengan kemampuan IPv6==		==Compile kernel dengan kemampuan IPv6==

	~~If both above shown results were negative and your~~ kernel ~~has no IP6 support~~, ~~than you have the following options~~:		Jika langkah di atas memperlihatkan hasil yang negatif, dan kernel yang kita gunakan tidak mendukung IPv6, maka kita mempunyai pilihan berikut:

	Update ~~your distribution to a current one which supports~~ IPv6 ~~out-of-the-box~~ (~~recommended for newbies~~)		* Update distribusi yang kita gunakan ke distribusi yang mendukung IPv6 (sangat di sarankan untuk pemula).
			* Compile kernel yang baru (mudah, jika kita mengetahui optipn yang harus di aktifkan).
			* Recompile kernel source bawaan distro anda (kadang tidak begitu mudah)
			* Compile kernel dengan USAGI extension

	~~Compile a new vanilla~~ kernel ~~(easy~~, ~~if you know which options you needed)~~		Jika kita memutuskan untuk compile kernel, kita ada baiknya

	~~Recompile kernel sources given by your Linux distribution (sometimes not so easy)~~

	~~Compile a kernel with USAGI extensions~~

	If you decide to compile a kernel, you should have previous experience in kernel compiling and read the Linux Kernel HOWTO.		If you decide to compile a kernel, you should have previous experience in kernel compiling and read the Linux Kernel HOWTO.

Onnowpurbo at 01:23, 22 June 2013

2013-06-22T01:23:13Z

← Older revision		Revision as of 01:23, 22 June 2013
Line 32:		Line 32:
	==Load Module Secara Automatis==		==Load Module Secara Automatis==

			Alternatif lain adalah meload modul IPv6 secara automatis / on demand.
			Kita hanya perlu menambahkan kalimat berikut di file konfigurasi untuk kernel modul loader
			(biasanya /etc/modules.conf atau /etc/conf.modules atau /etc/modules) :

	~~4.1.2.1. Automatically loading of~~ module		alias net-pf-10 ipv6 # untuk load IPv6 module on demand secara automatis

	~~Its possible to automatically~~ load ~~the~~ IPv6 module ~~on demand. You only have to add following line in the configuration file of the kernel module loader (normally /etc/modules.conf or /etc/conf.modules)~~:		Juga kita bisa men-disable load IPv6 module secara automatis menggunakan kalinat berikut:

	alias net-pf-10 ~~ipv6~~ # ~~automatically~~ load IPv6 module on demand		alias net-pf-10 off # disable load IPv6 module on demand secara automatis

	~~It's also possible to disable automatically loading of the IPv6~~ module ~~using following line~~		Catatan: di kernel 2.6.x, mekanisme load module di ubah. File konfigurasi di namakan
			/etc/modprobe.conf atau /etc/modprobe.d/*conf tidak lagi /etc/modules.conf.

	~~alias net-pf-10 off # disable automatically load of IPv6 module on demand~~		==Compile kernel dengan kemampuan IPv6==

	~~Additional note: in kernels series 2.6.x, the module loader mechanism was changed. The new configuration file has to be named /etc/modprobe.conf instead of /etc/modules.conf.~~
	~~4.1.3.~~ Compile kernel ~~with~~ IPv6 ~~capabilities~~

	If both above shown results were negative and your kernel has no IP6 support, than you have the following options:		If both above shown results were negative and your kernel has no IP6 support, than you have the following options:
Line 72:		Line 73:

	A major issue is that because of the network layer structure of kernel implementation an IPv6 packet isn't really recognized by it's IP header number (6 instead of 4). It's recognized by the protocol number of the Layer 2 transport protocol. Therefore any transport protocol which doesn't use such protocol number cannot dispatch IPv6 packets. Note: the packet is still transported over the link, but on receivers side, the dispatching won't work (you can see this e.g. using tcpdump).		A major issue is that because of the network layer structure of kernel implementation an IPv6 packet isn't really recognized by it's IP header number (6 instead of 4). It's recognized by the protocol number of the Layer 2 transport protocol. Therefore any transport protocol which doesn't use such protocol number cannot dispatch IPv6 packets. Note: the packet is still transported over the link, but on receivers side, the dispatching won't work (you can see this e.g. using tcpdump).

	4.1.4.1. Currently known never “IPv6 capable links”		4.1.4.1. Currently known never “IPv6 capable links”

Onnowpurbo: /* Meload Module IPv6 */

2013-06-21T02:06:08Z

Meload Module IPv6

← Older revision		Revision as of 02:06, 21 June 2013
Line 21:		Line 21:
	# modprobe ipv6		# modprobe ipv6

	~~If this is successful~~, ~~this~~ module ~~should be listed, testable with following auto-magically line:~~		Jika load tersebut berhasil, maka module IPv6 harusnya terdaftar dan dapat di test
			menggunakan script berikut secara automatis

	# lsmod \|grep -w 'ipv6' && echo "IPv6 module successfully loaded"		# lsmod \|grep -w 'ipv6' && echo "IPv6 module successfully loaded"

	~~And the check shown above should now run successfully~~.		Harusnya jalan dengan baik

			Catatan: unload module IPv6 saat ini masih belum jalan dengan baik. Mungkin akan terjadi crash kernel.

			==Load Module Secara Automatis==


	~~Note: unloading the module is currently not supported and can result, under some circumstances, in a kernel crash.~~
	4.1.2.1. Automatically loading of module		4.1.2.1. Automatically loading of module

Onnowpurbo: /* Cek dukungan IPv6 di kernel yang berjalan */

2013-06-21T01:56:31Z

Cek dukungan IPv6 di kernel yang berjalan

← Older revision		Revision as of 01:56, 21 June 2013
Line 5:		Line 5:
	==Cek dukungan IPv6 di kernel yang berjalan==		==Cek dukungan IPv6 di kernel yang berjalan==

	Untuk mencek apakah kernel yang berjalan mendukung IPv6, ~~folder~~ berikut harus ada		Untuk mencek apakah kernel yang berjalan mendukung IPv6, file berikut harus ada

	/proc/net/if_inet6		/proc/net/if_inet6