IPv4 and IPv6 interoperability

One of the main advantages is that the conjunction of LSIs and HITs allows the communication between IPv4 and IPv6 applications. We will show an example using the configuration described in the IPv4 section of this chapter.

oops:

crash:

We can check also the opposite case.

oops:

crash:

Tips: Displaying log information and traffic. 

For both, LSIs and HITs we can obtain more information about how they work showing more information messages with the daemons or capturing the network packets.

The log messages displayed by the hip daemon can be changed dynamically:

tools/hipconf debug none # <only HIP_DIE messages are shown>

tools/hipconf debug medium # <shows HIP_DIE, HIP_ERROR and HIP_INFO messages>

tools/hipconf debug all # <shows all messages, including HIP_DEBUG>

These options can be also set in "/etc/hip/hipd_config" to configure hipd and other libraries at startup.

See the log messages for information about the result of HIP base exchange and USAGI IPSec negotiation. Tcpdump or ethereal are good tools for dumping the network traffic during the base exchange. For tcpdump, you can use "tcpdump -n -i any esp or proto 139 or port 50500" to catch HIP-only traffic. It should be taken into account that LSIs are local identifiers, so they are not in the wire.

There is also a program called "hipsetup" in "hipl/test" directory for quick testing of the base exchange. Run it without arguments to see how it is used.

It should be noticed that starting a new hipd process automatically kills the previous one.