IPv6: Network Devices yang berbeda - Revision history

Onnowpurbo: /* Secara Virtual */

2013-06-30T01:15:06Z

Secara Virtual

← Older revision		Revision as of 01:15, 30 June 2013
Line 39:		Line 39:

	Ether-tap device adalah IPv6-enabled dan dapat di konfigurasi stateless. Untuk menggunakannya, modul “ethertap” harus di load terlebih dulu.		Ether-tap device adalah IPv6-enabled dan dapat di konfigurasi stateless. Untuk menggunakannya, modul “ethertap” harus di load terlebih dulu.

	~~===tun device===~~

	~~Currently not tested by me.~~

	~~===ATM===~~

	~~01/2002: Aren't currently supported by vanilla kernel, supported by USAGI extension~~

	~~===Others===~~

	~~Did I forget an interface?...~~

Onnowpurbo: /* Ether-tap device */

2013-06-30T01:14:40Z

Ether-tap device

← Older revision		Revision as of 01:14, 30 June 2013
Line 38:		Line 38:
	===Ether-tap device===		===Ether-tap device===

	Ether-tap ~~devices are~~ IPv6-enabled ~~and also~~ stateless ~~configured~~. ~~For use~~, ~~the module~~ “ethertap” ~~has to be loaded before~~.		Ether-tap device adalah IPv6-enabled dan dapat di konfigurasi stateless. Untuk menggunakannya, modul “ethertap” harus di load terlebih dulu.

	===tun device===		===tun device===

Onnowpurbo: /* SLIP + PLIP */

2013-06-30T01:13:36Z

SLIP + PLIP

← Older revision		Revision as of 01:13, 30 June 2013
Line 34:		Line 34:
	===SLIP + PLIP===		===SLIP + PLIP===

	~~Like mentioned earlier, this interfaces don't support~~ IPv6 ~~transport~~ (~~sending is~~ OK, ~~but dispatching on receiving don't work~~).		Interface ini tidak mendukung transportasi IPv6 (mengirim OK, tapi menerima tidak jalan).

	===Ether-tap device===		===Ether-tap device===

Onnowpurbo: /* Interface ISDN PPP */

2013-06-30T01:12:51Z

Interface ISDN PPP

← Older revision		Revision as of 01:12, 30 June 2013
Line 30:		Line 30:
	===Interface ISDN PPP===		===Interface ISDN PPP===

	ISDN PPP ~~interfaces~~ (ippp) ~~aren't~~ IPv6 ~~enabled by~~ kernel. ~~Also there are also no plans to do that because in~~ kernel 2.5.+ ~~they will be replaced by a more~~ generic ~~ppp interface layer~~.		Interface ISDN PPP (ippp) tidak di enable IPv6-nya di kernel. Juga tidak ada rencana untuk itu, karena di kernel 2.5+ akan di ubah oleh lapisan interface ppp yang generic.

	===SLIP + PLIP===		===SLIP + PLIP===

Onnowpurbo: /* Interface ISDN HDLC */

2013-06-30T01:06:19Z

Interface ISDN HDLC

← Older revision		Revision as of 01:06, 30 June 2013
Line 26:		Line 26:
	===Interface ISDN HDLC===		===Interface ISDN HDLC===

	IPv6 ~~capability for~~ HDLC ~~with encapsulation~~ ip ~~is already built-in in the~~ kernel		Kemampuan IPv6 untuk HDLC dengan enkapsulasi ip sudah ada dalam kernel.

	===Interface ISDN PPP===		===Interface ISDN PPP===

Onnowpurbo at 00:57, 30 June 2013

2013-06-30T00:57:28Z

