Table of Contents
With DHT support, the hip daemon pushes the hostname, RSA public HIT and public IP address to the DHT. The resolver can then look up this information automatically without DNS or manual /etc/(hip)/hosts configuration.
Once you start hipd, it will send its hostname, HIT and IP address to DHT. You can query this information with "hipconf dht get <hostname|HIT>".
To test, just run normally conntest-server and conntest-client-hip between hosts. You would see messages from hipd and conntest showing DNS->HIT->IP lookups. Everything should work without additional actions.
HIP daemon creates a file called /etc/hip/dhtservers when you execute it. You can add there DHT servers. The file has almost the same format as hosts files, with the addition of port definition with the servername (IP_address servername<:port>).
There is multiple DHT related hipconf commands that you can use to affect the behaviour of the DHT code of HIPL.
hipconf opendht on|off
hipconf dht gw <IPv4|hostname> <port (DHT default = 5851)> <TTL>
hipconf dht get <fqdn/hit>
hipconf dht set <name>
First one of these commands toggles the on/off status of the code. Second one forces the DHT code to change current serving gateway eith a new one. This command allows to change port and TTL definitions of DHT code on the fly. Third command is a simple get of value under a key. Fourth command lets you set a userdefined name to be sent to the DHT. By default result of "uname -n" is sent to the DHT.
For documentation, please also check http://kom.aau.dk/group/05gr680/