XORP Software Status
See the design documentation for details of the XORP processes.
As of March 2007 (Release 1.4), the status is as follows:
- RIB
- The basic RIB is complete. There are probably still some bugs but the core is reasonably stable. IPv4 and IPv6 are supported, and both unicast and multicast routes can be stored. Route redistribution from one routing protocol to another is supported. There is a mechanism to monitor the status of internal tables. While regular BGP nexthop resolution using IGP data works, recursive nexthop resolution does not work.
- FEA
- The unicast FEA for DragonFlyBSD, FreeBSD, NetBSD, OpenBSD, Linux,
Mac OS X, Windows Server 2003, the dummy FEA for testing purposes,
and the FEA for Click are basically complete. The multicast FEA (MFEA)
for DragonFlyBSD, FreeBSD, NetBSD, OpenBSD and Linux is basically
complete. The MFEA for Click doesn't exist.
- POLICY
- A policy module has been integrated with all routing protocols and
the RIB, allowing route redistribution and route filtering.
- BGP
- The core of BGP is basically complete, with respect to the
functionality described in RFC 4271. There are probably still some
bugs but the core is reasonably stable.
In addition, there is also support for multiprotocol externsion (RFC 2858) multiprotocol extensions for IPv6 (RFC 2545), Communities (RFC 1997), Capabilities (RFC 3392), route reflection (RFC 2796), Confederations (RFC 3065) and route flap damping (RFC 2439).
- OSPF
- OSPF version 2 and version 3 are available from the same code
base. OSPF version 2 has been available since release 1.2, OSPF
version 3 first became available in release 1.4. There is also support
for Not-So-Stubby areas. OSPF version 2 only supports IPv4, OSPF
version 3 supports IPv6. There are probably still some
bugs but the core is reasonably stable.
- RIP
- There are two RIP processes: RIPv2 for IPv4 and RIPng for
IPv6. RIPv2 is functionally complete and includes support for
authentication. RIPng is written and uses much of the same code
as RIPv2 but needs additional testing.
- IS-IS
- Not yet started.
- PIM-SM
- The PIM-SM implementation (including the Bootstrap mechanism)
is reasonably complete and fairly well tested, though there are still
few minor things that need polishing. The code appears stable, but
probably there are still some bugs.
- IGMP
- The IGMPv1 and v2 implementation is reasonably complete and fairly
well tested, though there are still few minor things that need
polishing. The IGMPv3 implementation is reasonably completed,
but needs more testing.
- MLD
- The MLDv1 implementation is reasonably complete, but
testing continues. The MLDv2 implementation is reasonably completed,
but needs more testing.
- Rtrmgr and Xorpsh Command Line Interface
- The rtrmgr is capable of starting up and using xorpsh, a user can
reconfigure the XORP processes that comprise a router. However, work
continues on improving its stability. Operational mode (monitoring a running
router) needs more polishing.
- LibXIPC
- The interfaces are stable, and the IPC mechanisms work well.
- SNMP
- We are using the Net-SNMP agent. We provide a XORP interface module that allows MIB modules to access information from XORP processes. Currently we have fully implemented one such module, BGP4-MIB (RFC 1657). The rtrmgr can be configured to start the SNMP agent and to load MIB modules. However, it has not been tested as well as the rest of the XORP modules, hence there could be some issues (see here).
Document id $XORP: www/status.html,v 1.39 2008/01/30 05:35:53 atanu Exp $.
Generated on 29/Jan/2008 at 21:29:44.
Feedback, comments, flames to feedback@xorp.org