Difference between revisions of "IPv6: Network Devices yang berbeda"
Onnowpurbo (talk | contribs) |
Onnowpurbo (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | + | Pada sebuah node, ada beberapa device network. Mereka tergabung dalam beberapa kelas. | |
| − | + | * Secara fisik, seperti eth0, tr0 | |
| + | * Secara virtual, seperti ppp0, tun0, tap0, sit0, isdn0, ippp0 | ||
| − | + | ==Secara Fisik== | |
| − | |||
| − | + | Menempel secara fisik seperti Ethernet atau Token-Ring secara normal tidak memerlukan penanganan khusus. | |
| − | |||
| − | + | ==Secara Virtual== | |
| − | + | Interface yang menempel secara virtual biasanya membutuhkan dukungan khusus. | |
| − | + | ||
| + | ===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. | ||
| − | + | ===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. | ||
| − | + | ===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 | ||
| − | + | ===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. | ||
| − | + | ===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). | ||
| − | + | ===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. | ||
| − | + | ===tun devices=== | |
Currently not tested by me. | Currently not tested by me. | ||
| − | + | ===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 | ||
| − | + | ===Others=== | |
Did I forget an interface?... | Did I forget an interface?... | ||
Revision as of 07:45, 27 June 2013
Pada sebuah node, ada beberapa device network. Mereka tergabung dalam beberapa kelas.
- Secara fisik, seperti eth0, tr0
- Secara virtual, seperti ppp0, tun0, tap0, sit0, isdn0, ippp0
Secara Fisik
Menempel secara fisik seperti Ethernet atau Token-Ring secara normal tidak memerlukan penanganan khusus.
Secara Virtual
Interface yang menempel secara virtual biasanya membutuhkan dukungan khusus.
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.
PPP interfaces
PPP interfaces get their IPv6 capability from an IPv6 enabled PPP daemon.
ISDN HDLC interfaces
IPv6 capability for HDLC with encapsulation ip is already built-in in the kernel
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.
SLIP + PLIP
Like mentioned earlier, this interfaces don't support IPv6 transport (sending is OK, but dispatching on receiving don't work).
Ether-tap device
Ether-tap devices are IPv6-enabled and also stateless configured. For use, the module “ethertap” has to be loaded before.
tun devices
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?...