ospfd:fix the bug that the empty area was not free after no area range command was...

    When we use the no area X.X.X.X range A.B.C.D/M command, if the area no longer has an interface to which it belongs, then the area should be deleted from the LSDB. This processing logic is consistent with instructions such as no network area and no area authentication.

Signed-off-by: Shbinging <bingshui@smail.nju.edu.cn>

diff --git a/ospfd/ospf_vty.c b/ospfd/ospf_vty.c
index 01cbfedc1c0dfb122b578598b8c8fb9eb84ac849..3be3de24cf389f782f1ee2b0249bf7b077469823 100644 (file)
--- a/ospfd/ospf_vty.c
+++ b/ospfd/ospf_vty.c
@@ -748,6 +748,8 @@ DEFUN (no_ospf_area_range,
 
        ospf_area_range_unset(ospf, area, area->ranges, &p);
 
+       ospf_area_check_free(ospf, area_id);
+
        return CMD_SUCCESS;
 }