It is recommended that you get the latest source and compile it yourself. As an alternative, you may download frozen, binary releases of the kernel from http://hipl.hiit.fi/hipl/release/. However, before reporting any bugs, please have a go with the latest source instead of the binaries because the bug may already have been resolved upstream. There is also a Knoppix based live cd available from the HIPL download pages.
As the first requirement, you also need know the basics on Linux kernel compilation and usage. Refer to linux/README for further instructions.
You need the following software to build and run the HIPL software bundle:
Mandatory:
Linux Operating System
A BEET patched Linux 2.6 kernel with dummy device, XFRM_USER, IPv6, IPsec and AES+3DES+SHA1 support. Also, you should have also CONFIG_IP_ADVANCED_ROUTER and CONFIG_IP_MULTIPLE_TABLES as built-in.
OpenSSL-library and developer headers
libxml2 and development headers for OpenDHT support
GNU make
the latest versions of autoconf, automake, autoreconf and libtool
iproute and its development headers
wxgtk 2.6.2 and libgtk-2.x library and development headers
Optional Software Requirements:
iputils-ping (or netkit-ping): ping, ping6
ipsec-tools: setkey
ip6tables userspace tools and IPv6 netfilter in the kernel (for the HIP firewall only)
iptables development headers (HIP firewall)
glib (www.gtk.org) and development headers (HIP firewall)
netcat6
latex, dvips, dvipdf, fig2dev, doxygen (for building the HIPL source code documentation)
java compiler for "jip" (java hip resolver) if you want to build HIP enabled java programs
Network Requirements
Make sure that the end-host firewall does not block HIP and ESP traffic (try "iptables -L") or otherwise you won't get any traffic through. As a workaround, you try enabling the NAT mode at the end-host.
Make sure that a middlebox is not blocking HIP traffic. If there is firewall between the machines, it might have been configured to block HIP or ESP traffic. If there is a NAT between the machines, it might also be blocking traffic. Either make sure that the middlebox allows HIP and ESP traffic, or you can try enabling the NAT mode at the end-host.