Raoul,

Here are some comments on the current IP Tunnel Administration doc 
(version 1.2) at http://www.opensolaris.org/os/project/clearview/docs/. 
  Overall, your additions and modifications are excellent.


Section 4.1.1:

* Under "-h <hoplimit>", I'd mention explicitly that this is the IPv4 
TTL for tunneling over IPv4 or the hop limit for tunneling over IPv6 
(equivalent concepts).

* Under "-e <encaplimit>", I'd give a brief explanation of what this 
does.  It limits the number of tunnels a given packet can recursively 
enter, or in other words, it determines how many levels of nested 
tunneling is allowed for a given packet.


Section 4.1.2:

* The first sentence in this section should mention what you're trying 
to do.  For example, "Tunnel IPv4 over IPv4 by creating an IPv4 
interface on an IPv4 tunnel link".

* Similarly in the next example, "Tunnel IPv6 over IPv6 by creating an 
IPv6 interface on an IPv6 tunnel link".

* I like how you used the reserved RFC 3849 IPv6 documentation prefix in 
your examples. :-)

* It would be good to have an IPv6 over IPv4 example, since this is how 
some sites bridge two IPv6 clouds together when there's an IPv4-only 
portion of network to traverse (and they're not using 6to4).


Section 4.2.1:

* You might want to mention in this section that modifying the name of a 
tunnel link is not done through modify-iptun, but rather through 
rename-link, and refer to the documentation for that dladm subcommand.


Section 5.2:

* Syntax error in step 2, you need -T in front of the tunnel type.

* Step 3c, you're creating an IPv6 interface, so the syntax is, 
"ifconfig <tunnel-name> inet6 plumb up"  (the up is also important, and 
missing)

* There's a missing step between 5 and 6 to enable IPv6 forwarding. 
This is done by issuing the command, "routeadm -e ipv6-forwarding".


-Seb

Reply via email to