While essentially being nothing more than a PC running some version of FreeBSD, 6WIND routers come with their own command line interface (CLI). Note that 6WIND no longer sell their hardware but we still give configuration examples here since existing 6WIND routers can obviously be used in IPv6 deployments. For the purpose of this example we assume one has just logged on to the rooter as user "admin".

1. First one has to go into the configuration mode for the running configuration:

sixwind{} edit running

2. Change to the "migration context":

sixwind{running} mig

3. Setup the IPv6-in-IPv4 tunnel:

sixwind{running-mig} 6in4 <tun-#> <local v4> <remote v4> <local v6> \
                                                                                                                      <remote v6>

As an actual example:

sixwind{running-mig} 6in4 0 128.1.2.3 68.2.3.4 2001:pTLA:y::xxx:2 \
                                                                                                    2001:pTLA:y::xxx:1

With this configuration the 6WIND router will create two /128 routes for both of the IPv6 addresses of the tunnel endpoints.

4. Leave the "migration context":

sixwind{running-mig} exit

We assume that the tunnel is going to be the only IPv6 connection for the 6WIND router (e.g., if it is the IPv6 access router for the site). Therefore the IPv6 default route needs to be set to this tunnel.

5. Change to the "routing context" :

sixwind{running} rtg

6. Configure the IPv6 default route:

sixwind{running-rtg} ipv6_defaultroute <local v6 IP>

In our example:

sixwind{running-rtg} ipv6_defaultroute 2001:pTLA:y::xxx:1

7. Leave the "routing context":

sixwind{running-rtg} exit

8. Apply the configured changes to the running configuration:

sixwind{running} addrunning

9. Exit the configuration mode:

sixwind{running} exit

Note: If you have performed step 8 immediately before typing in "exit" here everything should be fine. Should you have configured other changes after step 8 before exiting the configuration context the router will ask you if you want to apply these changes to the running configuration as well. Type "y" if you want the changes to be added to the running configuration, otherwise answer "n", in which case all changes after the last "addrunning" command will be lost.

10. Save changes to the startup configuration so the tunnel will still be configured after the next
reboot:

sixwind{} copy conf running start