The following configuration example was tested on a 6WINDgate 6231 running version 6.3.0b12 of SixOS.

Configuring a 6WIND router to become an ISATAP router is really rather easy and consists mainly of only two commands, one specifying the IPv4 address of the tunnelling interface the other defining the prefix to use for the global IPv6 addresses in the ISATAP subnet. This configuration enables the router to give itself a valid global (ISATAP style) IPv6 address as well as to send out router advertisements to possible clients.

For the following example we assume that one has logged on to the router as user “admin” or as a user with similar permissions.

1. The first step in the configuration is of course to switch to the configuration context for the configuration file one wants to edit which in the case of this example is the running configuration. Within the configuration context one has to enter the migration context:

sixwind{} edit running
sixwind{running} mig

2. Now follows the actual ISATAP configuration. First one has to configure an “ISATAP router”, that
is a separate routing process for the outgoing IPv4 interface one uses for the tunnelling. It is possible
to define several of these processes each with a different number and possibly different IPv4
addresses.

The theoretic command for this configuration is:

sixwind{running-mig} isatap_router 'number' 'address_v4' ['address_v4']

As ‘number’ one specifies the number of the ISATAP process, ‘address_v4’ is the IPv4 address of the interface the automatic tunnels end on. The optional ‘address_v4’ feature is given as either “up” or “down” and defines configured process is switched on or off. If no state is given the default is “down”.

Later on the state of an ISATAP routing process can also be changed by the command

sixwind{running-mig} isatap_router 'number' 'state'

In our example however we immediately specified the state as “up”:

sixwind{running-mig} isatap_router 1 128.176.191.74 up

3. Next a prefix has to be defined which is announced into the ISATAP subnet. This prefix should have length 64 and it should be taken care that there is not yet a route defined for this prefix, e.g. by having configured another interface of the router with an address within this prefix.

The theoretic command for this configuration step is:

sixwind{running-mig} isatap_prefix 'number' 'address_v6/len'

specifies the ISATAP routing process this prefix corresponds to and thus should be the same as in the
command above. In our example the prefix was configured as follows:

sixwind{running-mig} isatap_prefix 1 2001:db8:10:110::/64

4. At last after exiting from the migration context the new configuration has to be applied to the running configuration and one can also add it to the startup configuration to not loose it during a reboot:

sixwind{running-mig} exit
sixwind{running} addrunning
sixwind{running} exit
sixwind{} copy running start