Setting Up Tunneling

Tunneling enables the sharing of emetrics for routes on an Intranet even when there is a non-Trusted Solaris cloud of hosts and gateways between two Trusted Solaris gateways. All hosts must be in the same Intranet with gateways using Trusted Solaris extended RIP. Without tunneling, the security response packets generated by extended RIP on one gateway cannot be received on the remote Trusted Solaris gateway to pass along the emetrics of its known routes.

To set up tunneling, the Security Administrator role creates a tunnel file on a Trusted Solaris gateway. The tunnel file contains the IP addresses of remote networks connected to Trusted Solaris gateways. Unlabeled broadcast packets containing security information are sent directly to the networks listed in the tunnel file, where they are picked by Trusted Solaris gateways. See "To Set Up Tunneling".

The term tunneling as used here has nothing to do with the IP-in-IP tunneling feature in the Solaris environment.