[Xorp-users] Announcing XORP Release Candidate 1.6

Atanu Ghosh atanu at xorp.org
Wed Dec 24 18:59:49 PST 2008


Dear XORP developers,

We are pleased to announce availability of the release candidate (RC)
for version 1.6. The XORP team and contributors have worked very
hard over the last 6 months and 1.6 is a huge milestone in the
history of the XORP project. Please download and use it and provide
us with feedback. We are targeting January 7th as the general
availability date of this release.

Per my announcement in July, XORP is now commercially backed by two
well-known and highly-respected venture capitalists, and one of
the benefits for all of us in the XORP community is the additional
amount of resources we have been able to bring to the project.
These increased resources have resulted in our ability to release
1.6 just months after our announcement of XORP, Inc and release 1.5.

In terms of project milestones, 1.6 marks the first time
we have put the codebase through a comprehensive and rigorous QA
process, using some of the leading test tools in the market for
layer 3 testing. Of course, there will be areas where we have
not completely tested the codebase and we are looking forward to
hearing from the development community once you've had the
opportunity to try out release 1.6.

Here are some of the key improvements in 1.6, based on your
contributions and user feedback:

- Significantly improved memory performance on the BGP code
 (especially in scenarios with many peers)

- XRL performance improvements

- Improved policy code

- *NEW* VRRP support

- Numerous bug fixes (entire list is in 1.6 Release Notes
 available at http://www.xorp.org/releases/1.6-RC/docs/RELEASE_NOTES

To file bugs, please visit http://bugzilla.xorp.org/

Of late, we have noticed more users incorporating XORP into
their projects, both non-profit and commercial and want to
continue to encourage the community to do so. With the recent
world financial crisis, organizations will be looking more
to open-source as a cost-effective alternative to the
high premiums other networking vendors charge, so help us
spread the word about XORP.org and help all of us build the
momentum behind open-source networking!

Thank you very much for your interest and continued participation
in the XORP open networking platform project. We appreciate
the help and support the community has shown us over the years and
hope that you will enjoy this latest release. If you have any
questions, please feel free to contact us at info at xorp.net.

--The XORP Team

P.S.
Release notes included below.

------------------------------------------------------------------
		XORP RELEASE NOTES

Release 1.6-RC (12/24/2008)
============================
  ALL:
    - XORP now builds on Linux CentOS 5.2, Linux openSUSE-11.0,
      Linux Debian-5.0 (lenny, unreleased), Linux Ubuntu 8.10,
      Linux Red Hat Enterprise Linux Server release 5 (Tikanga),
      Linux Fedora 10, and OpenBSD-4.4.

    - XORP now builds on Linux systems with kernel 2.6.26 which is the
      first one to support IPv6 multicast routing.

  CONFIGURATION:
    - If a PIM-SM router is suppose to receive and process the PIM-SM
      Bootstrap messages, the configuration must have the "bootstrap {}"
      block included (even if it is empty):

      protocols {
          pimsm4 {
              bootstrap {
              }
          }
      }

      protocols {
          pimsm6 {
              bootstrap {
              }
          }
      }

      Previously, the Bootstrap messages were unconditionally processed
      even if the "bootstrap {}" block contained "disable: true"
      statement.

    - The following CLI operational command prefix has been changed:
      OLD: "show route admin distances"
      NEW: "show route admin distance"
     
    - The CLI "show version" command is supported

    - Addition of run-time configuration trace options for RIP/RIPng:

      protocols {
          rip {
              traceoptions {
                  disable: false
              }
          }
      }

  LIBXORP:
    - Class EtherMac is removed and is replaced/superseded by the
      existing class Mac.

    - Performance improvements and various bug fixes in the EventLoop
      and SelectorList implementation.

  LIBXIPC:
    - XRL performance enhancements. (Bug 808)

    - Issues that might be triggered under heavy system load have been fixed
      (Bug 800)

  LIBFEACLIENT:
    - No significant changes.

  XRL:
    - See LIBXIPC

  RTRMGR:
    - No significant changes.

  XORPSH:
    - Incorrect help "show bgp peers detail" command  (Bug 280)

    - Xorpsh exiting immediately on error doesn't work  (Bug 763)

    - "Show version" CLI supported  (Bug 789)

    -  Show route admin distance not working (Bug 812)

  POLICY:
    - Tag per route is not reset in case the policies are removed (Bug 567)

    - Implement per-peer BGP import/export policies  (Bug 667)

    - Enhance policy network-lists to included prefix length (Bug 674)

  FEA/MFEA:
    - Bug fix for OpenBSD when transmitting IGMP packets.

  RIB:
    - No significant changes

  RIP/RIPng:
    - Added traceoption support 

  OLSR:
    - 

  OSPF:
    - When the designated router was restarted the MaxAge LSAs that it
      generated when reflected back would be responded to with a MaxAge LSA,
      this process could continue indefinitely, leaving the neighbor state in
      EXCHANGE. (Bug 785)
	
  BGP:
    - Support for Red Hat Linux (Bug 793)

  STATIC_ROUTES:
    - No significant changes.

  MLD/IGMP:
    - Bug fix when checking the source address of IGMP packet if the
      source address is allowed to be 0.0.0.0.

  MLD/IGMP-Lite:
    - Bug fix when checking the source address of IGMP packet if the
      source address is allowed to be 0.0.0.0.

  PIM-SM:
      Ability to add candidate BSR after inserting Cand-RP with same group
      (Bug 803)

  FIB2MRIB:
    - No significant changes.


  SNMP:
    - 

  VRRP:
    - Initial implementation of VRRP version 2 as described in RFC 3768.

    - Supports running more than one VRRP instances on the same box although
      they need to be on different interfaces and different LANs for correct
      behavior (see ERRATA).

    - The following master failure modes have been tested and are known to work
      (i.e., backup becomes master): bringing the master's interface down,
      rebooting / crashing the master, physically removing the network cable.
      Note that in the latter case the master may fail to resume operations
      when the cable is restored (see ERRATA).

    - Successfully interoperates with vrrpd.



More information about the Xorp-users mailing list