RELEASE_NOTES Enea LINX for Linux ------------------- Version: 2.2.2 -------------- This is a patch release of Enea LINX for Linux open source package, containing the LINX kernel module, LINX Ethernet Connection Manager (CM) module, LINX TCP CM module, the LINX library, tools for supervising and for configuring inter-node communication and the LINX Gateway server. Main Changes to Linx for Linux 2.1 ---------------------------------- The Ethernet CM has been internally re-designed. External APIs, protocols etc. are not changed (it is possible to setup a connection between an old and a new Ethernet CM). The algorithm to detect a "dead-peer" has been simplified. This results in longer detection times, which in the end affects, for example, returning attach signals. The disconnect procedure has been changed, see rlnh_link.h for further information. If you have developed your own CM, you must update it according to the new rlnh_link.h. The Linx Gateway server is added as part of the Linx for Linux package allowing applications using the Gateway protocol to communicate with a LINX cluster. Supported Linux Kernel Versions ------------------------------- LINX version 2.2.2 supports vanilla kernels from 2.6.9 to 2.6.27. Vendor specific kernels may require modifications in the LINX source code. LINX Development Environment Requirements ----------------------------------------- LINX does not use any unusual features and should be easy to build in any modern self hosted or cross build environment. LINX Known Bugs and Limitations ------------------------------- Once a connection has been setup on an Ethernet interface, the interface's MTU, address and name must not be changed (e.g. ifconfig eth1 mtu 1000). If the LINX Ethernet CM detects such a change, it prints an error message to the kernel ring buffer. Note that from now on, the behaviour of the affected connections are unpredictable, e.g. signals may be truncated, etc. The only way to ensure correct behaviour is to re-create the affected connections. From one Ethernet interface, it is not possible to create multiple connections to the same destination address. Same applies to TCP/IP CM (IP address instead of MAC address etc.). Some kernel versions and distributions require that LINX is built with LINX_KERNEL_WORKAROUND_1 flag set to yes, see README. The build option SOCK_STAT=yes is broken and should not be used. The make system lacks proper dependencies. If the LINXDISC daemon is killed with SIGKILL, it cannot be restarted due to lack of cleanup. However, if the user removes the lockfile and established LINX-connections, the daemon may be started again.