This section describes how you manually configure IP in IP tunnels. For information on configuring an automatic 6to4 tunnel, refer to How to Configure a 6to4 Router.
IPv6 supports the following types of tunnel encapsulation:
IPv4 over IPv4 tunnels
IPv6 over IPv4 tunnels (native IPv6 and 6to4)
IPv6 over IPv6 tunnels
IPv4 over IPv6 tunnels
IPv6 to IPv6 over 6to4 tunnels
6to4 site tunnel to 6to4 relay router to native IPv6 site
For conceptual descriptions of tunnels, see Solaris Tunneling Interfaces for IPv6 and Tunneling Mechanism.
Task |
Description |
Instructions |
---|---|---|
Manually configuring IPv6 over IPv4 tunnels |
Shows the entries required for the hostname6.ip.tunn file. | |
Automatically configuring IPv6 over IPv4 tunnels (6to4 tunnels) |
Shows entries required for the hostname6.ip.6to4tun file. | |
Configuring IPv6 over IPv6 tunnels |
Shows the entries required for the hostname6.ip.6.tunn file. | |
Configuring IPv4 over IPv6 tunnels |
Shows the entries required for the hostname.ip6.tunn file. | |
Configuring IPv4 over IPv4 tunnels |
Shows the entries required for the hostname.ip.tunn file. | |
Configuring a tunnel between a 6to4 router and a 6to4 relay router |
Describes how to enable a tunnel to a 6to4 relay router by using the 6to4relay command. | |
Configuring your router to advertise over tunneling interfaces |
Shows the entries required for the /etc/inet/ndpd.conf file. |
How to Configure Your Router to Advertise Over Tunneling Interfaces |
The best way to pass IPv6 packets over an IPv4 network is to use an automatic 6to4 tunnel. For instructions for implementing 6to4 routing at your site, refer to How to Configure a 6to4 Router.
Become superuser.
Create the file /etc/hostname6.ip.tunn. Use the values 0, 1, 2, and so on, for n. Then, add entries by following these steps.
Add the tunnel source addresses. Then, add the tunnel destination addresses.
tsrc IPv4-source-addr tdst IPv4-destination-addr up |
(Optional) Add a logical interface for the source and destination IPv6 addresses.
addif IPv6-source-address IPv6-destination-address up |
Omit this step if you want the address autoconfigured for this interface. You do not need to configure link-local addresses for your tunnel. Link-local addresses are configured automatically.
When you finish configuring the tunnels, you must reboot.
You must perform the same steps at the other end of the tunnel for bidirectional communication to occur.
If your system is to be configured as a router, you must also configure your router to advertise over tunneling interfaces before rebooting. See How to Configure Your Router to Advertise Over Tunneling Interfaces.
This example shows a tunnel for which all IPv6 addresses are autoconfigured.
tsrc 129.146.86.138 tdst 192.168.7.19 up |
This example shows a tunnel for which global source and global destination addresses are manually configured. The site-local source and site-local destination addresses are also manually configured.
tsrc 120.46.86.138 tdst 190.68.7.19 up addif fec0::1234:a00:fe12:528 fec0::5678:a00:20ff:fe12:1234 up addif 2::1234:a00:fe12:528 2::5678:a00:20ff:fe12:1234 up |
Become Superuser.
Create the file /etc/hostname6.ip6.tunn. Use the values 0, 1, 2, and so on, for n. Then, add entries by following these steps.
Add the tunnel source address. Then, add the tunnel destination address.
tsrc IPv6-source-address tdst IPv6-destination-address IPv6-packet-source-address IPv6-packet-destination-address up |
(Optional) Add a logical interface for the source and destination IPv6 addresses.
addif IPv6-source-address IPv6-destination-address up |
Omit this step if you want the address autoconfigured for this interface. You do not need to configure link-local addresses for your tunnel. Link-local addresses are configured automatically.
When you finish configuring the tunnels, you must reboot.
You must perform the same steps at the other end of the tunnel for bidirectional communication to occur.
If your system is to be configured as a router, you must also configure your router to advertise over tunneling interfaces before rebooting. See How to Configure Your Router to Advertise Over Tunneling Interfaces.
This example shows the entry for an IPv6 over IPv6 tunnel.
tsrc 2000::114:a00:20ff:fe72:668c tdst 2000::103:a00:20ff:fe9b:a1c3 fe80::4 fe80::61 up |
Become Superuser.
Create the file /etc/hostname.ip6.tunn. Use the values 0, 1, 2, and so on, for n. Then, add entries by following these steps.
Add the tunnel source address. Then, add the tunnel destination address.
tsrc IPv6-source-address tdst IPv6-destination-address tunnel-IPv4-source-address tunnel-IPv4-destination-address up |
(Optional) Add a logical interface for the source and destination IPv6 addresses.
addif IPv6-source-address IPv6-destination-address up |
When you finish configuring the tunnels, you must reboot.
You must perform the same steps at the other end of the tunnel for bidirectional communication to occur.
If your system is to be configured as a router, you must also configure your router to advertise over tunneling interfaces before rebooting. See How to Configure Your Router to Advertise Over Tunneling Interfaces.
This example shows the entry for an IPv4 over IPv6 tunnel.
tsrc 2000::114:a00:20ff:fe72:668c tdst 2000::103:a00:20ff:fe9b:a1c3 10.0.0.4 10.0.0.61 up |
Become Superuser.
Create the file /etc/hostname.ip.tunn. Use the values 0, 1, 2, and so on, for n. Then, add entries by following these steps.
Add the tunnel source address. Then, add the tunnel destination address.
tsrc IPv4-source-address tdst IPv4-destination-address tunnel-IPv4-source-address tunnel-IPv4-destination-address up |
(Optional) Add a logical interface for the source and destination IPv4 addresses.
addif IPv4-source-address IPv4-destination-address up |
When you finish configuring the tunnels, you must reboot.
You must perform the same steps at the other end of the tunnel for bidirectional communication to occur.
If your system is to be configured as a router, you must also configure your router to advertise over tunneling interfaces before rebooting. See How to Configure Your Router to Advertise Over Tunneling Interfaces.
This example shows the entry for an IPv4 over IPv4 tunnel.
tsrc 120.46.86.158 tdst 120.46.86.122 10.0.0.4 10.0.0.61 up |
Following these steps for each tunnel.
Become superuser.
Edit the /etc/inet/ndpd.conf file. Add entries by using the following steps.
Reboot.
Because of major security issues, by default 6to4 relay router support is disabled in the Solaris operating system. See Considerations for Tunnels to a 6to4 Relay Router and Internet Draft, Security Considerations for 6to4.
Before you enable a tunnel to a 6to4 relay router, you must have completed the following tasks:
Configured a 6to4 router at your site, as explained in How to Configure a 6to4 Router.
Reviewed the security issues that are involved in tunneling to a 6to4 relay router.
Become superuser on the 6to4 router.
Enable a tunnel to the 6to4 relay router by using either of the following formats:
Enable a tunnel to an anycast 6to4 relay router.
# /usr/sbin/6to4relay -e |
The -e option sets up a tunnel between the 6to4 router and an anycast 6to4 relay router. Anycast 6to4 relay routers have the well-known IPv4 address 192.88.99.1. The anycast relay router that is physically nearest to your site becomes the endpoint for the 6to4 tunnel. This relay router then handles packet forwarding between your 6to4 site and a native IPv6 site.
For detailed information about anycast 6to4 relay routers, refer to RFC 3068, "An Anycast Prefix for 6to4 Relay Routers"
Enable a tunnel to a specific 6to4 relay router.
# /usr/sbin/6to4relay -e -a relay-router-address |
The -a option indicates that a specific router address is to follow. Replace relay-router-address with the IPv4 address of the specific 6to4 relay router with which you want to enable a tunnel.
The tunnel to the 6to4 relay router remains active until you remove the 6to4 tunnel pseudo-interface.
Delete the tunnel to the 6to4 relay router, when no longer needed, by typing the following:
# /usr/sbin/6to4relay -d |
(Optional) Make the tunnel to the 6to4 relay router persistent across reboots.
Your site might have a compelling reason to have the tunnel to the 6to4 relay router reinstated each time the 6to4 router reboots. To support this scenario, you must do the following.
Edit the/etc/default/inetinit file.
The line that you need to modify is at the end of the file.
Change the “NO” value in the line ACCEPT6TO4RELAY=NO to “YES.”
(Optional) Create a tunnel to a specific 6to4 relay router that persists across reboots.
For the parameter RELAY6TO4ADDR, change the address 192.88.99.1 to the IPv4 address of the 6to4 relay router that you want to use.
You can use /usr/bin/6to4relay to find out whether support for 6to4 relay routers is enabled. The next example shows the output when support for 6to4 relay routers is disabled, as is the default in the Solaris operating system:
# /usr/sbin/6to4relay 6to4relay: 6to4 Relay Router communication support is disabled. |
When support for 6to4 relay routers is enabled, you receive the following output:
# /usr/sbin/6to4relay 6to4relay: 6to4 Relay Router communication support is enabled. IPv4 destination address of Relay Router=192.88.99.1 |