From atanu at ICSI.Berkeley.EDU Wed Mar 21 11:58:27 2007 From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh) Date: Wed, 21 Mar 2007 11:58:27 -0700 Subject: [Xorp-announce] Announcing XORP Release 1.4 Message-ID: <66492.1174503507@tigger.icir.org> On behalf of the entire XORP team, I'm delighted to announce the XORP 1.4 Release, which is now available from . The major new feature with this release is: * OSPFv3 (draft-ietf-ospf-ospfv3-update-14.txt) In addition, this release contains numerous bug fixes. There are still a number of non-critical bugs that we know about which will not be addressed until the 1.5 release; these are documented in the XORP Bugzilla database . In general, to test XORP, we run automated regression tests on a daily basis with various operating systems and compilers. We also run a number of PCs as XORP routers. We have enabled as many protocols as feasible on those routers to test protocol interactions (for example a BGP IPv6 multicast feed being used by PIM-SM). In addition, automated scripts are run to externally toggle BGP peerings. Finally, we have automated scripts that interact directly with the xorpsh to change the configuration settings. We have put significant effort into testing but obviously we have not found all the problems. This is where you can help us to make XORP more stable, by downloading and using it! As always we'd welcome your comments - xorp-users at xorp.org is the right place for general discussion, and private feedback to the XORP core team can be sent to feedback at xorp.org. - The XORP Team P.S. Release notes are included below. ------------------------------------------------------------------ XORP RELEASE NOTES Release 1.4 (2007/03/20) ========================= ALL: - XORP now builds on DragonFlyBSD-1.8, FreeBSD-6.2, Linux Fedora Core6, Linux Debian-3.1 (sarge), NetBSD-3.1 and OpenBSD-4.0. - XORP now can be compiled with the Intel C/C++ compiler 9.* on Linux. - XORP now can be cross-compiled for IA-64, MIPS (Broadcom for Linksys WRT54G), PowerPC-603, Sparc64, and XScale processors. - Implementation of OSPFv3 (draft-ietf-ospf-ospfv3-update-14.txt). - Implementation of floating static routes (i.e., static routes for the same prefix with different next hop and metrics). CONFIGURATION: - Allow static routes to have "nexthop4" and "nexthop6" policy matching conditions in the "from" block. - Addition of new FEA configuration statements to retain XORP unicast forwarding entries on startup or shutdown: fea { unicast-forwarding4 { forwarding-entries { retain-on-startup: false retain-on-shutdown: false } } unicast-forwarding6 { forwarding-entries { retain-on-startup: false retain-on-shutdown: false } } } The default value for each statement is false. Note that those statements prevent the FEA itself from deleting the forwarding entries and does not prevent the RIB or any of the unicast routing protocols from deleting the entries on shutdown. - The "elements" policy statements for configuring sets of network routes have been deprecated: policy { network4-list foo { elements: "1.2.0.0/16,3.4.0.0/16" } network6-list bar { elements: "2222::/64,3333::/64" } } The new replacement statement is "network" and can be used to specify one element per line: policy { network4-list foo { network 1.2.0.0/16 network 3.4.0.0/16 } network6-list bar { network 2222::/64 network 3333::/64 } } - The following keywords are supported inside the policy configuration when comparing IPv4 or IPv6 network prefixes: exact, longer, orlonger, shorter, orshorter, not. For example: "network4 exact 10.0.0.0/8" SAME AS "network4 == 10.0.0.0/8" "network4 longer 10.0.0.0/8" SAME AS "network4 < 10.0.0.0/8" "network4 orlonger 10.0.0.0/8" SAME AS "network4 <= 10.0.0.0/8" "network4 shorter 10.0.0.0/8" SAME AS "network4 > 10.0.0.0/8" "network4 orshorter 10.0.0.0/8" SAME AS "network4 >= 10.0.0.0/8" "network4 not 10.0.0.0/8" SAME AS "network4 != 10.0.0.0/8" The original operators are supported as well. - A floating static route (also called "qualified" by some router vendors) can be added with a configuration like: protocols { static { route 10.10.0.0/16 { next-hop: 172.16.0.1 metric: 1 qualified-next-hop 172.17.0.2 { metric: 10 } } interface-route 10.30.30.0/24 { next-hop-interface: "rl0" next-hop-vif: "rl0" next-hop-router: 172.16.0.1 metric: 1 qualified-next-hop-interface rl1 { qualified-next-hop-vif rl1 { next-hop-router: 172.17.0.2 metric: 10 } } } } } LIBXORP: - The XORP scheduler now has support for priority-based tasks. LIBXIPC: - No significant changes. LIBFEACLIENT: - No significant changes. XRL: - No significant changes. RTRMGR: - Bug fix in the semantics of the rtrmgr template %activate keyword. XORPSH: - No significant changes. POLICY: - Bug fix related to creating export policies that match protocol's its own routes (e.g., a policy that modifies the BGP routes exported to its peers). - Various other bug fixes. FEA/MFEA: - Fix the routing socket based mechanism (used by BSD-derived systems) for obtaining the interface name (toward the destination) for a routing entry. - Apply a performance improvement when configuring a large number of interfaces/VIFs, each of them with the "default-system-config" configuration statement. - Bug fix related to atomically modifying the IP address of an interface. RIB: - Bug fix related to (not) installing redundant host-specific entries for the other side of a point-to-point interface if the netmask for the interface covers the host-specific entry. RIP: - No significant changes. OSPF: - OSPFv3 is now available. - The OSPFv3 protocol requires that link-local addresses are used, therefore it is necessary to configure a link-local address for each interface, this restriction will be removed in the future. - The OSPFv3 configuration allows multiple instances to be configured however only one instance will be created. Configuring multiple OSPFv3 instances is guaranteed to cause problems. - Bug fix related to the processing of previously generated LSAs on startup has been fixed. Restarting a router that was the designated router could exhibit this problem. - Bug fix on a broadcast interface if the router was not the designated router then the nexthop was incorrectly unconditionally set to the designated router; introducing an unnecessary extra hop. BGP: - BGP has taken advantage of the priority-based tasks in the XORP scheduler and background tasks are run at a low priority; leading to improved performance. STATIC_ROUTES: - Bug fix related to declaring some of the policy matching conditions in the "from" block. MLD/IGMP: - Bug fix related to atomically modifying the IP address of an interface. - Bug fix related to ignoring protocol messages that are not recognized by the configured protocol version on an interface. - Ignore control messages if the source address is not directly connected. - Don't send the periodic Group-Specific or Group-and-Source-Specific Queries for entries that are in IGMPv1 mode. PIM-SM: - Bug fix related to atomically modifying the IP address of an interface. - The PIM-SM control messages do not include the IP Router Alert option anymore, because it has been included from the newer revisions of the PIM-SM protocol specification (RFC 4601 and draft-ietf-pim-sm-bsr-09.txt,.ps). - Don't send PIM Hello message with DR Priority of 0 when shutting down an interface, because this is not part of the protocol specification. FIB2MRIB: - Bug fix related to updating the interface and vif name of a forwarding entry received from the FEA. CLI: - Performance improvement if the CLI is processing a large amount of data. E.g., if xorpsh is used in a pipe like: cat commands.txt | xorpsh SNMP: - Bug fix with the snmpd arguments when sampling whether snmpd can start and its version is >= 5.2.