← Older revision		Revision as of 00:57, 30 June 2013
Line 22:		Line 22:
	===Interface PPP===		===Interface PPP===

	PPP ~~interfaces get their~~ IPv6 ~~capability from an~~ IPv6 enabled PPP daemon.		Interface PPP memperoleh kemampuan IPv6 dari IPv6 enabled PPP daemon.

	===ISDN HDLC ~~interfaces~~===		===Interface ISDN HDLC===

	IPv6 capability for HDLC with encapsulation ip is already built-in in the kernel		IPv6 capability for HDLC with encapsulation ip is already built-in in the kernel

	===ISDN PPP ~~interfaces~~===		===Interface ISDN PPP===

	ISDN PPP interfaces (ippp) aren't IPv6 enabled by kernel. Also there are also no plans to do that because in kernel 2.5.+ they will be replaced by a more generic ppp interface layer.		ISDN PPP interfaces (ippp) aren't IPv6 enabled by kernel. Also there are also no plans to do that because in kernel 2.5.+ they will be replaced by a more generic ppp interface layer.
Line 40:		Line 40:
	Ether-tap devices are IPv6-enabled and also stateless configured. For use, the module “ethertap” has to be loaded before.		Ether-tap devices are IPv6-enabled and also stateless configured. For use, the module “ethertap” has to be loaded before.

	===tun ~~devices~~===		===tun device===

	Currently not tested by me.		Currently not tested by me.

Onnowpurbo at 00:49, 30 June 2013

2013-06-30T00:49:49Z

← Older revision		Revision as of 00:49, 30 June 2013
Line 14:		Line 14:


	===IPv6-in-IPv4 ~~tunnel interfaces~~===		===Interface tunnel IPv6-in-IPv4===

	~~These interfaces are normally named~~ sitx. ~~The name~~ sit ~~is a shortcut for~~ Simple Internet Transition. ~~This device has the capability to encapsulate~~ IPv6 ~~packets into~~ IPv4 ~~ones and~~ tunnel ~~them to a foreign endpoint~~.		Interface ini biasanya di kenal dengan nama sitx. Nama sit adalah kependekan dari Simple Internet Transition. Device ini mempunyai kemampuan untuk mengenkapsulasi paket IPv6 ke dalam paket IPv4 dan mengirimkan melalui tunnel ke ujung satu-nya.

	sit0 ~~has a special meaning and cannot be used for dedicated tunnels~~.		sit0 mempunyai arti spesial dan tidak dapat digunakan untuk tunnel khusus.

	===PPP ~~interfaces~~===		===Interface PPP===

	PPP interfaces get their IPv6 capability from an IPv6 enabled PPP daemon.		PPP interfaces get their IPv6 capability from an IPv6 enabled PPP daemon.

Onnowpurbo at 00:45, 27 June 2013

2013-06-27T00:45:11Z

← Older revision		Revision as of 00:45, 27 June 2013
Line 1:		Line 1:
	5.1. ~~Different network devices~~		Pada sebuah node, ada beberapa device network. Mereka tergabung dalam beberapa kelas.

	~~On a node~~, ~~there exist different network devices. They can be collected in classes~~		* Secara fisik, seperti eth0, tr0
			* Secara virtual, seperti ppp0, tun0, tap0, sit0, isdn0, ippp0

	* Physically bounded, like eth0, tr0		==Secara Fisik==
	* Virtually existing, like ppp0, tun0, tap0, sit0, isdn0, ippp0

	5.~~1.1. Physically bounded~~		Menempel secara fisik seperti Ethernet atau Token-Ring secara normal tidak memerlukan penanganan khusus.

	~~Physically bounded interfaces like Ethernet or Token-Ring are normal ones and need no special treatment.~~

	~~5.1.2. Virtually bounded~~		==Secara Virtual==

	~~Virtually bounded interfaces always need special support~~		Interface yang menempel secara virtual biasanya membutuhkan dukungan khusus.

	~~5.1.2.1.~~ IPv6-in-IPv4 tunnel interfaces
			===IPv6-in-IPv4 tunnel interfaces===

	These interfaces are normally named sitx. The name sit is a shortcut for Simple Internet Transition. This device has the capability to encapsulate IPv6 packets into IPv4 ones and tunnel them to a foreign endpoint.		These interfaces are normally named sitx. The name sit is a shortcut for Simple Internet Transition. This device has the capability to encapsulate IPv6 packets into IPv4 ones and tunnel them to a foreign endpoint.
