IPv6 Address : Bagian Host - Revision history

Onnowpurbo: /* Set secara Manual */

2019-02-24T01:45:38Z

Set secara Manual

← Older revision		Revision as of 01:45, 24 February 2019
Line 37:		Line 37:

	Untuk manual suffix seperti “::1” tampak di contoh di atas, dibutuhkan most significant bit ke 7 di set ke 0 (universal/local bit dari automatically generated identifier). Juga bit kombinasi yang lain yang di reserve untuk anycast address.		Untuk manual suffix seperti “::1” tampak di contoh di atas, dibutuhkan most significant bit ke 7 di set ke 0 (universal/local bit dari automatically generated identifier). Juga bit kombinasi yang lain yang di reserve untuk anycast address.


			==Youtube==

			* https://www.youtube.com/watch?v=n5TPR03KpsU - IPv6 bagian host

	==Referensi==		==Referensi==

Onnowpurbo: /* Referensi */

2018-09-18T00:38:47Z

Referensi

← Older revision		Revision as of 00:38, 18 September 2018
Line 41:		Line 41:

	* http://tldp.org/HOWTO/Linux+IPv6-HOWTO/x659.html		* http://tldp.org/HOWTO/Linux+IPv6-HOWTO/x659.html


			==Pranala Menarik==

			* [[IPv6]]

Onnowpurbo: /* Tipe Address (Bagian host) */

2013-06-20T02:22:39Z

Tipe Address (Bagian host)

← Older revision		Revision as of 02:22, 20 June 2013
Line 4:		Line 4:

	Untuk auto-configuration dan mobility, di putuskan untuk menggunakan 64 bit bagian bawah sebagai bagian host dari address di kebanyakan tipe address. Oleh karenanyta setiap subnet dapat menampung banyak sekali address.		Untuk auto-configuration dan mobility, di putuskan untuk menggunakan 64 bit bagian bawah sebagai bagian host dari address di kebanyakan tipe address. Oleh karenanyta setiap subnet dapat menampung banyak sekali address.



	For auto-configuration and mobility issues, it was decided to use the lower 64 bits as the host part of the address in most of the current address types. Therefore each single subnet can hold a large amount of addresses.

	Bagian host ini dapat dilihat berlainan:		Bagian host ini dapat dilihat berlainan:

Onnowpurbo: /* Masalah privacy dengan automatic computed address dan solusinya */

2013-06-14T01:59:27Z

Masalah privacy dengan automatic computed address dan solusinya

← Older revision		Revision as of 01:59, 14 June 2013
Line 29:		Line 29:
	==Masalah privacy dengan automatic computed address dan solusinya==		==Masalah privacy dengan automatic computed address dan solusinya==

	~~Because the~~ "~~automatically~~ computed" ~~host part is globally unique~~ (~~except when a~~ vendor ~~of a~~ NIC ~~uses the same~~ MAC address ~~on more than one~~ NIC), client ~~tracking is possible on the~~ host ~~when not using a~~ proxy ~~of any kind~~.		Karena bagian host dengan "automatic computed" secara global harusnya unik (kecuali jika vendor NIC menggunakan MAC address yang sama untuk beberapa NIC), maka tracking client menjadi mungkin untuk host yang tidak menggunakan proxy.

	~~This is a known problem~~, ~~and a solution was defined~~: privacy extension, ~~defined in~~ RFC 3041 / Privacy Extensions for Stateless Address Autoconfiguration in IPv6 (there is also already a newer draft available: draft-ietf-ipv6-privacy-addrs-v2-*). ~~Using a~~ random ~~and a static value a new~~ suffix ~~is generated from time to time~~. ~~Note~~: ~~this is only reasonable for outgoing~~ client ~~connections and isn't really useful for well-known servers.~~		Masalah ini sudah diketahui, dan solusinya sudah di definisikan berupa : privacy extension, yang didefinisikan di RFC 3041 / Privacy Extensions for Stateless Address Autoconfiguration in IPv6 (atau veri yang lebih baru). Menggunakan nilai random dan statik sebuah suffix di buat dari waktu ke waktu. Catatan: ini hanya mungkin untuk client yang melakukan sambungan ke luar dan ini tidak terlalu bermanfaat untuk server.
	~~3.3.2~~. ~~Manually set~~

	~~For servers, it's probably easier to remember simpler addresses, this can also be accommodated. It is possible to assign an additional IPv6 address to an interface, e.g.~~

	~~2001:0db8:100:f101::1~~		==Set secara Manual==

	For manual suffixes like “::1” shown in the above example, it's required that the 7th most significant bit is set to 0 (the universal/local bit of the automatically generated identifier). Also some other (otherwise unchosen ) bit combinations are reserved for anycast addresses, too.

			Untuk server, mungkin yang paling mudah untuk mengingat address yang lebih sederhana. Ini juga dapat di akomodasi. Sangat mungkin untuk menset alamat IPv6 tambahan ke sebuah interface, misalnya,

			2001:0db8:100:f101::1

			Untuk manual suffix seperti “::1” tampak di contoh di atas, dibutuhkan most significant bit ke 7 di set ke 0 (universal/local bit dari automatically generated identifier). Juga bit kombinasi yang lain yang di reserve untuk anycast address.

	==Referensi==		==Referensi==

	* http://tldp.org/HOWTO/Linux+IPv6-HOWTO/x659.html		* http://tldp.org/HOWTO/Linux+IPv6-HOWTO/x659.html

