With OpenDHT support, the hip daemon pushes the hostname, RSA public HIT and public IP address to the OpenDHT. 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 OpenDHT. You can query this information with "hipconf dht get <hostname|HIT>".
To test, just run normally conntest-server and conntest-client-gai between hosts. You would see messages from hipd and conntest showing DNS->HIT->IP lookups. Everything should work without additional actions.
By default OpenDHT support uses opendht.nyuld.net to resolve proximate gateway address. Some times this returns unstable servers address. After a few connection or status errors from DHT, will the gateway be resolved again (hopefully getting a stable one). Gateway addresses can be defined by hand to a file /etc/hip/dhtservers. This file follows the same syntax as /etc/hosts and can contain multiple gateway address-name pairs. If this file exists hipd chooses gateways from the file by random. currently running servers list is at http://www.opendht.org/servers.txt. The wget-dht-servers.sh script can create you the list automatically (in tools directory).
There is multiple OpenDHT related hipconf commands that you can use to affect the behaviour of the OpenDHT code of HIPL.
hipconf opendht on|off
hipconf dht gw <IPv4|hostname> <port (OpenDHT 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 OpenDHT code to change current serving gateway eith a new one. This command allows to change port and TTL definitions of OpenDHT 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 OpenDHT. By default result of "uname -n" is sent to the OpenDHT.
For documentation, please also check http://kom.aau.dk/group/05gr680/