Line 20:		Line 20:
	sit0 has a special meaning and cannot be used for dedicated tunnels.		sit0 has a special meaning and cannot be used for dedicated tunnels.

	~~5.1.2.2.~~ PPP interfaces		===PPP interfaces===

	PPP interfaces get their IPv6 capability from an IPv6 enabled PPP daemon.		PPP interfaces get their IPv6 capability from an IPv6 enabled PPP daemon.

	~~5.1.2.3.~~ ISDN HDLC interfaces		===ISDN HDLC interfaces===

	IPv6 capability for HDLC with encapsulation ip is already built-in in the kernel		IPv6 capability for HDLC with encapsulation ip is already built-in in the kernel

	~~5.1.2.4.~~ ISDN PPP interfaces		===ISDN PPP interfaces===

	ISDN PPP interfaces (ippp) aren't IPv6 enabled by kernel. Also there are also no plans to do that because in kernel 2.5.+ they will be replaced by a more generic ppp interface layer.		ISDN PPP interfaces (ippp) aren't IPv6 enabled by kernel. Also there are also no plans to do that because in kernel 2.5.+ they will be replaced by a more generic ppp interface layer.

	~~5.1.2.5.~~ SLIP + PLIP		===SLIP + PLIP===

	Like mentioned earlier, this interfaces don't support IPv6 transport (sending is OK, but dispatching on receiving don't work).		Like mentioned earlier, this interfaces don't support IPv6 transport (sending is OK, but dispatching on receiving don't work).

	~~5.1.2.6.~~ Ether-tap device		===Ether-tap device===

	Ether-tap devices are IPv6-enabled and also stateless configured. For use, the module “ethertap” has to be loaded before.		Ether-tap devices are IPv6-enabled and also stateless configured. For use, the module “ethertap” has to be loaded before.

	~~5.1.2.7.~~ tun devices		===tun devices===

	Currently not tested by me.		Currently not tested by me.

	~~5.1.2.8.~~ ATM		===ATM===

	01/2002: Aren't currently supported by vanilla kernel, supported by USAGI extension		01/2002: Aren't currently supported by vanilla kernel, supported by USAGI extension

	~~5.1.2.9.~~ Others		===Others===

	Did I forget an interface?...		Did I forget an interface?...

Onnowpurbo at 03:06, 26 June 2013

2013-06-26T03:06:50Z

← Older revision		Revision as of 03:06, 26 June 2013
Line 3:		Line 3:
	On a node, there exist different network devices. They can be collected in classes		On a node, there exist different network devices. They can be collected in classes

	Physically bounded, like eth0, tr0		* Physically bounded, like eth0, tr0
			* Virtually existing, like ppp0, tun0, tap0, sit0, isdn0, ippp0
	Virtually existing, like ppp0, tun0, tap0, sit0, isdn0, ippp0

	5.1.1. Physically bounded		5.1.1. Physically bounded

	Physically bounded interfaces like Ethernet or Token-Ring are normal ones and need no special treatment.		Physically bounded interfaces like Ethernet or Token-Ring are normal ones and need no special treatment.

	5.1.2. Virtually bounded		5.1.2. Virtually bounded

	Virtually bounded interfaces always need special support		Virtually bounded interfaces always need special support

	5.1.2.1. IPv6-in-IPv4 tunnel interfaces		5.1.2.1. IPv6-in-IPv4 tunnel interfaces