Onnowpurbo at 01:51, 14 June 2013

2013-06-14T01:51:56Z

← Older revision		Revision as of 01:51, 14 June 2013
Line 1:		Line 1:
	Sumber: http://tldp.org/HOWTO/Linux+IPv6-HOWTO/x659.html		Sumber: http://tldp.org/HOWTO/Linux+IPv6-HOWTO/x659.html

			=Tipe Address (Bagian host)=

			Untuk auto-configuration dan mobility, di putuskan untuk menggunakan 64 bit bagian bawah sebagai bagian host dari address di kebanyakan tipe address. Oleh karenanyta setiap subnet dapat menampung banyak sekali address.


	~~3.3. Address types (host part)~~

	For auto-configuration and mobility issues, it was decided to use the lower 64 bits as the host part of the address in most of the current address types. Therefore each single subnet can hold a large amount of addresses.		For auto-configuration and mobility issues, it was decided to use the lower 64 bits as the host part of the address in most of the current address types. Therefore each single subnet can hold a large amount of addresses.

	~~This~~ host ~~part can be inspected differently~~:		Bagian host ini dapat dilihat berlainan:
	~~3.3.1. Automatically~~ computed (~~also known as~~ stateless)
			==Automatic computed (juga dikenal sebagai stateless)==

	~~With~~ auto-configuration, ~~the~~ host ~~part of the~~ address ~~is computed by converting the~~ MAC address ~~of an~~ interface (~~if available~~), ~~with the~~ EUI-64 ~~method~~, ~~to a unique~~ IPv6 address. ~~If no~~ MAC address ~~is available for this~~ device ~~(happens e.g. on virtual devices)~~, ~~something else (like the~~ IPv4 ~~address or the~~ MAC address ~~of a physical~~ interface~~) is used instead~~.		Dengan auto-configuration, bagian host dari address dihitung dengan mengkonversikan MAC address dari interface (jika ada), dengan metoda EUI-64, ke IPv6 address yang unik. Jika tidak ada MAC address yang biasanya terjadi pada virtual device, maka yang lain seperti address IPv4 atau MAC address dari interface fisik yang akan digunakan.

	~~E.g. a~~ NIC ~~has following~~ MAC address (48 bit):		Contoh, NIC dengan MAC address (48 bit):

	00:10:a4:01:23:45		00:10:a4:01:23:45

	~~This would be expanded according to theIEEE-Tutorial~~ EUI-64 ~~design for~~ EUI-48 ~~identifiers to the~~ 64 bit interface identifier:		Berdasarkan tutorial IEEE EUI-64 disain untuk EUI-48 identifier ke 64 bit interface identifier sebagai:

	0210:a4ff:fe01:2345		0210:a4ff:fe01:2345

	~~With a given~~ prefix, ~~the result is the~~ IPv6 address ~~shown in example above~~:		Untuk prefix tertentu, maka hasil dari IPv6 address akan tampak sebagai berikut:

	2001:0db8:0100:f101:0210:a4ff:fe01:2345		2001:0db8:0100:f101:0210:a4ff:fe01:2345

	~~3.3.1.1. Privacy problem with automatically~~ computed ~~addresses and a solution~~		==Masalah privacy dengan automatic computed address dan solusinya==

	Because the "automatically computed" host part is globally unique (except when a vendor of a NIC uses the same MAC address on more than one NIC), client tracking is possible on the host when not using a proxy of any kind.		Because the "automatically computed" host part is globally unique (except when a vendor of a NIC uses the same MAC address on more than one NIC), client tracking is possible on the host when not using a proxy of any kind.
