The following reply was made to PR pkg/37058; it has been noted by GNATS.
From: OBATA Akio <obache@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc:
Subject: PR/37058 CVS commit: pkgsrc/net/xorp
Date: Sat, 13 Oct 2007 15:15:53 +0000 (UTC)
Module Name: pkgsrc
Committed By: obache
Date: Sat Oct 13 15:15:52 UTC 2007
Modified Files:
pkgsrc/net/xorp: Makefile PLIST distinfo
pkgsrc/net/xorp/patches: patch-ab patch-af
Removed Files:
pkgsrc/net/xorp/patches: patch-aa patch-ac patch-ad patch-ae
Log Message:
Update xorp to 1.4.
Patch provided by Mustafa Dogan in PR 37058.
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.
Release 1.3 (2006/08/02)
=========================
ALL:
- Numerous improvements, bug fixes and cleanup.
- XORP now builds on Linux Fedora Core5, DragonFlyBSD-1.4,
FreeBSD-6.1.
- Implementation of IGMPv3 (RFC 3376) and MLDv2 (RFC 3810).
Those are necessary to complete the Source-Specific Multicast
support.
CONFIGURATION:
- Addition of new OSPF configuration statement as part of the MD5
keys:
* max-time-drift: u32 (default to 3600, i.e., 1 hour)
It is used to set the maximum time drift (in seconds) among all
OSPF routers. The allowed values are in the range [0--65535]. If
the value is 65535, the time drift is unlimited.
- The following statements for configuring static routes have been
deprecated:
route4, route6, interface-route4, interface-route6, mrib-route4,
mrib-route6, mrib-interface-route4, mrib-interface-route6.
The new replacement statements are:
route, interface-route, mrib-route, mrib-interface-route.
Each of the new statements can be used to configure either IPv4Net
or IPv6Net route.
- The following statements for configuring RIP and RIPng have been
renamed:
* route-expiry-secs -> route-timeout
* route-deletion-secs -> deletion-delay
* table-request-secs -> request-interval
* interpacket-delay-msecs -> interpacket-delay
- The following statements for configuring RIP and RIPng random
intervals have been replaced:
* triggered-update-min-secs and triggered-update-max-secs with
triggered-delay and triggered-jitter
* table-announce-min-secs and table-announce-max-secs with
update-interval and update-jitter
Previously, each interval was specified as [foo-min, foo-max].
Now each interval is specified as
[foo - foo * jitter / 100, foo + foo * jitter / 100]
where "jitter" is specified as a percentage (an integer in the
interval [0, 100]) of the value of "foo".
- The "version" statement for configuring an IGMP interface/vif
allows values in the range [1-3]. Previously, the allowed range
was [1-2].
- The "version" statement for configuring a MLD interface/vif allows
values in the range [1-2]. Previously, the allowed range was [1-1].
- The following statement for configuring PIM-SM (pimsm4 and pimsm6)
has been renamed:
interval-sec -> interval
- If a "then" policy block contains "accept" or "reject" statement,
now all statements inside the "then" block are evaluated
regardless of their position.
- Addition of a new "exit" operational mode command that is
equivalent to the "quit" operational mode command.
- The "create" and "set" configuration commands are merged, so now
the new "set" command can be used for setting values and for
creating new configuration nodes. For backward compatibility,
the obsoleted "create" command is preserved as an alias for the
new "set" command, though it may be removed in the future.
LIBXORP:
- Few bug fixes in the RefTrie implementation.
LIBXIPC:
- Minor improvement in parsing XRL requests.
LIBFEACLIENT:
- No significant changes.
XRL:
- No significant changes.
RTRMGR:
- Various bug fixes.
XORPSH:
- Previously, the "commit" command was not available in
configuration mode if there were no pending configuration changes.
Now the "commit" command is always available, but the following
message will be printed instead:
"No configuration changes to commit."
- Various bug fixes.
POLICY:
- Various bug fixes.
FEA/MFEA:
- Bug fix in transmitting large packets on Linux when using IP raw
sockets.
- Linux-related netlink socket code refactoring and bug fix.
- Bug fix in obtaining the incoming interface for raw packets
(in case of *BSD).
- Bug fix in parsing the ancillary data from recvmsg().
- Accept zeroed source addresses of raw packets, because of
protocols like IGMPv3.
- Bug fix in restoring kernel routes that were automatically removed
when the MAC address or MTU on an interface is modified.
- Bug fix in processing IPv4 raw packets if they contain an IP option
with a bogus option length.
RIB:
- Several bug fixes and improvements.
RIP:
- Various bug fixes in the MD5 authentication support.
- Remove route flap when applying/deleting RIP-related import
policies.
- Fix an issue with INFINITY cost routes that might be bounced
indefinitely between two XORP routers.
OSPF:
- Various bug fixes in the MD5 authentication support.
BGP:
- Prefix limits on a per peer basis.
- Various bug fixes.
STATIC_ROUTES:
- No significant changes.
MLD/IGMP:
- Implementation of IGMPv3 (RFC 3376) and MLDv2 (RFC 3810).
- Unification of the IGMP and MLD execution path.
PIM-SM:
- Bug fix related to the SPT switch (the bug is *BSD specific).
- Use the RPF interface toward the BSR when transmitting a Cand-RP
Advertisement message. Previously the first interface that is UP
was chosen.
- Use the RPF interface toward the RP when transmitting PIM Register
messages toward the RP. Previously the interface of the directly
connected source was chosen.
FIB2MRIB:
- No significant changes.
CLI:
- Bug fix related to tracking the window size when it is resized.
SNMP:
- No significant changes.
To generate a diff of this commit:
cvs rdiff -r1.19 -r1.20 pkgsrc/net/xorp/Makefile
cvs rdiff -r1.3 -r1.4 pkgsrc/net/xorp/PLIST
cvs rdiff -r1.8 -r1.9 pkgsrc/net/xorp/distinfo
cvs rdiff -r1.3 -r0 pkgsrc/net/xorp/patches/patch-aa
cvs rdiff -r1.2 -r1.3 pkgsrc/net/xorp/patches/patch-ab
cvs rdiff -r1.1 -r0 pkgsrc/net/xorp/patches/patch-ac \
pkgsrc/net/xorp/patches/patch-ad pkgsrc/net/xorp/patches/patch-ae
cvs rdiff -r1.1 -r1.2 pkgsrc/net/xorp/patches/patch-af
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.