The Rice Monarch Project implementation of IETF Mobile IP directly supports both NetBSD and FreeBSD. The current version of the software is Release 1.1.0 and supports NetBSD 1.1 and FreeBSD 2.2.2. Earlier versions of the code have also run on older releases of NetBSD. The code should be easily portable to other systems based on 4.4BSD (or at least based on the Berkeley Net/3 networking kernel source), including BSDI, OpenBSD, and other versions of NetBSD and FreeBSD.
Our implementation, since Release 1.0.0, fully conforms to the IETF standard Mobile IP protocol for IPv4, as specified in RFC 2002, and includes both "IP-in-IP" and "minimal" encapsulation support (RFC 2003 and RFC 2004).
This release of the Rice Monarch Project's Mobile IPv4 implementation is available by ftp as a gzip'ed tar file:
Complete installation and operation instructions are available in "The Rice Monarch Project IETF Mobile IPv4 Implementation User's Guide", included in the tar file above in Postscript. This guide is also available separately:For information on the e-mail mailing lists we have set up related to our research in the Rice Monarch Project and to our software distributions, see our mailing lists page.
The newest alpha release of the Rice Monarch Mobile IPv4 code (mip-2.0.0-alpha) now supports Route Optimization. This release also contains improved support for multiple interfaces and foreign agents, as well as patches for FreeBSD 2.2.5.
The IETF has yet to standardize Route Optimization for IPv4, and this code represents an intermediate stepping stone between the current version of the drafts, and the direction the drafts are headed. Ideas appearing in the newest drafts are being tested out by this code, and this code will be updated to remain current with developments in the standardization process.Also new in this release is improved support for multiple simultaneous interfaces and foreign agents. The mobile node code, mobiled, has been greatly simplified with the addition of a table of ``registration methods.'' There is one entry in the table to represent each of the possible methods the mobile node can currently use to obtain connectivity. The registration method table greatly simplifies the logic in mobiled/control.c, making it easy to adjust the policy used to pick how a mobile node should obtain connectivity at any point in time from the available choices.
This alpha release code is available below. Users are asked to report
positive and negative experiences with it to the
monarch
@
monarch.cs.rice.edu mailing list.