Line 32:		Line 36:
	For servers, it's probably easier to remember simpler addresses, this can also be accommodated. It is possible to assign an additional IPv6 address to an interface, e.g.		For servers, it's probably easier to remember simpler addresses, this can also be accommodated. It is possible to assign an additional IPv6 address to an interface, e.g.

	2001:0db8:100:f101::1		2001:0db8:100:f101::1

	For manual suffixes like “::1” shown in the above example, it's required that the 7th most significant bit is set to 0 (the universal/local bit of the automatically generated identifier). Also some other (otherwise unchosen ) bit combinations are reserved for anycast addresses, too.		For manual suffixes like “::1” shown in the above example, it's required that the 7th most significant bit is set to 0 (the universal/local bit of the automatically generated identifier). Also some other (otherwise unchosen ) bit combinations are reserved for anycast addresses, too.

Onnowpurbo: New page: Sumber: http://tldp.org/HOWTO/Linux+IPv6-HOWTO/x659.html 3.3. Address types (host part) For auto-configuration and mobility issues, it was decided to use the lower 64 bits as the host p...

2013-04-28T08:21:26Z

New page: Sumber: http://tldp.org/HOWTO/Linux+IPv6-HOWTO/x659.html 3.3. Address types (host part) For auto-configuration and mobility issues, it was decided to use the lower 64 bits as the host p...

New page

Sumber: http://tldp.org/HOWTO/Linux+IPv6-HOWTO/x659.html

3.3. Address types (host part)

For auto-configuration and mobility issues, it was decided to use the lower 64 bits as the host part of the address in most of the current address types. Therefore each single subnet can hold a large amount of addresses.

This host part can be inspected differently:
3.3.1. Automatically computed (also known as stateless)

With auto-configuration, the host part of the address is computed by converting the MAC address of an interface (if available), with the EUI-64 method, to a unique IPv6 address. If no MAC address is available for this device (happens e.g. on virtual devices), something else (like the IPv4 address or the MAC address of a physical interface) is used instead.

E.g. a NIC has following MAC address (48 bit):

00:10:a4:01:23:45

This would be expanded according to theIEEE-Tutorial EUI-64 design for EUI-48 identifiers to the 64 bit interface identifier:

0210:a4ff:fe01:2345

With a given prefix, the result is the IPv6 address shown in example above:

2001:0db8:0100:f101:0210:a4ff:fe01:2345

3.3.1.1. Privacy problem with automatically computed addresses and a solution

Because the "automatically computed" host part is globally unique (except when a vendor of a NIC uses the same MAC address on more than one NIC), client tracking is possible on the host when not using a proxy of any kind.

This is a known problem, and a solution was defined: privacy extension, defined in RFC 3041 / Privacy Extensions for Stateless Address Autoconfiguration in IPv6 (there is also already a newer draft available: draft-ietf-ipv6-privacy-addrs-v2-*). Using a random and a static value a new suffix is generated from time to time. Note: this is only reasonable for outgoing client connections and isn't really useful for well-known servers.
3.3.2. Manually set

For servers, it's probably easier to remember simpler addresses, this can also be accommodated. It is possible to assign an additional IPv6 address to an interface, e.g.

2001:0db8:100:f101::1

For manual suffixes like “::1” shown in the above example, it's required that the 7th most significant bit is set to 0 (the universal/local bit of the automatically generated identifier). Also some other (otherwise unchosen ) bit combinations are reserved for anycast addresses, too.

==Referensi==

* http://tldp.org/HOWTO/Linux+IPv6-HOWTO/x659.html