Configuration of the DSTM client

Output from command “ifconfig”:

It is necessary to specify the name or the address of the DSTM server and sometimes the port.

Tests results and Issues

When installation and configuration is accomplished, it is possible for every DSTM client to communicate with IPv4 hosts using IPv4 enabled applications.

The performance testing of DSTM was done over a Very High Speed Network (1Gbps) and comparison was made between normal IPv4 communication and DSTM IPv4 communication over the network. When DSTM performance was measured after measuring IPv4 performance, then it was found that RTT (Round Trip Time) decreased just about 2 percent and throughput decreased just around 7 percent if the payload size was kept below 1212 bytes (limit after which fragmentation starts with DSTM configurations). If the payload size was bigger, throughput decreased a bit more due to the increase of load with the DSTM mechanism.

There are also some other issues:

• Some times in older kernel versions the make script in the dstmd/bsd folder works only after a slight and minor modification.
• One has to rebuild the full kernel after making the RPCv6 patch and if one uses the patch, then it is also very sensitive to system version.
• RPCv6 mechanism cannot cross firewall and cannot be used for VPN scenario.
• With KAME, the correct number of gif (interfaces) must be put in the system configuration file (no dynamic gif).
• All IPv4 communication must be initiated by the DSTM client, because the DSTM client is the one that requests the tunnel to be set up (Although there exists an implementation that was not tested yet making it possible for remote IPv4-only hosts to initiate a communication with a DSTM client in an IPv6-only network).