From f0ec832a78549a85cf4e47d884036c1178f749d3 Mon Sep 17 00:00:00 2001 From: "Andrew J. Schorr" Date: Mon, 30 Apr 2007 16:52:05 +0000 Subject: [ospfd] network command now behaves more logically when a peer prefix is defined 2007-04-30 Andrew J. Schorr * ospfd/ospfd.c: (ospf_network_match_iface) Comment out COMPATIBILITY_MODE. Going forward, the ospf "network" command will use a simple test: does the network command prefix contain the connected (destination) prefix of the interface? * doc/ospfd.texi: Add a paragraph to the description of the OSPFv2 network command to explain how we handle interfaces with peer addresses. --- doc/ChangeLog | 6 ++++++ doc/ospfd.texi | 7 +++++++ 2 files changed, 13 insertions(+) (limited to 'doc') diff --git a/doc/ChangeLog b/doc/ChangeLog index c84730c0..586852c6 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,9 @@ +2007-04-30 Andrew J. Schorr + + * ospfd.texi: Add a paragraph to the description of the OSPFv2 + network command to explain how we handle interfaces with + peer addresses. + 2007-04-29 Andrew J. Schorr * basic.texi: Document the new 'log timestamp precision' command. diff --git a/doc/ospfd.texi b/doc/ospfd.texi index bd53a692..f879a986 100644 --- a/doc/ospfd.texi +++ b/doc/ospfd.texi @@ -232,6 +232,13 @@ Prefix length in interface must be equal or bigger (ie. smaller network) than prefix length in network statement. For example statement above doesn't enable ospf on interface with address 192.168.1.1/23, but it does on interface with address 192.168.1.129/25. + +Note that the behavior when there is a peer address +defined on an interface changed after release 0.99.7. +Currently, if a peer prefix has been configured, +then we test whether the prefix in the network command contains +the destination prefix. Otherwise, we test whether the network command prefix +contains the local address prefix of the interface. @end deffn @node OSPF area -- cgit v1.2.1