Line 18:		Line 19:

	sit0 has a special meaning and cannot be used for dedicated tunnels.		sit0 has a special meaning and cannot be used for dedicated tunnels.

	5.1.2.2. PPP interfaces		5.1.2.2. PPP interfaces

	PPP interfaces get their IPv6 capability from an IPv6 enabled PPP daemon.		PPP interfaces get their IPv6 capability from an IPv6 enabled PPP daemon.

	5.1.2.3. ISDN HDLC interfaces		5.1.2.3. ISDN HDLC interfaces

	IPv6 capability for HDLC with encapsulation ip is already built-in in the kernel		IPv6 capability for HDLC with encapsulation ip is already built-in in the kernel

	5.1.2.4. ISDN PPP interfaces		5.1.2.4. ISDN PPP interfaces

	ISDN PPP interfaces (ippp) aren't IPv6 enabled by kernel. Also there are also no plans to do that because in kernel 2.5.+ they will be replaced by a more generic ppp interface layer.		ISDN PPP interfaces (ippp) aren't IPv6 enabled by kernel. Also there are also no plans to do that because in kernel 2.5.+ they will be replaced by a more generic ppp interface layer.

	5.1.2.5. SLIP + PLIP		5.1.2.5. SLIP + PLIP

	Like mentioned earlier, this interfaces don't support IPv6 transport (sending is OK, but dispatching on receiving don't work).		Like mentioned earlier, this interfaces don't support IPv6 transport (sending is OK, but dispatching on receiving don't work).

	5.1.2.6. Ether-tap device		5.1.2.6. Ether-tap device

	Ether-tap devices are IPv6-enabled and also stateless configured. For use, the module “ethertap” has to be loaded before.		Ether-tap devices are IPv6-enabled and also stateless configured. For use, the module “ethertap” has to be loaded before.

	5.1.2.7. tun devices		5.1.2.7. tun devices

	Currently not tested by me.		Currently not tested by me.

	5.1.2.8. ATM		5.1.2.8. ATM

	01/2002: Aren't currently supported by vanilla kernel, supported by USAGI extension		01/2002: Aren't currently supported by vanilla kernel, supported by USAGI extension

	5.1.2.9. Others		5.1.2.9. Others

	Did I forget an interface?...		Did I forget an interface?...

Onnowpurbo: New page: 5.1. Different network devices On a node, there exist different network devices. They can be collected in classes Physically bounded, like eth0, tr0 Virtually existing, like ppp...

2013-05-22T03:47:38Z

New page: 5.1. Different network devices On a node, there exist different network devices. They can be collected in classes Physically bounded, like eth0, tr0 Virtually existing, like ppp...

New page

5.1. Different network devices

On a node, there exist different network devices. They can be collected in classes

Physically bounded, like eth0, tr0

Virtually existing, like ppp0, tun0, tap0, sit0, isdn0, ippp0

5.1.1. Physically bounded

Physically bounded interfaces like Ethernet or Token-Ring are normal ones and need no special treatment.
5.1.2. Virtually bounded

Virtually bounded interfaces always need special support
5.1.2.1. IPv6-in-IPv4 tunnel interfaces

These interfaces are normally named sitx. The name sit is a shortcut for Simple Internet Transition. This device has the capability to encapsulate IPv6 packets into IPv4 ones and tunnel them to a foreign endpoint.

sit0 has a special meaning and cannot be used for dedicated tunnels.
5.1.2.2. PPP interfaces

PPP interfaces get their IPv6 capability from an IPv6 enabled PPP daemon.
5.1.2.3. ISDN HDLC interfaces

IPv6 capability for HDLC with encapsulation ip is already built-in in the kernel
5.1.2.4. ISDN PPP interfaces

ISDN PPP interfaces (ippp) aren't IPv6 enabled by kernel. Also there are also no plans to do that because in kernel 2.5.+ they will be replaced by a more generic ppp interface layer.
5.1.2.5. SLIP + PLIP

Like mentioned earlier, this interfaces don't support IPv6 transport (sending is OK, but dispatching on receiving don't work).
5.1.2.6. Ether-tap device

Ether-tap devices are IPv6-enabled and also stateless configured. For use, the module “ethertap” has to be loaded before.
5.1.2.7. tun devices

Currently not tested by me.
5.1.2.8. ATM

01/2002: Aren't currently supported by vanilla kernel, supported by USAGI extension
5.1.2.9. Others

Did I forget an interface?...