Contained WithinFind More DocumentationFeatured Support Resources | Scarica il manuale in formato PDF (4425 KB)
Configured TunnelsTunneling interfaces have the following format:
ppa is the physical point of attachment. At system startup, the tunneling module (tun) is pushed, by the ifconfig command, on top of IP to create a virtual interface. The push is accomplished by creating the appropriate hostname6.* file. For example, to create a tunnel to encapsulate IPv6 packets over an IPv4 network, IPv6 over IPv4, you would create the following file name:
The content of this file is passed to ifconfig after the interfaces have been plumbed. The content becomes the parameters that are necessary to configure a point-to-point tunnel. Example 10–11 hostname6.ip.tun0 File for an IPv6 Over IPv4 TunnelThe following is an example of entries in the hostname6.ip.tun0 file:
In this example, the IPv4 source and destination addresses are used as tokens to autoconfigure IPv6 link-local addresses. These addresses are the source and destination for the ip.tun0 interface. Two interfaces are configured. The ip.tun0 interface is configured. A logical interface, ip.tun0:1, is also configured. The logical interface has the source and destination IPv6 addresses specified by the addif command. The contents of these configuration files are passed to ifconfig without change when the system is started in multiuser mode. The entries in Example 10–11 are equivalent to the following:
The following shows the output of ifconfig -a for this tunnel.
You can configure more logical interfaces by adding lines to the configuration file by using the following syntax:
Note – When either end of the tunnel is an IPv6 router that advertises one or more prefixes over the tunnel, you do not need addif commands in the tunnel configuration files. Only tsrc and tdst might be required because all other addresses are autoconfigured. In some situations, specific source and destination link-local addresses need to be manually configured for a particular tunnel. Change the first line of the configuration file to include these link-local addresses. The following line is an example:
Notice that the source link-local address has a prefix length of 10. In this example, the ip.tun0 interface resembles the following:
To create a tunnel to encapsulate IPv6 packets over an IPv6 network, IPv6 over IPv6, you create the following file name:
Example 10–12 hostname6.ip6.tun0 File for an IPv6 over IPv6 TunnelThe following is an example of entries in the hostname6.ip6.tun0 file for IPv6 encapsulation over an IPv6 network:
To create a tunnel to encapsulate IPv4 packets over an IPv6 network, IPv4 over IPv6, you would create the following file name:
Example 10–13 hostname.ip6.tun0 File for an IPv4 Over IPv6 TunnelThe following is an example of entries in the hostname.ip6.tun0 file for IPv4 encapsulation over an IPv6 network:
To create a tunnel to encapsulate IPv4 packets over an IPv4 network, IPv4 over IPv4, you would create the following file name:
Example 10–14 hostname.ip.tun0 for an IPv4 Over IPv4 TunnelThe following is an example of entries in the hostname.ip.tun0 file for IPv4 encapsulation over an IPv4 network:
For specific information about tun, see the tun(7M) man page. .For a general description of tunneling concepts during the transition to IPv6, see Overview of IPv6 Tunnels. For a description of procedures for configuring tunnels, see Tasks for Configuring Tunnels for IPv6 Support (Task Map). |
||||||||||||||